Source: http://techreport.com/forums/viewtopic.php?f=6&t=83272
What is the longest time you've ever had to wait for Server 2008 or 2008
R2 to finish "Preparing to configure Windows. . . "? At this point it
got stuck for well over and hour and a 1/2 so I had to force shut it
down. Boot into safe mode which apparently did something enough to make
it boot up into Safe Mode (With and Without Networking). But whenever I
try to tell it to boot normally, I get that forever drawn out
"Preparing to configure Windows. . . " BS screen. I've attempted to
remove the Update Cache folder as I've read in multiple posts, but that
did nothing.
I'm at a point where I can either wait and hope that
this message isn't BSing me, or I can take a more proactive approach.
Anyone here have a solution to getting 2008 R2 to revert really quick
back to before the updates attempted to install, or has waiting a long
time paid off?
I've also seen notes regarding "Pending.xml"
Opening this file showed at the top that it had "Revert" = Yes, but I've
yet to see any progress on start up, thanks to Microsofts lack of
informational "progress bars", which don't even exist anymore. I've
read some places stating to delete it... others saying it would be a
huge mistake to do that since your system wouldn't be able to revert
changes on half installed updates. My "Pending.xml" is at 14-15MB,
which seems quite big for a file of that type /shrug.
/Sigh, why can't Microsoft just get their damn updates in orders
Source: http://techreport.com/forums/viewtopic.php?f=6&t=83272
Answer
Source: http://techreport.com/forums/viewtopic.php?f=6&t=83272
OK... Very presumptuous of you to post this not knowing the situation
fully. How about the customer didn't want to spend the cash to purchase
updated backup software, or even want me to come in to do anything as
of the last 6 months to save money? Yet I've managed on my own time to
make manual Acronis backups once a week. Its not my first option to try
restoring an image to a system, as that has nasty side effects
sometimes too, its a last resort. Hmmm, funny because all customers
want a full time tech, but they don't want to pay for one.
Anyhow,
I fixed the issue. Was able to get it to boot into Safe Mode. Removed
the SoftwareDistribution folder under C:/Windows (it rebuilds itself on
the next update process). I read enough to know DO NOT
remove or rename the "Pending.xml" file. Although this might get you
back into loading into windows, apparently it leaves your entire server
install dead in the water for all future updates, no way to patch it and
you have to backup/rebuild from scratch.
After removing the
"SoftwareDistribution" folder, I was able to disable Avast from the
services, which allowed windows to boot normally to the point where it
could revert the broken updates.
You know it really bothers the
heck out of me for you to jump the gun Ryu. Since when has the first
reaction of ANYONE on TR been to berate a member asking for assistance,
regardless of their situation. You should be ashamed to be a
moderator/admin and talking down to a member who simply asked for help
by the one group they trust for some help
Source: http://techreport.com/forums/viewtopic.php?f=6&t=83272
No comments:
Post a Comment