Since 1607: MSN.com and Flaky Windows Update

[Gongalong]

Hi folks,

 

Anyone come across either of these issues since updating to 1607?

 

Firstly, on the three machines I've updated to here, all three open MSN.com on login (!) on the default browser. Are MS trying to force this page upon us?

 

Secondly, flaky Windows Update. One of the machines here is fine, but another just sticks on 0% on the Windows Update page, the other gets stuck on downloading updates at 100%.

 

Not finding anything on either via Google.

 

Thanks

[mrwoberts]

I'm wondering if 'Windows Update Delivery Optimzation', has anything to do with this. see https://privacy.microsoft.com/en-GB/windows-10-windows-update-delivery-optimization

 

Here's an MS article to make changes to see if it makes a difference, https://support.microsoft.com/en-gb/kb/3088114

In essence, you can try forcing to fetch only from MS servers, rather than sharing internally if that's what it was doing previously.

[Gongalong]

Someone at another school has mentioned this, although WSUS is running on 2008R2 https://support.microsoft.com/en-us/kb/3159706

[mullet_man]

There is a bug with the Windows Update service on 1607 which is going to be fixed in an upcoming cumulative update planned for September.

 

More information is in this thread as lots of us will have this issue. I tested a laptop today and it eventually did download and install updates, it just seems to take a few hours and restarts but it does install.

 

http://www.edugeek.net/forums/windows-10/173821-user-profile-service-service-failed-weirdness.html

[JamboD]

I had the same issue regards MSN opening at logon, found the answer here. Just had to push out a Registry Key in GPP: "HKLM\System\CurrentControlSet\Services\NlaSvc\Parameters\Internet" set the EnableActiveProbing key to 0 and that fixed the problem.

 

This stops Windows from checking that it has an Internet connection at startup which means that until you access the Internet in some way the network icon will have a yellow warning symbol next to it but I'm happier with that than Edge opening at every logon - I wouldn't mind so much if it opened the custom homepage I've set!

[Gongalong]

@mullet_man Ah yes, subsequently I spotted the pinned thread on the WSUS forum https://social.technet.microsoft.com/Forums/office/en-US/5521e7f1-fa2d-4867-a47c-b276c66e6a82/windows-10-anniversary-update-1607

 

I didn't realise that the WSUS version was dependent on the server version, as you need 2012 (R2?) to have WSUS v4, which fully supports Win 10.

 

But WSUS didn't seem to be our issue. We've only updated three PCs here to 1607, and they all had problems with Windows Update or WSUS. I tried a bunch of fixes, including manually downloading and installing the three 1607 CUs, and also the Win 10 Windows Update troubleshooter. In one case the latter fixed it, and the other two cases were fixed by the former.

 

Annoying that Microsoft's QA has gone down the toilet!

[DJ-1701]

The WSUS issue I pinned down to needing KB3176929 install to resolve the update issue. I just downloaded the cab file and added as a package into my MDT so it would automatically install on new deployments of Windows 10 1607. Our WSUS server is on Server 2008 and to my knowledge didn't need an update to resolve this.

 

Windows 10 32-Bit Cab

http://download.windowsupdate.com/c/msdownload/update/software/crup/2016/08/windows10.0-kb3176929-x86_eea500c46bcd6c1e66eb82d357bc478236a0c76f.cab

 

Windows 10 64-Bit Cab

http://download.windowsupdate.com/c/msdownload/update/software/crup/2016/08/windows10.0-kb3176929-x64_142e76e8af8468c85147b0d17f0a7e86e98c8b0d.cab

Edited September 1, 2016 by DJ-1701

[mullet_man]

@Gongalong yes with the older WSUS on 2008r2 it can offer patches and updates for Windows but can't do full releases like the 1607 update. Am happy with this as am hoping to upgrade our servers next year.

@DJ-1701 I've found you need the serving update too, although this worked for me for a while and today I've just imaged 30 machines that all got stuck at the WSUS step. A new cumulative update was released yesterday too. Although the update for the WSUS issue which is a client issue is being released later in September on patch Tuesday apparently.

 

The updates do install eventually it seems be it is really flakey and takes hours even days. I think the best solution might be to change your GPO to tell the clients to look for updates online which should work. I might do this when I know the fix has been released so I know all the devices will update and update quicky.