{"id":423,"date":"2013-08-25T12:32:20","date_gmt":"2013-08-25T17:32:20","guid":{"rendered":"http:\/\/neosmart.net\/kb\/?p=423"},"modified":"2016-11-12T20:24:52","modified_gmt":"2016-11-13T02:24:52","slug":"0xc0000001","status":"publish","type":"post","link":"https:\/\/neosmart.net\/wiki\/0xc0000001\/","title":{"rendered":"0xc0000001: Fix for Windows XP, Vista, 7, 8, 8.1, 10"},"content":{"rendered":"

Get the fix to the 0xc0000001: A required device isn’t connected or can’t be accessed<\/strong>\u00a0boot error message affecting Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1<\/strong> and\u00a0Windows 10<\/strong>.<\/p>\n

About the “0xc0000001<\/strong>” error<\/h2>\n

The following information on this error has been compiled by NeoSmart Technologies, based on the information gathered and reported by our global network of engineers, developers, and technicians or partner organizations.<\/p>\n

Description and Symptoms<\/h3>\n

The error messages, alerts, warnings, and symptoms below are tied to this error.<\/p>\n

Symptom 1: 0xc0000001 error screen on startup<\/h4>\n

The 0xc0000001 error can be caused by a wide variety of causes, with the most common one being system file corruption, or damaged memory. Alternatively, this error can also be caused by a missing or damaged SAM(Security Account Manager) system file.<\/p>\n

\"0xc0000001<\/a><\/p>\n

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: \r\n\r\n1. Insert your Windows installation disc and restart your computer. \r\n2. Choose your language settings, and then click \"Next.\" \r\n3. Click \"Repair your computer.\" \r\n\r\nIf you do not have this disc, contact your system administrator or computer manufacturer for assistance. \r\n\r\nStatus: 0xc0000001 \r\n\r\nInfo: A required device isn't connected or can't be accessed.<\/pre>\n
On newer system, another error screen is displayed instead:<\/p>\n
\"0xc0000001<\/a><\/p>\n
Windows Recovery Environment\r\n\r\nYour PC couldn't start properly\r\n\r\nA required device isn't connected or can't be accessed.\r\n\r\nError code: 0xc0000001\r\n\r\nYou'll need to use the recovery tool on your installation media. If you don't have any installation media like disc or USB devices, contact your system administrator or PC manufacturer.\r\n\r\nPress Enter to try again\r\nPress F8 for alternate boot options<\/pre>\n
Note that the exact error message may vary from case to case, but the error code for this error is always “0xc0000001”.<\/p>\n
Alternatively, you may also see an error message right after Windows loads:<\/p>\n
\"0xc0000001<\/a><\/p>\n
Security Accounts Manager initialization failed because of the following error: A device attached to the system is not functioning. Error Status: 0xc0000001. Please click OK to shut down this system and reboot into Safe Mode, check event log for more detailed information.<\/pre>\n
Causes of this Error<\/h3>\n
This error has been known to occur as a result of one or more of the following:<\/p>\n
Cause 1: SAM file is damaged<\/h4>\n
The SAM(Security Accounts Manager) file stores the user credentials data and is essential to Windows booting process. If that file is missing or corrupt, then the boot process is halted.<\/p>\n
Cause 2:\u00a0System files are\u00a0damaged<\/h4>\n
Sometimes, this error may occur when the key boot-related system files become damaged because of disk write error, power outages or virus attacks.<\/p>\n
Cause 3:\u00a0File system integrity compromised<\/h4>\n
Alternatively, this error appears when the whole file system gets damaged on a grander scale for the same reasons.<\/p>\n
Cause 4: RAM\u00a0is damaged<\/h4>\n
In the worst case scenario, the PC’s memory could be permanently damaged.<\/p>\n
Fixing “0xc000000e” on Windows<\/h2>\n
Windows Setup CD\/DVD Required!<\/strong>
Some of the solutions below require the use of the Microsoft Windows setup CD or DVD. If your PC did not come with a Windows installation disc or if you no longer have your Windows setup media, you can use Easy Recovery Essentials for Windows<\/a> instead. EasyRE will automatically find and fix many problems, and can also be used to solve this problem with the directions below.<\/p>\n
Fix #1: Use\u00a0Easy Recovery Essentials<\/h3>\n
Easy Recovery Essentials can fix many errors such as this automatically using its built-in Automated Repair option. EasyRE is currently available for Windows XP<\/strong>, Vista<\/strong>, 7<\/strong>, 8<\/strong>, Windows 10<\/strong>, and Windows 11<\/strong> and can be downloaded and created on any PC.<\/p>\n
    \n
  1. Download Easy Recovery Essentials<\/a>. Make sure to note your Windows version (XP, Vista, 7, 8, 10, or Windows 11) before you download EasyRE. This guide can help you identify what version of Windows<\/a> you have installed.<\/li>\n
  2. Burn the image. Follow these instructions on how to burn the bootable ISO image<\/a>\u00a0very carefully, as making a bootable CD can be tricky! Alternatively, these instructions explain how to create a bootable EasyRE recovery USB stick\/drive<\/a>.<\/li>\n
  3. Boot up your PC from the Easy Recovery Essentials CD<\/a> or USB you created.<\/li>\n
  4. Once EasyRE is running, choose the “Automated Repair” option and click Continue<\/kbd>.\n
    \"EasyRE<\/a><\/p>\n
    Choose “Automated Repair” in Easy Recovery Essentials<\/p>\n<\/div>\n<\/li>\n
  5. After EasyRE scans your computer’s drives, identify and select the drive letter for your Windows installation\u00a0from the list, and then click on the Automated Repair<\/kbd> button to begin.\n
  6. Easy Recovery Essentials will start analyzing the selected drive for problems. EasyRE will test for and attempt to automatically correct errors with the disk, partition, bootsector, filesystem, bootloader, and registry. No intervention is required, as EasyRE’s repair is fully automated:\n
    \"EasyRE:<\/a><\/p>\n
    Easy Recovery Essentials searches for errors and makes corrections to the selected Windows installation.<\/p>\n<\/div>\n<\/li>\n
  7. Once the process is complete, EasyRE will report its findings. Click on the Restart<\/kbd> button to reboot your PC and test the changes.<\/li>\n
  8. The “0xc0000001” error should now be fixed as your PC begins to load:\"EasyRE:<\/a><\/li>\n<\/ol>\n
    You can download Easy Recovery Essentials from here<\/a>.<\/p>\n
    Fix #2: Copy the SAM File from the Repair Folder<\/h3>\n
    If you’re able to login into Windows, copy the SAM file from C:\\WINDOWS\\repair to C:\\WINDOWS\\system32\\config<\/code>. To do that,\u00a0boot from a Windows Install CD, open a command prompt, and enter:<\/p>\n
    copy C:\\Windows\\Repair\\Sam C:\\Windows\\System32\\Config<\/pre>\n
    If asked whether you want to overwrite the original file, reply “Y”(Yes).<\/p>\n
    This will remove all login credentials your Windows copy has, including username and password and revert back to the original username that was added when you installed Windows.<\/p>\n
    \"SAM<\/a><\/p>\n
    SAM file restored from a backup<\/p>\n<\/div>\n
    Fix #3: Run chkdsk<\/h3>\n
    If the hard drive has its file integrity compromised, it is possible to use built-in Windows CHKDSK utility to scan the disk and fix the file system errors.<\/p>\n
    Here are the steps to run CHKDSK:<\/p>\n
      \n
    1. Boot from your Windows install disc<\/li>\n
    2. Click on Repair your co<\/strong>mputer<\/strong>\u00a0after selecting proper language, time and keyboard input.<\/li>\n
    3. Select the Windows installation drive, which is usually C:\\<\/code>, and click Next<\/strong><\/li>\n
    4. Choose Command Prompt when the System Recovery Options box appears<\/li>\n
    5. Write the following command and press Enter<\/kbd> afterwards:\n
      chkdsk C: \/f<\/pre>\n
      Replace C: with the letter of the driver where Windows is installed.<\/li>\n<\/ol>\n
      Here is an example of what the PC’s console output should look like once the chkdsk.exe is complete:<\/p>\n
      \"Chkdsk<\/a><\/p>\n
      Chkdsk utility results screen<\/p>\n<\/div>\n
      Fix #4: Check RAM<\/h3>\n
      Check if you recently added any new RAM modules. Users have reported that a new RAM module was the actual cause for this boot error. Replace the RAM modules to see if they are causing this error to appear.<\/p>\n
      Fix #5: Run sfc \/scannow<\/h3>\n
      On Windows Vista and Windows 7, it is possible to use the built-in Windows SFC(system file checker) tool to automatically scan a computer’s system files and repair them if necessary.<\/p>\n
      Here are the steps to run SFC:<\/p>\n
        \n
      1. Boot from your Windows install disc<\/li>\n
      2. Click on Repair your co<\/strong>mputer<\/strong>\u00a0after selecting proper language, time and keyboard input.<\/li>\n
      3. Select the Windows installation drive, which is usually C:\\<\/code>, and click Next<\/strong><\/li>\n
      4. Choose Command Prompt when the System Recovery Options box appears<\/li>\n
      5. Write the following command and press Enter<\/kbd> afterwards:\n
        sfc \/scannow \/offbootdir=D:\\ \/offwindir=D:\\Windows\\<\/pre>\n
        Replace D: with the letter of the driver where Windows is installed, and D:\\Windows with the Windows folder location.<\/li>\n<\/ol>\n
        Here is an example of what the PC’s console output should look like once the sfc.exe scan is complete and missing files are successfully restored:<\/p>\n
        \"System<\/a><\/p>\n
        System files\u00a0restored by the SFC utility<\/p>\n<\/div>\n
        Fix #6: Check\u00a0the HDD<\/h3>\n
        If the error is caused by damaged hard disk cables, try any of the following tips to fix the error:<\/p>\n