[SOLVED] Windows Updates Not Installing

Again the [0x80070005 - E_ACCESSDENIED] issue, so please reboot the server again and attempt to update again!
 
Still the same issue, so reboot the server again and attempt to update and post the latest CBS logs.
 
Thanks. I have rebooted the server multiple times and get the same error. Thanks for all your help.
 
That's odd! Then I would suggest to perform an in-place-upgrade using the MSDN iso.

In-place upgrade Server 2022 with the MSDN (Retail) ISO.
  • Navigate to the URL below and sign-in with your MSDN registered account.
  • https://msdn.microsoft.com/subscriptions/securedownloads/
  • Use the search field to find and download the correct ISO file.
  • Mount the Windows Server ISO and run Setup.exe.
  • Use the option Download updates, drivers, and optional features (recommended) and click Next.
  • Note: If you don't want to update during the in-place upgrade, press Change how setup downloads updates and select Not right now - !!! Not recommended !!!
  • When the following screen is prompted enter your (25 digit) product key. Note: Do not use the public KMS key as listed here.

    653263088a599-windows-server-2022-setup.png

  • In the next screen, select the image of the installed Windows Server edition and click Next.
  • Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next.
  • After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.
 
Sorry, we have been in the middle of an EDR migration. Now I don't get the same errors as before. I now have two servers with the same CBS error. I have included the logs from the server in this thread. I will post another thread for the other server with the same issue. Thanks again. Still working through our bookings for Silverstone.
 

Attachments

Hi,

Please upload a new copy of the COMPONENTS hive.

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.
 
Here's the next fix.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
67139f52b3c1e-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

Hi,

Here's the next fix.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
67139f52b3c1e-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

Thanks Maxstar. So I ran the fix and retried updating. The update process took over 4 hours from what I can see. I went to bed at 10:30 and the update was at 74%. Looks like the server rebooted itself(Auto reboot is not enabled) just after midnight and came back up fine. The updates now show as installed in update history. I have included the CBS logs for info. There are alot of "Warning: Overlap: Registry condition found" info logs. Not sure if that is normal. Thanks
 

Attachments

Hi,

The latest CBS log is clean, and all the (info) lines with warnings can be ignored. So if there are no remaining issues we can mark this thread as solved!
 
You must log in or register to reply here.

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

Back
Top