完美解决 开机无法启动 提示0xc000000e（The perfect solution to boot can not boot prompt 0xc000000e）.docVIP

完美解决 开机无法启动 提示0xc000000e（The perfect solution to boot can not boot prompt 0xc000000e） The perfect solution to boot can not boot prompt 0xc000000e problem Abstract: This paper provides solutions to 0xc000000e problem and explain the principle, guarantee the perfect repair start menu, start menu will not become English or Chinese, and all startup items can be used normally. Keywords: Windows Vista SP1 Ghost 0xc000000e cant boot boot Description of the problem: C to use Ghost to restore the image file, the first boot after the restart is normal, black and white, prompt for: File: \Windows\system32\winload.exe Status: 0xc000000e Info: The selected entry could not be loaded because the application is missing or corrupt. Resolvent： Note: do not use the system according to the prompt repair of Windows Vista SP1 disk, or the start menu will become English, and which cannot be changed into Chinese. But this can only repair Windows Vista start, Windows XP cannot be repaired and a key Ghost start. With the reduction of Ghost image files to the C drive, if the CMD input Bcdedit /v for the first time to start to enter the WinPE, will show can not find the configuration file. We should start a system, everything is normal, after the restart will appear 0xc000000e error, and then use the WinPE disc to start the computer, WinPE system using the Ghost XP CD in the wind. The specific operation: CD into CD-ROM, press Ctrl + Alt + Delete, restart the computer. If Boot from CD/DVD automatically prompts... By default, please press the Enter key, the menu [B] WinPE into WinPE. WinPE is actually a CD version of Windows XP. There is a CMD on the desktop, click enter: (1) input C:, press enter, go to the C: disk. (Note: do not contain double quotes, below) (2) input CD Windows, go to C:\Windows. (3) input CD system32, go to C:\Windows\system32. (4) input Bcdedit /v, as shown below: -- -- -- Windows boot manager Employed The identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} Device unknown Des