Windows 10: Anniversary Update - a no go here

Windows tried to install the anniversary update. Downloaded fine - restarted itself with the normal percent completed figures then after restarting got the - 'System Thread Exception Not Handled' message.

Fortunately it auto restored the previous version of Win10 so no big deal. Quick look on the MS site is of little help - if any.

Viewed the Event Log and there are goodness knows how many messages. So I guess I'll wait until the next update. Don't think I'm missing a great deal by giving this one a miss.

Any input appreciated.

:)

 

Runtime Broker causing high CPU usage after anniversary update

Same here. It's going crazy for no reason since the anniversary update.

 

KB4013429 "failed to install" error 0x8e5e03fb

Hi Bill! Here you go! Skip the anniversary addition and install the "Creator" Here's where to get it earlier then with the April update!

How You Can Upgrade to Windows 10 Creators Update Right Now

 

In event viewer only the incidents marked as "error" or "critical" are important, the rest can be ignored. Maybe you want to download the iso and try a manual update.

 

I got mine from here found it a lot easier
https://support.microsoft.com/en-gb/...setting_client

 

If you check your C: directory do you have a folder named $Windows.~W? Prior to my upgrade completion the folder was there but now it seems to be gone. If it is still there, it may contain some log files within which could help.

You may need to set your system to see hidden files and uncheck the Hide Protected Operating system files to see it in the File Explorer View options.

 

Thanks for the feedback guys. Tried the alternative route as suggested - still no go.

System Event log shows 5 errors at time of attempting update -

a) The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

b) The Sync Host_46c19 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service.

b) listed 4 times.

Application log shows 1 error

a) Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details:
AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol.

System Error:
Access is denied.

Not sure if these are stopping the update or not - all over my head now. At least Win10 manages to restore the old version.

 

Having this same exact issue. System Thread Not Handled at 71%. Thought it was my anti-virus...disabled that. Same thing. Not sure what is going on here. Not computer literate at all so I guess I will be without this update until Microsoft fixes it.

 

All weird as my failed update left behind a file - 14393.160715-1616.rs1_release_CLIENTCombinedSL_RET_x64fre_en-us.esd - 2.47GB - which I assume could easily be turned into an ISO. Not sure exactly what the enhancements are in the update so I'm going to give this one a quiet miss unless there's an easy way to do it or MS sorts it.

Most though seem to have updated with no problems - so go figure time here with me.

 

I've got the exact same issue. Anniversary update goes to 80%, then reboots into a blue screen with "System Thread Exception Not Handled". No error code and no minidumps are created.

I've tried windows update version - it failed and then stopped appearing in the update list. Then i've downloaded manual update and it failed updating 3 times. Each time it would revert the windows (thankfully) to a previous installation.

Right now im creating a bootable usb stick so i might try fresh installation with 1607 update.

Out of a curiosity - do you guys have Avast/EaseUS/Aida64 installed on your pc? I've read that some specific software might cause issues with the update and those are the usual suspects i've got.

I've searched windows event logs and found this:

Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 1607.

No idea yet what that error code means.

 

I'm running Avast but it was disabled during the update download. The System Thread etc message came up when it had rebooted and installing the update outside of Windows. So don't think Avast would have been running then.

As an aside, running Avast on a Win10 laptop and that updated fine. Also, I neglected to disable Avast. Not sure there's been any improvement in the speed but it is only a 13" Dell XPS so sprightly but no speed freak. Also not particularly impressed with not being able to turn off the auto update via group policy editor. Managed to disable (I hope) the force feeding of apps using Winaero.

So the jury is out here - is it a worthwhile update for the consumer (me) or MS. Good luck with the fresh install but I don't feel there is enough there to warrant the trouble. Just my personal $0.02 worth.

 

I am running Avast. I tried with it enabled and disabled. I finally just gave up and created a bootable USD disk after reading how to. Installed the Anniversary Update this way.

 

Found the culprit - it was Avast after all. You have to uninstall it completely and use avast cleaner tool then update will install just fine. Also if you install avast after the update - it will cause BSOD's anyway. Developers are already working for a fix though personally i feel like they let me down - i've already made a clean installation and wasted a lot of time because of that bug.

 

I just found that out by trying to install Avast. Your post with the cleaner tool saved my skin! Quite a let down from Avast when they have known about the Anniversary Update for quite a bit of time. I think I will just use Windows Defender from now on.

 

Thanks for that. Simply disabling Avast doesn't work - on my system anyway. Had to totally delete it and reboot. Then the update went as smooth as could be. Now using Defender.