Windows 10 Bootcamp not booting - winload.exe Error Code 0xc000000e [SOLVED]

Discussion in 'Installation and Configuration' started by MalcolmH2, May 14, 2018.

  1. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    Windows 10 Bootcamp - Latest version (10.0.16299.371) - retail, digital licensed version, not preview version, mainstream channel
    Parallels 13.3.0 (43321)
    Bootcamp partition boots fine from restart, hold option, choose partition.
    VM Bootcamp that was working a couple of months ago, now returns BSD:
    Recovery
    Your PC/Device needs to be repaired
    File: \windows\system32\winload.exe
    Error code: 0xc000000e[​IMG]
    --
    Have tried bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd from Recovery USB drive. No change.
    Mounted EFI partition ( k ), tried bcdboot C:\Windows /l en-us /s k: /f ALL. No change.
    Think this may be red herring as booting in EFI mode? Don't know much about this though. See bootloader is winload.efi not winload.exe. Why does Parallels look for winload.exe and not via winload.efi? Have tried the vm.bios.efi=0 flag and also vm.bios.efi=1, the true flag results in the EFI shell screen. Maybe this is the issue? somehow the EFI loader is not working?
    [​IMG]
    Using EasyBCD can get the following info:
    Windows Boot Manager
    --------------------
    identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    device partition=\Device\HarddiskVolume4
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-us
    inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default {b33e53c1-57e4-11e8-b408-a73c84e26bbf}
    resumeobject {b33e53c0-57e4-11e8-b408-a73c84e26bbf}
    displayorder {b33e53c1-57e4-11e8-b408-a73c84e26bbf}
    toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout 10

    Windows Boot Loader
    -------------------
    identifier {b33e53c1-57e4-11e8-b408-a73c84e26bbf}
    device partition=C:
    path \windows\system32\winload.efi
    description Windows 10
    locale en-us
    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \windows
    resumeobject {b33e53c0-57e4-11e8-b408-a73c84e26bbf}
    nx OptIn
    bootmenupolicy Standard

    --
    Disabled SIP on Mac. No change.
    Tried recreating VM, minimal settings - no USB 3.0, directx 9, etc etc. No change.
    Tried turning off Fast Startup in Windows Power Settings. No change.
    Cleaned Windows hard drive of Windows.old. No change.
    System Integrity check, including DISM, all good.

    Seems to be related to Parallels, as it was working a couple of months ago, now just loaded up and no go. So maybe Windows updates have broken?

    If I change the Partition list to just the EFI partition and set the flag to vm.bios.efi=1
    I get a different error, which references the efi, which maybe is an improvement???
    [​IMG]
    F8 doesn't do anything.
    Any suggestions? I need this urgently for work...
     
    Last edited: Mar 3, 2019
  2. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    After a whole day of trying to track this @#$@#% down, I found that setting the Hard Drive in the settings to Source: Disconnected (plus both partitions, and SATA 0:1) allowed the VM to boot! urgh...

    EDIT - Nope it's back. Far out. So I'm not sure how this setting affected the boot, but I was able to boot for a couple of times. Trying to setup another VM that boots reliably... seems weird that this setting would work.
     
    Last edited: May 15, 2018
  3. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    OK restored the VM that worked.
    I've got two identical VM's, one works the other doesn't. Both have exactly the same settings as below:
    So this seems like some kind of bug.

    After some more experimenting, it seems if I try to change any setting in the VM that is working, it stops working. Sometimes it flashes up a DFInitialiseFailed (or something... grey text on black background... very fast so not sure exactly what it says)[​IMG]
     
    Last edited: Mar 3, 2019
  4. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    I can not get Bootcamp to work on Parallels. Is anyone experiencing this issue? Bootcamp works fine outside of Parallels, but none of my VM's for Bootcamp work at all (ie Parallels is useless to me and has been for months... I don't use it very often, but tried again today and still no update and can't use Parallels 13)

    Recovery
    Your PC/Device needs to be repaired
    File: \windows\system32\winload.exe
    Error code: 0xc000000e
     
  5. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    I've tried every combination I can think of. My only hope is I can some how manually configure the VM via Show In Finder>Show Package Contents and somehow tweak the settings to get it working again, but I don't know where to start. Nothing immediately stands out.

    Nothing really in log as far as I can see, VM loads up ok, but Windows doesn't boot. Blue screen is from Windows though (but not responsive)

    11-08 18:35:02.922 F /vm:5231:102411/ Virtual machine is ready to boot!
    11-08 18:35:02.935 F /monitor/ [SATA0:0] port stop req=0x00000000 st:1123342 gt:64
    11-08 18:35:02.936 F /monitor/ [SATA0:0] port stop req=0x00000000 st:1123343 gt:68
    11-08 18:35:02.944 F /monitor/ [SATA0:0] port stop req=0x00000000 st:1123351 gt:83
    11-08 18:35:02.945 F /monitor/ [SATA0:0] port stop req=0x00000000 st:1123352 gt:86
    11-08 18:35:03.066 F /vm:5231:20995/ VM state(VmStateRunning): enqueued 'DspVmStateInfo'(3028) command
    11-08 18:35:03.067 F /vm:5231:33795/ VM state(VmStateRunning): completed current 'DspVmStateInfo'(3028) command with result 0x0
    11-08 18:35:03.093 F /vm:5231:20995/ VM state(VmStateRunning): enqueued 'DspCmdVmInitiateDevStateNotifications'(1024) command
    11-08 18:35:03.099 F /vm:5231:33795/ VM state(VmStateRunning): completed current 'DspCmdVmInitiateDevStateNotifications'(1024) command with result 0x0
    11-08 18:35:03.100 F /vm:5231:20995/ VM state(VmStateRunning): enqueued 'DspEvtNotifyVm'(3014) command
    11-08 18:35:03.101 F /vm:5231:33795/ VM state(VmStateRunning): completed current 'DspEvtNotifyVm'(3014) command with result 0x0
    11-08 18:35:03.150 F /HostUtils:5231:36359/ [TSC frequency] host OS: 3058999610 Hz
    11-08 18:38:24.668 F /vm:5231:20995/ VM state(VmStateRunning): enqueued 'DspEvtNotifyVm'(3014) command
    11-08 18:38:24.669 F /vm:5231:33795/ VM state(VmStateRunning): completed current 'DspEvtNotifyVm'(3014) command with result 0x0
    11-08 18:38:26.052 F /vm:5231:20995/ VM state(VmStateRunning): enqueued 'VmLocalCmdKill'(20008) command
    11-08 18:38:26.052 F /vm:5231:33795/ VM state(VmStateRunning): changed to VmStateStopped
    11-08 18:38:26.052 F /vm:5231:102927/ VM state(VmStateStopped): enqueued 'VmLocalEventCpuStopped'(20031) command
    11-08 18:38:26.052 F /vm:5231:103183/ VM state(VmStateStopped): enqueued 'VmLocalEventCpuStopped'(20031) command
    11-08 18:38:26.052 F /vm:5231:103183/ VCPU2 state(VcpuStateRunning): changed to VcpuStateStopped
    11-08 18:38:26.052 F /vm:5231:102927/ VCPU3 state(VcpuStateRunning): changed to VcpuStateStopped
    11-08 18:38:26.053 F /vm:5231:33795/ SARE state(SareStateStart): enqueued 'SareCmdTerminate'(8) command
    11-08 18:38:26.053 F /vm:5231:33795/ Terminating CPU #3 ...
     
  6. Sathiya@Parallels

    Sathiya@Parallels Staff Member

    Messages:
    733
    Hello MalcolmH2. Please reproduce the issue, generate a Technical Report ID while the error message is being displayed (very important) and reply with the report ID number.
     
  7. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    Thanks for the response. The ID is 285393140, look forward to an analysis.
     
  8. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    Just bought Parallels 14 upgrade in case that fixed it, nope exactly same problem.
    Have issued another technical report, this time from Parallels 14. The ID is 285822560.
     
  9. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    Please inform whether there is a fix forthcoming for this. I haven been through multiple levels of support and neither Parallels 13 or 14 is working for my situation (I want to use Windows 10 & Mac in parallel - Windows is a bootcamp drive). I upgrade from 13 to 14 in the vain hope that it would fix the problem...

    I note another thread with what appears to be the same issue: https://forum.parallels.com/threads/win10-boot-camp-wont-boot-in-parallels.342774/page-3

    Have been waiting for 3 months now, lodged a Technical Support ticket 22nd November 2018 and it is now 4 March 2019.... still no correspondence or followup (support says... problem is known... no fix raised to higher level support.

    29th November after multiple LogMeIn sessions and remote attempts by Parallels Support:
    "Due to the complexity of the issue, it is now investigated along with our Development Team in the internal case. They are continually working on the cases lifted by the Support Team, however, do not share an ETA required for a fix.

    It usually takes time to go into a complicated virtualization software. Yet, we will do our best to find a solution as soon as possible.

    Thank you very much for your patience and understanding. We will get back to you as soon as we have an update."
     
    Last edited: Mar 3, 2019
  10. Daisy2

    Daisy2 Bit Poster

    Messages:
    2
    Hi MalcolmH2, Have you fixed this problem yet? I find some solutions from a Chinese article, but I didn't test if it works.
    The first solution:
    Because my mac and windows are installed on different disks, I tried to change the physical disk where windows is located to MBR mode, and activated the partition where windows is located. At the same time, I modified the BCD file in the Boot folder of a windows partition. Use it to start C:\\windows\system32\winload.exe. After the change, the physical machine starts successfully. Going to Parallels Desktop is also a success!

    The second solution:
    The easiest way is to delete the original Boot folder under the windows partition. In this way, Parallels Desktop will call the UEFI startup item, otherwise it will start Windows in the traditional way! Even if I enter the startup item selection interface, manually start EFI/Microsoft/Boot/bootmgfw.efi, as long as there is a Boot folder under the partition, it will still report 0xc000000e error!

    Hope it helps!
    Daisy
     
    MalcolmH2 likes this.
  11. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    OMG blessings on you and your family! Been waiting for over half a year for Parallels to solve this and nothing.
    I've tried your second solution, but rather than deleting the Boot folder, I've moved it into a BootBACKUP folder. I've kept the vm.bios.efi=1 flag on and both the EFI and Bootcamp partitions are checked on the Hard Disk>Select Partitions menu.
    Anyway Windows 10 Bootcamp boots fine from restart, plus it works inside Parallels!!
    A simple fix in the end - thankyou!!
     
  12. Daisy2

    Daisy2 Bit Poster

    Messages:
    2
    No problem! I'm glad your problem finally fixed!!!! ;)
     
    MalcolmH2 likes this.
  13. AntonA1

    AntonA1 Bit Poster

    Messages:
    4
    Excuse me, but which "original boot" folder did you removed/renamed?
    /Windows/Boot?
    or /EFI/Boot?
    or /EFI/Microsoft/Boot

    I tried all folders, but the story is the same. I even tried to add "vm.bios.efi=64" to boot flags. (parallels 14)
     
  14. AntonA1

    AntonA1 Bit Poster

    Messages:
    4
    please, can you help with folders? (latest message)
     
  15. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    12
    Hi AntonA1. The Boot folder I'm referring to is at root level ie C:\Boot which I renamed to c:/BootBACKUP. Hope that works for you. Otherwise Daisy2 above other steps might work for you.
     
  16. AntonA1

    AntonA1 Bit Poster

    Messages:
    4
    [​IMG]

    But i don't have that folder. Look at the screenshot?
     
  17. AntonA1

    AntonA1 Bit Poster

    Messages:
    4
    Problem solved. The folder "Boot" was hidden. Thank you so much!
     

Share This Page