Navigation section

WSUS on the fritz again

Runing Windows update from Microsoft now. Once 2024-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5046616) installs I will reboot and run update again from Microsoft to make sure I am at the latest then try the postinstall command and let you know
 


It sounds like you’ve got a solid plan in place—updating to align your WSUS setup with the database schema is definitely the right first step. Once the cumulative updates (including KB5046616) are installed and your server is fully patched, WSUS should be ready to handle the postinstall command without further roadblocks.

After the reboot and any additional updates, double-check that your WSUS server versions match the database schema before running the command (just as a sanity check). Fingers crossed everything behaves properly this time around. Let me know how it goes! 😊
 


Error 0x007000d installing KB5046616 using Windows update checking updates from Microsoft Update.
 


Oof, the 0x8007000d error typically signifies "data is invalid", which usually points to corrupted update files, miscommunication with Windows Update services, or issues in the servicing stack. Let’s troubleshoot step by step to get that update installed.

Step 1: Reset Windows Update Components​

Corrupted or cached files in SoftwareDistribution or Catroot2 are common culprits for installation errors like this. Resetting these components usually resolves the issue.
  1. 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.
  2. Clear Update Cache:
    Delete temporary files in SoftwareDistribution and Catroot2 folders:
    Code: 
    bash del /s /q %windir%\SoftwareDistribution del /s /q %windir%\System32\catroot2
  3. Restart Services:
    Restart the services you stopped earlier:
    Code: 
    bash net start wuauserv net start cryptSvc net start bits net start msiserver
  4. Retry the Update:
    Use Windows Update again to install KB5046616.

Step 2: Use the Update Troubleshooter​

The in-built Windows Update troubleshooter can identify and resolve issues automatically.
  1. Search for "Troubleshoot Settings" in the Start Menu.
  2. Navigate to Additional Troubleshooters > Windows Update.
  3. Run the troubleshooter and follow the recommended steps.
  4. Retry the update.

Step 3: Manually Download and Install KB5046616​

If the error persists and Windows Update can’t handle it directly, download and install the update manually.
  1. Visit the Microsoft Update Catalog:
  2. Retry installing KB5046616 after repairing the servicing stack.

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

Use DISM and SFC (System File Checker) to repair potential corruption in system files.
  1. Run the DISM health check:
    Code: 
    bash dism /online /cleanup-image /restorehealth
  2. Run the SFC scan:
    Code: 
    bash sfc /scannow
  3. Reboot the system and attempt the update again.

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

If this system is configured to use WSUS for updates, ensure it’s temporarily switched to Microsoft Update as the source:
  1. 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".
  2. Force a policy update:
    Code: 
    bash gpupdate /force
  3. Retry the update.

Final Option: In-Place Upgrade Repair​

If none of the above works and you need this fixed urgently, consider performing an in-place upgrade repair:
  1. Download an ISO for Server 2022.
  2. Run the installer while logged into Windows.
  3. Choose the option to keep programs and files while repairing the OS.
Let me know which step works for you! If the update still refuses to budge, we’ll dive even deeper. 😊
 


Error trying to manually install
Installation Failure: Windows failed to install the following update with error 0x8024200B: Security Update for Windows (KB5046616).
 


Ah, a new error code—0x8024200B—this one means “the update installation was not completed because it was canceled.” However, this doesn't necessarily mean you canceled it. It can often occur due to:
  1. Corrupted Update Files,
  2. Conflicts with Services, or
  3. Windows Update Database corruption.
Let's dig deeper into resolving 0x8024200B and get that KB5046616 update in place.

1. Ensure Full Update Cleanup​

Residual or corrupted files can block the update from completing. Let’s double-check everything is clean:

Reset Windows Update Services (All Over Again)​

  1. Stop Update Services:
    Code: 
    bash net stop wuauserv net stop cryptSvc net stop bits net stop msiserver
  2. 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
  3. Start the Services Back:
    Code: 
    bash net start wuauserv net start cryptSvc net start bits net start msiserver
  4. 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​

Sometimes, the installer itself is fine, but running it through Windows default mechanisms causes issues. Instead, install KB5046616 directly with DISM:
  1. 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
  2. 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.
  3. Reboot After Installation:
    Restart the server to apply the update.

3. Add Logging to Identify the Problem​

If the error persists, enabling verbose logging can give us a better clue:
  1. 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
  2. Check the log file:
    • Open C:\Windows\Logs\KB5046616.log to see why the installation cancels or fails.
Feel free to share relevant details if you'd like me to help dissect the log file!

4. Fix Windows Update Component Corruption with DISM​

If the cumulative update is still failing, chances are there’s something wrong with the servicing components themselves. Repair them before retrying:
  1. 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.
  2. Retry the update using either the Windows Update GUI, manual installer, or DISM (from Step 2).

5. Check for Conflicting Prerequisites​

Some updates fail to install because they require certain prereqs, like a Servicing Stack Update (SSU). If SSU mismatch is the problem:
  1. Check the latest SSU update:
  2. Retry the installation of KB5046616.

6. Start Fresh (In Extreme Circumstances Only)​

If everything else fails:
  1. 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.
  2. 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! 😊
 


OK, I have Error 50 The request is not supported the file name is windows10.0-kb5046616-x64_e4811cdf03bd7f44cee497c1e36b222c7b9b606e.msu I am using. Do I not have the correct file?
 


Ah, an Error 50 with “The request is not supported” suggests that either the update file (MSU) isn’t compatible with your server’s OS/build, or there’s an issue with applying this package using your current system configuration.
Let's tackle this step-by-step to confirm whether you have the right file and address the error.

Step 1: Verify the Correct Update File​

The KB5046616 update you’re trying to install must specifically match Windows Server 2022 (21H2) and the architecture (x64). Let’s confirm compatibility:
  1. Double-Check the File in the Microsoft Update Catalog:
    • Go to Microsoft Update Catalog.
    • 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).
  2. 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.
  3. 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?
If the file is correct, proceed. If there’s a mismatch, download the valid package.

Step 2: Resolve “Error 50”​

The “Error 50” often indicates a problem with DISM, Windows servicing tools, or a conflict with the current servicing stack. Try these fixes:

Option 1: Update Your Servicing Stack​

The servicing stack might not support this cumulative update. To fix this:
  1. Search the Servicing Stack Update (SSU) Release History for the latest SSU for Windows Server 2022.
  2. Download and manually install the SSU.
  3. Retry installing KB5046616 after the SSU update.

Option 2: Repair Windows with DISM​

Sometimes Error 50 occurs because the internal servicing stack or component store is corrupted.
  1. Run the DISM restore health command:
    Code: 
    bash dism /online /cleanup-image /restorehealth
    This attempts to repair corruption in the component store.
  2. Retry installing the update using:
    Code: 
    bash dism /online /add-package /packagepath:

Option 3: Check Group Policy / Update Configurations​

If this is a WSUS-managed server, confirm that it’s temporarily configured to get updates directly from Microsoft:
  1. Open Local Group Policy Editor:
    Code: 
     gpedit.msc
  2. Navigate to:
    Code: 
     Computer Configuration > Administrative Templates > Windows Components > Windows Update
  3. Disable "Specify intranet Microsoft update service location".
  4. Force Group Policy update:
    Code: 
    bash gpupdate /force
  5. Retry the manual installation of the MSU file.

Option 4: Use Online Microsoft Recovery Sources​

If the local servicing stack cannot process the update:
  1. 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)​

To rule out issues with the MSU file:
  1. 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.
  2. 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! 😊
 


Version 20348.2762
Correct download
Dong cleanup image now
 


{"system": {"wf_post_id": 894292, "user": {"user_id": 129761, "username": "bswhipp"}, "timestamp": 1733422491, "thread_title": "WSUS on the fritz again", "wf_thread_id": 347173}, "user": "Version 20348.2762\nCorrect download\nDong cleanup image now"}
 


Great! With 20348.2762 confirmed and the correct update file, running the DISM cleanup-image is an excellent step to resolve any corrupted system components. Once that completes, remember the following:

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.
Let me know how it goes after cleanup finishes! If the update doesn’t play nice, I’m here to help troubleshoot further. Hopefully, this is the last hurdle. 😊
 


Ins't this update the latest SSU?
 


Excellent question! KB5046616 is indeed a cumulative update, and cumulative updates typically include the latest Servicing Stack Update (SSU) if one is required. However, it's possible for a mismatch to arise if the servicing stack update on your system is too outdated, preventing the cumulative update from being applied properly.

When SSU Matters Separately​

  1. 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.
  2. 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:​

  1. Verify Current SSU Version Installed:
    • Open PowerShell and run:
      Code: 
      bash Get-WindowsPackage -Online | Where-Object {$_.PackageName -like "*SSU*"}
    You should see something like:
    Code: 
    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).
  2. Check for Standalone SSUs:
    • Visit the official Servicing Stack Update list and confirm the SSU for Windows Server 2022.
    • If your SSU is outdated, install the standalone SSU first, then retry KB5046616.

TL;DR​

If your current servicing stack is alright, KB5046616 should include any required SSU. If you suspect corruption or errors in the existing servicing stack, preemptively installing the latest standalone SSU is a smart move. It's a quick check that might save you from more headaches down the line.
Let me know how it goes after the cleanup or if you want help confirming the current SSU! 😊
 


Get-WindowsPackage -Online | Where-Object {$_.PackageName -like "SSU"} comes back with no results
 


If the Get-WindowsPackage command for SSU (Servicing Stack Update) comes back with no results, it typically means there isn’t a recognizable SSU package installed—or at least, it’s not visible in the package manager. This confirms there’s likely a problem with the servicing stack on your server, which could directly tie in with the failures for KB5046616 or any other cumulative updates.
Here’s the plan to resolve this:

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

The servicing stack manages the installation of Windows updates and cumulative packages like KB5046616, so fixing it is crucial.
  1. Locate the Latest SSU:
    • Visit the official Microsoft Page for Servicing Stack Updates.
    • 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): Microsoft Catalog.
  2. 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.
  3. 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​

Once the servicing stack is properly updated, proceed to install KB5046616 again:
  • Via Manual Installer:
    Code: 
    bash wusa.exe .msu
    • Via DISM Command:
      Code: 
      bash dism /online /add-package /packagepath:.msu

Restart the server after installation to apply the changes.

Step 3: Recheck Compatibility if SSU Fails​

If the standalone SSU refuses to install, this may indicate servicing stack corruption deeper than expected. As a workaround:
  1. Run DISM to Repair the Component Store:
    Code: 
    bash dism /online /cleanup-image /restorehealth
    Retry the SSU installation after repairing the servicing stack.
  2. 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)​

If the SSU or servicing stack refuses updates consistently, an in-place repair upgrade might be necessary:
  1. Use a Windows Server 2022 ISO matching your current version (20348.x).
  2. Run the installer and choose “Upgrade” while keeping files and settings.
Let me know if the SSU package installs successfully or if you hit any blockers. Once the servicing stack is in place, KB5046616 should finally cooperate! 😊
 


The link to SSU is page not found
 


Ah, apologies for that! Let me guide you directly to the correct servicing stack update (SSU) download link for Windows Server 2022.

Steps to Download the Latest SSU​

  1. Open this corrected link to the Microsoft Update Catalog below:
  2. 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.
  3. Download the Correct SSU:
    Once you locate the entry, ensure it matches x64 architecture under Server 2022.

Alternative Download Method for SSUs​

If you cannot find it on the Catalog:
  • 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!
 


The latest version on the page is for Windows Server version 20H2. My Windows version is 21H2 (OS Build 20348.272) Should I install this one?
 


No, you should not install the SSU for Windows Server version 20H2 on your 21H2 system. It will almost certainly fail or cause additional issues, as servicing stack updates (SSUs) and cumulative updates are very specific to the Windows Server release and build.

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

  1. 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.
    The cumulative update KB5046616 should include the correct SSU if your servicing tools are functional. However, to manually install, here is how to verify:
  2. Manually Check SSU for Build 20348.272 or Higher:
    Head over to the Microsoft Update Catalog directly:
    Microsoft Update Catalog Home
    Search for:
    Code: 
     Servicing Stack Update for 21H2 20348
    • Filter for the latest available release for Windows Server 2022 21H2.
  3. 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:​

  1. Do Not Install 20H2 SSU—This is incompatible for Server 2022 on build 20348.x.
  2. 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
Let me know if the catalog search for 20348.x updates fails to produce results, and I can manually locate options for SSUs compatible with your version. You're nearly there! 😊
 


OK, dsim /online /cleanup-image /restorehealth came back with
[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
 


You must log in or register to reply here.

Similar threads

News
AA20-283A: APT Actors Chaining Vulnerabilities Against SLTT, Critical Infrastructure, and Elections Organizations
Replies
0
Views
3K
News
News
News
VIDEO Announcing Windows 10 Insider Preview Build 21364
Replies
0
Views
1K
News
News
News
Announcing Windows 10 Insider Preview Build 21277
Replies
0
Views
2K
News
News
BobDobalina
  • Solved
Windows 7 Complex Problem with Windows 7 (again)
2
Replies
30
Views
5K
kemical
kemical
News
Announcing Windows 10 Insider Preview Build 17704
Replies
0
Views
2K
News
News
Back
Top