WSUS on the fritz again

Step 1: Reset Windows Update Components​

• Stop Windows Update Services:
  Run the following commands in an elevated Command Prompt:
  
  Code:

  bash net stop wuauserv net stop cryptSvc net stop bits net stop msiserver

  These commands stop the Windows Update service, Cryptographic service, BITS, and the MSI installer.
• Clear Update Cache:
  Delete temporary files in SoftwareDistribution and Catroot2 folders:
  
  Code:

  bash del /s /q %windir%\SoftwareDistribution del /s /q %windir%\System32\catroot2

• Restart Services:
  Restart the services you stopped earlier:
  
  Code:

  bash net start wuauserv net start cryptSvc net start bits net start msiserver

• Retry the Update:
  Use Windows Update again to install KB5046616.

Step 2: Use the Update Troubleshooter​

• Search for "Troubleshoot Settings" in the Start Menu.
• Navigate to Additional Troubleshooters > Windows Update.
• Run the troubleshooter and follow the recommended steps.
• Retry the update.

Step 3: Manually Download and Install KB5046616​

• Visit the Microsoft Update Catalog:
• Go to: https://support.microsoft.com/en-us/topic/servicing-stack-updates-2a01c85f-04b4-480c-8bff-17d1a93cc7de page.
• Download and install it via .msu.
• Retry installing KB5046616 after repairing the servicing stack.

Step 5: Scan and Repair System Files (Corruption Issues)​

• Run the DISM health check:
  
  Code:

  bash dism /online /cleanup-image /restorehealth

• Run the SFC scan:
  
  Code:

  bash sfc /scannow

• Reboot the system and attempt the update again.

Step 6: Check WSUS GPO and Update Source (if applicable)​

• Open Group Policy Editor:
• Navigate to:
  
  Code:

   Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update

• Disable (or temporarily change) the policy "Specify intranet Microsoft update service location".
• Force a policy update:
  
  Code:

  bash gpupdate /force

• Retry the update.

Final Option: In-Place Upgrade Repair​

• Download an ISO for Server 2022.
• Run the installer while logged into Windows.
• Choose the option to keep programs and files while repairing the OS.

• Corrupted Update Files,
• Conflicts with Services, or
• Windows Update Database corruption.

1. Ensure Full Update Cleanup​

Reset Windows Update Services (All Over Again)​

• Stop Update Services:
  
  Code:

  bash net stop wuauserv net stop cryptSvc net stop bits net stop msiserver

• Delete Pending Updates:
  Manually clear Windows Update queues:
  
  Code:

  bash del /f /s /q %SystemRoot%\SoftwareDistribution\DataStore del /f /s /q %SystemRoot%\SoftwareDistribution\Download del /f /s /q %SystemRoot%\System32\catroot2

• Start the Services Back:
  
  Code:

  bash net start wuauserv net start cryptSvc net start bits net start msiserver

• Retry the Update:
• For the manual installer or Windows Update, let’s see if this clears the issue.

2. Bypass Windows Update By Installing With the DISM Command​

• Locate the Update File:
  If you downloaded KB5046616 (e.g., windows10.0-kb5046616-x64.msu), take note of its full file path. For example:
  
  Code:

   C:\Downloads\windows10.0-kb5046616-x64.msu

• Install Using DISM:
  Use the DISM tool to directly apply the update:
  
  Code:

  bash dism /online /add-package /packagepath:"C:\Downloads\windows10.0-kb5046616-x64.msu"

  This bypasses Windows Update processes and forces installation.
• Reboot After Installation:
  Restart the server to apply the update.

3. Add Logging to Identify the Problem​

• Run the manual installer again, but this time gather a detailed log:
  
  Code:

  bash wusa.exe C:\Downloads\windows10.0-kb5046616-x64.msu /log:C:\Windows\Logs\KB5046616.log

• Check the log file:
• Open C:\Windows\Logs\KB5046616.log to see why the installation cancels or fails.

4. Fix Windows Update Component Corruption with DISM​

• Perform a Component Store Repair with DISM:
  First, scan and repair Windows internal files:
  
  Code:

  bash dism /online /cleanup-image /scanhealth dism /online /cleanup-image /restorehealth

• Restart once complete.
• Retry the update using either the Windows Update GUI, manual installer, or DISM (from Step 2).

5. Check for Conflicting Prerequisites​

• Check the latest SSU update:
• https://support.microsoft.com/en-us/topic/servicing-stack-updates-2a01c85f-04b4-480c-8bff-17d1a93cc7de.
• Manually download and install it.
• Retry the installation of KB5046616.

6. Start Fresh (In Extreme Circumstances Only)​

• Remove WSUS Configurations:
  Temporarily bypass WSUS configuration and point the system directly to Microsoft Update for a clean install:
• Open Group Policy Editor:
  
  Code:

   Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update

• Disable the policy "Specify intranet Microsoft update service location".
• Force a policy update:
  
  Code:

  bash gpupdate /force

• Try getting updates directly from Microsoft.
• In-Place Upgrade Repair (To Fix Deep Corruption):
  If servicing tools don’t work, consider an in-place upgrade repair:
• Use a Windows Server ISO (matching or newer).
• Run the installer to “upgrade” the system while keeping programs and data intact.
• Reapply updates after the repair.

Wrapping Up​

• First, try the DISM installation trick.
• If that doesn’t work, enable MSU logging and look at KB5046616.log for clues.
• Move to repair tools like DISM /restorehealth if the corruption persists.
  Let me know how things progress or share logs if you'd like me to analyze. KB5046616 is going down eventually!

Step 1: Verify the Correct Update File​

• Double-Check the File in the Microsoft Update Catalog:
• Go to https://www.catalog.update.microsoft.com/.
• Search for KB5046616.
• Look for entries that specifically match Windows Server 2022 21H2 with x64 architecture.
• Download the update, and compare it to your current file (windows10.0-kb5046616-x64_e4811cdf03bd7f44cee497c1e36b222c7b9b606e.msu).
• Check Your Windows Version and Build:
• Run the following to confirm your server’s version:
  
  Code:

  bash winver

• You should see Windows Server 2022, Version 21H2, Build 20348.x.
• If it’s not 21H2, then KB5046616 is incompatible with your server.
• Ensure the Update Matches:
  Compare the following:
• Does the MSU file metadata on the Update Catalog match Windows Server 2022?
• Is the update for 21H2, x64 architecture?

Step 2: Resolve “Error 50”​

Option 1: Update Your Servicing Stack​

• Search the https://support.microsoft.com/en-us/topic/servicing-stack-updates-2a01c85f-04b4-480c-8bff-17d1a93cc7de for the latest SSU for Windows Server 2022.
• Download and manually install the SSU.
• Retry installing KB5046616 after the SSU update.

Option 2: Repair Windows with DISM​

• Run the DISM restore health command:
  
  Code:

  bash dism /online /cleanup-image /restorehealth

  This attempts to repair corruption in the component store.
• Retry installing the update using:
  
  Code:

  bash dism /online /add-package /packagepath:

Option 3: Check Group Policy / Update Configurations​

• Open Local Group Policy Editor:
  
  Code:

   gpedit.msc

• Navigate to:
  
  Code:

   Computer Configuration > Administrative Templates > Windows Components > Windows Update

• Disable "Specify intranet Microsoft update service location".
• Force Group Policy update:
  
  Code:

  bash gpupdate /force

• Retry the manual installation of the MSU file.

Option 4: Use Online Microsoft Recovery Sources​

• Add the /source parameter to DISM, so it fetches missing components from the web:
  
  Code:

  bash dism /online /add-package /packagepath: /source:MicrosoftUpdate

Step 3: Alternate (Reconfirm File Integrity)​

• Ensure the file is not corrupted:
• Re-download KB5046616 from the Microsoft Update Catalog.
• Check the file size and compare it with the size listed on the catalog.
• Test Local Integration with DISM:
• Create a local folder:
  
  Code:

  bash mkdir "C:\Packages"

• Move the MSU file there and run:
  
  Code:

  bash dism /online /add-package /packagepath:"C:\Packages\windows10.0-kb5046616-x64_e4811cdf03bd7f44cee497c1e36b222c7b9b606e.msu"

Next Steps​

• Verify that you have the correct version of the update.
• Check your server’s build (if it’s older than 21H2, 20348.x, KB5046616 won’t apply).
• Update the servicing stack and retry DISM to repair corrupt components.
  Let me know if you confirm the file is correct and still face issues! If needed, we can analyze further logs or retry alternate approaches. This update is going to work one way or another!

Checklist to Finish the Update:​

1. Reboot the Server:
   • A system restart helps finalize any pending cleanup operations post DISM.
2. Retry the Installation:
   • Install the update using your downloaded MSU file manually:
     
     Code:

     bash wusa.exe \windows10.0-kb5046616-x64.msu

     • If it still doesn’t work, use DISM for direct deployment:
       
       Code:

       bash dism /online /add-package /packagepath:\windows10.0-kb5046616-x64.msu

   • Windows Update to Confirm:
     • After a successful install, double-check with Windows Update to ensure the server shifts to an up-to-date state.

If Issues Arise Post Cleanup​

• Keep an eye out for specific error codes if the update fails again—detailed logs are key to diagnosing persistent issues.
• Reassess the Servicing Stack Update (SSU), ensuring the system has the latest SSU for your Server 2022 version before applying the KB. You should still be able to install that independently if needed.

When SSU Matters Separately​

• If You’re Missing a Critical SSU Pre-Requisite:
• Sometimes a specific SSU is a prerequisite before a cumulative update like KB5046616 can be applied. If your current servicing stack is badly outdated or corrupted, the cumulative update might not get far enough to replace it.
• SSU Included in KB5046616:
• Windows Server 2022 cumulative updates generally include the latest servicing stack updates. However, installing an SSU manually beforehand may solve issues if your current servicing stack is broken or too far out of date.

What You Should Do to Double-Check:​

• Verify Current SSU Version Installed:
• Open PowerShell and run:
  
  Code:

  bash Get-WindowsPackage -Online | Where-Object {$_.PackageName -like "*SSU*"}

bash Package Identity: SSU-20348.1.2 State: Installed

• Look for the Package Identity matching the latest servicing stack update for Server 2022 (let’s verify if it's 20348.2762 or close).
• Check for Standalone SSUs:
• Visit the official https://support.microsoft.com/en-us/topic/servicing-stack-updates-2a01c85f-04b4-480c-8bff-17d1a93cc7de and confirm the SSU for Windows Server 2022.
• If your SSU is outdated, install the standalone SSU first, then retry KB5046616.

TL;DR​

Step 1: Install the Latest Servicing Stack Update (SSU) for Server 2022​

• Locate the Latest SSU:
• Visit the official Microsoft Page for https://support.microsoft.com/en-us/topic/servicing-stack-updates-2a01c85f-04b4-480c-8bff-17d1a93cc7de.
• Look for Windows Server 2022 (21H2). As of your 20348.2762 build, the latest SSU should be included in KB5031364 (October 2023).
• Direct Download Link for SSU (if needed via manual archive): https://www.catalog.update.microsoft.com/.
• Download and Manually Install:
• Download the Standalone SSU Package matching your system architecture (x64).
• Double-click the downloaded .msu file and follow the installation steps.
• Verify the SSU Installation:
• After resetting the servicing stack, run the following to confirm:
  
  Code:

  bash dism /online /get-packages

• You should see an SSU package (e.g., Package Identity: SSU 20348.xxx).

Step 2: Retry KB5046616 After Installing SSU​

• Via Manual Installer:
  
  Code:

  bash wusa.exe .msu

• Via DISM Command:
  
  Code:

  bash dism /online /add-package /packagepath:.msu

Step 3: Recheck Compatibility if SSU Fails​

• Run DISM to Repair the Component Store:
  
  Code:

  bash dism /online /cleanup-image /restorehealth

  Retry the SSU installation after repairing the servicing stack.
• Perform an Offline Update Install:
• Download and mount the Server 2022 ISO you used for installation.
• Use DISM with the /source option to repair the system using files from the ISO:
  
  Code:

  bash dism /online /restorehealth /source:WIM:\Sources\install.wim:1 /limitaccess

Final Check: In-Place Repair (Last Resort)​

• Use a Windows Server 2022 ISO matching your current version (20348.x).
• Run the installer and choose “Upgrade” while keeping files and settings.

Steps to Download the Latest SSU​

• Open this corrected link to the Microsoft Update Catalog below:
• https://www.catalog.update.microsoft.com/
• Search for "Servicing Stack Windows Server 2022".
  As of your server version (Build 20348.2762, which aligns with the cumulative updates released in late 2023):
• Look for the specific update package matching 20348.XXXX (Windows Server 2022) in the results.
• Example of a proper SSU might include SSU KB5031364 or similar.
• Download the Correct SSU:
  Once you locate the entry, ensure it matches x64 architecture under Server 2022.

Alternative Download Method for SSUs​

• Let me know which specific release of Server 2022 you're on, and I can locate the standalone .msu for certainty.
• Additionally, confirm whether you're directly connected to Microsoft Update or WSUS!
  

  ---

  Let me dig deeper if something still feels missing! Either way, no more dead-end links for you!

Correct Steps for 21H2 (Build 20348.x):​

• Direct Link to KB for 21H2 SSU:
• For your build (20348.272), you'll need an SSU that aligns with Windows Server 2022 (21H2), which is specific to build 20348.x and above.

• Manually Check SSU for Build 20348.272 or Higher:
  Head over to the Microsoft Update Catalog directly:
  https://www.catalog.update.microsoft.com/
  Search for:
  
  Code:

   Servicing Stack Update for 21H2 20348

• Filter for the latest available release for Windows Server 2022 21H2.
• Install Correct SSU for 20348 Build:
  If a matching SSU for 20348.x appears, download it for x64 architecture.

If No Proper SSU Specifically for Your Build is Found:​

• Do Not Install 20H2 SSU—This is incompatible for Server 2022 on build 20348.x.
• Rely on repairing your existing servicing stack:
• Use DISM:
  
  Code:

  bash dism /online /cleanup-image /restorehealth

• Retry installing KB5046616 manually:
  
  Code:

  bash wusa.exe windows10.0-kb5046616-x64.msu