[SOLVED] Server 2022 Two virtual servers with update errors both 0x80248007

Hi and welcome to Sysnative,

You have renamed the CBS log files, so please note I created a fix based on the CBSsql.log.

Step 1. Download
56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

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.
6190d993a26f3-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.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Thank you so much
I will run them the weekend, a question before I do will this work for both servers or just the sql one?
 
Hi,

Run this fix only on your SQL Server, create for DC (I assume your Domain Controller) a new thread without renaming any logfiles, just to avoid any confusions.
 
Hi,

Here's the next fix.

Step 1.
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.
6190d993a26f3-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.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi
I have tried the files and it seemed to succeed but it has now blue screened and will not boot (inaccesible boot device) I have tried slaving and repairing with bcdedit but no good, any tips, I am in a lot of stress!
 
Hi,

The last fix only contained manifest files for .NET Framework, so the BSOD must be caused by something else.
Are you able to collect the *.dmp files from the following directory? C:\WINDOWS\Minidump\*.*.
 
I have restored server from a week a go and the same error, so this has been pending for a couple of weeks at least (last reboot 18 days ago)!! I will have to slave the VHDX to anther machine to get the files. I have gone down the rebuild from scratch path at the moment. Again thank you for help
 
Are you running VMware ESXi? If so the BSOD might be related to the following issue:

February 14, 2023—KB5022842 (OS Build 20348.1547) - Microsoft Support

After installing this update on guest virtual machines (VMs) running Windows Server 2022 on some versions of VMware ESXi, Windows Server 2022 might not start up. Only Windows Server 2022 VMs with Secure Boot enabled are affected by this issue. Affected versions of VMware ESXi are versions vSphere ESXi 7.0.x and below.

Please see VMware’s documentation to mitigate this issue.

Microsoft and VMware are investigating this issue and will provide more information when it is available.
 

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

Back
Top