H
HPS Admin
Guest
I have a piece of software installed on PC's that is being corrupted by SP3.
After successfully installing Service Pack 3 on to the PC you are requested
to re-boot. During the re-boot the Windows Installer is invoked and our
software is re-installed/repaired before the login screen appears. As the PC
has no connection to our server when the software is installed, the installer
corrupts the programs configuration files with invalid paths to files.
I can correct the configuration files (text .ini files) after SP3 has done
it's stuff but I would like to know what would cause the Windows Installer to
be invoked in this way.
After successfully installing Service Pack 3 on to the PC you are requested
to re-boot. During the re-boot the Windows Installer is invoked and our
software is re-installed/repaired before the login screen appears. As the PC
has no connection to our server when the software is installed, the installer
corrupts the programs configuration files with invalid paths to files.
I can correct the configuration files (text .ini files) after SP3 has done
it's stuff but I would like to know what would cause the Windows Installer to
be invoked in this way.