locked
excessive number of PCs with "windows failed to start" status: 0xc000000e RRS feed

  • Question

  • Several of our Windows 7 Enterprise PCs have been coming in with the following message at boot:

    Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
    1. Insert your Windows installation disc and restart your computer.
    2. Choose your language settings, and then click "Next."
    3. Click "repair your computer."

    If you don't have this disc, contact your system administrator or computer manufacturer for assistance.

    Status: 0xc000000e

    Info: The boot selection failed because a required device is inaccessible.

    I know how to repair the PCs.

    What I need to know is how to find out what is causing this?  Better if you can point to a smoking gun that is currently causing this.

    We want to get ahead of this as we have many traveling users and have now been burned by having the issue happen while they were traveling.  We have also been seeing a couple return customers for the repair.

    Any help or guidance on finding the answer is much appreciated.


    The truth in truth is a terrible jest. --Blitzen Trapper

    Monday, December 7, 2015 10:03 PM

Answers

  • Hi,

    When your computer starts, the system BIOS begins to check a pre-determined list of drives and devices that might contain an operating system (Windows 8 or Windows 7). Normally, the computer boots from your primary hard drive, or a boot device that you have selected, where the operating system is stored. If the boot device is damaged, or if the computer attempts to boot from a different device, the operating system does not start up and you receive an error message.

    Or more simply: this error happens when Windows’ BOOTMGR tries to load the Boot\BCD registry (master boot record), but it’s either corrupted or has a bad configuration. At this step the boot loading process simply stops and the status code appears.

    Therefore, if some app or manually modify the BCD might cause this issue. For client, you can restrict user from running untrusted application or use policy to limit. For your reference: https://technet.microsoft.com/en-us/magazine/2008.06.srp.aspx?pr=blog


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    • Proposed as answer by Allen_WangJF Monday, December 21, 2015 11:40 AM
    • Marked as answer by Deason Wu Wednesday, December 30, 2015 8:13 AM
    Wednesday, December 9, 2015 2:18 AM

All replies

  • Do you use disk encryption, any changes/upgrades to the client, what about DLP or anything else that limits/monitors drive activity? Did you have any mass BIOS upgrades or changes to the BIOS settings with a script or managing back-end?

    Jack

    Monday, December 7, 2015 10:06 PM
  • No encryption.

    No consistent upgrades/updates that I noticed.  I haven't been able to replicate on a test system, anyways.

    No DLP and the like.

    No to the mass BIOS updates.


    The truth in truth is a terrible jest. --Blitzen Trapper

    Monday, December 7, 2015 10:15 PM
  • Hi,

    For your question, please run BCDEDIT tool to check the device value. If it display unknown, please modify the BCD store or rebuild it.

    Please try below steps:
    1. Boot to the Windows DVD
    2. Select Repair your computer---> Command Prompt, run "X:\sources\recovery" and type "bcdedit" to list Boot manager and boot loader.
    3. At the command prompt, type the following commands pressing the Enter key after each line(c: is the default system partition. If you original partition was another drive letter, this value can be set to that drive letter):

    bcdedit /set {DEFAULT.EN_US} device partition=c: 
    bcdedit /set {DEFAULT.EN_US} osdevice partition=c: 
    bcdedit /set {BOOTMGR.EN_US} device partition=c:

    4. Reboot the system after removing the OS disk.

    If it failed, we might need use bootrec to rebuild BCD. Open CMD after boot to Windows DVD and select repair computer, run following command and press Enter key after each line:

    bootrec /FixMbr
    bootrec /FixBoot
    bootrec /RebuildBcd

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    Tuesday, December 8, 2015 9:20 AM
  • Is this a repair or info towards a cause?

    Will running this on all 700 PCs make this problem not appear/reappear?

    Currently, on PCs with this error, I choose the repair link from the Boot Disk and get a prompt to repair and restart.  This fixes the issue.  Would doing the above be more permanent?

    My original questions were: What is causing this?  How can I prevent this from occurring?


    The truth in truth is a terrible jest. --Blitzen Trapper

    Tuesday, December 8, 2015 3:54 PM
  • Hi,

    When your computer starts, the system BIOS begins to check a pre-determined list of drives and devices that might contain an operating system (Windows 8 or Windows 7). Normally, the computer boots from your primary hard drive, or a boot device that you have selected, where the operating system is stored. If the boot device is damaged, or if the computer attempts to boot from a different device, the operating system does not start up and you receive an error message.

    Or more simply: this error happens when Windows’ BOOTMGR tries to load the Boot\BCD registry (master boot record), but it’s either corrupted or has a bad configuration. At this step the boot loading process simply stops and the status code appears.

    Therefore, if some app or manually modify the BCD might cause this issue. For client, you can restrict user from running untrusted application or use policy to limit. For your reference: https://technet.microsoft.com/en-us/magazine/2008.06.srp.aspx?pr=blog


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    • Proposed as answer by Allen_WangJF Monday, December 21, 2015 11:40 AM
    • Marked as answer by Deason Wu Wednesday, December 30, 2015 8:13 AM
    Wednesday, December 9, 2015 2:18 AM
  • review the event log for recent update, some update may not even show here
    Friday, December 11, 2015 3:50 AM