PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Installer error 1646, ERROR_PATCH_REMOVAL_UNSUPPORTED, means the update package is not eligible for uninstallation in its current state. It does not, by itself, show that Windows Installer is damaged or that the computer is infected.
First identify the application product code and the patch code, then check policy, installer version, installation context, privileges and patch metadata. If the patch was authored as non-removable, no command switch can make it removable; the supported remedy is to uninstall and reinstall the application without that patch.
As an Amazon Associate I earn from qualifying purchases.
What “Error Patch Removal Unsupported” means
Microsoft defines Windows Installer error 1646 (hexadecimal 0x66E) as: “Uninstallation of the update package is not supported.” In practical terms, Windows Installer has determined that the particular .msp patch cannot be removed from the particular MSI product installation you selected.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →A patch is not automatically removable just because it appears in an installed-updates list or because its file is available. Removability is decided when the patch is authored and installed. Windows Installer checks the patch’s metadata, the product and patch identities, the installation context, policy settings and the account’s rights before accepting a removal request.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
That distinction matters. Reinstalling Windows Installer, deleting the patch file, or repeatedly retrying the same command will not change an intrinsically non-uninstallable patch. The objective is to determine whether the failure is an identity, policy or permission problem, or whether the patch was never designed to be removed.
Fast decision guide
| Check | What a positive result means | Next action |
|---|---|---|
| Product and patch codes match the same installation | The removal request is addressing the intended MSI product and update | Continue to the eligibility checks |
| Patch was installed with Windows Installer 3.0 or later and contains removal metadata | The patch may be removable | Check policy, context and privileges, then run the documented command |
DisablePatchUninstall is set to 1 |
Per-machine policy blocks patch removal | Have an authorized administrator review the policy before retrying |
| The application is per-user but the command is run in a per-machine context, or vice versa | The command is aimed at the wrong installation context | Use the account and context in which the product was installed |
| The patch is a major-upgrade or administrative-installation patch, or lacks required metadata | The patch may be inherently non-removable | Use the reinstall path rather than forcing removal |
Before you try to remove the patch
Have the two identifiers ready
You need the MSI product code for the application and the patch code for the update. Both are normally GUIDs in braces, such as {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}. If a management system supplied the update, retain the complete .msp path as well. The product code identifies the application; the patch code identifies the update package.
Do not substitute a product code from a different edition, language, architecture or installation. Microsoft lists an unknown patch for the selected product as a removal failure condition. A command can therefore be syntactically correct and still fail because the patch belongs to another product code.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsUse an account with the necessary authority
Patch removal can require rights appropriate to the installation context. A per-machine installation is administered for the computer, while a per-user installation belongs to a particular user profile. If the account does not have rights in that context, Windows Installer can reject the request even when the patch itself is removable.
Open the command shell with the level of authority your organization permits. Do not bypass company policy or use another user’s credentials without authorization. If the application is managed by an enterprise deployment system, coordinate the change with its administrator so the patch is not immediately reapplied.
Preserve a recovery option
Removing a patch can alter the product’s patch sequence. Microsoft notes that obsolete or superseded patches can become active again after another patch is removed. Record the current product version and installed patch list, and make sure you have the application’s original installer and any other patches you intend to keep before proceeding.
Check whether the patch is eligible for removal
Installer version
Microsoft states that patches applied with Windows Installer versions earlier than 3.0 are not uninstallable. Windows Installer 3.0 introduced support for uninstallable patches. If the patch was installed by an earlier installer, an individual removal command cannot make it removable.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →This is an authoring and installation limitation, not evidence that the MSI engine is broken. If you cannot establish which installer version applied the patch, treat the version as an open eligibility question and continue with the policy, context and metadata checks.
Removal metadata
A removable patch must contain the metadata Windows Installer expects, including the MsiPatchMetadata information with AllowRemoval=1 where applicable. If the patch lacks that metadata or its database changes are incompatible with reversal, Windows Installer will return error 1646 regardless of the command syntax.
Rank #2
- Emergency Boot USB compatible with Windows 98, 2000, XP, Vista, 7, and 10. It has never ben so easy to repair a hard drive or recover lost files
- Plug and Play type usb - Just boot up the usb and then follow the onscreen instructions for ease of use
- Boots up any PC or Laptop model and brand.
- Virus and Malware Removal made easy for you
- This is your one stop shop for PC Repair of any need!
Metadata is part of the patch package’s design. Editing an .msp file, adding a registry value or changing a command-line switch does not convert a non-removable patch into a supported removable one.
Machine policy
A per-machine policy can prohibit every patch removal attempt. Inspect the following registry location only if you are authorized to review Windows Installer policy:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsInstallerLook for the DisablePatchUninstall value. Microsoft documents that a value of 1 prevents users and administrators from removing patches. A policy-controlled computer may receive this setting from domain management, so changing it locally can be unauthorized or temporary. If the value is present and set to 1, ask the policy owner whether removal is permitted instead of deleting the value yourself.
Installation context and privileges
Confirm whether the product was installed per-machine or per-user and run the operation in that same context. Also confirm that the account can modify the application installation. A mismatch can look like a missing or unknown patch even when the patch is correctly installed elsewhere on the computer.
Patch types and database changes
Some patch designs are not removable. Microsoft identifies major-upgrade patches, patches applied from an administrative installation and patches containing certain database-table changes among the cases that can block removal. These are properties of the package and its installation path, not conditions that can be repaired with a general Windows command.
Run the documented removal command
Use the product code and patch code in the correct positions
For an eligible patch, Microsoft documents this msiexec form:
msiexec /package {PRODUCT-CODE} /uninstall {PATCH-CODE} /passiveIn this syntax, replace {PRODUCT-CODE} with the MSI product’s GUID and {PATCH-CODE} with the update’s GUID. Do not reverse them. The /passive option runs with limited user interaction; it does not override policy, missing metadata or insufficient privileges.
Enter the command in an elevated Command Prompt or another approved administrative shell, keeping the braces and hyphens in each GUID. If the command reports that the patch is unknown, stop and verify that the patch was applied to this exact product code before trying again.
Use the MSIPATCHREMOVE property when appropriate
Microsoft also documents removal through an installation command using the MSIPATCHREMOVE property:
Rank #3
- Fresh USB Install With Key code Included
- 24/7 Tech Support from expert Technician
- Top product with Great Reviews
msiexec /I {PRODUCT-CODE} MSIPATCHREMOVE={PATCH-CODE} /qbHere, /I references the product to service, while MSIPATCHREMOVE names the patch to remove. The /qb user-interface level displays a basic progress interface. This alternate form still requires a removable patch, the correct identifiers and adequate authority; it is not a workaround for error 1646 caused by patch authoring or policy.
What a successful operation should do
If the patch is eligible and the identifiers and context are correct, Windows Installer services the product and removes that update. Verify the resulting product and patch state using the same management method that showed the patch originally. Review which superseded or obsolete patches are now active, because patch sequencing can change after removal.
What to do when the command still fails
The patch is unknown for the product
An unknown-patch result means Windows Installer cannot associate the supplied patch code with the product code in the command. Recheck every character, including braces and hyphens, and confirm that the update belongs to this exact application installation. Do not try a code copied from another computer or another product edition.
DisablePatchUninstall blocks the request
If the policy value is 1, removal is blocked for users and administrators under that per-machine policy. Contact the administrator who controls the policy. Once the policy decision is resolved, rerun the eligibility checks; do not assume that policy removal proves the patch itself is uninstallable.
The account or context is wrong
When the application is per-user, use the affected user’s installation context. When it is per-machine, use an account authorized to service the computer-wide installation. If a deployment service installed the product, its service account and management rules may be part of the expected context.
The patch is intrinsically non-removable
If the patch was applied by Windows Installer before version 3.0, lacks the required removal metadata, is a major-upgrade or administrative-installation patch, or contains incompatible database changes, no msiexec switch can make individual removal supported. Proceed to the reinstall method below.
Another patch becomes active
Patch removal can reactivate an update that had been marked obsolete or superseded. This is not necessarily a new error. Compare the post-removal patch sequence with the security and compatibility requirements for the application, then apply any other patches you intentionally need to retain.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Supported fallback: uninstall and reinstall the application
Microsoft’s explicit fallback for an intrinsically non-uninstallable patch is to remove the patched application and reinstall it without the unwanted patch. This is a product-level operation, so plan for application downtime and preserve application data according to the software vendor’s procedures.
- Confirm the application name, edition, product code and the patch you are trying to exclude.
- Obtain the original application installer or an approved installation source that does not automatically include the unwanted patch.
- Back up application data and record configuration, licenses and any patches you intend to reapply.
- Uninstall the application through the organization’s approved method. If the application is managed centrally, use that deployment system rather than mixing local and managed uninstall operations.
- Reinstall the application from the clean source without the non-removable patch.
- Apply the other patches you have decided to keep, in the sequence required by the application and its deployment process.
- Verify that the application launches and that required files, settings and integrations still work before returning the computer to normal use.
This process removes the patched product state rather than attempting to reverse an unsupported patch database change. It is more disruptive than a single-patch command, but it is the supported route when the package was never authored for removal.
Free tools Windows power users keep installed
One-click scans. No signup required.
Common mistakes to avoid
- Swapping the GUIDs: In the
/package ... /uninstall ...form, the package value is the product code and the uninstall value is the patch code. - Deleting the
.mspfile: The cached or original patch file is not the installed patch state. Deleting it does not uninstall the update and can make future servicing harder. - Editing the registry to fake removal: Removing product or patch registration entries can leave Windows Installer’s database inconsistent and is not a supported conversion of a non-removable patch.
- Changing policy without authorization: A domain or device-management policy may be intentional. Obtain approval before changing
DisablePatchUninstall. - Assuming every listed update is removable: Visibility in an installed-update list does not establish that the package contains the metadata and database structure required for uninstallation.
- Repeating the same command: If the blocker is patch authoring, installer version, policy or context, retries produce the same eligibility result.
Choosing the right remediation path
| Situation | Best-supported path | Operational cost |
|---|---|---|
| Correct product and patch codes; patch is eligible; no policy block | Run the documented msiexec removal command |
Single patch servicing operation |
| Patch code does not belong to the selected product | Identify the exact product installation and correct the identifiers | Diagnostic work only; do not remove anything yet |
DisablePatchUninstall=1 |
Obtain an authorized policy decision | Depends on organizational change control |
| Wrong account or per-user/per-machine mismatch | Use the installation’s correct context and authorized account | Usually less work than reinstalling |
| Old installer, missing metadata, major-upgrade, administrative-installation or incompatible database changes | Uninstall and reinstall the application without the patch, then reapply desired updates | Application downtime, backup and reconfiguration required |
The four questions that determine the path are eligibility, identity, authority and operational cost. If eligibility is “no,” focus on reinstalling. If eligibility is “possibly,” validate the identifiers, policy and context before running the command.
Quick Recap
As an optional shortcut for diagnosing broader Windows issues around a failed application or damaged system elements, Outbyte PC Repair can check more than 100 common Windows issues, clean temporary and cache files, review vulnerability settings and keep an app-crash log. It runs on Windows 11, 10, 8 and 7 and offers a free trial by category of at least two days before a paid subscription; results vary, it does not make a fundamentally non-removable MSI patch removable, and it complements rather than replaces antivirus software.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
