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

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

  1. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    7
    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: May 14, 2018
  2. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    7
    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:
    7
    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]

    [​IMG]

    [​IMG]
     
    Last edited: May 15, 2018
  4. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    7
    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:
    7
    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:
    584
    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:
    7
    Thanks for the response. The ID is 285393140, look forward to an analysis.
     
  8. MalcolmH2

    MalcolmH2 Bit Poster

    Messages:
    7
    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.
     

Share This Page