Click to See Complete Forum and Search --> : Warning! XP failed after last update!


whynox
October 14th, 2004, 02:34 AM
A yellow icon prompting for "IMPORTANT" update. After checking it out, went ahead with the download and installation of new updates. And that was the last time I gain access to my PC. After the installation complete it came out with the error below.

" Explorer.exe - unable to locate entry point
SHCreateThreadRef could not be located in the dynamic link library SHLWAPI.dll"

I tried repairing winXP using recorvery console to replace the shlwapi.dll and kernel32.dll I copied from my other working PC. But unsuccessful! Googled to look for solutions, so far I see quite a few complains of the same problem in other forums but no solutions are posted.

Anyone know how to resolve this problem.

Just to let you know how serious is this issue, I know as of now already 5 computers is down due to the last update. I have told all my friends and associates to disable automatic updating for the time being.

Gabriel
October 14th, 2004, 05:03 AM
Hi all,
Is there any other user who can confirm that?


10x,
Gabriel

Ya_know
October 14th, 2004, 08:21 AM
I'm patched to the teeth, went to windows update just now, no critical updates available, I don't have that problem, or any to speak of.

Which article number for the update? I'd be curious to see some of these other forum responses....

hudsonsmith
October 14th, 2004, 09:09 AM
There was a cumulative patch that came through yesterday. No issues here.

Was this yellow icon coming from ms automatic updates, or could this potentially have been some sort of rogue popup?

Have you tried a repair install?

GreenGrime
October 14th, 2004, 09:59 AM
No issues to report here either after the patch yesterday.

WinXP Pro SP2.

Tbone004
October 15th, 2004, 01:46 PM
i have the EXACT same problem. I'm incredibly desperate for I have a term paper due within a week.

WebHead
October 15th, 2004, 01:50 PM
I'm all caught up with updates on my notebook and desktop at home and no problems,.. although I do have something to note about SP2 (which might be related).

I typically use a downloaded copy of SP2 for my updates. However, did order the SP2 CD. I got the CD. The other day I tried to use the CD and both times it created a huge issue.

- Installed XP (XP Pro with SP1 included) until default install completed.
- Popped in SP2 CD. Installed, rebooted.
- Machine reboots, gets to near the login screen, the automatically reboots itself. Sasser? Doesn't seem to be because Windows doesn't login, plus I am not connected to the network.

I personally think there is a bunk version of SP2 floating around. It would be nice to see if there is any known issues with a certain rev of SP2.

whynox
October 16th, 2004, 01:52 AM
i have the EXACT same problem. I'm incredibly desperate for I have a term paper due within a week.

Here is a thread from another forum with the solution. Hope it help.

http://www.techimo.com/forum/showthread.php?p=1255740#post1255740

As I have imaged my drive, restored my c-drive image, so I did not try the above fix. My window broke so many times over the years, so I regularly image my c-drive to save a lot of time reinstalling everything again. I don't believe the "system restore" function in winXP. A virus restore itself even you clear it, this is how stupid the system restore works.

NooNoo
October 16th, 2004, 06:43 AM
Here is a thread from another forum with the solution. Hope it help.

http://www.techimo.com/forum/showthread.php?p=1255740#post1255740

As I have imaged my drive, restored my c-drive image, so I did not try the above fix. My window broke so many times over the years, so I regularly image my c-drive to save a lot of time reinstalling everything again. I don't believe the "system restore" function in winXP. A virus restore itself even you clear it, this is how stupid the system restore works.


System restore cannot differentiate between viral files and ordinary files. Viruses get themselves into the restore for a reason. System restore is not stupid - not having a decent av to prevent infection is.

csideshell
October 18th, 2004, 12:49 PM
If you receive an error message: "Explorer.EXE - Entry Point Not Found - The procedure entry point SHCreateThreadRef could not be located in the dynamic link library SHLWAPI.dll", this information will help resolve the issue.

This appears to have been caused by the following sequence of events:

You installed Windows XP Service Pack 2
The installation of Service Pack 2 failed due to a computer crash during the installation which resulted in the automatic Service Pack Recovery process. On next boot, you should have received an error message telling you that the install failed, and that you need to go to the control panel and uninstall SP2 and then try re-installing it. This message may have been dismissed accidentally or by another individual using your computer. In any event, the Service Pack recovery process was not completed by uninstalling the service pack from the Add/Remove Programs control panel, and the system is consequently in a partially installed state which is not stable.
You then installed the latest security update for Windows XP, MS04-038, KB834707. Because your system is still partially SP2, the SP2 version of this fix was downloaded and installed by Windows Update or Automatic Updates. However, the operating system files on the system are the original versions due to the SP Recovery process. This results in mismatched files causing this error.
To recover the system, carefully perform the following steps:

Boot normally and attempt to log in to your desktop. At this point you should get the error message listed above.
Press Control+Alt+Delete at the same time to start the Task Manager. (If you are using classic logon, click the "Task Manager" button.) You may get additional error messages but Task Manager will eventually start.
On the menu bar, select File and then New Task (Run).
Type in control appwiz.cpl into the new task box and hit OK. You may get additional errors that can be ignored.
The Add/Remove Control Panel should now be running. You can close Task Manager.
Near the bottom of the list, find the entry titled "Windows XP Hotfix – KB834707".
Click on it and click the "Remove" button. It will take some time to complete. Once the "Finish" button is visible, click on it and reboot your system. If you get messages about additional software or hotfixes installed, you can safely ignore them.
Do NOT stop now! Your system is still in the "failed SP2 install" state. You MUST complete the SP2 uninstall, and then re-install SP2.

Start the system and log in.
Click on Start and then Control Panel.
Click on the Add/Remove programs item.
Near the bottom of the list, find the entry titled "Windows XP Service Pack 2".
Click on it and remove Service Pack 2. You may get a warning about software you have installed after SP2. Make a note of it as you may need to reinstall some of them after the uninstall operation.
After Service Pack 2 has been successfully removed, you should visit http://www.microsoft.com/sp2install for instructions on installing Service Pack 2. You can get SP2 from http://windowsupdate.microsoft.com.
After Service Pack 2 has been successfully re-installed, you should re-visit Windows Update to get the proper version of the latest critical security updates.
FAQ:

Q: I don't believe I am in the "partially installed SP2" state. Is there any way to check that?

A: After step 7, your system should be able to log in. There are several ways to check.

Open the file c:\windows\svcpack.log, and scroll to the very bottom of the file. About 10 lines from the end, you should see:
0.xxx: Executing script \SystemRoot\sprecovr.txt
0.xxx: In cleanup mode. System will not be rebooted.

If you have these lines in svcpack.log, and you did not uninstall Service Pack 2 in Add/Remove Programs, you definitely have a machine in this partially installed state.
Click on the Start button, then Run, and type winver, then click OK. If the version is "Version 5.1 (Build 2600.xpsp_sp2_rtm.040803-2158: Service Pack 2" then you have the correct SP2 install. If, however, it has a number that is less than 040803 after the xpsp2, such as "Build 2600.xpsp2.030422-1633 : Service Pack 2" then you definitely have a machine in the partially installed state. [Corrected typo in version numbering, 11am.]

NooNoo
October 18th, 2004, 01:22 PM
Welcome to Windrivers csideshell



are you Raymond Chen? (http://weblogs.asp.net/oldnewthing/archive/2004/10/14/242241.aspx) If so, thanks for posting your work here. If not, please always quote your source of information.

Reylan Talonspyre
October 20th, 2004, 01:36 PM
Click on it and click the "Remove" button. It will take some time to complete. Once the "Finish" button is visible, click on it and reboot your system. If you get messages about additional software or hotfixes installed, you can safely ignore them.
Do NOT stop now! Your system is still in the "failed SP2 install" state. You MUST complete the SP2 uninstall, and then re-install SP2.

I would continue, but the computer did not reboot properly after I did this. My KB834707 is still on the computer (since after reboot same problem persisted and would not allow me to start into WinXP)

Is there another way?

EDIT: Nevermind, I see the update has been put in the Microsoft Knowledge Base ... thanks anyways.

EDIT 2: Nevermind AGAIN! I still need help, I have been failing around Step 7.

Thanks again!
http://support.microsoft.com/kb/888162