New
#21
Certainly... I have attached a screen capture, inline:
Attachment 121974
Certainly... I have attached a screen capture, inline:
Attachment 121974
It looks like you have a MBR partitioning, so you don't have to worry about the EFI partition.
Thank you. I am still skeptical about it being MBR, because we have an identical machine with identical hardware and OS and it has a EFI Partition on its SSD. Is there a test I can do to confirm I am MBR vs EFI?
Also, I an unclear on this point: is my goal to convert that last drive list on my screen capture to go from being "Healthy (Recovery Partition)" to "Healthy (EFI System Partition)" (or the MBR equivalent)? ...or is my goal to add another partition that will end up named "Healthy (EFI System Partition)" (or the MBR equivalent)?
And if I am creating another partition: does it matter where in the partition order it is? And where will the space needed for it come from (i.e. do I have to first make one of the existing partitions smaller in order so that there is some space to give to the new partition)?
This is my partitioning, with GPT
Attachment 122127
For the goal, see my previous post, I edited the post a little to correct a few things with MBR partitioning. The recovery partition is an optional partition that I believe is created when the OS is being reinstalled (or upgraded).
I believe the order doesn't really matter. As an example, a few days ago I reinstalled my system completely because I found out that the EFI partition was installed on Disk 1 between the 2nd and the 3rd partition (Disk 1 was at the time Disk 0 because I accidentally switched the connections). The partitioning of Disk 1 was a chaos due to a previous Windows installation that I used for testing.
To create a new partition, you have to shrink a partition.
Hi axe0.
Thank you.
So, I used Disk Management to Shrink a partition to get a spare 1GB.
Then I tried to create a new EFI partition using diskpart's "create partition efi size=260" command.
But sadly this resulted in a long error message: "No usable free extent could be found..." even though I have 1GB available.
Is there a limit to how many partitions I am allowed to have?
Open an admin command prompt and enter following commandsIs there a test I can do to confirm I am MBR vs EFI?
If you see a * below GPT, it means EFI partition should normally be present, then we'll go from there.Code:diskpart list disk
See below image for an example
Attachment 122325
Thank you.
Here is what I see when I do that:
==========
Microsoft DiskPart version 10.0.14393.0
Copyright (C) 1999-2013 Microsoft Corporation.
On computer: DAVIDMAIN
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 931 GB 700 MB
Disk 1 Online 14 GB 0 B
Disk 2 Online 14 GB 7240 MB
Disk 3 Online 239 GB 0 B
================
... as you can see, there are no asterisks in the Gpt column.
Disk 0 is the drive that is my drive C:, that used to happily boot Windows 10, but no longer does so. Disk 2 is the USB stick that I currently must use to boot Windows.
Thank you,
David
Thank you: this looks very promising! For clarity, I downloaded "Win14393PESE_x64 ISO v170116 (New)". I downloaded that .iso file, then unzipped it to a formatted FAT32 USB stick. Then I booted the computer from that stick, and then launched Fix Boot Problems.
It then offered me a list of primary partitions to choose from. Which of these should I choose?:
Disk 1 - Samsung SSD 850 EVO 1TB EMT02B6Q
SSD C drive (C:) NTFS
<No Name> (I:) NTFS
SSD D drive (D:) NTFS
Disk 2 - SanDisk SSD U110 16GB U21B001
System Reserved (Microdrive) (E:) NTFS
Microdrive (F:) NTFS
I selected drive C.
And then it offered four Boot Code Options checkboxes, and they were all check and I choosed the Finish button.
However the computer still won't boot without the USB stick, and in fact now it won't boot WITH the USB stick either.
And there are still no asterisks in the last column of PARTDISK's list of drives.
Now when I try to boot from the USB stick that worked yesterday, I get a blue screen that says
"Recovery
Your PC/Device needs to be repaired
File \windows\system32\winload.efi
Error code 0xc0000225
"
David
Last edited by davidbermancom; 03 Apr 2017 at 06:13.