#Bootrec /rebuildbcd fails how to

In Server 2003 I would usually just have to play with the boot.ini if there was an issue, but I'm not sure how to resolve in Server 2008 R2. Windows decided to force an update that Ive repeatedly declined, restarted my machine in the middle of doing something, and sent it into a boot loop. I understand that this is really a function of Server 2008, and I am just looking for some help in case I need to do this again. I've tried booting into the 2008 R2 ISO and doing some repair commands like StartRep, and bcdedit. Info: The boot selection failed because a required device is inaccessible. If you do not have this disc, contact your system administrator or computer manufacturer for assistance. If either of these options works, use Event Viewer to help identify and diagnose the cause of the boot problem. On the Advanced Boot Options screen, try to start the computer in Safe Mode or Safe Mode with Networking. Choose your language settigns, and then click 'Next.' Scenario 1: Try to start the computer in Safe mode or Last Known Good Configuration. Insert your Windows installation disc and restart your computer.Дў. A recent hardware or software change might be the cause. Upon boot, it goes into Windows Boot Manager and says: Note: If you have important files and data stored on the unbootable computer, you may recover important files from the computer by using a professional data recovery software. I tried this with Server 2008 R2 and ESXi 4.1 and now my VM is failing to start. If not, the bootrec /rebuildbcd device cannot be found Windows 10 issue could occur. You remember how in Server 2003/XP you could power down a VM and attach the boot VMDK to a helper VM as a secondary drive and read/write to it? Then you could power down the helper VM, remove the VMDK, and the original VM would boot with no issues?