0xc000000e Error on Windows after Partition Resize

Thanks for your response, heres the output you looked for :

00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS .....|

00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 f0 7c 11 |........?.....|.|

00000020 00 00 00 00 80 00 80 00 ff 5f 3c 09 00 00 00 00 |........._<.....|

00000030 00 00 0c 00 00 00 00 00 02 00 00 00 00 00 00 00 |................|

00000040 f6 00 00 00 01 00 00 00 00 42 75 2e 81 75 2e b0 |.........Bu..u..|

00000050 00 00 00 00 fa 33 c0 8e d0 bc 00 7c fb 68 c0 07 |.....3.....|.h..|

00000060 1f 1e 68 66 00 cb 88 16 0e 00 66 81 3e 03 00 4e |..hf......f.>..N|

00000070 54 46 53 75 15 b4 41 bb aa 55 cd 13 72 0c 81 fb |TFSu..A..U..r...|

00000080 55 aa 75 06 f7 c1 01 00 75 03 e9 dd 00 1e 83 ec |U.u.....u.......|

00000090 18 68 1a 00 b4 48 8a 16 0e 00 8b f4 16 1f cd 13 |.h...H..........|

000000a0 9f 83 c4 18 9e 58 1f 72 e1 3b 06 0b 00 75 db a3 |.....X.r.;...u..|

000000b0 0f 00 c1 2e 0f 00 04 1e 5a 33 db b9 00 20 2b c8 |........Z3... +.|

000000c0 66 ff 06 11 00 03 16 0f 00 8e c2 ff 06 16 00 e8 |f...............|

000000d0 4b 00 2b c8 77 ef b8 00 bb cd 1a 66 23 c0 75 2d |K.+.w......f#.u-|

000000e0 66 81 fb 54 43 50 41 75 24 81 f9 02 01 72 1e 16 |f..TCPAu$....r..|

000000f0 68 07 bb 16 68 52 11 16 68 09 00 66 53 66 53 66 |h...hR..h..fSfSf|

00000100 55 16 16 16 68 b8 01 66 61 0e 07 cd 1a 33 c0 bf |U...h..fa....3..|

00000110 0a 13 b9 f6 0c fc f3 aa e9 fe 01 90 90 66 60 1e |.............f`.|

00000120 06 66 a1 11 00 66 03 06 1c 00 1e 66 68 00 00 00 |.f...f.....fh...|

00000130 00 66 50 06 53 68 01 00 68 10 00 b4 42 8a 16 0e |.fP.Sh..h...B...|

00000140 00 16 1f 8b f4 cd 13 66 59 5b 5a 66 59 66 59 1f |.......fY[ZfYfY.|

00000150 0f 82 16 00 66 ff 06 11 00 03 16 0f 00 8e c2 ff |....f...........|

00000160 0e 16 00 75 bc 07 1f 66 61 c3 a1 f6 01 e8 09 00 |...u...fa.......|

00000170 a1 fa 01 e8 03 00 f4 eb fd 8b f0 ac 3c 00 74 09 |............<.t.|

00000180 b4 0e bb 07 00 cd 10 eb f2 c3 0d 0a 41 20 64 69 |............A di|

00000190 73 6b 20 72 65 61 64 20 65 72 72 6f 72 20 6f 63 |sk read error oc|

000001a0 63 75 72 72 65 64 00 0d 0a 42 4f 4f 54 4d 47 52 |curred...BOOTMGR|

000001b0 20 69 73 20 63 6f 6d 70 72 65 73 73 65 64 00 0d | is compressed..|

000001c0 0a 50 72 65 73 73 20 43 74 72 6c 2b 41 6c 74 2b |.Press Ctrl+Alt+|

000001d0 44 65 6c 20 74 6f 20 72 65 73 74 61 72 74 0d 0a |Del to restart..|

000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

000001f0 00 00 00 00 00 00 8a 01 a7 01 bf 01 00 00 55 aa |..............U.|

00000200

Cathal.

So I mounted the EFI partition and had a look around, The Microsoft directory exists and so does the BCD file under :

/Volumes/EFI/EFI/Microsoft/Boot/BCD

I booted back into the Windows USB, but looking at diskpart, it doesn't see any volumes apart from the BOOTCAMP partition and itself on the USB stick.

Surely it would need to see or mount the EFI partition if it was to edit those files ?

I may be completely wrong though, thanks again for your help thus far.

I remember being at this point a day or two ago, but gave up as I could not see the EFI volume, so could not select it to assign it a drive letter. I assumed it was something Apple specific, so gave up on that idea and looked elsewhere.

Using diskpart I select Disk 0, and list volumes.

I get just 2, a 73 GB volume (BOOTCAMP), and a ~8GB one for the USB Stick.

If I list partitions I see a partition 200mb (EFI), a 139GB one (OSX), 619MB one(Apple recovery I assume), and Bootcamp.

I tried to assign the partition a drive letter, but it tells me I can only assign a letter to a volume. I didn't think it would work but no harm in trying 🙂

Any ideas ?

Thanks again.

EDIT:

Looking at the 'HELP ASSIGN' command in disk part it says that you should always be able to assign a drive letter to an ESP partition. That's odd.

Ok, so I tried to assign a letter to EFI for a while before trying the other method,

I renamed the BCD on my USB stick to BCD.bak and ran the following command from the USB stick:

bcdboot c:\Windows /l en-gb /s d: /f ALL      //assigning C:\windows os to the BCD on D: which is the usb stick

It told me that the operation completed successfully.

I booted back into osx, remounted the EFI, copied the new BCD to it and put BCD.bak back the way it was.

Booting into windows, i now get a different error code : 0xc0000225

The file \Windows\system32\winload.efi is missing or contains errors

I really thought it would boot up.

The winload.efi file appears to be present.

Any further ideas ?

Thanks again.

I set the directory to C: and ran

sfc.exe /scannow /offbootdir=C:\ offwindir=C:\Windows

Did not find any integrity violations, so it seems ok, probably an issue with the BCD I created and passed across then?

Maybe if I could assign a letter to the EFI it would work, but I just cant seem to be able to do it.

Thanks for replying through this, you have a lot of patience 🙂

Hi Loner T,

Sorry about my late response,

So I have been playing around with EasyBCD with no luck. I decided to go a bit more in depth with bcdedit.

The current config for the BCD on the machine is :

Windows Boot Manager

--------------------

identifier {bootmgr}

device unknown

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

locale en-gb

inherit {globalsettings}

default {default}

resumeobject {27b79d36-afd4-11e5-8928-b9e0101f7078}

displayorder {default}

toolsdisplayorder {memdiag}

timeout 30

Windows Boot Loader

-------------------

identifier {default}

device unknown

path \windows\system32\winload.efi

description Windows 10

locale en-gb

inherit {bootloadersettings}

isolatedcontext Yes

allowedinmemorysettings 0x15000075

osdevice unknown

systemroot \windows

resumeobject {27b79d36-afd4-11e5-8928-b9e0101f7078}

nx OptIn

bootmenupolicy Standard

I notice there are 3 values with 'unknown'

Boot Manager device, Boot Loader device, and Boot Loader osdevice.

I have tried changing these values to :

Windows Boot Manager

--------------------

device boot

Windows Boot Loader

-------------------

device partition=C:

osdevice partition=C:

(Removed other values to shorten post)

boot, partition=C:, and partition=C:

I have also tried using all 'boot', and all 'partition=C:'

The error is always the same. I know that I am editing the correct BCD as if I disable Metro bootloader in EasyBCD, the error is displayed in the Legacy Bootloader.

I assume that this is where my issue is, as far as i can tell the bootloader is looking for winload.efi in the EFI partition, not in the BOOTCAMP partition.

This is just what I can gather. Do you by any chance have a BCD file from a booting PC of similar congifuration that i could use to compare with my machine or know where i could find one ?

Or do you have any further ideas? ... I'm starting to loose hope 😟

Thanks again,

Cathal.

Thank you for that. I look forward to seeing it. I re-enabled the Metro bootloader afterwards, it was just a test to ensure that editing my BCD actually was having an effect, and I wasn't editing some other file.

I still find it curious that I cannot mount the EFI partition in diskpart. It only shows the BOOTCAMP volume, even though it reports the disk itself as being full.

I double checked to make sure the EFI partition is in FAT32 and not some other format. Why isn't the volume showing in diskpart?

Maybe there is a partition table issue?

Surely if we can manage to mount the EFI partition the fix to this should be simple?

EDIT :

The 'original' BCD I showed above Is the one I created using rebuild BCD when booted from the USB stick and copied across as detailed above, I stupidly don't have a copy of the actual original.

I got the idea to replace the values from 'unknown' to 'boot' and 'partition=C:' from both information I found online and from referencing the BCD on my main workstation pc, however that PC does not use EFI boot.