Before I break this machine....
Before I break this machine....
Author
Discussion

Origin Unknown

Original Poster:

2,454 posts

191 months

Thursday 31st March 2022
quotequote all
Installed WIN11 on a new SSD. No longer need the existing WIN10 install which is on an NVMe. Seems that EFI part wa\s still on the NVMe so have recreated the EFI part and populated with the right files using bcedit, before I blat the whole NVMe, I've done this correctly, right?

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 2794 GB 0 B *
* Disk 1 Online 931 GB 0 B *
Disk 2 Online 238 GB 238 GB *

DISKPART> list part

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Reserved 16 MB 1024 KB
Partition 2 Primary 931 GB 17 MB
Partition 3 System 200 MB 931 GB

DISKPART> sel disk 2

Disk 2 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 260 MB 1024 KB

DISKPART> list vol

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 D DATA NTFS Partition 2780 GB Healthy
Volume 1 E RECOVERY NTFS Partition 13 GB Healthy
Volume 2 C NTFS Partition 931 GB Healthy Boot
Volume 3 FAT32 Partition 200 MB Healthy Hidden
Volume 5 FAT32 Partition 260 MB Healthy System

DISKPART>


Disk 1 is new SSD, Disk 2 is the old SSD
Vol 3 sits on the new SSD and Vol 5 sits on the old. VCol5 and Disk 2 are the ones I want to blat


Origin Unknown

Original Poster:

2,454 posts

191 months

Thursday 31st March 2022
quotequote all
{{{
C:\Windows\system32>bcdedit /enum active

Windows Boot Manager


identifier {bootmgr}
device partition=\Device\HarddiskVolume3
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-GB
inherit {globalsettings}
default {current}
resumeobject {7875c775-2f49-11ec-ab0e-af2cffe3ad2d}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader


identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 11
locale en-GB
inherit {bootloadersettings}
recoverysequence {7875c777-2f49-11ec-ab0e-af2cffe3ad2d}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {7875c775-2f49-11ec-ab0e-af2cffe3ad2d}
nx OptIn
bootmenupolicy Standard

C:\Windows\system32>
}}}

mattley

3,029 posts

244 months

Thursday 31st March 2022
quotequote all
Never install windows on a machine with more than the disk you want to install to installed. There is no control in the windows installer and sometimes it puts the boot sector on the wrong drive. rolleyes

dundarach

5,941 posts

250 months

Thursday 31st March 2022
quotequote all
Are you installing via usb?

If so whip all the others out, format the bugger and set it up again.

Then shove the old ones back in.

I'd always start from the least hardware possible to boot and add back in.

Origin Unknown

Original Poster:

2,454 posts

191 months

Thursday 31st March 2022
quotequote all
Yea that ship has sailed laugh I do not want to reinstall WIN11 again as I have it exactly as I want it after many months. Secondly, not a clue where the NVMe is actually located in the machine. I cannot for the life of me find it.

The above does look correct though?

snuffy

12,131 posts

306 months

Thursday 31st March 2022
quotequote all
Origin Unknown said:
Secondly, not a clue where the NVMe is actually located in the machine. I cannot for the life of me find it.
Two places to look:

On the front side of the Motherboard, if you can't see it, it will be hidden under a heatsink, but not a silver thing with fins, but a black bit of metal exactly the same size as the M.2 drive. Which means it's not that easy to spot, cus it sort of blends in.

Or, on the back of the Motherboard, which is not where you'd expect to find one.