2 replies to this topic

[Fox2]

I think I'm possibly seeing the same bug some have reported on uploading the XP and Win 2003 updates via apup.exe (or possibly related to Office2007???). There is a difference in that I'm uploading XP SP3 updates and not XP SP2, but it could be the same bug. The problem is that APUP reports a file error ("continue at your own risk?") as others have reported (I think), ... but it then dies with a runtime error 0, and if started with the /log option, the .log file is deleted.

It's 100% replicable for me on a clean Win 2003 system:

Install win2k3, and run a clean download of APUP, checking the following updates: <AP updater 1.04, AP engine 5.6.81, AP for winXP SP3 x86, AP for win2K3 SP2, DirectX/DotNet/Extras/Office add-on packs, AP for office 2007, SP1 add-on for Office 2007>. It's a total 1.4 GB download hence testing it by removing one of these at a time, is undesirable - way too many hours. The log would be useful but that gets deleted as part of the fail, and without the log all it would tell me is "package X is involved somehow" anyway.

Can one of the developers let me know what steps might capture useful debug information on this?

Edited by Fox2, 12 July 2008 - 08:37 AM.

[Fox2]

(Empty reply - a 2nd bug was reported, then moved to separate report topic)

Edited by Fox2, 12 July 2008 - 08:29 AM.

[James]

As the person who gave advice in YOUR LINK (above) I'm not sure that you are seeing the same bug.

At the point at which APUP starts showing errors, but before you start clicking buttons, is the log file still visible (by opening another command shell, then using the dir command)? If so, it can be copied to another file. If not, then there is currently no other diagnostic information available from APUP.

--