←  AutoPatcher for Windows 7 SP1

AutoPatcher Forum

»

AutoPatcher not patching at all...

Jarry's Photo Jarry 01 Nov 2012

Well, this is very strange:

I just installed Windows7/64b, and SP1 (manually). Then I started AutoPatcher, from the list I picked autopatcher (updater, engine, modules) and w7/64b. It downloaded ~2GB of data.

Then I started "autopatcher.exe", selected all security and recommended patches and clicked start. Initially it estimated about 1:30 hour to work, but "patching" was done in about 30 seconds (?). No error came. Then I restarted system, checked installed updates, and only one is there: SP1 (KB976932). So AutoPatcher did not install single patch!

I repeated this twice, with the same effect: autopatcher just runs very quickly through list of patches, but does not install any. What am I doing wron? btw, of course I started autopatcher.exe as administrator...
Quote

ViroMan's Photo ViroMan 01 Nov 2012

hmm... will examine a few apms.

edit:
Looking at the apms... they don't look wrong. Don't have win7 installed so I can't test.

waiting to see if I can get conformation on the problem. In the meantime... Jarry... can you rerun autopatcher but, add /verbose to the command line. It will generate a better log file. Then look for the log file(called autopatcher.log) in windows dir.
Edited by ViroMan, 01 November 2012 - 10:49 PM.
Quote

Jarry's Photo Jarry 02 Nov 2012

I already found solution, and I hate to say it, but it was my fault. After Windows7 installation I usually turn services I consider useless/dangerous off, and two of them were "windows update" and "background inteligent transfer service" (thinking they were not required for off-line updating). Apparently, they are (or maybe just one of them). As soon as I put them back to "automatic", Autopatcher worked like charm...

Maybe autopatcher could check if all necessary services are running (and maybe start them manually, if not). Because it did not say anything about missing windows_update, even when started with /verbose switch. The only trace I found was in WindowsUpdate.log which contained a lot of messages like this:

2012-11-02 17:13:04:787 804 9b4 COMAPI ----------- COMAPI: IUpdateServiceManager::AddScanPackageService -----------
2012-11-02 17:13:04:787 804 9b4 COMAPI - ServiceName = Windows Update Standalone Installer
2012-11-02 17:13:04:787 804 9b4 COMAPI - ScanFileLocation = C:\26d0c5054f65b00f4182c86392121a\wsusscan.cab
2012-11-02 17:13:04:787 804 9b4 COMAPI FATAL: Unable to connect to the service (hr=80070422)
2012-11-02 17:13:04:787 804 9b4 COMAPI WARNING: Unable to establish connection to the service. (hr=80070422)
2012-11-02 17:13:04:787 804 9b4 COMAPI - Exit code = 0x80070422

Edited by Jarry, 02 November 2012 - 05:43 PM.
Quote

ViroMan's Photo ViroMan 03 Nov 2012

hmm... well I will think about adding it to the revamped ap2 sounds like its useful to know. I am not even sure how to check if a service is running I would need to look that up.
Quote