How to fix Error 1646 on Windows 11

by

Why This Error Happens

Error 1646 occurs because Windows Installer (MSI) technology does not allow certain update packages to be uninstalled independently once they have been integrated into the base application or the OS servicing stack. This typically happens when the update was “slipstreamed” into the original installation or merged via a Cumulative Update (CU), removing the standalone uninstall registry keys required for rollback. Corrupted metadata in the Component Based Servicing (CBS) store can also trigger this error even when a valid uninstall path theoretically exists.

Step-by-Step Resolution Guide

Step 1: Verify the Update Type via Command Line

  • Open Command Prompt as Administrator (Right-click Start > Terminal (Admin)).
  • Run wmic qfe list brief /format:table to check if the update is listed as a standalone package or a bundled Security Update.
  • If it belongs to a Cumulative Update, standard uninstallation via Control Panel will fail with Error 1646, confirming this is by design rather than a corruption issue.

Step 2: Use DISM to Remove the Package

  • Since standard appwiz.cpl (Programs and Features) won’t work for merged packages, use the Deployment Image Servicing and Management (DISM) tool instead.
  • Run DISM /Online /Get-Packages to find the exact Package Identity Name (e.g., Package_for_KB5031354~31bf3856ad364e35~amd64~~22621.1.1.1).
  • Execute DISM /Online /Remove-Package /PackageName:<Full_Package_Name_Here> /quiet /norestart to force the removal at the servicing level.

Step 3: Repair the Component Store

  • If DISM removal also fails, the CBS store is likely corrupted, preventing the OS from recognizing a valid uninstall path.
  • Run DISM /Online /Cleanup-Image /RestoreHealth to repair the underlying component store using Windows Update as the source.
  • Follow this with sfc /scannow to fix any corrupted system files that might be blocking the standard uninstallation logic.

Step 4: Utilize System Restore as a Rollback Method

  • If the update must be removed and DISM fails due to strict dependency locks, use System Restore instead of the Uninstaller.
  • Navigate to Settings > System > Recovery > Advanced startup or search for “Create a restore point” in the Start menu.
  • Select a restore point dated before the update installation to fully revert the system state without triggering the MSI uninstaller.

Alternative or Verification Steps

  • Verify the Fix: After using DISM or System Restore, reboot the machine and run Get-HotFix -Id KBXXXXXXX in PowerShell to confirm the specific KB is no longer listed in the installed updates.
  • Alternative Fix: If the update is critical for security compliance but causing an unrelated bug, do not attempt to force an uninstall; instead, wait for a “Fix Pack” from Microsoft or use the Windows Update Troubleshooter located in Settings > System > Troubleshoot > Other troubleshooters to reset update components.