Timeline for We couldn't create a new partition or locate an existing one - Windows 11
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2022 at 8:37 | comment | added | harrymc | After, reformat the disk into one Unallocated space, disconnect Disk 0, leaving only Disk 1 inside the computer, then install Windows 11. | |
| Aug 3, 2022 at 8:22 | comment | added | harrymc | The allocated System partition is too small to be EFI. Your BIOS settings may be incorrect. Verify that you have the latest BIOS from the manufacturer, enable "fTPM" (AMD) or "IPTT" (Intel), disable Legacy, and enable UEFI. BIOS versions differ, so I cannot point to the exact settings. If you need more info, let me know the computer model, motherboard and BIOS version. | |
| Aug 2, 2022 at 21:08 | comment | added | Scottmeup | First install attempt is onto unallocated space: windows creates partitions and errors. Machine is rebooted and the next install attempt is onto the partitions created by windows installer. Images 1 to 3 in the post show what happens. | |
| Aug 2, 2022 at 14:49 | comment | added | ChanganAuto | I wrongly upvoted your answer. Later I've found the problem, please check my answer. | |
| Aug 2, 2022 at 13:57 | comment | added | harrymc | So the disk is OK. But how come that you're installing into a partition and not into Unallocated space? | |
| Aug 2, 2022 at 13:27 | comment | added | Scottmeup | No change after formatting slowly. SMART status & BIOS test check out OK. I've added some screenshots that show what's happening. Could BIOS settings or the presence of another bootable OS on a different disk be causing a problem? | |
| Aug 2, 2022 at 11:08 | comment | added | harrymc | Formatting the disk will erase everything. You may use a Linux Live USB to check the SMART attributes of the disk, if you suspect errors. | |
| Aug 2, 2022 at 11:05 | comment | added | Scottmeup | I'll give it a shot. The system was working until I wiped it. It's a 1TB SSD and the install worked a couple of weeks ago. I'm wondering if letting a linux partition manager touch it has left any traces that windows doesn't like. | |
| Aug 2, 2022 at 11:00 | comment | added | harrymc | I can think of these reasons for error: (1) The unallocated space was not large enough, (2) The installation lacks a driver for the disk (very unlikely), (3) The disk has a hardware problem. For the third point, try to format the disk with slow format (not quick) for all sectors to refreshed. This will take some time for a large disk. | |
| Aug 2, 2022 at 10:55 | comment | added | Scottmeup | I started with unallocated space and selected that. Windows 11 installer created 3 partitions and errored. After that I selected the largest partition that Windows isntaller had created and it errorred again. | |
| Aug 2, 2022 at 10:53 | comment | added | harrymc | Are you selecting Unallocated space, or an existing partition? | |
| Aug 2, 2022 at 10:52 | comment | added | Scottmeup |
I've tried this a few times, and deleted all partitions on the drive and let Windows installer re-create them. It still errors on We couldn't create a new partition or locate an existing one when the main volume on the drive is selected.
|
|
| Aug 2, 2022 at 10:22 | history | answered | harrymc | CC BY-SA 4.0 |