I am getting a "Missing Script" error in MS installer when installing
an X-Rite colorMunki device and asked since I cannot find a way to
"fix" it. X-Rite is trying to help but I may have to contact MS.
I don't believe you can do installs in Windows's safe mode, so much for
trying the install in safe mode. However, you can use msconfig.exe
(Sysinternals' Autoruns is more thorough) to disable all startup
programs. Then disable your anti-virus and other security software
(permanently until you later reenable it). Reboot Windows into normal
mode. Could be one of those programs interferes with the installer.
There should be an error code (number) besides just a "missing script"
error message. If the error dialog doesn't give a number, look in Event
Viewer for the error to see if an numeric error code is specified in the
description of the error.
Windows Installer Error Messages
As I recall, the installer author can have multiple scripts and decide
which to run. Looks like their installer hit a condition under Windows
7 (for your unidentified edition) where it calls a script but the author
forgot to include it. Microsoft cannot do anything about an author that
incorrectly codes the scripts within the .msi file. Only X-Rite can fix
their installer. That would be like complaining to the hardware store
that the nut you bought was the wrong size (they'll probably exchange
the nut for the correct one once you tell them but it wasn't their fault
for selling you the wrong nut size in the first place).
If their installer creates an install log file (not the one use for
later uninstallation but a log of the install), it should have a section
titled "rollback". I remember hunting for that string because that's
after the installer puked and reversed its changes made so far. I would
look backward from the rollback message to see on what the installer
reported as an error.
If their author decided not to have an option to save a debug log, you
might be able to create one by running:
msiexec.exe /i <msipath> /L*v <debugfile>
<msipath> is wherever you stored the .msi file. If the path to the file
or the filename has spaces, be sure to enclose it in double-quotes.
Same for the path and filename for the debugfile which will have the
verbose status messages. /i = add status messages, /v = verbose output.
Don't bother adding /x for extra debugging info unless /i wasn't enough.
I don't think /L needs to be uppercase but that's how I see it mentioned
in help articles. For info on using the program, run "msiexec /?".
Even if you cannot understand the debug file's content, X-Rite
programmers should. It would give them something more than your
description of the problem.