Shulou(Shulou.com)06/02 Report--

Real case: a vm does not start properly on esxi. Boot to Checking file system on C:. If you try to enter Safe Mode, you will not be able to enter the Windows system either.

Solution: edit the registry of the VM that fails to boot and skip boot automatic detection of disk C.

Some students want to ask, the system can not get in, how to edit the registry? Don't worry, here are the details of step, which you have stepped on every day. Welcome to reprint and give likes!

Detailed steps:

There will be a malfunctioning VM. Let's call it VM01. Turn it off. Find a vm that can be started normally, we call it VM02, and turn off the VM02. After VM02 shuts down, right-click VM02 and select Edit Settings. Click VM Options and select Advanced > Edit Configuration > Add RowInsert a new row with the name devices.hotplug and a value of false.On the Virtual Hardware tab, select Existing Hard Disk from the New device drop-down menu and click Add.

Then select the .vmdk file for the faulty VM01. Click OK to save the configuration. Click PowerOn, power on VM02, and log in to the system. Open the registry with administrator privileges. Registry of load malfunctioning VM01: select KHEY_LOCAL_MACHINE first

13. Select File- > Load Hive...

14. A file path selection box will pop up. Note that this path is the system disk of the VM in question, pointing to this path:\ WINDOWS\ SYSTEM32\ CONFIG\ SYSTEM

15. Click Open, you will be asked to enter the name of the hive, just enter one, here I enter is: VDI19

16. Then expand:

\ CurrentControlSet001\ Control\ Session Manager\ BootExecute

Change the value of BootExecute to: autocheck autocheck / KRV C *

17. Similarly, expand\ CurrentControlSet002\ Control\ Session Manager\ BootExecute, if any

Change the value of BootExecute to: autocheck autocheck / KRV C *

18. Click Save.

19. Click File- > Unload Hive...

20. Remove the disk of the faulty VM that you added earlier

21. Remember: do not be cheap, do not check Delete files from datastore, otherwise there is nothing, what you have done before is futile!

twenty-two。 Click OK to save.

23. Go to the original malfunctioning VM, click PowerOn to boot, this time you will soon arrive at the Welcome interface of Windows. At this point, the problem is solved.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.