Double-click an installer, or hit launch on a game. What shows up isn't the app. It's a little box with error code 0x800700C1 in it.
Other times the wording changes to “%1 is not a valid Win32 application” and the hex code never appears at all.
Windows is saying something simple here. The file it tried to run isn't a working program file.
Usually that traces back to a download that cut off partway. Sometimes it's the wrong build for your machine, 32-bit when you needed 64-bit. And sometimes the system files underneath are damaged.
The code turns up in a few places on Windows 11 and Windows 10: opening a program, installing a Microsoft Store app, running Windows Update. Start with the first fix below and work down.
So Why Does 0x800700C1 Show Up?
0x800700C1 is just the HRESULT for ERROR_BAD_EXE_FORMAT. Most people never see that name. They get “%1 is not a valid Win32 application” instead. DISM calls the same problem error 193.
Translated: Windows read the file, didn't recognize it as a program it could run, and stopped.

The chain of events is short. Windows opens the .exe or .dll, reads the header, and checks which processor the thing was compiled for.
Truncated file? Built for a different chip? Never an executable at all? Loading dies right there, and the code pops up.
The most common causes include:
- An .exe or .msi download that cut out partway through, or never really finished
- Wrong architecture, such as a 64-bit program on 32-bit Windows, or an x86 build on an ARM device
- A file that isn't actually an executable, often a renamed or half-saved download
- An app installation that was damaged or never finished
- Damaged Windows system files, or a corrupted component store
- Antivirus quarantining one piece of an app and leaving the rest sitting there
- Malware that modified program files
- A Windows update that went bad or got interrupted
- Gaming Services missing or out of date, which mostly bites Xbox and Game Pass titles
Do one quick test before you touch anything. Open Notepad. Then open the Settings app.
If both of those open fine and only one program throws 0x800700C1, that tells you something. That app's files are the problem. But if a few unrelated programs choke, or Windows Update and DISM are also erroring out, the system files are where to look.
And no, reinstalling doesn't always fix it. An architecture mismatch shrugs off a reinstall. So does a damaged component store, and so does antivirus that re-quarantines the file about ten seconds after it lands back on disk.
One more warning. Whatever you do, don't go grabbing a replacement DLL off some random download site. Those files are a well-worn malware route.
How to Fix Error Code 0x800700C1
Go in order. Test the app after every single step. Change three things at once and you won't know which one did the job.
Only seeing this code inside Windows Update or DISM? Skip ahead to fixes 7 and 8. Nothing before those will matter.
1. Restart the PC, Then Try the Program Again
Not filler. A pending update or a locked file can make an executable unreadable. And it stays that way until the session ends. Meanwhile the loader keeps reaching for that same broken copy. Every double-click. Every time.
Pick Restart. Shut down isn't the same thing (fast startup keeps part of the old session alive on most Windows 11 and Windows 10 machines).
Clean restart and the error came back? Then it's the file or Windows itself. Keep reading.
2. Download the File Again, and Check It Matches Your System
A download that died partway through gives you no warning. It stalls at 80%, the connection drops, and what's left in your Downloads folder still looks fine. Normal .exe name, right icon, the lot. But Windows doesn't catch on until it tries to read the header. That's when it quits.
Throw that file out before round two. Browsers are perfectly happy to resume into the same damaged copy, so you spend a second attempt on bytes that were already garbage.
Architecture is the other half of this. A 64-bit build won't launch on 32-bit Windows at all, and ARM laptops refuse some older x86 installers outright, which is probably the most common road to this particular code.
So figure out what your system actually is, then grab the file that matches:
- Open Settings > System > About and read the System type line.
- Go back to the vendor's own download page. Not a mirror, not a software aggregator.
- Download the build that matches whatever About said. It says 64-bit, 32-bit, or ARM64. One of those three.
- Download again on a connection that holds. Wired beats Wi-Fi for this. Can't plug in? Move closer to the router.
- Then compare the finished file size to whatever the site lists.
- Confirm the extension reads .exe or .msi, not .zip, .partial, or .crdownload.
Fresh file, right architecture, and 0x800700C1 still showing up? That rules out the download. Which means something on the PC itself is blocking the install.
For Developers: 0x800700C1 in IIS or .NET
Downloads have nothing to do with this one. The same code pops up when a 32-bit assembly gets loaded into a 64-bit application pool. In IIS Manager > Application Pools, select the pool, open Advanced Settings, and set Enable 32-Bit Applications to True.
Save it, recycle the pool, then fire the request one more time. Worker processes already running won't pick up the change on their own.
3. Run the App as Administrator and Try Compatibility Mode
This one fixes it more often than you'd think. An installer that can't write to a protected folder will sometimes throw a format error and never mention permissions once. And older programs often expect an environment current Windows doesn't hand out anymore.
Try the elevated launch first. But if nothing changes, compatibility settings are next.
- Right-click the file, pick Run as administrator, then approve the prompt.
- Still failing? Right-click the file again and go to Properties.
- Open the Compatibility tab.
- Tick Run this program in compatibility mode for and pick an earlier Windows version.
- Tick Run this program as an administrator too.
- Click Apply, then OK, and launch the program again.
Compatibility mode is good at rescuing old desktop software. It almost never helps with a Microsoft Store app, though. So skip this whole step if the error came from the Store or the Xbox app.
4. Repair First, Then Reset, Then Reinstall
There's a repair ladder buried in the app settings, and most people skip right past it to uninstall. Repair keeps your app data and sign-ins intact. Reset throws out settings and local data, so try them in that order.

Go through these in order:
- Open Settings > Apps > Installed apps.
- Find the app and click the three dots next to it.
- Choose Advanced options.
- Click Repair and wait for the tick mark to appear.
- Then launch the app and see what happens.
- If the error returns, go back to that same screen and click Reset.
Some apps show neither button. Annoying, but pretty normal with older desktop installers. In that case, uninstall it, restart the PC, then install a fresh copy from the file you downloaded back in fix 2.
Don't skip that restart in the middle. Windows hangs onto locked files from the old install, and a fresh setup will happily reuse them. That's how you end up with the exact same broken app twice.
5. Fix Xbox, Game Pass and Microsoft Store Apps
A Game Pass game never runs on its own. It leans on the Xbox app, the Microsoft Store, and a background piece called Gaming Services, all at once.
So when 0x800700C1 lands on a Game Pass title, the game files are rarely the thing at fault. Usually it's the launcher or one of those services underneath. Same story with most Microsoft Store error codes.
Update the Microsoft Store, Xbox App and Gaming Services
Stale components cause this more often than you'd think, and a Windows feature update is a common trigger. Run through the update pass below:
- Launch the Microsoft Store app from Start.
- Over on the left sidebar, pick Library.
- Click Get updates and let every pending item finish.
- Keep an eye out for Gaming Services and the Xbox app in that list. Both get patched this way.
- Restart the PC after the updates land, then start the game again.
Sometimes Gaming Services won't update at all, or it just doesn't appear. Then it has to be pulled off and put back, and the guide on how to reinstall Gaming Services covers that with PowerShell.
Run Verify and Repair on the Installed Game
Head into the Xbox app, pull up the game's manage or options menu, and look for Verify and repair in there. What it does is scan the files already on disk and swap out whatever came up bad, which beats pulling the whole game down again.
Not every game offers it. That comes down to how the title was packaged, so the button is just missing on some. Not there? Uninstall the game from the Xbox app. Reboot. Install it again from scratch.
6. Check the Antivirus Quarantine, Then Run a Malware Scan
Antivirus will sometimes quarantine one lone DLL (or some tiny helper executable) and leave everything else in the folder alone. The app then loads a file that isn't whole anymore, and Windows throws the bad format error. This one fixes it more often than you'd think.

Start in Windows Security. Head to Virus & threat protection and click Protection history, then scroll the recent entries for anything with the broken program's name or install path on it.
Found one you recognize as a legitimate file from a vendor you trust? Hit Restore, then add an exclusion for that folder so the scanner doesn't grab it again next week.
Now, the opposite problem is just as real. Malware that rewrites program files causes the same error, so kick off a Full scan with Microsoft Defender (an offline scan is the better call if the machine has been acting weird in other ways).
Running something other than Defender? Those products keep their own quarantine list, usually buried under Protection or Threat History somewhere.
7. Install Pending Windows Updates, Then Run the Troubleshooter
When 0x800700C1 comes from Windows Update itself, it's one of two things. Either the update payload downloaded wrong, or the component store can't apply what it got. Point is, the file Windows wants to open isn't a valid image anymore.
So run the check again. A second pass often grabs a clean copy, and the built-in troubleshooter resets the update services while it runs, which is where most Windows Update errors start anyway.
Here's the order to work through:
- Open Settings > Windows Update and hit Check for updates.
- Install whatever shows up, including optional quality updates if they appear.
- If one update keeps failing, head to Settings > System > Troubleshoot > Other troubleshooters.
- Scroll to Windows Update and click Run.
- Let it run its course, restart the PC, and check for updates again.
A clean round of updates sorts this out for a fair number of people. Especially if the error turned up right after an install died halfway.
But if that same update fails again with the same code, the component store underneath is damaged. That needs actual repair work. That's fix 8.
8. Run DISM and Then SFC to Repair System Files
Reach for this one when several unrelated programs are falling over at once, or when Windows Update refuses to install anything. It is slower than the other fixes here, but it catches damage the quick stuff can't touch.
DISM repairs the component store, which is the pile of files Windows rebuilds its system files from. So running DISM and SFC to repair Windows system files in that order is the whole trick, because SFC pulls from that store and a broken store gives it nothing good to copy.
Run these in order. Don't skip ahead. On an older drive, budget 20 minutes or more:
- Right-click Start, then pick Terminal (Admin) or Windows PowerShell (Admin) from the menu that pops up.
- Type
DISM /Online /Cleanup-Image /RestoreHealthand press Enter. - Wait. The percentage will park itself at 20% or 62.3% for minutes without moving. That's normal. Annoying, yes. Still normal. But leave the window alone.
- When it says the operation completed, type
sfc /scannowand hit Enter. - Let verification hit 100%, reboot, and try the app that kept failing.
What If DISM Itself Fails With Error 193
Sometimes the repair tool is the broken thing. DISM will throw error 193 at you. It's the same underlying problem as 0x800700C1, just wearing a different number.
If you ran it in the old Command Prompt, run the identical command again from Windows Terminal (Admin). Different host process. That swap alone fixes it more often than you'd think.
Still stuck? If that still fails, start suspecting the drive. Same admin window, run chkdsk C: /f. It'll ask to schedule the check for your next restart. Say yes, then reboot so it runs before Windows loads.
On a big drive that scan crawls. Let it finish. Don't cut power. Back at the desktop, give the DISM command one more go.
9. Perform a Repair Install of Windows
Microsoft calls this one an in-place upgrade. It swaps out every Windows system file while your personal files, your installed apps and most of your settings stay put, which is a lot gentler than the name suggests.
Yes, this is the last resort. Still, it beats a clean install by a mile, and it gets at component store damage that DISM couldn't touch.
Here's the order:
- Grab the official Windows 11 or Windows 10 installation media or ISO direct from Microsoft.
- Double-click the ISO so it mounts. Or just open the USB drive you made earlier.
- From inside that drive, run Setup.exe.
- The installer will ask what you want to keep. Pick Keep personal files and apps.
- Then leave it alone. The PC restarts on its own a few times, and that's normal.
Budget an hour for this, and more than that on an older machine. Back up anything you'd hate to lose before you start, even though the process is built to leave your data intact.
Error still showing up after all that? Then it isn't software anymore. You're most likely dealing with failing hardware or a disk that's on its way out.
How to Prevent 0x800700C1 Problems
Most repeat cases trace back to the same few habits. Changing them is not hard. The point is to stop broken files from landing on the machine at all, and to keep Windows in good enough shape to run what you install.
A few habits can prevent repeat problems:
- Pull installers from the vendor's own site or the Microsoft Store, never from mirrors or driver pack sites
- Compare the downloaded file size against the size listed on the download page before you run it
- Look up your system type once and remember it, so you grab 64-bit, 32-bit, or ARM64 builds correctly
- Never download loose DLL files from third-party “fix” websites
- Let Windows updates finish on their own instead of forcing a shutdown mid-install
- Update the Microsoft Store, Xbox app, and Gaming Services through Library > Get updates
- Add trusted program folders to your antivirus exclusions when they keep getting flagged
- Run
sfc /scannownow and then after a messy update or an unexpected power loss
Interrupted downloads deserve their own mention. They cause more of these errors than anything else on the list.
So if your connection drops a lot, grab large installers in a browser that resumes properly. And delete the old attempt before you try again.
Frequently Asked Questions
What does error code 0x800700C1 mean?
Behind the hex is ERROR_BAD_EXE_FORMAT. Windows tried to launch the file, read the header at the top of it, and decided the thing isn't a real program for this machine. So it stopped before anything ran.
Most of the time that points to one of a few problems: the file got cut short during a download, something corrupted it on disk, or it was built for a CPU architecture yours can't run (an ARM64 build on an Intel laptop, say). The installer being 32-bit or 64-bit isn't usually the issue here.
Is 0x800700C1 the same as DISM error 193?
It is. Same failure, printed two different ways. DISM prints the decimal system code 193, while apps and Windows Update hand you the hex HRESULT 0x800700C1.
Why does Windows Update fail with 0x800700C1?
Two usual suspects. Either the update files came down damaged, or the component store doing the install is already busted.
Start with the Windows Update Troubleshooter. DISM next, then sfc /scannow. That order clears most of these.
Can a virus cause error 0x800700C1?
Sure. Malware that rewrites or swaps program files leaves them unreadable to the Windows loader.
Your antivirus catches blame here too, more often than you'd think. It quarantines one infected piece of an app, and everything else in that app starts throwing the same error.
Final Thoughts
Order matters here more than any single fix does. Restart first, since that alone clears a surprising number of these. Then grab a fresh copy of the installer and confirm it matches your system type, because bad downloads and a 32-bit file on a 64-bit machine cause most of what people run into.
Only then should you repair the app, peek at your antivirus quarantine folder, and run DISM followed by SFC. Save the full reinstall and the Windows repair install for last. They take the longest and they're the most disruptive, so there's no reason to start there.
Watch the symptom, too. One program failing points at that program. Several failing, or a Windows Update that refuses to finish, points at your system files instead.
So, one stubborn app or the whole machine? The exact wording of the error helps more than you'd think, so copy it down. Drop it in the comments and someone can help you figure out where yours lands.




