[SOLVED] Windows 2019 SFC Issues and Windows Update Concerns - WU

[Maxstar]

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 SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• 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.

DISM /online /cleanup-image /RestoreHealth

 

[danielcberman]

Please see attached for SFCFix.txt

DISM Command failed with the following message

[== 4.5% ] Error: 2 The system cannot find the file specified.

Please see attached for new CBS logs

 

[Maxstar]

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 SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• 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.

DISM /online /cleanup-image /RestoreHealth

 

[danielcberman]

Please see attached for SFCFix.txt

DISM Command failed with the following message

[== 4.5% ] Error: 2 The system cannot find the file specified.

Please see attached for new CBS logs. Reading through the CBS logs it looks like the CSI errors are increasing, is this expected at this point in the troubleshooting process?

 

[Maxstar]

Reading through the CBS logs it looks like the CSI errors are increasing, is this expected at this point in the troubleshooting process?

Yes, the COMPONENTS hive is pretty damaged, for now we are just replacing all the missing 'ComponentFamilies' keys! But as you can see in the log of ComponentsScanner, thousands of Components keys are missing too!

Fixing such kind of problems can take a lot of time to make some progress! And to be honest, I would perform an in-place-upgrade at this stage! Let me know what you prefer.

 

[danielcberman]

This is a WSUS server for small network of less than 70 endpoints so it's important but not critical. It does nothing else besides WSUS. If it's down for a couple of hours or even a day or two it's not the end of the world. Any thoughts or tips on a repair using the Windows 2019 install ISO?

 

[Maxstar]

(...) If it's down for a couple of hours or even a day or two it's not the end of the world.

Then I would just following the instructions below.

• 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.
  
  
  
  
  
• 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.

 

[danielcberman]

Thank you for the guidance. I finally found the AVMA Windows product keys that my predecessor left. I fired up a new VM, activated it, patched it and now it will only boot into safe mode. I think you can safely resolve this thread, but if you could take a look at,

Windows Server 2019 - Fully Patched - Will Only Boot Into Safemode

I would appreciate it.

 

[Maxstar]

Hi,

Hmm, that's odd and will mark this thread as solved then.

I am currently working on several threads, so I will take a look at the other thread as soon as possible.