Windows 10 - 1607 and WSUS

[abaxter2]

Hi all,

 

Just a heads up really as I am still seeing issues with WSUS and windows 10 1607 updates - seems to be a bug and seems after a few reboots the clients do install windows 10 updates - Office updates etc are all good apart from if a windows 10 update is included with the other updates

 

The latest windows 10 1607 update (KB3176934) seems to be the worst I have seen so far for failing to install! -

https://social.technet.microsoft.com/Forums/scriptcenter/en-US/31718a20-64dd-43f7-87d7-c86f03f74a4d/14393-windows-update-crash-every-minute?forum=win10itprogeneral

 

Getting beyond a joke now! Microsoft sort it out grrr.

[abaxter2]

On and now update KB3176936 - https://support.microsoft.com/en-us/kb/3176936

[abaxter2]

Just an update as I think I have found why my Windows updates are playing up! It looks like it is down to how Windows Update Delivery Optimization is delivering updates - I would only like my updates to come from my WSUS server and to do this you need to set the following:

 

Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization

 

Select "Download Mode" and select "Bypass"

 

After a gpupdate / force I then see under the client windows update setting > "Choose how updates are delivered" that it now states some settings are managed by your organization and that "Download windows updates and apps from other PC's" is turned off :-)

 

Now all my updates come from WSUS only and things are looking up!

 

More information here:

https://support.microsoft.com/en-gb/kb/3088114

https://blogs.technet.microsoft.com/mniehaus/2016/08/08/using-wsus-with-windows-10-1607/

https://blogs.technet.microsoft.com/mniehaus/2016/08/16/windows-10-delivery-optimization-and-wsus-take-2/

[abaxter2]

Just a little bit more information as it looks like microsoft are at long last on the case as I have just found this:

 

"Hi everyone, and apologies for the frustration you're experiencing. This thread calls out several different symptoms, for each of which I'll provide guidance. Note that Configuration Manager will exhibit the same symptoms as each of the scenarios below.

 

1. WSUS 3.0 SP2 on WS08R2 SP1 (or unpatched WS12/R2) cannot download ESDs

This is by design. WSUS 3.2 cannot sync or distribute ESDs, and WS12/R2 can only do so if both KB3095113 and KB3159706 are installed on the machine, and all necessary post-install steps from KB3159706 have been followed. As folks have noted, these post-install steps [and the general way that this update was released] caused unnecessary pain and confusion. We'll choose a less disruptive strategy for future WSUS updates.

 

2. Clients have upgraded to 1706 using Anniversary Update, but cannot get Cumulative Updates

This is a bug in the Windows client that will be fixed in an upcoming cumulative update. In the meantime, clients may experience some delay in getting the monthly content, but they will eventually download it. The workaround here is to simply wait longer than usual, or to scan directly against Windows Update if you've waited several days and haven't seen any download success in that time.

 

3. WSUS can sync/distribute feature updates (such as 1511), but cannot deploy the 1607 feature update

This is a newly reported issue that we are currently investigating. Again, the workaround is to pull the 1607 feature update from Windows Update instead of WSUS. We understand why you might not want to pull such a large file from the Internet once for each of your clients, and are figuring this out as soon as we can. We'll share further updates on the investigation as they become available."

 

This was posted on the Friday the 27/08/2016

 

Point 2 of above is the issue I am seeing so keeping my eye open for the next update (hoping its before the end of this week!)

 

For the whole blog see here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/5521e7f1-fa2d-4867-a47c-b276c66e6a82/windows-10-anniversary-update-1607?forum=winserverwsus

[mavhc]

I had to add .esd mimetype to my 2012r2 WSUS server, and set bypass in gpo

[abaxter2]

Thanks mavhc,

 

Already set to bypass in gpo and the .esd type are listed is the link I posted above but some are pointing out that by adding these is breaking WSUS but it does now look like that microsoft are on the case with an update about to be released.

[abaxter2]

Hi all,

 

Just another quick update:

 

I have found that any device that has not reported a status for a few days (gray triangle in WSUS) and you know that machine has been on then you are looking at a possible rebuild :-( I have found that that if you try installing the updates manually and if successful after a couple of reboots the device will start seeing new updates and install updates but if you are see the following message when you sign in:

 

"C:\windows\system32\config\systemprofile\desktop is unavailable. If the location is on this PC, make sure the device or drive is connected or the disc is inserted, and then try again. if the location is on a network make sure you're connected to the network or internente, and then try again. If the location still can't be found, it might have been moved or deleted."

 

If you see this message you will need to rebuild as gone past a fixable stage. So keeping an eye on your "Last Status Report" in your WSUS will at least give you an idea of machines that are going belly up.

 

The other thing I have found is that the update to fix this problem is coming on 13/09/2016 (patch Tuesday):

 

"To clarify, scenario #2 is a problem with the Windows Update client when it downloads from WSUS, and it affects all updates (not just cumulative). Service crashes are expected when this occurs; however, because it is nondeterministic, the download should eventually succeed. Alternatively, you can have your clients scan against Windows Update directly, or download and install directly from the Microsoft Update Catalog. A fix is scheduled for September's Patch Tuesday (9/13). Given the bootstrapping issue that some have mentioned, you may want to deploy the September cumulative update directly to expedite resolution."

 

But it does look like it will need a manual install!

 

I have also found that most of my machine with the latest updates (including KB3176934 and update KB3176936 are installing the august 31st update KB3176938 fine but still early days!

 

It is to late for me to go back as my school starts up again this coming Monday and all my machines are built but I can see myself burning the midnight oil for a few more weeks yet.

 

Fingers crossed the up and coming update on the 13th of this month does at long last put this issue to bed.

[abaxter2]

So here it is the update we have been waiting for!!

 

Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3189866) (https://support.microsoft.com/en-us/kb/3189866)

 

The only thing is that the WSUS issue is not mentioned in the improvements or fixes! but this was the date and update that was promised to fix these issues.

 

So far not installing to well on my Win 10 1607 build clients so looking like a manual install -need to get it installed quickly before my clients start to brick.

 

Any new builds I do will have this updated included in my build image before deploying.

 

I guess we will not know if this update does indeed fix the WSUS issue until the next Cumulative Update for Windows 10 Version 1607 and hope its not like the update Microsoft released to fix the black screen - what doesn't lol.

 

Still keep moving forward and at least I am not bored ha ha.

Edited September 14, 2016 by abaxter2

[Simcfc73]

Just sat here doing it on the machines at work that I can startup from home

 

I am using PDQ deploy to restart the WU service and push the install out manually. Done well over 100 so far no problem. I did go in and run WU and it seems to work fine but I havent done much in anger yet.

 

There is one update online that isnt showing on my WSUS yet so I did that by checking online (Septembers dodgy program update thingy)

[DMcCoy]

Not only is wsus not working on 1607, when the update service crashes it's taking a number of other services with it, like the profile service. So it does not update *and* it renders the machine unusable until it's rebooted.

 

Windows 10 turning out to be rather rubbish:

 

Issues with SSDs

wsus broken

start layout breaks with roaming profiles

reboot/shutdown doesn't finish closing roaming profile files, locking them and making subsequent logins fail if the account is used again before they timeout

[FragglePete]

So here it is the update we have been waiting for!!

 

Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3189866) (https://support.microsoft.com/en-us/kb/3189866)

 

The only thing is that the WSUS issue is not mentioned in the improvements or fixes! but this was the date and update that was promised to fix these issues.

 

So far not installing to well on my Win 10 1607 build clients so looking like a manual install -need to get it installed quickly before my clients start to brick.

 

Any new builds I do will have this updated included in my build image before deploying.

 

I guess we will not know if this update does indeed fix the WSUS issue until the next Cumulative Update for Windows 10 Version 1607 and hope its not like the update Microsoft released to fix the black screen - what doesn't lol.

 

Still keep moving forward and at least I am not bored ha ha.

 

I applied this to my own work machine yesterday; it did a couple of reboots during the update process and then I logged on....... black screen with cursor!!!! FFS!

 

Pete

[newpersn]

I applied this to my own work machine yesterday; it did a couple of reboots during the update process and then I logged on....... black screen with cursor!!!! FFS!

 

Pete

 

I get this. but on some computers it goes to the desktop after a short wait (about a minute) I sure it might be sticking on my printer VBS script..

[mavhc]

What are the SSD issues?

[newpersn]

What are the SSD issues?

 

Shouldnt have any issues with SSD's

 

Only problem i got currently is the WSUS. I applying the "fix" slowly as i've disabled windows update is it kills our internet connection....

[abaxter2]

Applying KB3189866 does get WSUS working again but this was the case with all previous Cumulative Updates for Windows 10 Version 1607 (once applied WSUS would work again) - so I am guessing we will not know if KB3189866 has infact fixed this issue until the next cumulative Update.

 

I will be adding this latest cumulative update to my base image so that any future new / rebuilds will hopefully not have this issue.

 

I am even thinking that in October I will create a LTSB image of Windows 10 1607 (once Microsoft release this) as at current every new cumulative update seems to break more than it fixes.

 

Windows 10 1607 or in fact all version of Windows 10 shows a lot of promise but at current is very up and down.

Edited September 15, 2016 by abaxter2

[DMcCoy]

Shouldnt have any issues with SSD's

 

Only problem i got currently is the WSUS. I applying the "fix" slowly as i've disabled windows update is it kills our internet connection....

 

https://support.microsoft.com/en-us/kb/3083595

 

Seeing this on a number of older SSDs, had to turn off sleep as it was BSODing on wake too.

[Sheridan]

I've applied the latest update today and WSUS is still broken, none of my W10 clients are reporting to WSUS anymore.

[abaxter2]

@Sheridan sorry to hear that but KB3189866 is to fix the WSUS update problem - crazy I know Microsoft release an update to fix an update! I have found that if you can apply the update manually WSUS will start working again and fingers crossed this is the long term fix for this issue - well that is what was promised!

[Sheridan]

None of the 10's I've tried it on have reported into WSUS. Oddly a lot of my W7 machines have also stopped reporting, but a large amount are still working! - so my WSUS server might be completed shafted.

[mavhc]

Used Chrome to dl KB3189866 via KB3189866

 

Installed manually, only 4 1607 machines anyway, seems to fix it

[free780]

You can always use SCCM to push out the CU as a package. I don't know what to believe in a real bug with Win 10 or just consequences of the environment. Not made the plunge into 1607 yet. Still finding the 'features' in 1511.

[abaxter2]

It has been confirmed a bug in win 10 1607 via Microsoft and they promised a fix in a CU on the 13th - this was released in the form of (KB3189866) but the problem is if you are already running build 1607 then you will need to apply manually / via SCCM if you have SCCM or via third party tool such as pdq deploy.

 

The other problem is after the client tries to install the update and fails a few times the client is bricked and even after installing the update it will not sync with WSUS and will require a rebuild.

 

Another update fo make sure is already installed is KB3176936: https://support.microsoft.com/en-us/kb/3176936

 

I am finding with these update in place WSUS is working as it should and I have already updated my build images to include these updates so any future builds should not have the WSUS issue.

 

Just will not know for sure if this CU has finally fix the WSUS issue until the next CU is released.

[abaxter2]

@Sheridan,

 

Are you running server 2012r2 or 2008 if so have you seen the below:

 

1. WSUS 3.0 SP2 on WS08R2 SP1 (or unpatched WS12/R2) cannot download ESDs

This is by design. WSUS 3.2 cannot sync or distribute ESDs, and WS12/R2 can only do so if both KB3095113 and KB3159706 are installed on the machine, and all necessary post-install steps from KB3159706 have been followed. As folks have noted, these post-install steps [and the general way that this update was released] caused unnecessary pain and confusion. We'll choose a less disruptive strategy for future WSUS updates.

[Sheridan]

@Sheridan,

 

Are you running server 2012r2 or 2008 if so have you seen the below:

 

1. WSUS 3.0 SP2 on WS08R2 SP1 (or unpatched WS12/R2) cannot download ESDs

This is by design. WSUS 3.2 cannot sync or distribute ESDs, and WS12/R2 can only do so if both KB3095113 and KB3159706 are installed on the machine, and all necessary post-install steps from KB3159706 have been followed. As folks have noted, these post-install steps [and the general way that this update was released] caused unnecessary pain and confusion. We'll choose a less disruptive strategy for future WSUS updates.

 

We are running Wsus on server 2008 r2. It seems to not work for any Windows 10 machines, and now only perhaps half of the Windows 7 machines. The last date date seems to coincide with when I converted the physical Wsus server to a virtual one. However that doesn't explain why in a room of Windows 7 pcs half are connecting and half aren't!

 

Our Wsus server seems to be detecting windows10 as the OS but the clients fail to connect, so they must have connected at some point to register the OS!

[abaxter2]

@Sheridan,

 

Sorry I am not running server 2008 r2 so cannot confirm this but I have heard that WSUS 3.0 SP2 on 2008 r2 cannot update Windows 10:

https://blogs.technet.microsoft.com/wsus/2016/01/22/for-those-on-wsus-3-0-sp2-or-sbs-2011/

 

But as I say I am not on server 2008 r2 so cannot confirm (Sorry).