Fixing Error Code 720 and Type Mismatch Issues in Windows 10 and Windows 11
Honestly, if you’re here because of error code 720 or those creepy type mismatch exe errors popping up—been there, done that. These errors seem to come out of nowhere, especially if you weren’t messing with anything major. One minute, your app or program is working fine, and the next, it’s giving you grief, halting your workflow or gaming session. After some trial, error, and a good chunk of frustration, here’s what finally made a difference for me.
Checking App Compatibility
The first thing I messed with was the app itself. Right-click on the app icon, then choose Properties. This pops up a window with a few tabs—look for the Compatibility tab. Sometimes, Windows gets confused if the app was built for an older version, so forcing compatibility might help.
Under Compatibility Mode, hit Run compatibility troubleshooter. It’s a pretty straightforward wizard—just follow the prompts. Usually, selecting to run it under an older Windows version like Windows 7 or Windows 8 helps. Also, check the box for Run this program as an administrator. That last part is often the difference-maker—gives the app elevated permissions that might be causing the mismatch errors or permission-related issues.
If the app isn’t there, or the options are grayed out, sometimes it’s because of restrictions, upgrades, or OEM customizations. I’ve run into cases where the OEM locked down certain settings—on my older ASUS, the compatibility options were buried in Advanced menus. Maybe try updating your BIOS or chipset drivers if options are missing, but be cautious—more on that later.
Running System File Checks
Next, it’s time to get some system tools involved. Head into an Administrator Command Prompt. Just click Start, type cmd, right-click on the Command Prompt and pick Run as administrator. PowerShell works too, if that’s your vibe.
Run these commands—press Enter after each, and don’t rush:
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowDISM is great for repairing system images, especially if they’re corrupted. I’ve seen silly errors vanish after just fixing the image. SFC checks for missing or corrupt system files—sometimes, a missing DLL or similar causes mismatch errors or app failures. Honestly, this can take a while—think at least 10-20 minutes, maybe longer—but it’s worth it. Your system might just need a tune-up.
Once all that’s done, restart your PC and hopefully, the errors have eased up. If not, it’s probably driver or driver-related config issues lurking behind the scenes, which leads to the next step.
Updating Drivers
If you suspect driver issues, which is often the case with these kinds of errors, go to Device Manager. Right-click the Start button, select it, and look for devices with yellow triangles—that’s your sign something’s off.
Right-click and choose Update driver. Pick Search automatically for updated driver software. If Windows doesn’t find anything, it’s time to visit the manufacturer’s website or your PC support page—sometimes, their drivers are more recent than what Windows offers, especially with chipset, graphics, or network cards.
Be cautious with third-party driver tools—some can be shady. Stick to official sources or trusted sites. Updating your graphics driver, network adapter, or motherboard chipset can sometimes make all the difference in clearing up mismatch issues or app crashes.
Using Built-in Troubleshooters and Resetting Apps
Windows actually has some handy troubleshooting options. Head over to Settings → Apps → Installed apps. Find your problematic app, click the three dots, then choose Advanced options. From there, you can try Repair. It’s less destructive and aims to fix corrupt cache or config files without deleting your info.
If that doesn’t work, try Reset. Be warned—resetting erases all app data, settings, and cache, effectively giving you a clean slate. Sometimes, that’s the only fix if the app’s own data got corrupted or misconfigured. If resetting doesn’t do the trick, consider uninstalling completely, then downloading the latest version again from the official site or Microsoft Store. I’ve had to do this more times than I care to admit with stubborn apps.
System Restore as a Last Resort
If nothing else works, System Restore is your buddy. Type rstrui in the Start menu or go through Control Panel → Recovery → Open System Restore. Pick a restore point predating the error, hit next, and let Windows roll things back. Sometimes, an update or a driver change causes the misfire, and going back a few days fixes a lot of headaches. Expect a reboot, and give it some patience—this process can take 15-30 minutes.
Some Final Tips
This kind of error can be stubborn and sometimes weirdly specific to your system. What finally helped in my case was a combination of updating drivers, running system checks, and resetting the app. Don’t forget to double-check your BIOS settings—especially around security features like TPM—and make sure your Windows is fully updated. On some machines, certain options like Secure Boot or Intel PTT are in the BIOS and can affect compatibility.
If BIOS-related features are missing or grayed out, check if your system’s firmware is up to date—OEM updates often fix these issues or add support for newer security modules like fTPM or Intel PTT. Also, some OEMs lock down certain BIOS options—sometimes, you have to disable features like Secure Boot or enable TPM modules explicitly.
One last thing—watch for on-screen instructions
Whenever you get prompts or instructions on screen, read them carefully. Sometimes they ask you to pick a region, confirm settings, or click “Finish” at just the right moment. Missing small details here can mean you’re not completing the process properly. During troubleshooting or setup wizards, I learned to not rush—these tiny steps matter. It’s all about following the prompts diligently and confirming every choice before closing or rebooting.
Sometimes, repeating a step or reapplying a setting is needed—don’t get fed up if it doesn’t work instantly. Persist—each small correction adds up. Usually, if I stay patient and methodical, the errors clear up, and I get back in control.