So I have hit this problem: STOP: c000021a {Fatal System Error} The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000026c (0x00000000 0x00000000). It appears some other users have too. I have tried hitting F8 and I get to the place where I can choose the last known good config, but that doesn't help me. I am still continuously rebooting with that error code. I don't know what else to do, and would appreciate any help to get me restarted. Our company QuickBooks file is in that partition and I need to get to it. Yes I know, it's always an emergency, why didn't you back up, blah blah. Thanks for the sermon in advance.
Good luck. Let me know if you get any responses. Help about this topic is pretty thin around here...as are replies. I just ended up reinstalling and now I have to get on the horn with M$ to fight for a new activation number. Grrrrrrrrrrrrrrr....
I've seen this problem being discussed recently in several MS-related forums & also experienced it myself. I believe the cause is a particularly vicious piece of malware called Smitfraud, which tries to simulate a BSOD & then offer you the opportunity of "fixing" it with their software if you purchase it from them. If you fall for the scam they just take your money & run. Unfortunately it looks like the BSOD routine was poorly written & in some cases like VMs it just cycles through the boot process & actually crashes (instead of fake crashing) at the end of it. There are various anti-malware programs that claim to disinfect Smitfraud but I've yet to have success with any of them.
I think your VM (a.k.a. Windows) is infected. Best way is to make a clean new VM. Even if you supposly clean it, it respawns it self again and again.
Having the same problem. This is very frustrating, ever since trying the last update in March, I have had nothing but problems with this. To top it off, I get an e-mail today asking me to preorder the new version - so I have a nonworking copy of parallels and you want to screw me out of an additional $39.00 for what is probably another nonworking release. No thanks.
Hi there, since i have been experimenting with Parallels an VMWare lately i experienced the same continuing reboot using both virtualization programs. As i didn't find a solution with parallels i checked the VMWare-Forum and found the following discussion containing a solution which worked in VMWare: http://www.vmware.com/community/thread.jspa?threadID=80060 I haven't tried this in parallels but i will and i'll post the result right away. See you later macinfloh
Hello again, i tried the registry fix using parallels and everything worked fine. i can now use Windows by either starting parallels or VMWare or booting natively. But i take no responsibility for any problems that may occur. So if anybody wants to try this, remember to back up your data BEFORE you do it. macinfloh
