DonationCoder.com Forum
Main Area and Open Discussion => General Software Discussion => Topic started by: techidave on August 11, 2012, 08:07 AM
-
Yesterday my Win 7 Pro desktop was stuck in a "Installing 1 of 14 updates" for hours... like 8 hours. I (grudgingly) powered it down thinking it was stuck. And now when powering up it is stuck at "loading desktop".
Is there a fix without reloading windows?
-
i don't know the solution, but most likely yes, so don't panic. im sure you're not the only person to suffer this.
-
Can you get into Safe Mode and maybe try something like System Restore?
-
system restore is turned off. I have not tried safe mode yet. I just wondered what my options were.
-
Boot into safe mode with command prompt and run sfc /scannow
-
Well things are looking up. After a good ol' fashion shutdown and turn back on, things are finally working.
Guess I panicked too soon.
thanks for the help!
-
You might want to turn on system restore, also. That has saved me more times than I can count.
-
You might want to turn on system restore, also. That has saved me more times than I can count.
-wraith808
+1 :Thmbsup:
-
+2 :Thmbsup:
Actually I have come across this issue a number of times and booting into safe mode and then restarting often seems to reset something. Failing that System Restore can be a really good fall back.
Unless you make daily image backups turning off SR is asking for trouble!
-
Short of a full-on System Restore being that there was not a successful logon, Last Know Good Configuration is/would be the quickest option.
-
I don't think LKGC works if System Restore is switched off - might be wrong but I thought it was tied to SR ?
-
AFAIK the saved data that LKGC uses is dynamically updated after each successful boot regardless of whether SR is enabled or not. The problem it has for general systems problem solving is it only has a limited timeframe where the 'last known' might still be useful. Because once you get to a desktop (even a screwed up desktop) that becomes your current last known 'good' config.
SR was created to get around this problem since SR tracks key registry data plus a whole lot more, making for a higher chance of getting a good outcome.
So for dealing with an unsuccessful bootup that's keeping you from getting to the desktop LKGC works pretty well. I've had about an 80% success rate with it for that. But if you do get to the desktop, and hang once you're there, your only options are to either do a safe boot and try to fix whatever the problem is, or do an SR if you're really stumped.
-----
Note: I don't know if it's true or not, but I was told that immediately rebooting and seeing a problem go away following a system update isn't unusual. That trick works for a JOOTT situation whenever a system update didn't completely or successfully install. Supposedly there's a built-in mechanism for checking, and if Windows detects an update didn't complete, it will rerun the update prior to fully booting up and: "problem solved."
Makes sense if it really is so.
-
AFAIK the saved data that LKGC uses is dynamically updated after each successful boot regardless of whether SR is enabled or not.-40hz
Correct, the Clone Control Set is automatically generated regardless of SR's config. That's why the registry has 3 copies of the Current Control Set.
The problem it has for general systems problem solving is it only has a limited timeframe where the 'last known' might still be useful. Because once you get to a desktop (even a screwed up desktop) that becomes your current last known 'good' config. -40hz
True the LKGC is updated by/to the CCS during login, but I don't think immediately after the login is accepted ... As I have gotten away with it a time or two when the login was freezing quickly. Granted those could have been flukes.
-
^Agree. It's definitely not when wGINA or the newer WinCP passes the user credentials. There's a slight lag in there somewhere. I think WE has to be fully active and the desktop at least partly loaded before the control set gets updated. You do get the occasional break that way.
8) :Thmbsup: