You're staring at ERROR_INSTALL_TRANSFORM_FAILURE (0x00000658) and the installer just quit. Yeah, that's annoying. But this one's usually a quick fix.
The Fix That Works Most of the Time
- Close all running installers and programs. If you have a leftover setup window, kill it from Task Manager (press Ctrl+Shift+Esc, find the setup process, right-click, End Task).
- Clear the temp folder. Press Win+R, type
%temp%, hit Enter. Select everything in that folder and delete it. Some files will be in use — just skip those by clicking "Skip" when prompted. - Re-register the Windows Installer service. Open Command Prompt as administrator (press Win, type
cmd, right-click, Run as administrator). Then paste this and press Enter:
msiexec /unregister
msiexec /regserver- Restart the computer. Yes, you need to do this. The re-registration doesn't fully take effect until the service restarts.
- Run your original installer again. Should work now.
If it still fails, move on to the next section.
Why This Works
What's actually happening here is that Windows Installer uses a staging area in your temp folder to unpack the MSI and its transforms. A transform (.mst) is a patch file that modifies the MSI database at install time — it might add a license key, remove a component, or set a registry value.
The 0x00000658 error literally means the transform couldn't be applied. One common cause is a corrupted or incomplete temp file from a previous failed install. The installer reads the transform from that temp location, gets garbage, and aborts.
Clearing %temp% wipes that stale data. Re-registering msiexec resets the Windows Installer service's internal state — it's kind of like clearing the cache in your browser but for the installer engine. The reason step 3 works is that the service sometimes holds onto a bad reference in its own database, and re-registering forces it to rebuild that.
The restart matters because Windows Installer runs as a service, and you need the service to start fresh with the new registration.
Less Common Variations
Sometimes the fix above doesn't cut it. Here's what else can trigger this error and how to handle each.
Corrupted MSI or MST Files
If you downloaded the installer from the internet, the file might be incomplete or damaged. Check the file size against the vendor's stated size. If you have a checksum (SHA-1 or MD5), verify it. If it's from a CD, try copying the entire install folder to your hard drive and run from there — optical drives can have read errors.
Insufficient Permissions
If you're installing for all users on the machine and your account lacks admin rights, the transform can fail because it tries to write to Program Files. Right-click the installer and select "Run as administrator." If that doesn't help, check if the vendor offers a per-user install switch — often /peruser or ALLUSERS=2 as a command-line parameter.
Antivirus Interference
Security software sometimes locks down temp files or quarantines parts of the transform mid-install. Temporarily disable your antivirus (not Windows Defender's real-time protection, but third-party ones like McAfee or Norton). If the install succeeds with AV off, add an exception for your install folder.
Transform File Itself Is Bad
If you're using a custom transform created by your IT team, the .mst might reference tables that don't exist in the MSI. You'd see this in a corporate deployment scenario, not with a standard consumer product. Use Orca (part of the Windows SDK) to validate the transform against the MSI. Open the MSI in Orca, go to Transforms menu, Apply Transform, and see if it errors out.
Group Policy Lockdown
On managed machines, a policy can restrict which transforms are allowed. Run gpresult /h policy.html in an admin command prompt and open the HTML file. Look under Computer Configuration\Administrative Templates\Windows Components\Windows Installer. If "Prohibit non-administrators from applying transforms" is enabled, that's your culprit — talk to your admin.
Prevention Tips
- Clean temp regularly. There's a built-in tool — open Disk Cleanup (cleanmgr.exe), select your system drive, and tick "Temporary files." Run it monthly. That keeps the installer staging area tidy.
- Always download fresh installers. Don't reuse a setup file that's been sitting in your Downloads folder for months. Vendor sites update their installers, and older versions may have bugs that trigger this error.
- Disable antivirus during large installs. Not permanently, just while installing software you trust. It reduces the chance of file locks.
- Keep Windows updated. Microsoft patches the Windows Installer engine periodically. Those cumulative updates often include fixes for edge-case transform failures.
That's the whole picture. Start with the temp-clearing and re-registration — nine times out of ten that's all you need. The rest is for when the same error keeps popping back on specific software or in managed environments.