KB5035845 Fails to Install

Topic

New Reply

I wanted to report an issue with KB5035845 failing to install. The behavior today is the same as I had noted last month with trying to install KB5034763.

I have a Lenovo with an Intel chip, so that isn’t the issue, even though that was a factor for Win 11. I am running Win 10 22H2 build 19045.3930.

I had a lot of help last month, documented in that discussion – much appreciated – but nothing worked.

Same as last month – using WuMgr, I successfully downloaded and “installed” the update, but on the restart, it would get to 96% and say “Couldn’t complete installation, undoing changes, trying again” – twice and then finally rebooted. The update screen seemed to stall at about 94% and then said it couldn’t install.

In my event viewer, it has the following message:

Package KB5035845 failed to be changed to the Installed state. Status: 0x800f0922.

UserData

– CbsPackageChangeState

PackageIdentifier KB5035845

IntendedPackageState 5112

IntendedPackageStateTextized Installed

ErrorCode 0x800f0922

Client UpdateAgentLCU

Same error code as with KB5034763.

Before attempting to install KB5035845 I deleted the $WinREAgent folder as was suggested by MS for the earlier problem, I turned off my antivirus, cleaned up the temp and updates files, and made backups.

I also looked up the error code again and will again go through some of the steps they outline, but last month I did run sfc /scannow and Dism /Online /Cleanup-Image /ScanHealth and a few other tools, and nothing was found that would help. Also, running the Update Troubleshooter showed no problems.

I also did attempt to install it manually, but wasn’t sure just how to do that, so I wasn’t able to.

Coincidentally, in the attempt this time, WuMgr showed KB 5034441 which I hadn’t gotten in January, so I tried to install that thinking that not having that might be causing this issue, and that update did install, but subsequently not KB5035845 – which led me to believe that this current issue isn’t a space issue.

At this moment, I am at a loss. I just wanted to get on record that this is the second month in a row this has happened, and see if anyone might have any suggestions as to what to do next. I have backups, but am not sure that rolling back is going to help anything.

Thanks for any ideas and to those who tried last month – thanks again as well!

Reply | Quote

Replies

Try fixing by running repair-install.

1 user thanked author for this post.

LHiggins

Reply | Quote

Alex5723 wrote:

Try fixing by running repair-install.

Is that an over the top repair/install? Sounds like it might be above my pay grade LOL!

Do we have instructions on how to do that here – I looked around but can’t seem to find any. I’m guessing I’d need an ISO file?

Thanks for the tip – I’ll look into it more.

But wonder what went wrong that caused this issue two months in a row? Nothing changed or different on my laptop.

 

Reply | Quote

LHiggins wrote:

Is that an over the top repair/install? Sounds like it might be above my pay grade LOL!

Do we have instructions on how to do that here – I looked around but can’t seem to find any. I’m guessing I’d need an ISO file?

https://www.askwoody.com/forums/topic/6000015-repair-install-of-windows-10-22h2/

2 users thanked author for this post.

lmacri, LHiggins

Reply | Quote

Thanks so much! I’ll check it out. Hopefully that will be the way to get things working again!!

Reply | Quote

I’d try running the Windows Update troubleshooter first.

 

1 user thanked author for this post.

LHiggins

Reply | Quote

OldGuyForum wrote:

I’d try running the Windows Update troubleshooter first.

Thanks! I did already do that and it didn’t show anything.

Reply | Quote

I’d reset and re-register the Windows Update components.

First, image your drive.

Then, open Notepad, and copy and paste the following text…

 

net stop cryptsvc
net stop bits
net stop wuauserv
::
reg delete “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v SusClientId /f
reg delete “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v SusClientIDValidation /f
::
if exist c:\windows\SoftwareDistribution.old rd /s /q c:\windows\SoftwareDistribution.old
if exist c:\windows\System32\catroot2.old rd /s /q c:\windows\System32\catroot2.old
::
rename c:\windows\SoftwareDistribution softwaredistribution.old
rename c:\windows\System32\catroot2 catroot2.old
::
net start cryptsvc
net start bits
net start wuauserv
::
wuauclt /resetauthorization /detectnow
::
PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()

 

Save the Notepad file to your Desktop, and name it WUReset.bat

Right-click on WUReset, and select “Run as administrator”.

After it completes, reboot, and run Windows Update.

 

 

3 users thanked author for this post.

windbg, ecsjjgg, LHiggins

Reply | Quote

Thanks for the input! Is that any different from the directions Susan gave to reset the software distribution folder? I did follow those and it didn’t have any effect. Yours are a little different – is that a different process?

I can give that a try if it resets a different function and see if it does have any effect.

Thanks again!

Reply | Quote

LHiggins wrote:

Is that any different from the directions Susan gave

It is different…

I’ve used this for over 4 years with no issues.

 

1 user thanked author for this post.

LHiggins

Reply | Quote

OldGuyForum wrote:

It is different… I’ve used this for over 4 years with no issues.

Great! Thanks! I can give that a try and see if it helps before I do the over the top repair. I have tried many things, and nothing seems to work, so maybe in the end, the repair is what I’ll finally need to do. And if that doesn’t work, no idea what then…

Thanks again for the help!

Reply | Quote

LHiggins wrote:

so maybe in the end, the repair is what I’ll finally need to do.

Agree.

 

1 user thanked author for this post.

LHiggins

Reply | Quote

Alex5723 wrote:

Try fixing by running repair-install.

Just a quick update. After fiddling a bit more with a few other supposed things to try, including an attempt at a manual install of KB5035845 – which failed again, I did the over the top repair this morning. It all went well and seems to be working fine.

I checked WuMgr and there were 3 updates showing now – KB5034441, KB5034685 and KB5035845. I hid KB5034441, and using WuMgr, downloaded just the Feb .NET update KB5034685 – which downloaded and installed OK.

I think I am now going to wait until the problem KB5035845 shows up on my Windows Update page and try to download it from there rather than with WuMgr and just see if the repair did fix something with the update process itself.

If that doesn’t work, I think I am just going to give up – hide that update and wait for next month.

 

Reply | Quote

Checked the Installed Updates (not Update History) to see if KB5035845 is there. The over the top repair may have installed it.

1 user thanked author for this post.

LHiggins

Reply | Quote

PKCano wrote:

Checked the Installed Updates (not Update History) to see if KB5035845 is there. The over the top repair may have installed it.

No – unfortunately, it isn’t there. It is showing in WuMgr and I am thinking that it might be best to wait to download it through the Windows Update page once it show there – probably later today or tomorrow.

 

Reply | Quote

And a quick update. I finally had success with the install of KB5035845 this morning after the OS repair. I did a few other things before trying it, but I am pretty sure that the repair was the key and what put things back in working order.

Thanks to everyone who helped me figure this out! Very much appreciated!

 

1 user thanked author for this post.

lmacri

Reply | Quote

HUH I saw the post of the fixed issues after I made my posts.

Oh well, maybe what I posted will help someone else.

 

SO glad you got you’re update woes resolved

——————————————-

 

 

You can do the following to get out of the windows updates install/UN-install cycle:

Type Services.msc in the Search box->run the Services app as Admin, right click the following services and then click stop

Windows Update Service
Background Intelligent Transfer Service

copy:

C:\Windows\SoftwareDistribution\

paste into the run cmd (windows key + R)

hit enter

This folder has all the files related to Windows updates.
Open the “Download” folder, select and delete all the files.

Restart Windows Update and Background Intelligent Transfer services in Services app by opening both and choosing Start.

You can or not, using WUHIDE, hide that update – Your call.

If you don’t hide it it will simply download and attempt the update again.If you hide it you can always UN-hide it using the same tool found here:

https://learn.microsoft.com/en-us/archive/technet-wiki/53184.show-or-hide-updates-utility-fixing-automatic-installation-of-a-problematic-update-in-windows-10-version-1903

Restart your PC

———————-

If you haven’t already try to do Lenovo updates.

Download the Lenovo system updater tool here:

https://support.lenovo.com/ca/en/downloads/ds012808-lenovo-system-update-for-windows-10-7-32-bit-64-bit-desktop-notebook-workstation

run as admin, install all critical and recommended updates – I never install the optional ones (Corporate laptops)

after the first reboot, run it again and keep doing that after every reboot until it says no updates available.

Then try that windows update once more.

Crazy as it sounds, at work we have images fail all the time, we install clean Windows = a non-enterprise Windows 10 Pro not joined to the domain-> on the PC, then do the above, re-image and it works like a charm every single time UNLESS their is an ACTUAL hardware problem.

It may or not resolve this issue however, I feel that when it comes to OEM’s you still need to be careful and aware of possible issues, but installing then 99% of the time result sin security and stability fixes and a better running laptop.

1 user thanked author for this post.

LHiggins

Reply | Quote

THIS is what the update does: if you don’t think you need it, hide it permanently

 

https://www.bleepingcomputer.com/news/microsoft/windows-10-kb5035845-update-released-with-9-new-changes-fixes/

AND, as someone else here says you can do an in-place install or over lay install whatever you want to call it.

It is simple to do:

Get your windows 10 install medium, connect it to you PC, start it, go through the wizard, when it comes to choose what type of installation you simply choose the one that mentions keeping your files and settings and click on that and then continue.

Like always back up all your important data BEFORE doing any type of Windows installation, clean or in-place.

 

Cheers and Good Luck!

1 user thanked author for this post.

LHiggins

Reply | Quote

The next interation of this will be offered up next month.  Security updates are cumulative.  When a patch will not install and the error message is pointing to drive space you may want to take more actions.  Repair installs (with a few exceptions) usually work to get a system working again.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Resolved.

Reply | Quote