Welcome Guest ( Log In | Click here to Register a free account now! )


Register a free account to unlock additional features at BleepingComputer.com
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

entry May 9 2008, 01:11 PM
As issues with the installation of XP SP3 emerge I'll try to post them here along with Resolutions


PRIOR to installing SP3, one should read:
Steps to take before you install Windows XP Service Pack 3

See the If you are running antivirus software section. It specifically states
QUOTE
If the configuration of your antivirus software prevents certain system files from being changed, the Windows XP SP3 installation may fail. Try temporarily disabling your antivirus software. To do this, right-click your antivirus program icon, and then click Disable. This icon typically appears in the lower right corner of the computer screen.
Antivirus software can prevent system files from being changed by guarding the registry using Permissions.
That is why some Symantec "products" ( as described in the " After installing SP3, Device Manager is blank; " heading ) caused the registry subkeys to become damaged/corrupted.
The issue is NOT caused by the application of SP3.



Computer fails to boot after XP SP3 installation (AMD Processors)

You receive a “Stop 0x0000007E” error message after you upgrade to Windows XP Service Pack 2 or Service Pack 3 on a non-Intel-processor-based computer
QUOTE
We do not support using Sysprep to install an operating system from an image if the image was created by using a computer that has a different processor. For example, you cannot create a Sysprep image on a computer that has an Intel processor and deploy the image to a computer that has an AMD processor.
    RESOLUTION:
    1) Start the system in Safe Mode
    2) Click Start > Run
    3) Type or copy and paste the below into the Open: line exactly as it is written
    4) sc config intelppm start= disabled
    5) Click OK or press Enter
    6) Restart to normal Windows mode
Credit goes to fellow MVP Bill Castner for the above Resolution

An excellent ongoing article on this and other SP3 issues is available on fellow MVP Jesper Johansson's blog -
Does your AMD-based computer boot after installing XP SP3?


System can not update or the Automatic Update service causes a 100% CPU cycle issue after the installation of SP3

For some reason, SP3 includes a much lower Version level of the Windows Update Agent. That reason escapes me.
To resolve the updating issue, install the latest Version of the Windows Update Agent.
Links to the WUA and how to install it can be viewed by clicking the WUA link above.



After installing SP3, Device Manager is blank; Network Connections is blank; USB safely remove icon is missing; USB device, scanner, non-functional, driver not accessible.
(The scanner is available at boot time, it is and remains unusable. The scanner software uses the registry)

The issue is caused by applying SP3 with Norton Internet Security, Norton Antivirus, or Norton 360 installed and actively monitoring the system. The registry will contain corrupted subkeys in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet or ControlSet001.
The subkeys will start with $%& for it's Value Data.
A poster in this thread, MRFREEZE61, has laid out steps to resolve the subkey corruption.
The post was made 07 May 2008, 11:01 PM UTC



Windows XP SP3 vs Media Center 2005 Extender Software Issues

Fellow MVP and DTS member Jason Tang has posted this issue and a resolution for it on his blog
QUOTE
Some of you that are still using Media Center 2005 (with Update Rollup 2) and Extenders for that platform may have run into issues with the Extender software after you have installed Windows XP Service Pack 3.

In particular, attempts to install the Extender software would fail or attempts to add new Extender devices to the host computer would fail.

When trying to install the Extender software on a system or when trying to add either a V1 Extender or Xbox 360 Extender device to your host machine with Service Pack 3 installed, you would get a message similar to this.

or


To get around this, follow these steps so that you can re-install the Extender software after Windows XP Service Pack 3 is installed.

1. Go to Start, Run and type 'cmd'

2. At the command prompt, type 'reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB895961" /v Installed /t REG_DWORD /d 1 /f' and press 'Enter' (Starts with reg and ends with /f, all in one line)
3. Run the Extender setup again. To download the Extender setup files, follow this link: http://go.microsoft.com/fwlink/?LinkId=73537

What does the above fix do? It basically adds a registry key so that the hotfix KB895961 (essentially, the Extender software) can be re-installed after Windows XP Service Pack 3 is installed. It seems that Windows XP Service Pack 3 interferes with configurations where the Extender software is already installed, and Extender software itself, without any registry modifications, would not install when Windows XP Service Pack 3 is installed.

Hope this helps people who have run into this issue.

 
« Next Oldest · The Clippings of Chairman Mow · Next Newest »
 
SMTWTFS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28