Copying the userinit.exe file back again fixed the problem... should have tried that before
Just to add to this, I had a customer yesterday with the exact same problem.
In the end I had to extract the hard drive and install it as a slave drive, then load up the Registry hive using this guide. Interestingly when navigating to theThe Userinit entry was there, but the value was completely blank! It clearly creates the same problem as removal of the spyware itself.Code:HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
I then entered the value:
and then unloaded the hive which solved the problem. Interesingly Microsoft themselves don't seem to document this technique.Code:C:\WINDOWS\system32\userinit.exe,
There are currently 1 users browsing this thread. (0 members and 1 guests)