This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 75%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EU%3C/text%3E%3C/svg%3E)
Following the installation of the Windows 11 Version 24H2 update, I have encountered numerous application crashes and hangs. Notably, the MSIEXEC.exe located in the SysWoW64 directory is crashing frequently, causing problems with many 32-bit applications during updates and installations. In contrast, the MSIEXEC.exe found in the System32 directory seems to be functioning without issues.
Has anyone else experienced similar problems?
Additionally, it would be helpful if others could share any known cases of application crashes, like the one mentioned above, in the comments to help us track application crash issue.
Seeing the same behavior on a brand new Dell XPS laptop, with an i7-13620H. A few things we've tried, with no success:
We can confirm that it only happens when running the 32-bit version of msiexec, and it's fundamental enough that it even crashed when calling "msiexec /?".
Other 24H2 systems work fine, so we're not sure what's unique about this one. Our current theories:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 61%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
For us, this was either the SentinelOne issue, or the fresh installs are broken. I updated SentinelOne agent from 24.1 something to 24.2 something and attempted to reinstall the update and it succeeded, so SentinelOne was to blame in our case.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 3%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMG%3C/text%3E%3C/svg%3E)
You guys saved my arse today. Huge find. Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 92%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
The same issue happened to me today. I had to update SentinelOne to v24.1. Right after the update, I was able to run a normal installer.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 19%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECD%3C/text%3E%3C/svg%3E)
thank you so much. After updating to v24.1 my problems all went away.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 86%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Thank you, same here.
Same! I was on SentinelOne 23.3.3.x something and after the update all Windows installer files started working again, life saver!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 20%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
User agent was on 23.x and this happened today, your post saved me a headache, thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 87%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Upgraded several of our problem machines from SentinelOne v23.xx to v24.xx, reran the program installer, and the installer ran as expected.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 84%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENA%3C/text%3E%3C/svg%3E)
This was my experience also. Thanks for the tip.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 23%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Repair the Windows Installer Service (MSIEXEC):
[Clear the Windows Installer cache. But it's not generally recommended.
net stop msiserver
del /f /q %systemroot%\Installer*.*
net start msiserver]
Open Command Prompt as Admin and execute the following commands. Press the Enter key after each command:
msiexec /unregister
msiexec /regserver
Open Command Prompt as Admin and execute the following commands:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
Clear the Windows Installer cache: net stop msiserver del /f /q %systemroot%\Installer*.* net start msiserver
Clearing windows installer cache will results in repair / uninstall failure of MSI based product.
Is this recommended ?
Clearing the Windows Installer cache is generally not recommended.If space is limited or the cache is corrupted, a better option might be to manually clear only unused or redundant files rather than the entire cache. Alternatively, there are third-party tools like the Microsoft Program Install and Uninstall Troubleshooter to fix issues without deleting these critical files.