Hello everyone! So let me explain the situation first. I received a new computer but without Windows. The computer has an SSD, so I looked to install Windows on it. It turns out that by mistake I installed it on the HDD of the computer. I finally managed to install it on the SSD by converting the partition to GPT. I managed to delete the system files from my HDD by formatting it, but the EFI system partition remains. My question is: how can I move this EFI partition to the SSD? Because as it currently stands, I assume that at startup the HDD is being used, whereas I've installed Windows on the SSD to avoid that. I'm posting a screenshot of the disk manager. Thanks in advance for your insightful opinions!

EFI partition on wrong disk : CCM

Réponse 1 / 8

jee pee Posted messages 9403 Registration date Status Modérateur Last intervention 9 948

Hello,

I have never done this, but in this discussion, the issue was similar to yours, and after resolving it, the person shared the solution they used to create the EFI partition and fill it: https://forums.commentcamarche.net/forum/affich-35448867-bootage-sur-windows-boot-manager#9

--
a stranger is a friend you haven't met yet.

letolah Posted messages 30 Status Membre

It seemed interesting but I'm stuck...

Huitre

Hi,

There is no need to reinstall Windows to add the EFI partition and the boot files on the SSD. In your case, you also need to move the recovery partition, which is also misplaced.

The missing partitions could be placed at the end of the disk, but it is better to put them at the beginning. So, with partitioning software, you need to reduce the C volume by 800 MB from the left. And do not touch the small hidden MSR partition of 15 MB.

Réponse 2 / 8

Papounet17000 Posted messages 26460 Registration date Status Membre Last intervention 9 894

Hi,

If I were you, I would restart the Windows 10 installation.
At the beginning of the process, I would delete all the partitions on the hard drive and the SSD, then select the SSD for the Windows installation.
All the partitions will be recreated on the SSD.
Since it's already in GPT, it shouldn't be a problem.

--
The words in blue are clickable links.

letolah Posted messages 30 Status Membre

If I restart the installation, will I lose everything I've already installed?
And how do I delete all the HDD partitions at the beginning of the installation? Is this offered at some point or do I have to go through diskpart?
Because I had tried to re-initialize the PC but it only offered to erase the disk where Windows was running, which is the SSD.

letolah Posted messages 30 Status Membre

According to what I've read, I need to disconnect my HDD because the EFI always installs on the first drive. By setting my SSD as disk 0 maybe...

Réponse 3 / 8

Huitre

Re,

You need to launch the command prompt as admin (right-click on the start menu or on cmd). You are in users. If you restarted the PC in the meantime, the letter z has disappeared. So, I need another

diskpart
sel disk 1
list vol
list part
exit

letolah Posted messages 30 Status Membre

I hadn't restarted the PC

Réponse 4 / 8

Huitre

The startup issue with the SSD is theoretically resolved, and the SSD is theoretically capable of booting on its own (but the result of bcdedit /enum firmware is incomplete to guarantee that). We now need the result of

reagentc /info

letolah Posted messages 30 Status Membre

Could I delete the recovery and EFI partitions from the HDD in the end?

Huitre

That's the goal. I need the end of the result from the command

bcdedit /enum firmware

The screenshot provided above is incomplete: give the entire result by copy-pasting if you want.

letolah Posted messages 30 Status Membre

It seemed to me that I had everything set up

Firmware Boot Manager
-------------------------------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{a423b929-8c30-11e8-a70a-806e6f6e6963}
{6ccd14bc-8cf9-11e8-a711-806e6f6e6963}
{2bc0f4a8-8c30-11e8-bffc-8f55593ff13a}
{2bc0f4aa-8c30-11e8-bffc-8f55593ff13a}
{2bc0f4a9-8c30-11e8-bffc-8f55593ff13a}
timeout 0

Windows Boot Manager
---------------------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {2bc0f4ad-8c30-11e8-bffc-8f55593ff13a}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Software Application (101fffff)
--------------------------------
identifier {2bc0f4a8-8c30-11e8-bffc-8f55593ff13a}
description EFI USB Device

Software Application (101fffff)
--------------------------------
identifier {2bc0f4a9-8c30-11e8-bffc-8f55593ff13a}
description Notebook Hard Drive - ST1000LM049-2GH172

Software Application (101fffff)
--------------------------------
identifier {2bc0f4aa-8c30-11e8-bffc-8f55593ff13a}
description Notebook Hard Drive - SAMSUNG MZVLW256HEHP-000H1

Software Application (101fffff)
--------------------------------
identifier {6ccd14bc-8cf9-11e8-a711-806e6f6e6963}
device partition=\Device\HarddiskVolume5
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager

Software Application (101fffff)
--------------------------------
identifier {a423b929-8c30-11e8-a70a-806e6f6e6963}
description Internal Hard Disk or Solid State Disk

Huitre

To ensure that your SSD boots without any intervention from the HDD, you need to run 2 commands:

bcdedit /set {fwbootmgr} displayorder {6ccd14bc-8cf9-11e8-a711-806e6f6e6963} /addfirst

reagentc /disable

The first command forces the BIOS/UEFI to boot from the EFI files on the SSD, and the second disables advanced boot options. If this is confirmed, you should restart. However, you will not be able to format the HDD yet, as we need to recover the contents of the recovery partition for everything to be complete.

letolah Posted messages 30 Status Membre

It's done! Thank you for spending so much time on it ...

C:\Windows\system32>bcdedit /set {fwbootmgr} displayorder {6ccd14bc-8cf9-11e8-a711-806e6f6e6963} /addfirst
The operation was successful.

C:\Windows\system32>reagentc /disable
REAGENTC.EXE: operation successful.

Réponse 5 / 8

Huitre

Re,

We now need to recover the winre.wim file (hidden and system). It may be on the recovery partition and/or on C if I trust reagentc. We'll take this opportunity to inspect the status of the recovery partition which has changed since version 18-03. And we'll assign it a temporary letter.

diskpart
sel disk 0
sel part 1
assign letter=p
detail part
exit

Give me the result (copy-paste preferred). Then, we'll search for winre.wim in the three possible locations:

dir /a p:\recovery\windowsre
dir /a c:\recovery\windowsre
dir /a c:\windows\system32\recovery

If winre.wim is not visible, try replacing dir /a with dir /a:hs. Just let me know if you see it and where. The goal is for me to know where it is so we can copy it to the SSD.

letolah Posted messages 30 Status Membre

Hello!

Detailed partition result:

Partition 1
Type: de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden: No
Required: Yes
Attrib: 0X0000000000000001
Offset in bytes: 1048576

Volume No Ltr Name Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------

Volume 6 P NTFS Partition 499 M Healthy Hidden

Winre.wim result:

C:\Windows\system32>dir /a p:\recovery\windowsre
The specified file could not be found.

C:\Windows\system32>dir /a c:\recovery\windowsre
The volume in drive C is called SSD
The serial number of the volume is 4C75-14A4

Directory of c:\recovery

File not found

C:\Windows\system32>dir /a c:\windows\system32\recovery
The volume in drive C is called SSD
The serial number of the volume is 4C75-14A4

Directory of c:\windows\system32\recovery

07/23/2018 21:01 <DIR> .
07/23/2018 21:01 <DIR> ..
07/23/2018 21:01 1,080 ReAgent.xml
06/19/2018 21:44 520,927,633 Winre.wim
2 file(s) 520,928,713 bytes
2 Dir(s) 180,174,336,000 bytes free

Huitre

Sure,

To simplify things, we're going to make the file visible:

attrib -h -s -r c:\windows\system32\recovery\winre.wim

You will go to volume R. At the root, create a folder named Recovery, then inside that, a subfolder named WindowsRe. In this last folder, copy and paste the file winre.wim located in c:\windows\system32\recovery.
You also need to copy the file boot.sdi from c:\windows\system32.

When that's done, we'll move on to the final commands.

letolah Posted messages 30 Status Membre

It's good!

Réponse 6 / 8

Huitre

OK.

Let's first change the status of this partition R to that of recovery:

diskpart
sel disk 1
list part

In the output of "list part", make sure that the 805 MiB partition is indeed number 3 (otherwise, adjust the number accordingly, of course).

sel part 3
set id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
exit

We inform the system that the advanced startup will take place on volume R

reagentc /setreimage /path r:\Recovery\WindowsRE

If it responds that the operation was successful. We reactivate reagentc

reagentc /enable

Likewise, if it responds that everything is fine, we perform a check to see if the SSD is fully autonomous. So, result of

bcdedit /v

and

reagentc /info

If the result is good, the HDD will be fully formatable, and we will only need to remove the letter R from the recovery partition.

letolah Posted messages 30 Status Membre

Here is the result, but it doesn't seem to have taken the correct partition at the end

DISKPART> list part

Partition Number Type Size Offset
------------- ---------------- ------- --------
Partition 1 Reserved 15 M 17 K
Partition 2 System 300 M 16 M
Partition 3 Recovery 805 M 316 M
Partition 4 Primary 237 G 1121 M

DISKPART> sel part 3

Partition 3 is now the selected partition.

C:\Windows\system32>reagentc /setreimage /path r:\Recovery\WindowsRE
Directory set: \\?\GLOBALROOT\device\harddisk1\partition3\Recovery\WindowsRE

REAGENTC.EXE: operation successful.

C:\Windows\system32>reagentc /enable
REAGENTC.EXE: operation successful.

C:\Windows\system32>bcdedit /v

Windows Boot Manager
---------------------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {2bc0f4ae-8c30-11e8-bffc-8f55593ff13a}
resumeobject {2bc0f4ad-8c30-11e8-bffc-8f55593ff13a}
displayorder {2bc0f4ae-8c30-11e8-bffc-8f55593ff13a}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Boot Loader
-----------------------------
identifier {2bc0f4ae-8c30-11e8-bffc-8f55593ff13a}
device partition=C:
path \Windows\system32\winload.efi
description Windows 10
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {b1e96ff9-8f8f-11e8-a714-7c7635d96de4}
displaymessageoverride SystemImageRecovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {2bc0f4ad-8c30-11e8-bffc-8f55593ff13a}
nx OptIn
bootmenupolicy Standard

C:\Windows\system32>reagentc /info
Recovery Environment Configuration Information
Windows (WinRE) and System Reset:

WinRE Status: Enabled
WinRE Location: \\?\GLOBALROOT\device\harddisk1\partition4\Recovery\WindowsRE
Boot Configuration Data (BCD) Identifier: b1e96ff9-8f8f-11e8-a714-7c7635d96de4
Recovery Image Location:
Recovery Image Index: 0
Custom Image Location:
Custom Image Index: 0

REAGENTC.EXE: operation successful.

Will I be able to resize the partitions afterwards?

Huitre

Indeed... We don't quite achieve the expected result... Even the efi partition being used is still that of the hdd.

If you can disconnect the hdd, now is the time to try without it. Otherwise, we'll approach it differently.

letolah Posted messages 30 Status Membre

It's a laptop, so there's not much way to unplug the HDD...

Huitre

As long as we boot from the EFI of the hard drive, you'll be stuck. Try installing the free version of the EasyUEFI software... I want to see how it displays the boot order.

Surprisingly, your NVRAM hasn't recorded the change made. Also specify the brand of the PC.

However, everything was done by the book.

letolah Posted messages 30 Status Membre

Re,
I'm not home yet, but I can already tell you that I have an HP. It also seems to me that in the Setup Menu at startup, I can choose the EFI files to boot with.

Réponse 7 / 8

letolah Posted messages 30 Status Membre

The change was not saved... And what if I make the change and disable the HDD line?

Huitre

I don't know what it might imply. HPs are known for having a locked BIOS-UEFI. Try accessing the BIOS and see if you can follow this:

system configuration > UEFI boot order > OS boot manager >

It should look something like this:

http://oi65.tinypic.com/2j2uf7t.jpg

If you see 2 entries for "Windows boot manager", try selecting the second one and save. This is often done for dual-booting with Ubuntu on HPs. Example (no Ubuntu in your case):

http://oi63.tinypic.com/2iks2hj.jpg

letolah Posted messages 30 Status Membre

Bad news ...

Huitre

Try the boot manager... It should be the same. If it can't be modified, try forcing the boot on the SSD's EFI (you told me you can) and we'll delete the HDD's EFI.

We'll see what happens next. Always have an installation medium ready just in case.

letolah Posted messages 30 Status Membre

Is it to say try OS boot manager? It's already first, isn't it?

letolah Posted messages 30 Status Membre

I managed to put the SSD first:

Réponse 8 / 8

Scarabe

Hello ikewdu

Huitre

:)

EFI partition on wrong disk

8 réponses

Epson printer prints unexpectedly

Texture issues in enshrouded

Announcement: online source code archive

Samsung tv music on startup

Écrire o barré avec un clavier azerty

Application extension issue on ps4

Orange unlimited numbers

Text messages from 36111

Tomb raider anniversary on wii

Notice shows wr30 m