[SOLVED] KB5031356 install fails with 0x800f0805

[Haole Boy]

Aloha. I have a Win10 Home 22H2 machine that fails on the install of KB5031356 with error code 0x800f0805. I've tried resetting Windows Update with no success. sfc /scannow does not find any corruptions. DISM /restorehealth also runs clean. Your component scan program found no corruptions. Your assistance would be greatly appreciated. Please see the attachment for the CBS log and some other doc. Mahalo.

 

[Haole Boy]

Bump...

 

[Maxstar]

Hi,

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

• Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
• Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
• Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
• Press the Scan button.
• Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
• Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.

 

[Haole Boy]

Aloha. Sorry for the delay in getting back to you. Requested files are attached

Harry Z

 

[Maxstar]

Hi,

Please check your activation status: select the Start button > Settings > Update & Security > Activation.
Post a screenshot of this window.

 

[Haole Boy]

Hi,

Please check your activation status: select the Start button > Settings > Update & Security > Activation.
Post a screenshot of this window.

Aloha. I'm attaching the screen shot you requested. Mahalo, Harry Z

 

[Maxstar]

Hi,

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[Haole Boy]

Here are the files you asked for, plus a little more... After running the fixlist, and a reboot, I tried running Windows Update again. All the updates are now failing with 0x800f0805 (see attached screenshot). I ran
- sfc /scannow
- Dism /Online /Cleanup-Image /RestoreHealth
- ComponentsScanner

No problems found in any of them. Created a zip file of the CBS folder and am attaching it to this post.

Also, I noticed that the fixlist file referenced WebRoot. That program has been uninstalled for a very long time now. How do I get rid of any remnants?

Mahalo, Harry Z

 

[Maxstar]

Hi,

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

Export CBS (Component Based Servicing) hive

• Click on the Start button and type regedit
• When you see regedit on the list, right-click on it and select Run as administrator.
• When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
  

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (*.*).
  
  
  
  
  
• Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
• Right-click on the saved file and choose Send > Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[Haole Boy]

Hau'oli Makahiki Hou! (Happy New Year)

I'm attaching the requested documentation in a single zip file.

 

[Maxstar]

Happy new year!

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

• Open the startmenu and type the command cmd.
• After you find the Command Prompt, right click on it and select Run as Administrator.
• Copy and paste the following into the Command Prompt and press enter.

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

Right-click on the file FRST64.exe and choose Run as administrator.

• Copy and paste the following (code) into the Search box and click the Search Registry button.

KB3064238

• When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
• Post the logfile SearchReg.txt as attachment in your next reply.

 

[Haole Boy]

File attached per your request

Harry Z

 

[Maxstar]

Hi,

Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[Haole Boy]

Aloha @Maxstar . I finally got back to this. I ran FRST with your provided fixlist. Results attached to this post. Then tried Windows update both before and after a reboot, and it still fails. See attached screen shot.

I was not sure if you needed this, but I ran 'scf /scannow' and dism /online /Cleanup-Image /RestoreHealth. Both ran without error. Also ran the Components Scanner - results attached, along with latest CBS log zip file.

This machine is still Win 10 22H2. I'm more than willing to run an in-place upgrade to get it to 23H2, if you think that might resolve the situation.

Mahalo for your assistance. Harry Z

 

[Maxstar]

Hi,

This machine is still Win 10 22H2. I'm more than willing to run an in-place upgrade to get it to 23H2, if you think that might resolve the situation.

Windows 10 22H2 is the latest release, and will be supported till the EOL-date (14-10-2025). As for Windows 10 there will be no new 23H2 / 24H2 release.

What you could do to resolve this odd 0x800f0805 issue is to perform a rapair install.

This will reinstall and update the operating system and fix any corruptions, without removing any file or program. But make always a backup of all your important data!

• Go to this Microsoft page and under the title Create Windows 10 installation media press on Download tool now.
• Save the tool on your Desktop and double click to run it.
• On the License terms page, if you accept the license terms, select Accept.
• On the What do you want to do page, select Create installation media (USB....) and then select Next.
• Choose the ISO file option. Once the download is complete, right click the ISO and select the option Mount.
• Open the Windows File Explorer and open mounted ISO, and run the setup.exe file.
• Follow the instructions and click on the option Change what to keep.
• Select the option Keep personal files and apps and click next.
• Windows Setup will now start the in-place upgrade installation to repair Windows.

 

[Haole Boy]

Aloha @Maxstar . Sorry for the long delay in responding. But, I'm happy to report that a repair install has resolved the Windows Update issues. Mahalo nui loa for your assistance!

 

[Maxstar]

Hi,

You're welcome. Glad to hear the problem has been resolved.