The device cannot be started because of the inexplicable appearance, and the option of attaching a boot grub MBR file cannot be started. Several binary files are displayed and the device cannot be found.
Probably because the file system is damaged, the very important file \ Boot \ BCD is damaged,
In the Windows nt6 boot system, the BCD file is more advanced than the previous boot. ini + ntldr + \ Windows Kernel File boot method, but it is also more troublesome.
1. The first method is relatively safe, but it takes time
Let's talk about how to fix it. I started the USB flash drive in win7 and started to fix the system. I didn't find the win7 system. But it was probably because the BCD file was seriously damaged ?? (However, It is disgusting that the menu can still be displayed, but it cannot be guided)
I fixed it like this. I started the USB flash drive with win7 and re-installed it to the original win7 file so that the original file was moved to Windows. Old ..
After installation, go to PE, Linux, MacOSX, and other systems, and. the four folders in old are moved out (users program programdata is ignored in Windows). Of course, you can move the new system to another folder or delete it directly.
Then restart and select the first windows7 to enter...
2. The second method requires support from another win system.
Since the BCD file is corrupted, you can just create one again ..
A simple method is to enter another system, use easybcd to create a new BCD, and then add windows7 to overwrite the original boot \ BCD file.
It seems that easybcd cannot be directly run in winpe. If you run easybcd, you may need to install other software;
In the future, it is best to add a BCD editing software to the winpe Maintenance System. It seems that there are such software under the PE, but generally there is no...