Windows command guide
How to Re-register Windows Installer with msiexec
Many Windows applications still use MSI-based setup and repair routines. If Windows Installer registration is damaged, setup packages may refuse to open, repair operations can fail, and uninstall routines may break even when the software itself is fine. Re-registering the service is a focused fix for that installation layer.
This guide is written around the specific symptom-command match for re-register windows installer, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
msiexec /unregister && msiexec /regserver
Best place to run it
Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.
Fast repair workflow
- Start from the exact symptom on this page: MSI packages do not launch correctly
- Run the service or app repair line exactly as shown: msiexec /unregister && msiexec /regserver.
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Re-open the affected app, service, or feature and check whether the same component still fails.
- If the issue persists, check service state, dependencies, package integrity, or event logs before doing a broader repair.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
@echo off
echo Run this CMD sequence in an elevated Command Prompt.
echo Starting targeted repair sequence...
msiexec /unregister && msiexec /regserver
echo.
echo Review the output before closing this window.
pause
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
sc query type= service state= all | findstr /I RUNNING
What problem this command is trying to solve
This command targets broken registration of the Windows Installer service.
- MSI packages do not launch correctly.
- Repair or uninstall jobs fail with installer-related errors.
- Windows behaves as if msiexec is not registered properly.
How the command works
The first command removes the current Windows Installer registration. The second registers the service again, rebuilding the system link that MSI packages rely on.
When it makes sense to run it
Use it when MSI-based installations or removals are failing repeatedly and the symptoms point to installer infrastructure rather than one bad app package.
Before you run this command
- Open an elevated Command Prompt or PowerShell window before running msiexec /unregister && msiexec /regserver.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: msi packages do not launch correctly.
- Identify the exact Windows component that is failing before you use msiexec /unregister && msiexec /regserver, so you do not reset unrelated parts of the system.
What result to expect
After running msiexec /unregister && msiexec /regserver, compare the result against the symptom that brought you here. The most useful checkpoint is whether msi packages do not launch correctly becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after msiexec /unregister && msiexec /regserver is to repeat the action that previously triggered the problem. If repair or uninstall jobs fail with installer-related errors still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Why administrator rights matter here
This command changes a Windows service, package, or built-in app component. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.
Before you run it
Run Command Prompt as administrator. This command affects the installer service, so it is best used when you are troubleshooting real MSI problems.
When this is probably the wrong fix
This is not the right first fix for every generic crash. Use it when the failing part is a Windows service, built-in app package, indexing component, print queue, audio stack, or similar subsystem.
What to do if it does not help
If msiexec /unregister && msiexec /regserver does not improve msi packages do not launch correctly, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about a Windows service, package, or built-in app component.
Frequently asked questions
Should I use msiexec /unregister && msiexec /regserver for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: This command targets broken registration of the Windows Installer service.
What should I check right after msiexec /unregister && msiexec /regserver?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether msi packages do not launch correctly becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on msiexec /unregister && msiexec /regserver alone?
This is not the right first fix for every generic crash. Use it when the failing part is a Windows service, built-in app package, indexing component, print queue, audio stack, or similar subsystem.