Win 10 update to 1903 failed - Error 0x80070005

[sludge7051-x]

Win 10 update to 1903 failed - Error 0x80070005

Apparently, this is a permissions access error.

Could this be due to Avast?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Is this the fix?

Avast / Menu / Settings / Troubleshooting / [un-check] Enable Self-Defense

Can I be sure (to save time)?  or would just a de-install/re-install of Avast make it a no-brainer?

[schmidthouse]

Just updated 2 machines running Win 10 1903  64 Bit (one on latest Stable version and one on latest beta version Avast Prem).
No issue updating.

"Could this be due to Avast?".....Not here

Check your access settings, Admin
Any other security software that might interfere with MS updates?

[bob3160]

Here are some suggestions: https://www.bynarycodes.com/windows-10-version-1809-update-error-0x80070005/
I personally disabled all Avast shields before starting the upgrade.


I also disconnected all attached external drives.

[schmidthouse]

@ Bob
Ah, I misunderstood the OP's issue. 

[jasonbuechler]

I registered on the forum JUST so I could angrily post this confirmation of @sludge7051-x 's theory:
Yes, when updating to 1903 (from 1803, in my case), the 0x80070005 error was explicitly caused by Avast.
NOTE: Avast caused this issue EVEN THOUGH the first thing I did was "permanently disable all shields" (!!!). 

I'll elaborate more later, but in a post in a microsoft forum so that people actually see it, since I spent hours searching for information on why time and time and time again my 1903 update failed.

I finally tracked it down, and caught Avast red-handed:

The damning event was Event ID 1001 from Windows Error Reporting, and was found in Event Viewer > Windows Logs > Application ... outrageously it was of "Information" type, so that all of my scouring through warnings, errors, and critical types produced nothing.

Here's the details: https://gist.github.com/jasonbuechler/e4d8b81ade95b65b8aeac5d06b27f337
...note that the first "attached file" is .....\Sources\Panther\SetupAct.log
Well if you go to the directory that's in, there's also a MUCh more useful log: setuperr.log
Here's that file: https://gist.github.com/jasonbuechler/2c16ddf85e69a055fe7d748c26deaeef

And the money-shot:

Code: [Select]

2019-06-23 20:29:35, Error      [0x080782] MIG    CRegistryDataStore::Create: Failed to set reflection key flags for HKCU\Software\AVAST Software\Avast[gle=0x00000005]
2019-06-23 20:29:35, Error      [0x080789] MIG    CRegistryDataStore::Create: Failed to set LUA key flags for HKCU\Software\AVAST Software\Avast[gle=0x00000005]
2019-06-23 20:29:35, Error                 SP     Error WRITE, 0x00000005 while gathering/applying object: Registry, HKCU\Software\AVAST Software\Avast [HideBalloon]. Will return 0
2019-06-23 20:29:35, Error                 MIG    Error 5 while applying object HKCU\Software\AVAST Software\Avast [HideBalloon]. Shell application requested abort
2019-06-23 20:29:35, Error      [0x08097b] MIG    Abandoning apply due to error for object: HKCU\Software\AVAST Software\Avast [HideBalloon]
2019-06-23 20:29:35, Error                        Apply failed. Last error: 0x00000000
2019-06-23 20:29:35, Error                 SP     pSPExecuteApply: Apply operation failed. Error: 0x0000002C
2019-06-23 20:29:35, Error                 SP     Apply (first boot apply, offline phase): Migration phase failed. Result: 44[gle=0x00000002]

Again, I had already done a "permanently disable all shields", long before this.

So, I uninstalled Avast.
It didn't hurt a bit, as the "you're being tracked! oooh scary!" nag-messages were over-the-line for me, already.

Rebooted, started the 1903 update again... voila... not 20 minutes later, it was done.

Again -- I had to uninstall avast to actually successfully update to 1903. Disabling it was insufficient!!!??!

[Spec8472]

Thank you for sharing the logs. This looks like Avast self-protection blockage. Will try to reproduce this.

[bob3160]

Thank you for sharing the logs. This looks like Avast self-protection blockage. Will try to reproduce this.

So my recommendation to turn off the Self Defense Module before attempting an update to 1903
might not be such a bad idea.

[Spec8472]

Unfortunately I was not able to reproduce the bug  . The update 1809->1903 with Avast (All shields on, self protection on) was successful.

[Spec8472]

For all affected users: Can you please provide the "c:\ProgramData\AVAST Software\Avast\log\selfdef.log" file?

Thank you

[jasonbuechler]

Unfortunately I was not able to reproduce the bug  . The update 1809->1903 with Avast (All shields on, self protection on) was successful.

Yeah, I'm not shocked... I'm sure Microsoft is as much to blame as anyone else, and there's probably a myriad of thousands of variables involved that MS just somehow can't figure out a way to get around. 

I found the following immediately after getting 1903 installed, while goooogling some section of that #1001 event... there's certainly a 100% chance I could be wrong, since this tool is made by microsoft, but it might be a fantastic tool to future sufferers of windows update bugs:

https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag 

About SetupDiag

SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful.

SetupDiag works by examining Windows Setup log files. It attempts to parse these log files to determine the root cause of a failure to update or upgrade the computer to Windows 10. SetupDiag can be run on the computer that failed to update, or you can export logs from the computer to another location and run SetupDiag in offline mode.

But, unanswered questions include: "WHY DOES THE ERROR NOT POINT TO THIS?" and "WHY DOES NOTHING ELSE POINT TO THIS?"

For all affected users: Can you please provide the "c:\ProgramData\AVAST Software\Avast\log\selfdef.log" file?

I don't know if mine is gone because of uninstalling, but my folder structure looks a big different, and I don't have that specific log, but I'll attach a zip of the logs I do have.  Here's my folder structure, in case that's relevant:

Code: [Select]

PS C:\ProgramData\AVAST Software> tree /f

├───Browser
├───Persistent Data
│   └───Avast
│       └───Logs
│               AvEmUpdate.log
│               AvEmUpdate.log.old
│               event_manager.log
│               Setup.log
│               Update.log
│               Update.log.old
│               Update.log.tmp.911424e7-58aa-4c7d-b972-43b270995276
│               Update.log.tmp.aa3576be-7f44-4c29-a1df-7ed9c77ddd0a
│
└───Subscriptions
        license.avastlic


[1QuickNotary]

I too am having problems with the upgrade! If I go to open Avast Cleanup Premium, it says "oops, can't open", restart computer, reinstall app or contact support. I thought I would check here in the forums first. I use Microsoft Office 365 on a daily basis and it will not allow it to open at all! I am not a developer or programmer so some of your discussion sadly goes over my head. I have no idea how to post my logs. Not sure how to even find them. If directed, I am willing to go to the locations and do directed tasks to fix this. Any help would be appreciated!

[Spec8472]

jasonbuechler: Thank you for your effort, but the file selfdef.log is missing because Avast AV is already uninstalled.

[Michael529]

This thread has gone quiet but I had 0x80070005 today, trying to move from Windows 10 x64 1809 to 1903. I run Avast Free 19.6.2383 (build 19.6.4546.508). I doubt it matters but the vps was 190722-4. The shields were all turned off before the upgrade started; if it matters, all normally run set to high sensitivity.

Earlier in the thread @Spec8472 asked for the selfdef.log. Mine is attached. I took a quick look at the log and there are entries during my attempts to upgrade.

Odd that some machines object to the upgrade and others run smoothly. Of course, it may not be an Avast problem!

[Michael529]

Well, I uninstalled Avast and the upgrade ran successfully. Which suggests that there is an Avast problem. But doesn't answer the question of why some machines ran the upgrade successfully and mine didn't.

[bob3160]

Well, I uninstalled Avast and the upgrade ran successfully. Which suggests that there is an Avast problem. But doesn't answer the question of why some machines ran the upgrade successfully and mine didn't.

See if this is of any help to you:
https://forum.avast.com/index.php?topic=156141.msg1506768#msg1506768