Fixing 'Operation is not supported' Error in Windows 11 Updates

Attention Windows 11 users! Have you ever found yourself staring at an ominous "Operation is not supported" error while trying to install a post-checkpoint update by double-clicking the .msu package? If this mysterious roadblock has ever thrown a wrench into your update plans, don’t worry—we’ve all been there. Let’s break down what’s happening here, why it’s happening, and how you can resolve it with minimal fuss.

---

What’s Going On?​

This issue targets users who:

• Have recently installed the latest Checkpoint Cumulative Update (CCU) on their system (in this case, for example, the September 2024 Required Update—KB5043080).
• Later installed a Feature on Demand (FoD) or Language Pack (LP) from a local resource while being disconnected from Windows Update (WU) or Windows Server Update Services (WSUS).

Then, when attempting to manually install a post-checkpoint cumulative update by double-clicking its .msu file, the installation fails, presenting the error:
"Operation is not supported."
To make matters worse, this error kicks you into a loop where you’re redirected to a "Learn More" message or Microsoft Support article without much clarity on what’s wrong.

---

What’s Causing This Annoying Problem?​

The culprit lies in the interaction between the Feature on Demand (FoD) or Language Pack (LP) you manually added and the update hierarchy. When an FoD or LP is installed from local sources (for instance, an offline folder) instead of through official services like WSUS or WU, files skip certain metadata and updating mechanisms that normally keep everything in sync.
As newer updates arrive, these "orphaned" packages can’t properly validate or be patched for compatibility, leaving you stuck when attempting to install upcoming cumulative updates.
Imagine trying to install new engine parts in an older car, only to find out the car's computer system refuses to recognize the new components. Frustrating, isn’t it?

---

The Fix: How to Resolve the Issue​

Fear not—there’s a workaround, though it involves some manual effort. Microsoft has outlined a method using the DISM (Deployment Image Servicing and Management) tool to get everything in order. Let’s walk through the steps:

Step 1: Reinstall Checkpoint Updates and Latest Updates​

You’ll need to manually download and reinstall both your newest Checkpoint Cumulative Updates (CCUs) AND the specific post-checkpoint update to get everything synchronized.

1. Identify the Update KB Numbers:
   • Look up the respective KB numbers for your update on the Microsoft Update Catalog.
   • For instance, KB5043080 is the September 2024 required update.
2. Download the .msu Files:
   • Visit the Microsoft Update Catalog, search for the relevant KB number, and download the update files for your system’s architecture (x64, arm64, etc.).
   • Pro tip: Store all your downloaded .msu files in a dedicated folder, like C:\Packages, to avoid confusion.

---

Step 2: Install the Updates Using DISM​

Now that the files are downloaded, you’ll need to use the robust DISM tool instead of the standard double-click method. Why? DISM performs a much "deeper" integration, ensuring package installation without dependency errors.
Here’s how to do it step by step:

1. Open a Command Prompt with Administrative Privileges:
   • Press Win + S, type "Command Prompt," right-click and select Run as Administrator.
2. Navigate to the Folder Containing Updates:
   Use the cd command to navigate to the directory where you stored the .msu files:
   

   cmd
   cd C:\Packages

3. Run the DISM Add-WindowsPackage Command:
   Install the checkpoint cumulative updates in the proper order. Replace UpdateName.msu with your downloaded update filenames:
   

   cmd
   dism /online /add-package /packagepath:UpdateName.msu

   Example:
   

   cmd
   dism /online /add-package /packagepath:KB5043080.msu

4. Verify Installation:
   After installing each update, verify its successful application with:
   

   cmd
   dism /online /get-packages

---

Step 3: Reboot and Retry Regular Updates​

• After applying all updates via DISM, reboot your system.
• Test if the post-checkpoint issue persists by running Windows Update or attempting to install updates manually again.

---

Why Does Microsoft Recommend DISM Instead of Double-Click?​

Microsoft’s DISM tool is essentially a Swiss Army knife for managing Windows updates, patches, and servicing tasks. Here’s why it works better than double-clicking .msu files directly:

• Error Handling: DISM can troubleshoot and work around conditions like partial updates and missing dependencies.
• Batch Processing: You can apply multiple updates in one go.
• Direct System Integration: It modifies system components directly, skipping GUI overhead.

---

Proactive Tips to Avoid This in the Future​

Save yourself some time and headaches down the road by following these best practices:

1. Stick to Connected Updates: Activate connectivity to WU or WSUS when downloading and applying Language Packs or Features on Demand.
2. Centralized Update Storage: Always catalog your updates in an organized folder.
3. Regular Maintenance with DISM: Run DISM health check commands regularly to maintain a clean and optimized environment:
   

   cmd
   dism /online /cleanup-image /restorehealth

---

Takeaway​

While the "Operation is not supported" error may feel like a dead-end, it’s merely a misunderstanding between updates installed offline and the evolving state of your system. By leveraging tools like DISM and manually reinstalling checkpoint updates, you can cut through the chaos and restore normalcy.
Got any questions? Encountered a quirky behavior not covered here? Feel free to drop into the WindowsForum.com community for expert advice and discussions!
Happy troubleshooting!

---

Source: Microsoft Support “Operation is not supported” error installing a post-checkpoint update by double-clicking the .msu package - Microsoft Support