0xc0000001 at boot - Windows 10

I was under the mistaken impression that the system image backup and restore function that comes with Windows would be a good way to backup my partition. Turns out it doesn't play all that nice with at least some dual boot situations. Anyway, I got the restore to go, and straightened up the inconstancies with the partition tables. I have Windows 10 installed.


When I tried to start Windows, it went into an automatic repair loop. I found out how to disable that via bcdedit, but now I get a Blue Screen with a 0xc0000001 at boot.


chkdsk /r c: found some problems, but otherwise didn't help. Tried bootrec, that did nothing. sfc /scannow says something about a pending repair and refuses to run.


I'm not really sure where to proceed from here. The last thing I want to do is reinstall from scratch, since that defeats my purpose of making the system image. First thing I want to do is get sfc /scannow to run, then maybe I can look at replacing corrupted system files, or whatever might be the problem. I saw something about an offline scan for sfc, would that be what I'm looking for?

MacBook Pro (Retina, Mid 2012), OS X El Capitan (10.11.1)

Posted on Nov 3, 2015 3:48 PM

Reply
51 replies

Nov 5, 2015 4:19 AM in response to Sam Wilkins

From NeoSmart WiKi - https://neosmart.net/wiki/0xc0000001/ ....


Here are the steps to run

sfc
at boot:

  1. Boot from the install CD
  2. Select your language, time and keyboard method
  3. Select Repair your computer
  4. Select your operating system when the “System Recovery Options” box appears, but note down the drive’s letter (
    F:
    ,
    G:
    etc.). In our example this will be
    D:
  5. Select Command Prompt
  6. Type the following command with your hard drive’s letter:sfc /scannow /offbootdir=d:\ /offwindir=d:\windows
  7. When scanning is complete, type
    exit
    to quit the Command Prompt:exit
  8. Press Enter

Nov 5, 2015 10:59 AM in response to Loner T

Step 4 didn't exactly happen like it said it would, but I'm guessing it's because that was written for Windows 7. I used c: since that's the drive letter for my Windows.


It said it found corrupt files but it was unable to fix some of them, and that details are included in the CBS.Log. It also said that logging is currently not supported in offline servicing scenarios. Which I assume is why when I opened that file, the latest entry is October 17.


What can we do to find out what files need replacing? Is there a third party tool I can use, or some way to clear the flag that says a repair is pending?

Nov 6, 2015 8:37 PM in response to Sam Wilkins

I hope you haven't forgotten about me. I found some stuff about DISM, I'm thinking about trying it. I don't actually have a lot of faith that it will work. I'm mostly here because basically all of the solutions I've found for similar problems apply to Windows 7 or 8, and I'm not sure if I should be trying them with 10. But maybe there's not a whole lot of difference in this area of Windows between recent versions. Please let me know if that's the case.

Nov 9, 2015 5:08 PM in response to Loner T

Hi LonerT and Sam,


Don't mean to barge in. As LonerT knows I have a Mac Mini late 2012 running Win 10. I got stuck in the endless Windows 10 Repair, fix and reboot, repeat loop as well. It would not go away. and when I finally did get the desktop up, All test were fine until Power up or Restart. Ultimately, the only solution was to Remove Windows 10 and start all over again. Frustrating. El Capitan doesn't make it better, either until they update BCA.

Welcome to the new Windows blue screen of misery then death. 😠


Cheers!!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

0xc0000001 at boot - Windows 10

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.