[SOLVED] Server 2022 - All cumulative Updates error with 0x800f081f

Sorry to be late getting back to you, I didn't get a notification of your reply.

Nothing new being flagged in your latest CBS.log, so please try updating again.

If successful please let me know.

If not, please post me a copy of the CBS.log created after your update attempt.
 
No need to apologize, you're helping me!

Failed again, however, it's a new error.

0x800f0982
 

Attachments

  • 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:5034770
  • Let me know if it says it was successful or if there are any errors.
 
OK, then please do the following .....


  • 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 ... KB5034770 ... 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.
 
I'm working through this.. need to create some exceptions. Thank you.
 
  • Download the attached fixlist.txt and save it to the same location as FRST (must be in same folder or it won't process).
  • NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system
  • Now press the Fix button once and wait.
  • FRST will process fixlist.txt
  • When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
  • Please post me the log
 

Attachments

Please reboot your machine (when possible) to finalise the Registry edit just performed.

Once you've done that ...

  • 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
 
Please can you send me a copy of your CBS hive file ....

  • 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
 
Lot of things I need to check, and I'm going to have to consult with my colleagues, so it's going to be a while before I get back to you.

At this time I have no real idea how long that might be, but it certainly won't be today.

If there's going to be any really long delay, I'll get back to you and let you know.
 
I appreciate your help. No worries. The system itself is functioning just fine, just unable to patch it.

Typically I'd just rebuild at this point, but, the nature of this product makes me want to avoid that at all costs.
 
the nature of this product makes me want to avoid that at all costs.

Well we'll try our best to ensure that's not necessary, but I can't give any guarantees at this point.

It's been a long day, and I'm turning in for the night now, hopefully I'll have some news from my colleagues in the morning.
 
I completely understand. I'm very grateful for your volunteer work helping me out on this. Enjoy your night.
 
Back earlier than expected. Turns out what I thought would be difficult to deal with was a whole lot easier than I imagined it would be.

So ....

  • Download the attached fixlist.txt and save it to the same location as FRST (must be in same folder or it won't process).
  • NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system
  • Now press the Fix button once and wait.
  • FRST will process fixlist.txt
  • When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
  • Please post me the log


PS. I really am turning in now, so I'll see your reply in the morning.
 

Attachments

Somewhat surprised to see all the "not found" entries in your fixlog.txt
Need to check to see whether it's just FRST that's not reporting things properly, and the items flagged in your last CBS.log are now gone, or whether they're still present.

So ....


  • 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
 

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

Back
Top