I was hoping there would be smarter people here than I am.
I have a Windows 7 desktop that boots into black screen with mouse, no login screen. You can move the mouse but nothing else. Ctrl-Alt-Del, Ctrl+Shift+Esc, Windows+R, Esc, Alt+Tab and Win+Tab does nothing.
Similar to this case: Can't boot windows 7:(
I have a password, one user account.
I know that this is Windows corruption because I had a faulty power supply that shut down the computer multiple times in a row.
I know that my SSD is fine as well as rest of the parts. This is all because of the sudden shutdowns.
Booting in to Safe Mode results in same black screen with mouse.
Booting in to Safe Mode with low res video results in black screen with huge mouse that can’t be moved.
Booting in to Safe Mode with Command line gives you black screen.
Bootting from USB Win7 installation media and running Fix computer gives nothing.
Runing SFC /scannow /offwindir /offbootdir finds some errors, fixes some and cannot fix all. Now, if someone knows how to read CBS log that is generated while booted from USB installation media, that would be really helpful.
Returning to previous save point did not fix the problem.
I have installed Windows 10 to another SSD and Windows 7 to third SSD, just to see that everything works.
Since I have the second Windows 7 installation that is working, I can transplant files to the broken installation, but I do not know what the files are.
Running SFC from the second win7 installation says that it can not fix all the errors.
Runing DISM and then SFC gives same results.
Trying to read CBS log with findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt gives you an empty file.
I have a clone of the broken installation so I am willing to try anything and everything.
I have not yet tried to make another user account or tried to activate the Admin account.
I have not yet tried to see if user account has a backup registery, because this seems to me to be login service that is broken.
So, any help?
I am runing out of ideas and would really love to fix this installation instead of just reinstalling.
All the forums and threads about this problem have ended up in reinstall, but commoon, we are better than that. Or at least I hope one of you are.