Fix STATUS_INVALID_IMAGE_WIN_64 (0xC000035A) on Windows

Quick answer: Reinstall or update the app. If it's a system file, run sfc /scannow and DISM /online /cleanup-image /restorehealth in an admin command prompt.

I'm Derek, IT consultant. I've seen this error pop up on maybe a dozen machines over the last two years. Last month a client tried to open an old accounting program from 2010. Windows threw this error: STATUS_INVALID_IMAGE_WIN_64 (0xC000035A). The file was a 32-bit .exe but the system expected 64-bit. Or sometimes it's the opposite – a 64-bit file on a 32-bit OS, but that's rare now. The real cause? The image header says one thing, the OS expects another. Happens when a download gets corrupted, a program installs wrong, or a DLL gets mixed up.

Why you see this error

Windows checks the IMAGE_FILE_HEADER of an executable. It looks at the machine type: 0x8664 for x64, 0x14C for x86. If the file says 32-bit but the system is 64-bit Windows (which is most PCs now), you get 0xC000035A. Common triggers:

Old 16-bit or 32-bit software that hasn't been updated.
Corrupted downloads – I once had a client whose installer got cut off halfway.
Malware infection – some malware replaces legit .exe files with stub files that have wrong headers.
Windows update glitch – a .NET update or Visual C++ redistributable that didn't install right.

Step-by-step fix

Check the file's architecture – Open File Explorer, right-click the .exe or DLL, select Properties, go to Details tab. Look at 'File version' info – but that's not always reliable. Better: use a tool like dumpbin (part of Visual Studio Build Tools) or a free utility like PE Bear. In a command prompt:
```
dumpbin /headers "C:\path\to\file.exe" | findstr machine
```
This will show 'x86' or 'x64'. If it's x86 but your Windows is 64-bit, the file is the wrong format.
Reinstall the software – Uninstall it properly via Control Panel > Programs and Features. Download a fresh installer from the official source. Don't use old backups or shady download sites.
Run System File Checker – Open an admin command prompt (right-click Start, choose 'Command Prompt (Admin)' or 'Windows Terminal (Admin)'). Type:
```
sfc /scannow
```
Let it run. It'll replace corrupted system files if it finds any. Reboot after.
Use DISM – If SFC finds issues it can't fix, run:
```
DISM /online /cleanup-image /restorehealth
```
This repairs the component store. Takes 10-20 minutes. Then run SFC again.
Check for malware – Run a full scan with Windows Defender or a third-party tool like Malwarebytes. Malware can mess with file headers.

What if the main fix doesn't work?

For a specific app: Look for a 64-bit version of that software. Many old programs have modern 64-bit alternatives. My accounting client switched to a newer version.
If it's a system DLL (like something in C:\Windows\System32): That's serious. You might need a repair install of Windows. Use the 'Reset this PC' option but keep your files.
Check Windows version – Open Settings > System > About. Look at 'System type'. If it says '32-bit operating system', you can't run 64-bit files. That's a different error code. But if it's 64-bit, you're good.

Prevention tip

Never download software from unofficial sites. Use only the official publisher's download link. If you're managing multiple machines, keep a log of what apps are installed and their architecture. For old software, run it in a virtual machine with a 32-bit OS – I've set up Windows 10 32-bit in VirtualBox for a few clients. That avoids the headache completely.

If this fix still doesn't work, check the Windows Event Log (Event Viewer > Windows Logs > Application). Look for errors with ID 1000 or 1001 that mention 'STATUS_INVALID_IMAGE_WIN_64'. That often points to a specific file. Replace that file from a known-good backup or reinstall the app.

I had a client last month whose entire print queue died because of this – the printer driver installer was corrupted. Replaced it with a fresh download, error gone.