Windows XP forum: XP startup-Fatal system error-session manager initialization

I'm getting the same problem. Have you had any luck?

Mine is a Dell Dimension. At least you got through to their tech support. I tried several times, and would be put on hold a while to talk to an actualperson, then the system would just hang up on me. I had to do it via email... it worked, but it's not as efficient having to wait for responses. I miss the good ol' days when companies cared about good customer service.

Anyway, I replaced the hard drive and cable to the hard drive, installed XP, put on all updates, installed all software. I don't think this is due to Spyware since I just installed the OS and the first thing I did was updates and antivirus. The last thing I installed was Office 2000. I had rebooted several times without a hitch, and Office was the last thing I needed to do. It won't boot into Last Known Good Config.

I saw on Microsoft's sight that at one point in time this was a problem in Windows 2k. Wonder if XP SP2 can cause this? I may try reformatting, installing everything and getting Office XP on it. It that doesn't work, I'll try installing all updates but SP2. Let me know if you have any progress, and I'll do the same.

i have the same on my computer hoping that you have sorted yours out now can you help me

I just developed that same problem last night. I started installing a game on my computer and the process locked up. I shut down (couldn't just use the restart option) and then after that <boom> no access at all. I've tried all booting options and still get blue screen right after the Windows xp startup screen appears. (Goes black and then blue) I've tried replacing several files in Windows\system32\config, but that did not help either. Any help would be greatly appreciated.

thanks

I was installing a program, that i got from download.com, and out of the blue it decides it wants to install .NET Framework for me. So I hit Cancel. And the system slows but nothing happens, so I hit Ctrl+Alt+Delete, and ended the installer, after that, all my programs had fatal errors and had to close. So I decided to Reboot my PC (I have a Dell Inspiron 4100, with Windows XP Professional) upon Reboot, after the Windows XP Boot Screen, the screen goes black for a second, then blue saying c000021a {Fatal System Error} And then the system automatically Reboots on its own, repeating that process over and over. I think if I could get my PC to boot into DOS, I could delete the .NET Framework files and that might fix it. But I dont know how to get it into DOS, without logging into Windows. Can someone please help.

When I first got my computer running windows xp I kinda had the same problem. I would get a fatal system error and the computer would shut down on its own. It was a microsoft problem. I called microsoft told them what was happening and they fixed it.

and its a real *****! So far, attempting to boot to Safe Mode or any other option on the F8 boot menu has no effect. The initialization error occurs before even safe mode is reached, so it becomes an endless loop of splash screen, reboot, splash screen, reboot, rinse and repeat.

The only solution that has yet worked for me is reloading the operating system from the install CD. Fortunately I have built all my systems from scratch with genuine M$ install CDs, not the big OEM house restore disks. Thus, I can use the repair option in the first screen of the retail install and not lose have the routine reset the partition to the original factory load. I am currently on my third reload of the evening and it is 1:30 in the freakin' morning so I am not a happy camper and I am not likely to finish troubleshooting this tonight, but here is what I know so far.

When the OS is reloaded from the original CD (a 40 minute process that looks exactly like a virgin install, but actually just overwrites the Windoze system files without blowing off the registry or any programs or data) TURN OFF Automatic Updates!!!! You may go to the Windoze Updates site manually and let it search for updates, but use the "Custom Install" not the "Express Install." This will allow you select the specific patches to be installed. When I started working on this issue earlier tonight and determined what was happening, I began installing the updates one at a time to find the one that caused the failure. I got halfway through the list of 16 and then got lazy. I did 4 at once and everything was fine. Then I did the last 4 on the list and bang, I'm dead again.

DO NOT INSTALL UPDATE NUMBERS 890859, 891781, 893066, or 893086. It is one of these that killed me. I do not yet know which one. Stay tuned and maybe I'll have some time on Sunday (won't have any time tomorrow, sorry) or one of you can take over the detective work.

Now if I were to rename my computer as "Kenny," then I could truthfully say, "Those ********, they killed Kenny."

dw

I had exactly the same problem with one PC. Uninstalled the Hotfix and the problem was gone. Great tip in this link, did not know how easy it is to uninstall a hotfix, this will save me hours of working time in the future.
Why does MS hide these great help tips even to developers??

ms

Like many of you, my techie will make quite a bit over the next two days correcting the damage MS has wrecked on two computers here even reaching out to non MS items such as ACT. My question to the readers; what are the alternatives to Office for example. Mozilla Firefox is a browser alternative but much will only work with Explorer so we are stuck with that for know at least.

Have people solved the problem by not installing this update then?

I got my brand new laptop exactly 2 weeks ago today, and today that error came up, it also did it exactly one week ago. So once a week since I got it! I've been too scared to put all my files on it in case it happens again so I REALLY hope it works. Thanks for letting me know!

So any feedback on whether the prob has happened agin for anyone would be great!

Thanks

Now I got another problem, I lost my internet connection, so Ill have to do the tedious work of finding the problematic update once again.
XP really gets into it!

The good news is that the main problem is solved... KILL the 890859! NOW!

Charles

Just checked my XP home machine and the update has been on there since Jan/2006....

Rob

Hi!

I followed the instructions, but de $NTUninstallxxxxxx$\spuninst folder contains no spuninst.txt file! All the oterh $NTUninstallxxxxxx$\spuninst have spuninst.txt

Any sugestions?
Thanks in advance

Pedro

i got into my HD via another installation of home, did a search for the kb890859 uninst file and ran it, which seemed to work, but my Winxppro still wouldn't boot. i then went to manually rectify the problem using the recovery console only to find the spuninst.txt file is missing!!! can someone PLEASE display the contents of this file or a copy so i can get back in?

I also used HP WINXP, the explorer often closed automatic by quickly operations on it. Where could I get patch to fix it?