Windows Server 2008 R2 Hyper-V Virtual Machine failing to start after updates - black screen

I have restarted a Windows Server 2008 R2 Virtual Machine for windows updates yesterday.  The updates installed as normal, but upon restarting, the VM will not come up.  It starts to load windows for a second, and then goes to a black screen.  Two other VM's running on this machine came back up fine.  

I've tried booting to a Windows install cd, and going to the repair console.  chkdsk /f finds nothing wrong.  I've ran the command bootsect.exe /nt60 all /force with no change.  I've also tried this:

Type the command:
bcdedit
You should see the windows boot manager in one partition and the loader in another one.
If that is the case, then type the following commands and then reboot the guest:
bootrec /fixmbr
bootrec /fixboot
If that is not the case, try the following command and reboot the guest:
bcdboot d:\Windows  

(when booting to the windows cd it finds the main c: drive as D:, so thats why I used d: above)

Does anyone else have any other suggestions?  Its an exchange server so it'll be a ton of work to rebuild.  

Thanks,
rsoxhaterAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

A KarelinCommented:
Can you load in safe mode or command line?
0
rsoxhaterAuthor Commented:
Safe mode does not load.  I can get to command line via "Startup repair" or via the windows install dvd then choose repair your computer.
0
A KarelinCommented:
try to uninstall last updates
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

rsoxhaterAuthor Commented:
The virtual machine does not load or come up, I did try last known good configuration with same result.
0
A KarelinCommented:
you can try uninstall by command line
0
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
How long was the VM left in this state before throwing in the towel?

I suggest the following, hoping your backups are good,:

Boot to OS ISO and down to the command prompt.
C:
cd \Windows\winsxs
ren pending.xml pending.xml.BAD
exit

If the VM does not exit after the above reboot it using the GUI.
0
rsoxhaterAuthor Commented:
this is the startup repair result, you were right about the patch it seems:

Root Cause Found:

A patch is preventing the system from starting.

Repair Action: System files integrity check and repair
Result: Failed. Error code = 0xa
Time Taken = 5406 ms

Is there way to see what update caused it?
0
A KarelinCommented:
Do you have WSUS? You can see last updates in your WSUS and try to uninstall them one be one.
0
rsoxhaterAuthor Commented:
WSUS for the desktops, I've always done the servers manually.
0
A KarelinCommented:
I have always done too. I use WSUS for servers and desktops, and for servers only like for reports and check states.
0
rsoxhaterAuthor Commented:
Renaming the pending.xml above let me run sfc /SCANNOW /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows.  It found the errors in the cbs.log file.   I had this same issue (although the system would boot) on a windows 7 with the cbs.log after the december updates.  

http://support.microsoft.com/kb/3004394
0
rsoxhaterAuthor Commented:
ok, I was able to get the server back up.  I renamed pending.xml.bad back to pending.xml.  Found this command to revert updates, it was for windows 7 but worked fine on Server 2008R2

dism.exe /Image:c:\ /Cleanup-Image /RevertPendingActions

Changed the c to d since it was mounted as D in the recovery console.  Let it run through, and restarted.  Chose start windows normally, windows booted, did its thing to revert the updates, and I was able to login.  

I will definitely get in the habit of snapshotting before restarting for updates on the VM's.  Thank you both for the help.
0
rsoxhaterAuthor Commented:
And for anyone else finding this, I ran that command from the x:/sources/recovery folder on the 2008R2 dvd, not sure if it matters where its run from.
0
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Just keep in mind that a snapshot creates a differencing disk that continues to grow until changes are committed to the parent disk by deleting the snapshot.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hyper-V

From novice to tech pro — start learning today.