Welcome screen: Logon, then immediate logoff. Can boot safe mode.

[gregrocker]

What we know for sure is that if you invest further time now in a Clean Reinstall Windows 7
following those steps for drivers and other best practices, and using only the tools and methods given, you will get and keep a perfect install for as long as you do.

This compiles everything that's worked best in tens of thousands of installs we've directly helped with here during which time this became the top tech forums in history. Over 1.5 million consumers have used that tutorial without a single complaint or return problem - if they stick only with the steps, tools and methods given.

Be sure to delete all partitions during the booted install. Test performance after each phase of install - getting online, installing all Updates, supplying any drivers missing after Updates, installing each program, making each setting change. This will allow you to pinpoint any Update, driver, program or setting that is causing the problem if it recurs. We can help you do this in real time.

You'll want to pay close attention to drivers because Safe Mode most often works due to a third party driver that isn't loading. So I'd install the Updates driver first, test performance, then install the rest of Updates in small groups after which you test performance. Finally test performance after installing each driver still missing in Device Manager.

 

[steve1066]

A search of my registry has found several entries such as these:

Key Name: HKEY_USERS\S-1-5-21-2337138864-3731227399-2134062496-1001_Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache
Class Name: <NO CLASS>
Last Write Time: 7/17/2015 - 1:31 PM


Value 51
Name: E:\userinit.exe
Type: REG_SZ
Data: Userinit Logon Application

They all reference a nonexistent E: drive. I don't know about these things myself so I'm asking:

Would changing and/or deleting these entries 1.) be a good idea, 2.) be a bad idea, or 3.) make no difference one way or the other?

Edit: more info

This webpage discusses a very similar situation.

After Cloning A Drive Windows Logs Off As Soon As You Log In

Cause Of The Instant Log Off – When you login, the Winlogon process tries to run the userinit.exe file which, in turn, runs logon scripts and starts Explorer – the Windows user interface i.e. the desktop. In typical systems, Winlogon looks for this userinit file in the C:\Windows\System32 folder.
In our cloned drive scenario, Windows has reassigned the drive letter of the boot volume – instead of C: it is now something else e.g. F: drive. Therefore, Winlogon can’t find userinit (because it is now located in F:\Windows\system32 instead) so Explorer can’t load and the only option is to log you back off.

 

[NoelDP]

Safe Mode basically boots with an absolute minimum of the necessary drivers to be able to run Windows - most services are also disabled.
You can try booting to Safe Mode, then using MSConfig to set a minimal Clean Boot to Normal mode - see this article...
http://support.microsoft.com/kb/929135
If that boots OK, then re-enable a few drivers/services at a time until you find what kills the system - then disable that one and continue the re-enabling in stages.
That way you should find the problematic one(s)

Let's have a look at your event logs...
Please open Event Viewer
In the left pane, navigate to the Windows Logs
right-click on Applications and select 'Save all events as...' save as Apps.evtx
repeat for the System logs - save as Sys.evtx
Compress both files, and attach to your reply or upload to your favourite fileshare site (preferably Dropbox or OneDrive/SkyDrive)*and post a link in your reply

 

[steve1066]

Tried clean boot didn't help.

Reinstalled.

So it goes.

 

[NoelDP]

Oh well...
Good luck with the new install!

 

[gregrocker]

How is performance now?

Any drivers still missing after all Updates installed?

 

[GokAy]

Since you opted for the re-install, make sure to backup/image your System Reserved (if there is one) and C partitions.
http://www.sevenforums.com/tutorials/73828-imaging-free-macrium.html

Keep the first one you create. Also make another one every week/2 weeks/month depending on how much your system change. And keep, say, the last 3-4 backups. This way you can always fall back to a backup in a matter of minutes if something mess up instead of trying to troubleshoot for days. Ask here or in the tutorial thread if you would have any questions.