Fix: Change Analysis Diagnostic Does Not Install in Windows XP SP3

When you run the Change Analysis Diagnostic Tool installer in a computer running Windows XP SP3 the setup fails. Although the Change Analysis Diagnostic download page states that the tool supports only Windows XP Service Pack 2, you can install and use it in Windows XP SP3 systems as well, using the workaround provided in this article.

The following error message is shown when you install the tool in non XP SP2 systems.

KB924732 Setup Error

Setup has detected that the Service Pack version of this system
is newer than the update you are applying.

There is no need to install this update.

Note: The following workarounds can also be used for KB923800 Setup Error when installing Offline Crash Diagnostic tool in non XP SP2 systems.

Workaround #1

The Change Analysis Diagnostic Installer is a self-extracting executable, which can be opened using WinZip or any other decompression tool.

Install and run WinZip.

Open the Change Analysis Diagnostic setup file in WinZip

Extract statechangediag.exe and scstyle.xsl to a folder

Close WinZip.

Statechangediag.exe is the main executable file which can be relocated to any place and run. The log file is generated in the same folder where the executable is present.

Workaround #2

The Change Analysis Diagnostic installer gets the Service Pack version from the registry, and runs only if the system has Windows XP Service Pack 2 installed. You can temporarily change the Service Pack version in the registry and then run the installer.

1. Click Start, Run. Type Regedit.exe and press ENTER

2. Navigate to the following key:

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Windows

3. Note down the existing value data for CSDVersion, as you’ll have to reinstate the original value data later. (The values of CSDVersion will be 0x100 for SP1, 0x200 for SP2, 0x300 for SP3 and so forth.)

4. Double-click CSDVersion and set its data to 0x200

5. Run the Change Analysis Diagnostic installer.

6. After setup is complete, restore the original value data for CSDVersion.

7. Exit the Registry Editor.

About the author

Ramesh Srinivasan founded back in 2005. He is passionate about Microsoft technologies and has a vast experience in the ITeS industry — delivering support for Microsoft's consumer products. He has been a Microsoft MVP [2003 to 2012] who contributes to various Windows support forums.