Software repair invoked by SP3

[HPS Admin]

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.

 

[Stephen Harris]

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.

MS recommends disabling programs that monitor the computer
like anti-virus programs because these can disrupt the script
SP3 uses for installation. Does your software generate real-
time system monitoring? All I could think of.

 

[smlunatick]

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 thePC
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.

Sounds like a common Windows Installer database corruption for that
software entry. Most common fix is to install the Windows Installer
Cleaner, remove the "offending" entry and re-install the software.

 

[PA Bear [MS MVP]]

WinXP SP3 - Read all prerequisites for a successful installation
http://msmvps.com/blogs/harrywaldro...requisites-for-a-successful-installation.aspx

Free unlimited installation and compatibility support is available for
Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat and
e-mail support is available only in the United States and Canada. Go to
http://support.microsoft.com/oas/default.aspx?gprid=1173 | select "Windows
XP" then select "Windows XP Service Pack 3"

 

[Peter Foldes]

See the following

http://support.microsoft.com/kb/290301

 

[HPS Admin]

From the responses, people seem to think it is likely to be a Windows
Installer corruption, so why is applying SP3 invoking the repair and not when
other software is installed on the PC using the installer? What process does
the post-SP3 go through that causes XP to invoke the repair - it occurs
before the login prompt is displayed and therefor before the CMD scripts run
to complete the SP3 install. This would suggest SP3 is corrupting the
installer information somewhere.