Preview update KB5067036 fails with 0x80070005

AGAIN my two Windows 11 PCs refuse to install a major update.
When installing the "Preview update KB5067036" it fail with 0x80070005 and rollback after only 7%.
I am so sick and tired of having to do a repair-install EVERY time there is a major update.
Why is the updates so sensitive and fails all the time. This never was a problem on Windows 10.
I have tried trouble shooters and cleared windows update folder and done all fixes I found.
But I'd really like to avoid another repair-install (it messes up all settings and default apps).

Log file from latest attempt enclosed. Can anyone tell what is the problem here?

LarsErikOsterud said:

"Preview update KB5067036"

Click to expand...

It's only a "Preview" Update. Wait for the stable release - when this should be fixed.

Well the .Net framework is not installing either (same error) and on both my Windows 11 PCs :-(
I get fail installs and rollback everytime there is a major update.
Last time I had to do a clean install (even repair-install didn't work).
I'm getting tired of using all my time just to install an update :-(
Updates where never this "touchy" on Windows 10...

LarsErikOsterud said:

even repair-install didn't work

Click to expand...

Repair Install preserves "custom user settings" - unless the issue was related to a corrupted windows component (which would be replaced - thus, the fix) - won't make much difference. Clean install - resets ALL settings to Default. Some of the recent updates - are more picky about any changes to Windows default settings (like disabling telemetry and such - just an example). Taking into account an upcoming Windows update (as reviewed in the Windows Insider builds) - this "strictness" will be addressed - so it won't cause issues for the general audience. At least - that's what they claim, remains to be seen.

Anyway, based on above error log - you have 2x error codes.

1) - 0x80070005

Do you have at least 20GB of free space on Windows partition (C:/ - i presume)? If not, this could be one cause.

How about connectivity issues? If the connection keeps braking - this can corrupt update files while downloaded. Downloading the update from Microsoft catalog - can work as a workaround if this is truly the issue.

Power issue or incorrect Date Time?

2) - 0x800706BA

This is usually caused by one of the following services being disabled: Remote Procedure Call (RPC), Windows Update, or Background Intelligent Transfer Service (BITS). A firewall blocking the necessary RPC communication ports (like TCP/135). Or some corrupt system files - which prevents any of above services from running.

Tho, quite frankly (experience) - could also be none of the above - since the 0x80070005 error code is also rather useless for troubleshooting. It's enough to disable telemetry - and that code will appear - just because Microsoft devs responsible for a given Windows update - forced telemetry as a requirement. Thus, a reinstall (which preserves that setting) - won't fix the issue - but a Windows reset - which sets it On by default - would work. This is just a random example - of Devil's work (or Microsoft devs responsible for Windows updates - as known by others).

For the second Eror code - check the Service - and see if RPC is running (and set to auto-start on win boot). Here, save this as a .bat file using notepad (or notepad++):


Save it as BatShitCrazyUpdatefix.bat Run it, and reboot.

At times it helps with this particular error code - but not with the 1st.

40 GB free. Have downloaded the update manually from the catalog as well. Same problem.
Power is OK. Date and time is right. All the services are running as they should.
Remember this happends to both my Windows 11 systems (one new and one old PC).
It is not the same error as I had the last time update failed. But equally frustrating.
And the error messages are not very good to explain what is the problem.

A repair install messes up all folders in the Start Menu (use Classic Shell) and WinX.
Also it sets back several file associations (like Notepad2, HTML, picture viewer).
And it shouldn't be nessecary to do a repair-install evey time thee is an update?
And this happends on both my Windows 11 systems :-(

Wish I never had updated them to Windows 11 :-(

neves said:

For the second Eror code - check the Service - and see if RPC is running (and set to auto-start on win boot). Here, save this as a .bat file:

Code:

@echo off
Echo Stopping Windows Update services...
net stop wuauserv
net stop bits
timeout /t 5
Echo Clearing SoftwareDistribution folder...
rmdir /s /q %windir%\SoftwareDistribution
timeout /t 5
Echo Restarting Windows Update services...
net start wuauserv
net start bits
Echo Done.
pause

At times it helps with this particular error code - but not with the 1st.

Click to expand...

All that is checked and done allready....

LarsErikOsterud said:

All that is checked and done allready....

Click to expand...

Was expecting that much. Then i recommend waiting for the stable release. Definitely not worth resetting Windows for a preview update (not even for a so called stable release - if it's buggy). Have this issue - on a perfectly running system (errors free - other than this particular update error log) - and it would take 3 stable updates (from the upcoming months) - to fail - to make me consider other options. This monthly obsession with every update release - is rather dysfunctional (imo). Security updates are my only priority (even daily releases). If it would cover some serious exploit - sure, worth my attention - but more recently - Microsoft brakes windows with one update - only to fix it with another. Just my 2 cents, everyone can do what they want (with their limited time - on this planet).

I don't have the solution, I just hope the error isn't on Microsoft's side because it would add to another error that Microsoft seems to have fixed and that I had.

As 0x8007005 indicates a permission issue I got an idea and tried running "tweaking.com's Windows Repair" and reset permissions for files, registry and services and THEN the updates did installed. This must be the 1000 time this tool saves me (even have saved me once when repair-install wouldn't).

Don't know what permissions was wrong or why, but at least I got it fixed.