Following on from my previous question (Can't remove recovery partition) I have been trying to use Diskpart - with the following results:
Is my disk locked in a permanent way or is this something I can easily address without additional tools?
You need to add the
delete partition override
Enables DiskPart to delete any partition regardless of type. Normally, DiskPart enables you to delete only known data partitions.
"Cannot delete a protected partition without the force protection parameter set."
This is a warning from Windows that you need to be doubly sure that you want to delete this partition.
If you see this error when trying to delete a partition then use:
delete partition override
!!! It's a stupid message of Windows, asking for a parameter that is not even indicated by "HELP DELETE PARTITION", the correct parameter supported ("OVERRRIDE", not "FORCE PROTECTION") is still not documented correctly... !!! My opinion is that it is an old bug of DISKPART, signaled since long, but constantly ignored by Microsoft).
It is needed to allwo deleting the superfluous "recovery" partition that pollutes the drives after each release (the recovery partition is recreatred again and again, taking space from the main partition at end each time its size needs to be increased, and leaving old recovery partitions unused, except they are still refenrenced by old BCD entries (see the result of command "BCDEDIT /ENUM ALL", I don't know).
Old recovery partitions have to be deleted, they are not even usable (I bet they are kept only as old backups but there's not even any tool in Windows to use them again...). They are protected with a flag which cannot be changed without deleting these partition with the override flag.
On a SSD, these recovery partitions are taking previous space (about 500MB each one, but growing from version to version: I have found a dozen of these old unused partitions, the one in use being the one immediately after the main partition, all the other ones being old garbages).
Deleting these partitions will not be enough, you'll need then to recover the lost space by moving again the first recovery partition to the end of disk, and then extend again the main partition.
Each version of windows 10 will eat more than 1/2 GB of space by leaviong old recoveries after the new one added.
Note: the recovery partition size needed to avoid this recreation is larger than what MSDN/Technet documents: if it has not enough freee space, a new one is created with just the minimum needed (which grows over time, so each new image version adds its own new recovery partition before the previous one, formatted in NTFS, but left invisible and not mounted by default with a drive letter in the Windows Explorer). A new partition is even created when the previous recovery partition is still large enough to contain the new recovery bootloader and winRE image...
To perform this cleanup, you need external tools (such as Partition Magic). Windows is stupid sometimes.
type commands on diskpart:
The clean command will do the service.. ;)