Fix NS_E_WIZARD_RUNNING (0XC00D1584) — wizard stuck

That error pops up when a Windows wizard blocks itself — two instances of the same setup dialog can't run at once. Here's the real trigger and how to kill the stuck one.

When this error actually shows up

You're trying to install something — a printer driver, a Windows feature, maybe an old DirectX runtime — and you get this dialog box: "Another wizard is currently running. Please close the other wizard or wait until it finishes before continuing." The error code underneath is 0XC00D1584 (or NS_E_WIZARD_RUNNING in developer speak).

This happens most often when you've previously launched a setup or configuration wizard — like the Windows Features dialog, the Add Printer wizard, or even a third-party installer — and it didn't fully exit. You might not see any window on your screen, but the process is still sitting in the background holding a lock. Common triggers: you clicked through a wizard and closed it via the X button instead of Finish/Cancel, or you had a system restore or driver installation hang midway.

What's actually happening here

Windows uses a mutex (a system-wide lock) to prevent multiple instances of the same wizard from stomping on each other. That's smart — you don't want two installers fighting over registry keys or file locks. But the problem is that mutex doesn't always get cleaned up when a wizard crashes or gets killed improperly. The lock persists, and any new wizard that checks for that mutex sees it as still owned, even though the owning process is long dead. The error code 0XC00D1584 is the COM/Windows Shell equivalent of "resource busy, and not in a retry-friendly way."

Microsoft's designers assumed wizards would always exit gracefully. Real life doesn't work that way. Half the time the mutex is orphaned by a hung process that didn't release it. The OS doesn't automatically clean those up — you have to do it manually.

The fix: kill the stuck wizard process

Skip the reboot if you can. Rebooting works, but it's overkill. You can clear this in under 30 seconds.

Hit Ctrl + Shift + Esc to open Task Manager. (Or press Ctrl + Alt + Del and select Task Manager — but that's slower.)
Click the Processes tab. Look for anything named like wizard.exe, rundll32.exe (which hosts many wizards), mmc.exe (for MMC-based wizards like Device Manager), dccw.exe (Display Color Calibration), or any third-party installers still listed. Sort by Name to spot them faster.
Select the offending process and click End task. If you're not sure which one, look for processes using high CPU or memory that you don't recognize from normal operation. On Windows 10/11, you can also check the Details tab and sort by Description — any wizard will usually say something like "Windows Setup Wizard" or "Printer Installation Wizard."
Wait 2–3 seconds. Then try launching your original wizard again.

That's usually enough. The mutex is tied to the process — when the process dies, the OS releases the mutex automatically.

If Task Manager doesn't show it

Sometimes the wizard is running as a child process of a different parent — like svchost.exe hosting a COM object. You won't see it directly. In that case, open a Command Prompt as Administrator and run:

taskkill /f /im rundll32.exe

This kills all rundll32.exe instances, which usually clears orphaned wizard locks. But be warned: this also kills any other DLL-hosted tasks running at that moment (like some control panel applets). You'll lose unsaved work in those. Only do this if the first step didn't work and you're sure no other critical rundll32 tasks are open.

Another option: use Handle from Sysinternals to find the specific mutex name. Fire up handle.exe as admin, search for Wizard or Mutex, and note the PID. Then kill that PID with taskkill /pid <number> /f. But that's advanced — 90% of people won't need it.

Still failing? Check for hidden windows off-screen

One more thing: sometimes the wizard window is still alive but positioned off-screen (common with multi-monitor setups when a monitor gets disconnected). Press Alt + Tab repeatedly and see if a wizard window appears that you can bring to front and close normally. If you find one, close it with Finish or Cancel — don't just X out. That's the clean way.

If none of this works, a reboot is your nuclear option. It clears every orphaned mutex in the system. But honestly, in five years of doing this, I've only needed to reboot once — the Task Manager kill always worked.