RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
----------------------------------------------------------------
01-Apr-2003 17:12 5.2.2.14 272,384 Update.exe
01-Apr-2003 17:12 5.2.2.14 44,544 Spuninst.exe
Do not install this hotfix directly on the computer that has the problem. The package contains a fixed version of Update.exe that replaces the one in SP3. To use this hotfix:
- Extract SP3 to a temporary folder.
- Replace Update.exe in the temporary folder with the fixed version.
- Install SP3 by running Update.exe from the temporary folder.
If you must later remove SP3, use the Spuninst.exe that is provided in this fix.
WORKAROUND
To work around this problem, apply one of the workarounds that are found in the "Workaround" section of the following Microsoft Knowledge Base article:
297379 Programs Can Revert to the Default Settings on Terminal Server