[1607, au] Windows 10 1607 and failed cumulative update KB4013429

[Zourous]

Anyone else have this failing to install (never mind the issues the update itself causes) ?

 

This update has done what all the other cumulative updates have done so far for us which is to download, install, reach 100% and then fail and undo the changes only to try again later and do the same thing. I've turned off the updates for windows 10 at the moment as it is preventing students from logging into devices.

[deano3693]

We have a few machines with this issue thankfully all office machines that are used rarely and WOL so staff don't notice! Did you find a solution?

 

I've tried resetting Windows update on the machine, installing manually all to no avail!

[abaxter2]

The March 14th update has a number of issues and Microsoft have released the two following updates:

 

March 20th: https://support.microsoft.com/en-gb/help/4015438/windows-10-update-kb4015438

 

March 22nd: https://support.microsoft.com/en-us/help/4016635/windows-10-update-kb4016635

 

You may need to approve the March 22nd update (KB4016635) in WSUS

[abaxter2]

@Zourous if you are having problems with all windows 1607 updates the first I would recommend checking is:

 

Are using the first release of build 1607 or the November 2016 release - if using the November 2016 version this includes the fixes for updates via WSUS if your base image is based on the first release you should check if the following updates are installed:

 

KB3193494: https://support.microsoft.com/en-gb/help/3193494/cumulative-update-for-windows-10-version-1607-september-20,-2016 this is the updates that fixes updates via WSUS but of course you may find you have to install manauly.

 

I would also check if you have installed any of the following service stacks:

Aug 2016: KB3176936: https://support.microsoft.com/en-us/help/3176936/servicing-stack-update-for-windows-10-version-1607-august-23,-2016

Oct 2016: KB3199209: https://support.microsoft.com/en-gb/help/3199209/servicing-stack-update-for-windows-10-version-1607-october-18,-2016

Oct 27th: KB3199986: https://support.microsoft.com/en-gb/help/3199986/servicing-stack-update-for-windows-10-version-1607-and-windows-server-2016-october-27,-2016

Edited March 23, 2017 by abaxter2

[Zourous]

Hi @abaxter, thanks for your efforts, but the 2 new March KB's do exactly then same and fail at 100%. Yes, we know about the November 2016 version and had rebuilt the image from this, but still every cumulative update released after this fails. I am just running them manually on one PC at the moment to test. I'll keep digging, just can't understand why some people have success and others fail. I've never know updates to be so flaky.

[abaxter2]

They have been hard work to say the least with win 10 1607!!

 

The other thing I have done is set the following GPO:

 

Computer Configuration > Administrative Templates > Windows Components > Delivery Optimization

 

Select "Download Mode" and select "Bypass"

 

I set this as only wanted my updates to come via WSUS, more information here: https://blogs.technet.microsoft.com/mniehaus/2016/08/16/windows-10-delivery-optimization-and-wsus-take-2/

 

Latest ADMX files here: https://www.microsoft.com/en-us/download/details.aspx?id=53430&tduid=(c3b6aaf28b6c41469f57291e0ba3b120)(266696)(1503186)(12538X700576Xfc7a133953f4d2043accd620c07c2019)()

[samb56]

Hi All,

 

I feel better are reading this thread, we are in exactly the same position here all Cumulative updates updates on 1511 fail, yet on a few 1607 machines we have work perfect. Has anyone had any luck?

[Zourous]

The lack of response in numbers on here makes me think it is a general corruption thing. The event log reports the error code 0x800F0922. Searching for this on the internet points to several things that for the most part I've checked. I tried the W10 reset option on a image that has the problem and the update went on afterwards. We are now going to build the image from scratch and then test at various stages to see if the update goes on as it must be something we are doing to have this happen twice in two images that have been built separately. I'll let you know if I find out more, but I have a feeling it's an error code that could have numerous different causes.

[speckytecky]

We have been running Windows 10 EDU 1607 on a few machines and it's been well received but recently it's refusing to update. Tried all sorts from various forums to no avail in trying to sort this. Today I've run an in place upgrade to EDU 1703. All looked like it was going well and everything completed fine but trying to run updates yet again they fail with error message 0x80244022.

 

I guess others folk have encountered this issue - has anyone managed to resolve it yet please?

[CadlaM]

@speckytecky. Are you updating direct to MS or through WSUS? What bsecurity measures do you have in place? Proxy; on PC Firewall; Other web sucurity?

[speckytecky]

Thanks @CadlaM (Colin) Trying both direct and WSUS. Proxy is fine and working for the Internet we are behind the SWGfL Firewall.

 

@speckytecky. Are you updating direct to MS or through WSUS? What bsecurity measures do you have in place? Proxy; on PC Firewall; Other web sucurity?

[Zourous]

I think I've found out what our particular issue was after hours and hours of trial and error testing. The trouble is before we run the sysprep on a base image we have set a number W10 tweaks to get it how we want it (student lock down tweaks basically). Then after that cumulative updates would refuse to go on. From the 1607 Jan17 iso even the sysprep hangs or reboots on the "just a moment" screen from the boot-up. In our instance disabling the UAC was one of the issues and the other one was a user agreement message we added (via reg key) before the login screen.

[Michael]

I know this discussion was started in March 2017, but the May 2017 update is solid. I've yet to test the June 2017 update, but I'll be honest, I don't apply every update every month. It really depends what's fixed and if end users are experiencing issues.