Windows 10 - 1607 and WSUS

[Simcfc73]

I tested 2 new computers and its a nightmare. WU hangs installing 356 and refuses to stop the WU service. I cant install anything on it.

[abaxter2]

@Simcfc73 what build number are you running? the wsus issues is not fixed until at least build 10.0.14393.189 if you are not on 10.0.14393.189 or above you will find issues with wsus

[Simcfc73]

Mine doesnt like Cumultivie updates at all. I am on 223 and its hanging with the update from yesterday. Its actually hanging when I ran 'check online' so I think its beyond a WSUS isssue. Its only those that hang, the rest of the updates flies through.

[abaxter2]

The other update to make sure is installed on the clients is KB3176936: https://support.microsoft.com/en-gb/kb/3176936

 

I thought this update would be included in CU updates but yesterday I wanted to test how the monthly roll update would work on a fresh install base image of 10.0.14393.0 and found that updates where taking ages but after installing KB3176936 all kicked in.

 

So even if the september CU or the latest CU does include the WSUS fix you may still need KB3176936 installed first to get CU updates to install so might be worth downloading this update manually from the Microsoft update catalog - running it to check it is installed.

[Simcfc73]

I've just experienced the same thing, frshly installed PC which i rolled out kb3194798-x64 to hoping it had everything included and when I looked its hanging installing 936. Its only 10Mb so deployed that and its happily installing all the Office updates.

 

I'm tempted to slipstream 798 into my WDS image if I can get my head round it. I did it 100 years ago but haven' with W10 yet... as well as creating an answer file

[Simcfc73]

Still happening on updates. Sat watching a new PC installing KB3199209 which is stuck on 68%.. now its on 67%.. WHY IS IT GOING BACKWARDS.

 

I'm going round finishing off W10 on my network and forcing 798 to install after its deployed.. I have 2 machines that are trying to install it again even though it says its successful.

[BarryBKS]

The black screen with cursor is an issue that will occur on any Windows 10 1607 installation when Windows Updates have been installed.

 

Currently Microsoft have not released any information as to why, but if a PC in this condition is left for about 2 hours, it may resolve itself or if powered down and restarted, should return to a working PC.

 

See this post on Microsoft Community for more information.

 

The black screen is not related to WSUS as I have seen it on home PCs running 1607.

 

Hope this is of help to remove any red herrings.

Edited October 19, 2016 by BarryBKS