5 replies to this topic

[911CD.net]

I've screwed up my Windows 10 SSD drive.  It no longer boots and a Jan 15 backup on it fails to restore the system drives.

 

When the notebook boots I get "Windows 10 error code 0xc000000e".  If I press Enter I get "File: \windows\system32\winload.efi".

 

I Googled and found some bootrec commands to run to rebuild the BCD from my Windows Repair USB drive.  The bootrec /FixMbr runs but the bootrec /FixBoot fails because I need Admin rights and I don't know how to do that.

 

How this came about.  My old notebook has a 1 Tb SSD drive.  My new Christmas notebook has a 256 GB drive.  I tried to install my 1 Tb SSD in the new notebook, and keep my Data partition on it intact.  Once I finished DDing the new notebook's SSD drive's partitions to my old SSD drive I opened the new notebook and found that it's SSD drive is an m.2 type.  So copied the old notebooks drives, from a backup hhd drive, to the 1 Tb drive and reinstalled it into the old notebook and now have this mess.

 

I don't want to reinstall Windows 10 on the drive and then spend days installing Windows updates and my apps/utilities/bookmarks/addons and etc. 

 

One of the things I did which I think is the basis of the problem, the c: drives of the two notebooks are slightly different in size with old notebook's C: drive 213 GB and the new notebook's c: drive 219 GB.  When I restored the old notebook's c: drive to the SSD drive I thought I kept the c: drive as 219 GB but I just checked the backup drive's c: drive and it is 212 GB so the notebook's is probably the same.  I'm attaching an image of what the drive use to look like.

 

To be able to boot the notebook and restore it's Jan 15 Windows 7 backup is my goal.  Can you help me achieve that?

 

[911CD.net]

A current picture of the drive.

 

[Wonko the Sane]

It is strange that from (I presume) the Windows 10 Recovery Environment you don't have the privileges to run bootrec /fixboot.

 

I would rather try rebuilding the BCD, assigning a drive letter to the FAT32 partition (let's say W: ) with diskpart and then running BCDBOOT:

https://docs.microso...view=windows-11

 

diskpart

list volume

select volume # <- choose the FAT32 volume without a drive letter assigned

assign letter W <- W or another not used letter

exit

bcdboot d:\Windows /s W: /f UEFI <- the d:\windows is the path to the install change drive letter according to your setup  

 

But have you not the possibility to check the current BCD with BOOTICE?

 

In any case I would make a backup copy of the BCD before attempting to fix it.

 

Maybe the origin comes from the (stupid) entry in NVRAM, did you try to clear it?

https://aps2.support...03QJ0000R01.htm

 

Wonko

[911CD.net]

   Wonko 

 

So good to hear from you.      And as usual your skills solved my problem.     I used the diskpart and bcdboot steps.

 

Thank you old friend, I am posting this with the notebook that was broken.

 

Stay safe.     

[911CD.net]

So, the tale continues.

 

When I boot the notebook I get a screen that shows:

 

Choose an operating system

 

  Windows 10

    on volume 3

 

  Windows 10

 

If I choose the top one I get Windows 10.      If I choose the bottom one I get my "Windows 10 error code 0xc000000e" "File: \windows\system32\winload.efi" error again.

 

And bootice doesn't work, in an Admin Command prompt.

Microsoft Windows [Version 10.0.19044.1469]
(c) Microsoft Corporation. All rights reserved.
C:\windows\system32>bootice
'bootice' is not recognized as an internal or external command,
operable program or batch file.
C:\windows\system32>

But bcdedit works. 

C:\windows\system32>bcdedit
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\GRUB2WIN\G2BOOTMGR\GNUGRUB.KERNEL64.EFI
description             Grub2Win EFI - 64 Bit
locale                  en-us
inherit                 {globalsettings}
default                 {current}
resumeobject            {91306013-839c-11ec-b22b-b64b2049c953}
displayorder            {current}
                        {b13662ef-6e29-11e9-81ed-a7f3dc6f6716}
toolsdisplayorder       {memdiag}
timeout                 99
Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \windows
resumeobject            {91306013-839c-11ec-b22b-b64b2049c953}
nx                      OptIn
bootmenupolicy          Standard
Windows Boot Loader
-------------------
identifier              {b13662ef-6e29-11e9-81ed-a7f3dc6f6716}
device                  unknown
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {b13662f1-6e29-11e9-81ed-a7f3dc6f6716}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                unknown
systemroot              \WINDOWS
resumeobject            {b13662ee-6e29-11e9-81ed-a7f3dc6f6716}
nx                      OptIn
bootmenupolicy          Standard
C:\windows\system32>

Just have to remember how to delete a loader.      

C:\windows\system32>bcdedit /delete  {b13662ef-6e29-11e9-81ed-a7f3dc6f6716}   /cleanup
The operation completed successfully.
C:\windows\system32>bcdedit
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\GRUB2WIN\G2BOOTMGR\GNUGRUB.KERNEL64.EFI
description             Grub2Win EFI - 64 Bit
locale                  en-us
inherit                 {globalsettings}
default                 {current}
resumeobject            {91306013-839c-11ec-b22b-b64b2049c953}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 99
Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \windows
resumeobject            {91306013-839c-11ec-b22b-b64b2049c953}
nx                      OptIn
bootmenupolicy          Standard
C:\windows\system32>

Looks like my memory worked.     Now to see if it worked.

[Wonko the Sane]

Yep , bootice is a third party program, get it here and add it to the *whatever* you boot from, it is simply the best/most handy tool around (for a next time, should it happen ):

 

http://reboot.pro/in...ds&showfile=592

 

To give some context, in the "borked" entry you have both device and osdevice "unknown" whilst in the (new) working one you have partition=C:, if I recall correctly the drive letter identity is found through either Disk Signature+offset or (cannot really remember) volume serial, when you applied the clone (or whatever) you probably changed one of these making the old reference become invalid.

 

 

Wonko