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:
- 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
).
- Check Your Windows Version and Build:
- Run the following to confirm your server’s version:
- 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?
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:
- Search the Servicing Stack Update (SSU) Release History 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
Sometimes
Error 50 occurs because the internal servicing stack or component store is corrupted.
- 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
If this is a WSUS-managed server, confirm that it’s temporarily configured to get updates directly from Microsoft:
- Open Local Group Policy Editor:
- Navigate to:
Code:
Computer Configuration > Administrative Templates > Windows Components > Windows Update
- Disable "Specify intranet Microsoft update service location".
- Force Group Policy update:
- Retry the manual installation of the MSU file.
Option 4: Use Online Microsoft Recovery Sources
If the local servicing stack cannot process the update:
- 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:
- 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:
- 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!