ICE errors during build

[sharma021]

We are currently encountering an issue during the MSI build process. It seems to be related to a failure with the script engine.
We are seeing errors that indicate problems accessing or registering the scripting components necessary for the installation package. This is preventing the MSI from building successfully.

Error executing ICE action 'ICE32'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wixtoolset.org/documentation/error217/ for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2738. ".
(ICE32,ICE09,ICE61)

As an alternate approach we have suppressed the ICE errors.
I also tried re-registering the vbscript.dll but the error still persists.

what can be the possible reasons? is there a way to completely fix these issues?
Thank you

[robmen]

Windows is deprecating VBScript, and those ICEs were implemented in VBScript. Is it possible that your computer recently had VBScript removed/disabled? That'd be the first thing to check.

[sharma021]

Hi @robmen
Thank you for the clarification earlier.

I did some more digging on my end to rule out the VBScript registration issue. I’ve verified that vbscript.dll is indeed present on my system at C:\Windows\System32\vbscript.dll. I also checked the registry (under HKEY_CLASSES_ROOT\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}), and it points to the correct location. I tried re-registering it using regsvr32 vbscript.dll from an elevated command prompt, and it registered successfully—no errors.

However, despite these checks, I’m still encountering the same ICE errors during build.

I understand that VBScript is being deprecated by Microsoft, and that’s likely the root cause, but I’m trying to understand the actual impact of these ICE errors. Specifically:
• Do these ICE errors affect the functioning of my MSI installer in any meaningful way—especially the custom actions or PS scripts I’m running?
(I am have PS scripts, and custom action triggering cmd but I am not using any vb script)
• Is there a recommended workaround or fix for these ICE errors, given that suppression (via -sice) doesn’t seem like a good long-term solution from what I’ve read?

Any insights or best practices for working around this while still maintaining MSI integrity would be really appreciated.

Thanks again for the support!