On Win7, shouldn't KB3172605 be part of the routine?

On Win7, shouldn't KB3172605 be part of the routine?

Postby paul1149 » 27.01.2017, 15:28

Hi guys,

I've noticed on several Win7 machines, that the process gets stuck on "listing missing updates" unless KB 3172605 is installed. I left a machine updating last night, and when I got to it this morning it was still stuck on "listing missing updates", so a lot of time was lost. I then force a reboot, install the patch, and the reboot back into WSUS. At that point, everything proceeds fine.

I had tried manually installing 2605 before WSUSOffline, but evidently required dependencies weren't present, so it has to be done later in the process.

Is there any reason why 2605 couldn't be incorporated into the WSUS routine just before the listing function?

I'm on WSUS 10.9. It was win7 x64.

Thanks.
paul1149
 
Posts: 52
Joined: 02.12.2011, 23:43

Re: On Win7, shouldn't KB3172605 be part of the routine?

Postby WSUSUpdateAdmin » 27.01.2017, 15:49

Hi.

paul1149 wrote:[...]Is there any reason why 2605 couldn't be incorporated into the WSUS routine just before the listing function?[...]

It is, actually:
Code: Select all
27.01.2017 15:45:59,00 - Info: Starting WSUS Offline Update (v. 10.9)
27.01.2017 15:45:59,00 - Info: Used path "D:\cmd\" on TEMP-PC (user: Administrator)
27.01.2017 15:45:59,00 - Info: Option /verify detected
27.01.2017 15:45:59,01 - Info: Option /showlog detected
27.01.2017 15:45:59,01 - Info: Option /seconly detected
27.01.2017 15:46:04,16 - Info: Found Microsoft Windows version 6.1.7601.18247 (w61 x64 deu sp1)
27.01.2017 15:46:04,16 - Info: Found Microsoft Windows Software Licensing Management Tool info...
27.01.2017 15:46:04,16 - Info: Name: Windows(R) 7, Professional edition
27.01.2017 15:46:04,16 - Info: Beschreibung: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
27.01.2017 15:46:04,16 - Info: Teil-Product Key: XXXXX
27.01.2017 15:46:04,16 - Info: Lizenzstatus: Lizenziert
27.01.2017 15:46:04,16 - Info: Ablauf der Volumenaktivierung: 27180 Minute(n) (18 Tag(e))
27.01.2017 15:46:04,18 - Info: Found total physical memory: 2 GB
27.01.2017 15:46:04,18 - Info: Found Windows Update Agent version 7.5.7601.17514
27.01.2017 15:46:04,18 - Info: Found Windows Installer version 5.0.7601.17514
27.01.2017 15:46:04,18 - Info: Found Windows Script Host version 5.8.9600.16428
27.01.2017 15:46:04,18 - Info: Found Internet Explorer version 9.11.9600.16428
27.01.2017 15:46:04,18 - Info: Found Microsoft Silverlight version 0.0.0.0
27.01.2017 15:46:04,18 - Info: Found Remote Desktop Client version 6.1.7601.17514
27.01.2017 15:46:04,18 - Info: Found Microsoft .NET Framework 3.5 version 3.5.30729.5420
27.01.2017 15:46:04,18 - Info: Found Windows PowerShell version 2.0
27.01.2017 15:46:04,18 - Info: Found Microsoft .NET Framework 4 version 4.6.01590
27.01.2017 15:46:04,18 - Info: Found Windows Management Framework version 0.0.0.0
27.01.2017 15:46:04,18 - Info: Found Microsoft Security Essentials version 0.0.0.0
27.01.2017 15:46:04,18 - Info: Found Microsoft Security Essentials definitions version 0.0.0.0
27.01.2017 15:46:04,18 - Info: Found Network Inspection System definitions version 0.0.0.0
27.01.2017 15:46:04,18 - Info: Found Windows Defender definitions version 1.95.191.0
27.01.2017 15:46:04,18 - Info: Medium build date: 27.01.2017
27.01.2017 15:46:04,19 - Info: Medium supports Microsoft Windows (w61 x64 glb)
27.01.2017 15:46:04,36 - Info: Disabled screensaver
27.01.2017 15:46:32,94 - Info: Installed ..\wddefs\x64-glb\mpas-feX64.exe
27.01.2017 15:46:41,43 - Info: Starting service 'Windows Update' (wuauserv)
27.01.2017 15:46:41,44 - Info: Waiting for service 'wuauserv' to reach state 'RUNNING' (timeout: 60s)
27.01.2017 15:46:41,44 - Info: Service 'wuauserv' reached state 'RUNNING'
27.01.2017 15:46:41,43 - Info: Started service 'Windows Update' (wuauserv)
27.01.2017 15:47:17,84 - Info: Installed ..\w61-x64\glb\Windows6.1-KB3177467-x64.msu
27.01.2017 15:48:35,43 - Info: Installed ..\w61-x64\glb\windows6.1-kb3172605-x64_2bb9bc55f347eee34b1454b50c436eb6fd9301fc.msu
27.01.2017 15:48:45,71 - Info: Installed ..\w61-x64\glb\windows6.1-kb2552343-x64_51acdacad4855a2a04f35e2ac511fd3832a5d931.cab
27.01.2017 15:48:45,74 - Info: Installed 3 updates
27.01.2017 15:48:45,74 - Info: Installation successful (Updates pending)
27.01.2017 15:48:45,76 - Info: Ending WSUS Offline Update


Regards,
T. Wittrock
WSUSUpdateAdmin
Administrator
 
Posts: 2245
Joined: 07.07.2009, 14:38

Re: On Win7, shouldn't KB3172605 be part of the routine?

Postby Denniss » 27.01.2017, 18:16

The typical problem: Automatic Updates are active and the Windows Update Agent is already stuck so WOU is unable to stop it and restart it for its own use. Solution: disable automatic updates, reboot, start WOU and continue as instructed. Once WOU reports completion re-enable automatic updates.
Denniss
 
Posts: 869
Joined: 01.08.2009, 10:51

Re: On Win7, shouldn't KB3172605 be part of the routine?

Postby aker » 27.01.2017, 22:46

Do you have a log file for us?
(C:\Windows\wsusofflineupdate.log)
Wer Rechtschreibfehler findet, darf sie behalten oder an den Meistbietenden versteigern. / Everybody finding a misspelling is allowed to keep or sell it.
aker

WSUS Offline Update „Community Edition“
https://gitlab.com/wsusoffline/wsusoffline/-/releases
aker
 
Posts: 3999
Joined: 02.03.2011, 15:32

Re: On Win7, shouldn't KB3172605 be part of the routine?

Postby paul1149 » 04.02.2017, 03:43

Hi guys,

Sorry for the delay getting back. I have forum notifications enabled, but didn't receive anything.

Anyway, I'm beginning to think the missing 2605 package might be part of a broader problem I've been having. Namely, some packages simply do not get installed. This happens frequently with .Net 4.6.2. It just happened that all the packages after "listing missing..." were skipped. I realized that when I went online and Updates wanted to install 450MB of updates on a x8 netbook. This is the second time that has happened (2 different machines). I reran WSUSOffline and this time the packages were installed.

So maybe 2605 is in the routine, but somehow gets skipped? I don't know. I'm doing my manual routine for 2605, and also checking for .Net 4.6.2 at the same time, which often hasn't been installed.

I always turn off automatic WU checking before I run WSUSo. As for logs, the only one I see is the download log. The kb3172605 package is in the w61\glb folder.

BW.
paul1149
 
Posts: 52
Joined: 02.12.2011, 23:43

Re: On Win7, shouldn't KB3172605 be part of the routine?

Postby aker » 04.02.2017, 15:20

Could you post the log file?
Maybe the package failed for some reason...
Wer Rechtschreibfehler findet, darf sie behalten oder an den Meistbietenden versteigern. / Everybody finding a misspelling is allowed to keep or sell it.
aker

WSUS Offline Update „Community Edition“
https://gitlab.com/wsusoffline/wsusoffline/-/releases
aker
 
Posts: 3999
Joined: 02.03.2011, 15:32

Re: On Win7, shouldn't KB3172605 be part of the routine?

Postby paul1149 » 04.02.2017, 20:02

Here's the download.log.

Whatever the problem is, it is causing over a hundred packages to be skipped at a time. It's like WSUSo jumps from "Listing missing..." to rebooting almost immediately.
paul1149
 
Posts: 52
Joined: 02.12.2011, 23:43

Re: On Win7, shouldn't KB3172605 be part of the routine?

Postby aker » 05.02.2017, 18:08

Sorry, I meant the installer's one: C:\Windows\wsusofflineupdate.log.
Wer Rechtschreibfehler findet, darf sie behalten oder an den Meistbietenden versteigern. / Everybody finding a misspelling is allowed to keep or sell it.
aker

WSUS Offline Update „Community Edition“
https://gitlab.com/wsusoffline/wsusoffline/-/releases
aker
 
Posts: 3999
Joined: 02.03.2011, 15:32

Re: On Win7, shouldn't KB3172605 be part of the routine?

Postby paul1149 » 15.02.2017, 22:15

Apologies again for the late response, I'm still not receiving notifications for some reason.

Also, I missed the address of the log file posted earlier. Sorry. Here's the installer's log on an Asus netbook I just worked on. It's Win7 x32. It seemed to install all the extras I checked, including .Net 4.6.2. But when it went to "listing missing updates" I then cancelled, rebooted, cancelled again, and manually installed KB3172605. That wouldn't have been successful had it already been installed, I'm quite sure, so it seems that was missed by WSO. After I rebooted WSO listed the missing updates and installed them fine.

Here's the log.

BW.
paul1149
 
Posts: 52
Joined: 02.12.2011, 23:43

Re: On Win7, shouldn't KB3172605 be part of the routine?

Postby aker » 16.02.2017, 08:35

Strange...
Tue 02/14/2017 18:44:35.13 - Info: Installed ..\w61\glb\Windows6.1-KB3177467-x86.msu
Tue 02/14/2017 18:44:58.29 - Info: Installed ..\w61\glb\Windows6.1-KB3172605-x86.msu

Some errors while configuring updates on reboot?
Wer Rechtschreibfehler findet, darf sie behalten oder an den Meistbietenden versteigern. / Everybody finding a misspelling is allowed to keep or sell it.
aker

WSUS Offline Update „Community Edition“
https://gitlab.com/wsusoffline/wsusoffline/-/releases
aker
 
Posts: 3999
Joined: 02.03.2011, 15:32

Next

Return to Installation / Updating

Who is online

Users browsing this forum: Google [Bot] and 216 guests