server 2022 update error 0x800f0905

Status
Not open for further replies.
T

tombrugmans

Member
Joined
Sep 27, 2023
Posts
14
I can't get my server 2022 installation to update and keep getting the following error: There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f0905)
 

Attachments

Looking over your logs, back soon.
 
From an elevated command prompt, please run the following command .... DISM /Online /Get-CurrentEdition ... and post me the result.

If it fails (and I expect that it will), please post the following log ..... C:\Windows\Logs\DISM\Dism.log
 
The output:
C:\Windows\system32>DISM /Online /Get-CurrentEdition

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.859

Current edition is:

Current Edition : ServerStandard

The operation completed successfully.
 

Attachments

OK, not quite what I was expecting, so can you please do the following for me ....

  • 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
 
Last edited:
  • Click on the Search button and type Cmd
  • From the search results choose Command Prompt then Run as Administrator
  • When prompted by UAC allow the prompt.
  • When the Command Prompt Window opens, copy and paste the following command into it, then press Enter
wusa /uninstall /KB:5030216
Click to expand...
  • Let me know if it says it was successful or if there are any errors.
 
Yes, that's what I expected it to say. Trouble being that your CBS.log shows that there are entries for that update present on your machine, but not the accompanying files they reference.

So, let's see if we can find out what "orphans" are present ....

  • Click Search and type CMD
  • Right click the CMD App from the search results and select Run as Administrator
  • With the App open ...
    • Copy/Paste the following Command into it ...
    • reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
      • This loads your COMPONENT hive.
    • You can now close the Command window.
  • Next ...
  • Download Farbar Recovery Scan Tool and save it to your Desktop
    • 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 on FRST64.exe and choose Run as administrator
    • Copy and paste ... KB5030216 ... into the Search box.
    • Click the Search Registry button.
    • When the scan is complete ...
      • A log will open on your Desktop ... SearchReg.txt
    • Attach the file ... SearchReg.txt ... to your next reply.
  • You may close any remaining open windows now.
 
Here is the log not much to see:

Farbar Recovery Scan Tool (x64) Version: 25-09-2023
Ran by tom.admin (28-09-2023 15:50:01)
Running from C:\Users\tom.admin\Desktop
Boot Mode: Normal

================== Search Registry: "KB5030216" ===========


====== End of Search ======


edit: also no files:
Farbar Recovery Scan Tool (x64) Version: 25-09-2023
Ran by tom.admin (28-09-2023 15:50:16)
Running from C:\Users\tom.admin\Desktop
Boot Mode: Normal

================== Search Files: "KB5030216" =============


====== End of Search ======
 
Not what I expected. I'm going to have to consult with my colleagues on this. May be a while before I get back to you.
 
Sorry to be so very late getting back to you, but still waiting for a reply to my questions from my colleagues. It's extremely busy on the forum at present, and we have very few trained helpers, so most will be fully engaged with their own topics, and it may be some time before they get the chance to communicate with me.

So, in the meantime, I'd like to check whether the errors I saw in your earlier CBS.log are still present, or whether there may be other causes not shown in that log, so can you please do the following for me ....

  • 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
 
OK, latest CBS.log is not showing the earlier error.

So can you please do the following for me ...

  • Download and run Process Monitor
    • Leave this running while you perform the next steps.
  • Try updating the system just like you have in the past.
  • Stop Process Monitor as soon as it fails.
    • You can simply do this by clicking the "Square" icon on the toolbar (third one from the left) or by hitting Ctrl+E
  • Select the File menu ... Save ... and save the file to your Desktop.
    • The name will be LogFile.PML.
  • Zip the file, and upload to a file sharing service.
  • Provide the link to LogFile.PML
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Also attach a copy of your ... C:\Windows\Logs\CBS\CBS.log ... with your reply.
 
Would help if you had zipped the .pml file as I asked you to in my previous post.

It has just taken me over half an hour to download the 4.4 GB file that is Logfile.PML using the link you provided.

Looking it over now, but large files of this time can take a while to go through, so may be some time before I get back to you.
 
No problem, I've got the file OK, just letting you know in case we have to do this again at some point. Zipping the file speeds up the download quite a bit. ;):-)
 
It seems your ProcMon scan was stopped a little early, since the errors flagged in your latest CBS.log occur approx 5 mins after the last entry in your Logfile.pml

This is somewhat unusual, but then quite a few things in this case have been not quite what I expected.

So, can you please run a second scan, using the instructions in post #14, but this time wait for 5 minutes or so after the update fails, before terminating the ProcMon scan.

Once finished, please Zip your Logfile.pml and post me a link to it, and please do the same for your latest CBS.log as well.
 
Status
Not open for further replies.

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

Back
Top