It was a temporary repair mode registry that disappears when you close the repair mode. Here is how to edit the real thing:. Thanks for the answer, I tried that, in step I tried step 9 as you said just in case. Normally starting windows led me to an auto chkdsk. And it's stuck in the same screen, please wait on the logon, turn black for a few seconds I see the pointer back to win 7 please wait, and so on and so on.
If Step 9 failed to fix the problem then it is caused by something other than the registry. If so then I have no fix other than a destructive Factory Restore. To avoid having to re-install everything you need to take out some "insurance" by creating an image of your installation and updating it once or twice a year.
There certainly is. You need to boot the machine back into Repair Mode as before, search for the system drive as before, then run regedit. Whether this will do any good I do not know. Make sure to create a backup copy of the registry before you start. Something I wanted to do a couple of times, maybe you can help me. I remember on XP there was a step on the installation using the installation disk that detected current windows installs on disk and asked you to press X can't remember now if you wanted to repair that installation.
There was a couple of times where I had corrupted or missing windows files, and windows wouldn't boot in either normal or safe mode that this repair fixed the problem.
Can't this be done on 7? Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows 7 Miscellaneous. Use this forum to discuss miscellaneous issues that cannot be covered in any other Windows 7 forum.
Sign in to vote. Wednesday, November 7, PM. Here is how to edit the real thing: Boot into Repair Mode. I can get into safe mode, but beyond that it's hit and miss. I have gone over a few articles, and I've tried a few things with temporary results. When it first happened, I ran Start Up Repair and it proceeded to the login screen. The next day it stuck at Please Wait again, so I ran sfc. That time it allowed me to login twice I believe. It stopped again the next day, and everything has been a hit and miss trial.
Occasionally it will allow me to login, but not even close to consistently. I found multiple hotfixes, but everyone I try either says the update is not applicable, or it will start to install, and then simply say the update was not installed.
This machine is the only one experiencing the issue on the domain. In addition, I had read a few times that a possible cause was WMI and one its repositories building up too much, or something along those lines. I believe this rules out another cause, and my only idea.
The last thing I tried was disabling IPv6, which I heard could fix the issue, and got nothing. I want to avoid just wiping and reloading Windows, since all of the user's data is on the local machine. Any advice? Wednesday, January 22, PM. Hi, Thank you for your update. You may check the System under Windows Logs. Right click the item you want to update and then select update driver software…… Hope it helps.
Thursday, January 30, AM. Hi, Please understand that there are lots of factors can lead to logon hang. What information appears in event logs Event Viewer? Based on the current situation, I would also suggest you try the following: 1. Perform a system restore using the Windows installation disc.
Refer the link provided below to run the system restore using the system recovery options.
