How to fix "Unsupported 16-bit application" error in Windows?

The Unsupported 16-Bit Application message means Windows could not read the .exe file as a 32-bit or 64-bit program. On a new program such as opencode or a game launcher the file is almost always broken, empty or a placeholder, and a clean reinstall fixes it. On a real 1990s program it is final: 64-bit Windows, and so every Windows 11 PC, cannot run 16-bit code.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What the Unsupported 16-Bit Application error means in Windows 11 and 10

The dialog is titled Unsupported 16-Bit Application and names the full path of the file Windows tried to start. The text reads like this, here with the path from an opencode install:

The message as Windows shows it

Unsupported 16-Bit Application

The program or feature "...\opencode.exe" cannot start or run due to incompatibility with 64-bit versions of Windows.
Please contact the software vendor to ask if a 64-bit Windows compatible version is available.

16-bit programs were written for MS-DOS and Windows 3.1, before Windows 95. Microsoft states that x64-based versions of Windows do not support 16-bit programs, 16-bit processes or 16-bit components. Windows 11 exists only in 64-bit editions, so on Windows 11 this is never something you can switch on.

Why Windows says unsupported 16-bit application on Windows 11

Most often the .exe is broken: a placeholder that an installer never replaced, or a download that stopped early. Less often the program really is 16-bit, or a 32-bit program uses a 16-bit setup. Rarely the file is something you did not install at all.

Users on Minecraft help forums report the same message from the Minecraft Launcher. Mojang has not published an explanation that we could find, so treat the launcher case like any other new program: its file is not 16-bit, it is broken.

How to fix the Unsupported 16-Bit Application error

Fixes 1 to 3 repair a new program whose file is broken, and they solve most cases. Fixes 4 to 6 are for real old software. Fixes 7 and 8 check the rare case of a strange file or damaged Windows files.

Fix 1. Check the size of the .exe and download the program again

5 minutesNo riskEveryone with a program made in the last 15 years, before anything else.

Windows says 16-bit when it cannot read the file's header. A file of 0 bytes, a few hundred bytes or far below the normal size has no valid header, so the fix is a complete copy of the file, not a Windows setting.

1. Read the path in the error message and open that folder in File Explorer.
2. Right-click the .exe and select Properties.
3. On the General tab, read Size. Write it down.
4. Compare it with the size the maker gives on its download page, or with the same file on another PC.
5. If the file is tiny or 0 bytes, delete it and download the installer again from the maker's own site.
6. Run the new installer and start the program again.

In PowerShell you can read the size directly. The command below is the one an opencode user used to find the broken file; change the path to yours.

Get-Item "$env:APPDATA\npm\node_modules\opencode-ai\bin\opencode.exe" | Select Name,Length

Fix 2. Reinstall opencode with npm scripts allowed

5 minutesNo riskYou installed or updated opencode with npm install -g opencode-ai on Windows.

The opencode npm package ships a 479-byte placeholder opencode.exe. Its postinstall script replaces it with the real Windows binary of about 184 MB. Newer npm versions can block that script, and the placeholder then triggers the 16-bit dialog.

1. Open Terminal or PowerShell.
2. Run npm config get ignore-scripts. If it prints true, run npm config set ignore-scripts false.
3. Install again with scripts allowed for this one package, using the command below.
4. Run opencode --version. A version number means the real binary is in place.

Reinstall with the postinstall script allowed

npm install -g --allow-scripts=opencode-ai opencode-ai

Without a reinstall, you can run the package's own script once. It swaps the placeholder for the real file that npm already downloaded into node_modules\opencode-windows-x64:

Run the skipped postinstall step by hand

node "$env:APPDATA\npm\node_modules\opencode-ai\postinstall.mjs"

Fix 3. Uninstall the launcher or app and install a fresh copy

15 minutesLow riskMinecraft Launcher, another game launcher or an app that worked before shows the error.

A launcher updates its own files. When an update stops halfway, the main .exe can stay damaged, and repeated starts do not repair it. Removing the program and installing the current version from its maker replaces every file.

1. Select Start > Settings > Apps > Installed apps.
2. Find the program, select the three dots next to it and select Uninstall.
3. Restart the PC.
4. Download the installer again from the maker's own site or from the Microsoft Store. For Minecraft that is minecraft.net.
5. Install it and sign in again if the program asks.

Both ways, on Windows 11 and Windows 10: Uninstall a program or app in Windows Your game worlds and settings are usually stored outside the program folder, but check the maker's help before you delete any folder by hand.

Fix 4. Install Microsoft's 16-bit InstallShield support package for old setups

10 minutesLow riskAn old CD or download installs a 32-bit program, but its setup.exe stops with this error.

Many late 1990s programs are 32-bit, but their setup starts from a 16-bit InstallShield stub. Microsoft says 64-bit Windows can convert some of these installers to 32-bit, and publishes a support package for the 16-bit InstallShield case.

1. Open Microsoft's article 896458 on Microsoft Learn.
2. Under Use 16-bit InstallShield installers to install 32-bit applications, select the 16-bit InstallShield Support package link.
3. Run the downloaded 16BitInstallShieldSupport.msi and finish the setup.
4. Start the old program's setup.exe again.

Fix 5. Get a 32-bit or 64-bit version of the program

15 minutesNo riskThe program really is from the MS-DOS or Windows 3.1 era, and you need it on this PC.

The message itself asks you to contact the software vendor for a 64-bit compatible version. Microsoft also advises upgrading critical programs to 64-bit versions. A current version removes the problem for good on Windows 11.

1. Note the program's name and version from its box, disk label or the folder name.
2. Search the maker's site for a current version, an upgrade or a Windows 10 or 11 edition.
3. If the maker is gone, look for a program that opens the same file types, and test it on a copy of your data.
4. Keep the original disks and your data files until the new program reads them correctly.

Fix 6. Run the old program in a 32-bit Windows

1 hour or moreLow riskA real 16-bit program has no replacement and you must keep using it.

Microsoft's only supported way to run 16-bit code is to install the program on a 32-bit Windows. In 32-bit Windows 10 the 16-bit support is the NTVDM feature under Legacy Components. It does not exist in 64-bit Windows or in Windows 11.

1. Choose where the 32-bit Windows will run. Microsoft describes a dual boot on a separate disk volume or a separate hard disk; a virtual machine keeps it apart from your main Windows.
2. Install a 32-bit Windows 10 there with a licence you own.
3. Press Win + R, type optionalfeatures.exe and select OK.
4. Expand Legacy Components, select NTVDM and select OK.
5. Install the old program inside that Windows and start it.

Fix 7. Scan the file with Microsoft Defender

10 minutesNo riskThe path points to a file you never installed, or to C:\Windows or System32.

A normal program never needs to start an unknown .exe from the Windows folder. A strange file there, or a download that security software removes or cuts off, can produce this dialog, and a scan tells you which it is.

1. Open Windows Security from Start.
2. Select Virus & threat protection, then Quick scan.
3. If nothing is found, open Scan options, select Custom scan and scan the folder from the error message.
4. Open Protection history and check whether the program's file was quarantined.

Full steps for every scan type: How to scan for malware with Microsoft Defender

Fix 8. Repair Windows system files

20 minutesNo riskA Windows tool, not a program you installed, shows the 16-bit dialog.

This is the rare case where the broken .exe belongs to Windows itself. SFC and DISM replace damaged Windows files with good copies. They cannot add 16-bit support to 64-bit Windows, so skip this fix for an old program.

1. Open a command window as administrator.
2. Run sfc /scannow and wait until it reaches 100 %.
3. If it reports files it could not repair, run the DISM command from the procedure below, then SFC again.
4. Restart the PC.

Full procedure: Run DISM and SFC to repair Windows system files

Unsupported 16-Bit Application still there: what to check and send

Windows does not write a detailed reason for this dialog, so the evidence comes from the file and from the installer that put it there.

• npm programs: npm keeps a log of every install in %LOCALAPPDATA%\npm-cache\_logs. Open the newest debug-0.log and search for install-scripts. A line saying scripts were blocked is the cause of Fix 2.
• The file itself: the exact path from the dialog, the size from Properties and the size the maker says it should have.
• Your Windows: Settings > System > About shows the edition and System type. 64-bit can never run 16-bit code.
• Not a hardware fault: this message comes from how Windows reads a file. It is not a sign of a failing disk or memory, unless many unrelated files are damaged at once.

Avoid the 16-bit error the next time you install a program

Compatibility mode still has its use for programs that are 32-bit but expect an older Windows: How to run a program as administrator or in compatibility mode

Frequently asked questions

Can Windows 11 run 16-bit applications?

No. Windows 11 is only made in 64-bit editions, and Microsoft states that x64 versions of Windows do not support 16-bit programs, processes or components. No setting, update or feature adds it. A program that is truly 16-bit runs only in a 32-bit Windows, for example in a virtual machine, as Fix 6 describes. Most new programs that show this message on Windows 11 are not 16-bit at all: their .exe is broken, and a reinstall fixes it.

How do I fix unsupported 16 bit application in Windows 10?

First check which Windows 10 you have under Settings > System > About > System type. On 64-bit Windows 10 the steps are the same as on Windows 11: check the file size (Fix 1), reinstall the program (Fix 3) or, for a real old program, find a newer version. On 32-bit Windows 10 you can turn on NTVDM under Legacy Components to run 16-bit programs. Windows 10 lost support on 14 October 2025, so do this only on an offline PC.

Why does Minecraft say unsupported 16 bit application?

Minecraft and its launcher are not 16-bit programs, so the message points to a damaged launcher file. Users on Minecraft help forums report it after an interrupted download or update. Check the size of the launcher .exe named in the dialog (Fix 1), then uninstall the launcher, restart and install a fresh copy from minecraft.net or the Microsoft Store (Fix 3). Your worlds are usually kept outside the launcher's program folder, but back them up before deleting folders.

Why does opencode show unsupported 16 bit application?

The opencode npm package installs a 479-byte placeholder opencode.exe and replaces it in a postinstall script. When npm blocks that script, the placeholder stays, and Windows reads it as 16-bit code. Reinstall with npm install -g --allow-scripts=opencode-ai opencode-ai, or run the package's postinstall.mjs with node, as in Fix 2. Users report the same after opencode updates itself.

Is the Claude Code unsupported 16 bit application error the same problem?

We found no published report for Claude Code that we could check, so we cannot confirm its cause. The same test applies to any command-line tool: find the .exe in the dialog, read its size in Properties and compare it with a normal install. A tiny or empty file means the install did not finish. Reinstall the tool with its official command and read the warnings the installer prints.

What does "This 16-bit installer cannot be run by Windows" mean?

It is a related message from an old setup program. Many 32-bit programs from the late 1990s start their installation with a 16-bit InstallShield stub. Microsoft publishes a 16-bit InstallShield Support package for this case in its article 896458, as Fix 4 describes. If the program itself is 16-bit too, the support package will not help and you need a newer version or a 32-bit Windows.

Does compatibility mode fix the 16-bit error?

Not for real 16-bit programs. Compatibility mode changes how Windows presents itself to a 32-bit or 64-bit program; it cannot run code that 64-bit Windows does not support. Its oldest option is Windows 95, which is itself 32-bit. For a new program with a broken .exe, compatibility mode does nothing either, because the file still cannot be read. Use it only for 32-bit programs that expect an older Windows.

Can I enable NTVDM in Windows 11?

No. NTVDM, the NT Virtual DOS Machine that ran 16-bit programs, ships only with 32-bit Windows. Windows 11 has no 32-bit edition, so Legacy Components in Windows Features does not list it, and commands that try to enable it fail. Old guides that tell you to tick NTVDM were written for 32-bit Windows 10. On Windows 11 the options are a newer program or a 32-bit Windows in a virtual machine.

Is the Unsupported 16-Bit Application message a virus?

The message itself is a normal Windows dialog. It can point to a problem only when the path names a file you never installed, especially in C:\Windows or System32, or when it appears at every sign-in. Then scan that folder with Microsoft Defender (Fix 7). When it names a program you just installed, such as a game launcher or a developer tool, the cause is a broken file, not malware.

Does this page cover the error in other languages?

Yes. Windows shows the same dialog in your display language, for example "aplicación de 16 bits no compatible" in Spanish or "desteklenmeyen 16 bit uygulama" in Turkish. The cause and the fixes do not change with the language. Read the path in the dialog, check the file size and follow the chooser table above to find your fix.