Login Process Intitialazation initialization failure

[Anesthetic]

I know you guys have seen this problem before; however, I guarantee you that my problem is slightly unique.

I use Storagecraft Shadow Protect to make backup copies of my Operating System (Windows 7). The last time I backed up was on the 17th of this month. Subsequent to that, I reverted to that backup several times, without changing it at all.

Now, today, I decided to revert my system to that backup once again and behold: Login Process Initialization failure.

How could this effect my backups? I backed up my system BEFORE I ever even encountered this error.

On top of that, the ASUS recovery disc I have can't read the HDDs. (The HDDs are working fine, they've been tested).

I tried the repair disc. And, these system recovery discs just suck. It won't even work.

I even tried reverting to a backup I made several months ago.... same error. How is that even possible?

I tried reverting to a backup I made back in February, and the operating system boots perfectly; however, for some reason, it's unstable. (It wasn't unstable before, and I have it backed up on 3 Hard Drives). Additionally, nothing can be installed and some of the programs are missing in the Uninstall List. :shock:

Oh! One more thing! To prove that the ASUS recovery disc is being stupid, I actually found a Windows Vista install disc and just loaded it to see if it was able to read the two internal HDDs. It read them perfectly and when I clicked install, it began to install. (I cancelled it right away as it was only for testing).

When attempting to install the restore disc, selecting the option to install to the entire HDD, I get the following error:

Access Violation at address 00405045 in module 'PERecover.exe Read of address 0000000C'

 

[centaur78]

Are you still having the "Logon Process Initialization Failure" ??

Second you just mentioned Windows ..... is it RTM or SP1 ???

 

[Anesthetic]

Are you still having the "Logon Process Initialization Failure" ??

Second you just mentioned Windows ..... is it RTM or SP1 ???

I believe SP1. It's all up to date.

 

[centaur78]

Are you still having the "Logon Process Initialization Failure" ??

 

[Anesthetic]

Are you still having the "Logon Process Initialization Failure" ??

Yes, that is correct.

 

[centaur78]

Well try this fix for big daddy

and let us know how it goes

 

[Anesthetic]

Well try this fix for big daddy

and let us know how it goes

Oh yea, btw, I am getting this error message prior to the logon screen. I can't even boot into windows. This error doesn't go away and I have to do a hard shut down in order to turn the PC off. So, it doesn't look like I'd be able to install anything.

 

[centaur78]

are you able to get into safemode ?

 

[Anesthetic]

are you able to get into safemode ?

That is negative. =\

 

[centaur78]

Al right

Try the Windows 7 disk and go into repair option and use the command prompt to do

SFC /SCANNOW

Let me know what you get with this ??

 

[Anesthetic]

Okay. After screwing around with the partitions, it seems that the Disk wanted to install to the backup HDD instead of the one the OS was originally on. I am thinking the backup software might have had something to do with it? Not sure?

But anyways, within the clean install, I did what you said and this happened: Windows Resource Protection found corrupt files and successfully repaired them. Detailes are included in the CBS.log.

I have attached the log.

How are these errors occurring in a clean installation? Also, I tried to switch the Disks: 0 to 1 and 1 back to 0, but I'm not clear on how to do that correctly. I don't like this OS being on the newer HDD. This newer HDD is for backups.

 

[centaur78]

hmm bit confused now !!

If you did sfc /scannow... you should now be able to login...

but... if you are doing a clean install.... there is no need to do sfc...