Fixing ERROR_VDM_DISALLOWED (0x00000506) on 64-bit Windows

What's actually happening

You're seeing error 0x00000506 — %1 is a 16-bit application. This isn't a random glitch. Windows 10 and 11 on 64-bit hardware removed the NTVDM (NT Virtual DOS Machine) subsystem starting with version 2004. No NTVDM means no 16-bit code runs. Period.

The error triggers when you double-click an old .exe from the DOS or early Windows era — think Lotus 1-2-3, WordPerfect 5.1, or some ancient in-house accounting tool that HR still swears by. If your CPU is x64, there's no 16-bit emulation layer unless you specifically add it.

Real talk: NTVDM is gone by default on Windows 10 2004 and later, and it's not even available in Windows 11 ARM builds. Don't waste time looking for it there.

Cause #1: NTVDM feature is disabled (most common)

On Windows 10 (pre-2004) and some Windows 11 x64 builds, NTVDM is an optional Windows Feature that's turned off. Enabling it fixes the error instantly.

How to enable NTVDM

1. Press Win + R, type optionalfeatures, hit Enter.
2. Expand the Legacy Components folder.
3. Check the box for NTVDM (might show as "NT Virtual DOS Machine" or "16-bit Application Support").
4. Click OK and let Windows install the feature.
5. Reboot.

That's it. Try launching your 16-bit app again. If the error changes to something else (like a missing DLL), that's a separate problem — usually related to the app needing 16-bit drivers or hardware access.

If NTVDM isn't listed at all in Optional Features, you're on a build that removed it entirely. Skip to Cause #2.

Cause #2: Running 64-bit Windows without NTVDM support

Windows 10 version 2004 and later, plus all Windows 11 builds, dropped NTVDM from x64 installations. No checkbox to tick. Microsoft's official line is "use a virtual machine." They're not wrong.

Your options (listed by how well they work)

• Option A: DOSBox — Best for pure DOS apps. Free, lightweight, actively maintained. Download it from the official site, mount your app directory, and run the .exe inside DOSBox. 9 times out of 10 this works without any tweaking.
• Option B: Windows XP Mode + Virtual PC — If your 16-bit app needs Windows 3.1 or 9x compatibility, install Windows XP Mode (free from Microsoft, requires Virtual PC). XP Mode runs 16-bit apps natively because the XP guest is 32-bit. This is the most compatible solution for legacy Windows apps.
• Option C: Third-party emulators — vDos or vDosPlus are decent for DOS apps with specific hardware needs. They handle things like LPT ports and serial connections better than DOSBox.

Skip the idea of running a 32-bit copy of Windows 10 in a VM. That's overkill unless you have dozens of 16-bit apps to support. Stick with DOSBox or XP Mode.

Cause #3: Registry blocks (rare, but happens)

Sometimes a group policy or security setting explicitly disables NTVDM via registry. This doesn't matter if NTVDM isn't installed, but if you already enabled it and still get error 0x00000506, check these keys.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW
"DisallowedPolicy" = dword:00000000

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AppCompat
"VDMDisallowed" = dword:00000000

Set both to 0 (or delete them if they exist). Reboot. If the error persists, it's not a registry problem — go back to Cause #2.

Quick-reference summary table

I've seen this error on maybe fifty machines over the last decade. Nine out of ten times, enabling NTVDM was the fix. For the rest, DOSBox or XP Mode saved the day. Don't overthink it — pick the right tool for your app's era and move on.