Fix ERROR_BAD_CONFIGURATION (0x0000064A) – Corrupt Config Data

What's breaking your application

You're staring at ERROR_BAD_CONFIGURATION (0x0000064A) and it's the kind of error that makes you want to throw the computer out a window. I get it. Let's fix it fast.

The real fix: reset or repair the registry key

Nine times out of ten, this error hits when a registry entry for a specific product gets corrupted—maybe from a failed update, a crash during install, or a drive that's got bad sectors. Last month a client's accounting software threw this after Windows Update killed a pending install. Here's what worked:

1. Open Regedit (search for it in Start).
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData.
3. Look for the product GUID (long string with curly braces) that matches the app giving the error. You can find the GUID in Event Viewer under Windows Logs > Application – look for Event ID 1001 or 11708 with the error code.
4. Export that key first as backup, then delete it. Yes, delete it. Don't be shy – Windows will rebuild it when you reinstall the app.
5. Reboot, then reinstall the application from its original installer (not a shortcut).

That's it for the root cause. If the registry key is truly hosed, this wipes the slate clean and lets the installer start fresh.

When the fix above doesn't work

Sometimes the corruption is deeper. Try these in order:

• SFC scan: Run sfc /scannow from an admin command prompt. Catches system file corruption that mirrors config errors.
• DISM repair: Run DISM /Online /Cleanup-Image /RestoreHealth before SFC if SFC fails. I've seen DISM fix a corrupt component store that was causing config errors for half a dozen apps.
• Check disk: Run chkdsk /f /r on the drive where Windows is installed (usually C:). Bad sectors can corrupt registry hives. A client of mine had this error pop up for all their Adobe products after a power surge – chkdsk found 18 bad sectors and fixed them.

Less common variations

Sometimes the error shows as 0x8007064A or just Error 1606. These are cousins of the same corrupt-config problem. The fix is the same: nuke the registry entry for that product. For 0x8007064A, also try running msiexec /unregister then msiexec /regserver from admin command prompt – re-registers the Windows Installer service, which can clear up misconfiguration.

Why this works

Windows Installer stores all its knowledge about installed products in the registry under that Installer\UserData path. When that data gets garbled, the installer thinks the config is corrupt and throws 0x0000064A. By deleting the key, you force the installer to treat the product as uninstalled. A clean reinstall recreates the config fresh, no corruption carried over.

This is not a magic bullet for every error—but for this specific code, it's the first thing I try. I've fixed it on Windows 10, 11, and even Server 2019 the same way.

Prevention: keep your registry healthy

You can't stop every corruption, but you can reduce the odds:

• Don't force-shut down during updates. That's the #1 cause I see. Let updates finish even if you're late for a meeting.
• Run chkdsk monthly. Schedule it with Task Scheduler if you're lazy (I am). One less thing to blow up.
• Keep backups of critical registry keys. Before any major software install, right-click the key and export it. Takes 10 seconds, saves hours.
• Avoid registry cleaners. They cause more corruption than they fix. I've never seen one that's worth the risk.

If you're still stuck after all this, the culprit might be a failing drive. Grab something like CrystalDiskInfo and check your drive's SMART status. If it's going bad, nothing software-wise will save you – replace the drive, restore from backup.