[SOLVED] Server 2022 not installing KB5026370 with error 0x800f0905

BenHague

Member
Joined
Jun 8, 2023
Posts
5
Hi,
I'm trying to install KB5026370 on Windows Server 2022 Datacenter and getting the error 0x800f0905. I've tried the MS fixit tool, running wusa and resetting the WU components unsuccessfully. ComponentScanner and SFCFix can't find any problems. I'm running out of ideas, so I'm hoping someone might be able to help.
Thanks,
Ben
 

Attachments

Can you please run the following command from an elevated command prompt ...

DISM /Online /Get-CurrentEdition

... if it fails (and I expect it will), can you please post me the following log ...

%Systemroot%\Logs\DISM\Dism.log
 
Can you please run the following command from an elevated command prompt ...

DISM /Online /Get-CurrentEdition

... if it fails (and I expect it will), can you please post me the following log ...

%Systemroot%\Logs\DISM\Dism.log
Command and output is:
"C:\Users\Administrator>dism /online /get-currentedition

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.1668

Current edition is:

Current Edition : ServerDatacenter

The operation completed successfully."

Log attached anyway
 

Attachments

Can you please post me a copy of your CBS Hive ....

  • Click on the Start button and in the search box, 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 To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 
OK, I think I can see what the problem might be, but I'm going to have to consult on how to address it. This may take some time, but I'll get back to you as soon as I can.
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download SFCFix.exe and save it to your desktop.
  • Download the attachment SFCFixScript.txt and also save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Secfix.txt:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-06-16 14:45:34.336
Microsoft Windows Server 10 Build 20348 - amd64
Using .txt script file at C:\Users\Administrator\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8\Owners.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8\Owners.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2023-06-16 14:45:34.492
Script hash: RhK9qgr2osyBftqr3Q2LWG0viCRRwrEUPEXQ0l9dsac=
----------------------EOF-----------------------

DISM results:
C:\Users\Administrator>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.1726

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Files attached, thanks.
 

Attachments

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Had to copy Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.cat and Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.mum into C:\Users\Administrator\AppData\Local\niemiro\Archive\Packages\ manually, but then SFCFix ran sucecssfully:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-06-16 18:24:21.239
Microsoft Windows Server 10 Build 20348 - amd64
Using .zip script file at C:\Users\Administrator\Desktop\SFCFix.zip [2]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\Servicing\Packages

Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.cat to C:\WINDOWS\Servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.cat.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.mum to C:\WINDOWS\Servicing\Packages\Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.1668.1.8.mum.

Successfully restored ownership for C:\WINDOWS\Servicing\Packages
Successfully restored permissions on C:\WINDOWS\Servicing\Packages
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2023-06-16 18:24:24.239
Script hash: Ce/HWrA+trQwSIWw6avsgA81fCBh3T/sr/DmeLwabpE=
----------------------EOF-----------------------
Then Dism /Online /Cleanup-Image /RestoreHealth ran successfully, and Windows Update has also run successfully, so the problem seems to be fixed.

Thanks a lot for all your help.
 
You're welcome. Glad to hear you're now able to update.

I'll mark this topic as solved then.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top