Diskpart - Can't delete a partition without the force protected parameter set
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?
windows windows-10 partitioning diskpart
edited Mar 20 '17 at 10:04
Community♦
1
asked May 16 '16 at 10:18
Mr. BoyMr. Boy
1,752164667
add a comment |
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?
windows windows-10 partitioning diskpart
edited Mar 20 '17 at 10:04
Community♦
1
asked May 16 '16 at 10:18
Mr. BoyMr. Boy
1,752164667
add a comment |
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?
windows windows-10 partitioning diskpart
edited Mar 20 '17 at 10:04
Community♦
1
asked May 16 '16 at 10:18
Mr. BoyMr. Boy
1,752164667
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?
windows windows-10 partitioning diskpart
windows windows-10 partitioning diskpart
edited Mar 20 '17 at 10:04
Community♦
1
asked May 16 '16 at 10:18
Mr. BoyMr. Boy
1,752164667
edited Mar 20 '17 at 10:04
Community♦
1
asked May 16 '16 at 10:18
Mr. BoyMr. Boy
1,752164667
edited Mar 20 '17 at 10:04
Community♦
1
edited Mar 20 '17 at 10:04
Community♦
1
edited Mar 20 '17 at 10:04
Community♦
1
1
asked May 16 '16 at 10:18
Mr. BoyMr. Boy
1,752164667
asked May 16 '16 at 10:18
Mr. BoyMr. Boy
1,752164667
asked May 16 '16 at 10:18
Mr. BoyMr. Boy
1,752164667
1,752164667
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Is my disk locked in a permanent way?
You need to add the override option:
delete partition override
override
Enables DiskPart to delete any partition regardless of type. Normally,
DiskPart enables you to delete only known data partitions.
Source DiskPart Command-Line Options
How to delete an OEM partition
"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
Source How to delete an OEM partition
answered May 16 '16 at 10:28
DavidPostill♦DavidPostill
105k25227262
add a comment |
!!! 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.
answered Jul 21 '18 at 19:52
verdy_pverdy_p
20722
add a comment |
type commands on diskpart:
- list disk
- select disk x
- clean
The clean command will do the service..
;)
Renato Ricci
answered Feb 27 '18 at 22:19
Renato RicciRenato Ricci
1
3
That cleans the entire disk, which is not what OP is asking. This makes what you are suggesting dangerous because it will fully wipe ALL data from ALL partitions across the ENTIRE disk. Please read questions carefully before answering, and make sure that your answer solves the actual problem.
– music2myear
Feb 27 '18 at 22:50
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1077372%2fdiskpart-cant-delete-a-partition-without-the-force-protected-parameter-set%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Is my disk locked in a permanent way?
You need to add the override option:
delete partition override
override
Enables DiskPart to delete any partition regardless of type. Normally,
DiskPart enables you to delete only known data partitions.
Source DiskPart Command-Line Options
How to delete an OEM partition
"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
Source How to delete an OEM partition
answered May 16 '16 at 10:28
DavidPostill♦DavidPostill
105k25227262
add a comment |
Is my disk locked in a permanent way?
You need to add the override option:
delete partition override
override
Enables DiskPart to delete any partition regardless of type. Normally,
DiskPart enables you to delete only known data partitions.
Source DiskPart Command-Line Options
How to delete an OEM partition
"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
Source How to delete an OEM partition
answered May 16 '16 at 10:28
DavidPostill♦DavidPostill
105k25227262
add a comment |
Is my disk locked in a permanent way?
You need to add the override option:
delete partition override
override
Enables DiskPart to delete any partition regardless of type. Normally,
DiskPart enables you to delete only known data partitions.
Source DiskPart Command-Line Options
How to delete an OEM partition
"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
Source How to delete an OEM partition
answered May 16 '16 at 10:28
DavidPostill♦DavidPostill
105k25227262
Is my disk locked in a permanent way?
You need to add the override option:
delete partition override
override
Enables DiskPart to delete any partition regardless of type. Normally,
DiskPart enables you to delete only known data partitions.
Source DiskPart Command-Line Options
How to delete an OEM partition
"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
Source How to delete an OEM partition
answered May 16 '16 at 10:28
DavidPostill♦DavidPostill
105k25227262
edited Aug 9 '16 at 19:34
answered May 16 '16 at 10:28
DavidPostill♦DavidPostill
105k25227262
answered May 16 '16 at 10:28
DavidPostill♦DavidPostill
105k25227262
answered May 16 '16 at 10:28
DavidPostill♦DavidPostill
105k25227262
105k25227262
add a comment |
add a comment |
!!! 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.
answered Jul 21 '18 at 19:52
verdy_pverdy_p
20722
add a comment |
!!! 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.
answered Jul 21 '18 at 19:52
verdy_pverdy_p
20722
add a comment |
!!! 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.
answered Jul 21 '18 at 19:52
verdy_pverdy_p
20722
!!! 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.
answered Jul 21 '18 at 19:52
verdy_pverdy_p
20722
answered Jul 21 '18 at 19:52
verdy_pverdy_p
20722
answered Jul 21 '18 at 19:52
verdy_pverdy_p
20722
answered Jul 21 '18 at 19:52
verdy_pverdy_p
20722
20722
add a comment |
add a comment |
type commands on diskpart:
- list disk
- select disk x
- clean
The clean command will do the service..
;)
Renato Ricci
answered Feb 27 '18 at 22:19
Renato RicciRenato Ricci
1
3
That cleans the entire disk, which is not what OP is asking. This makes what you are suggesting dangerous because it will fully wipe ALL data from ALL partitions across the ENTIRE disk. Please read questions carefully before answering, and make sure that your answer solves the actual problem.
– music2myear
Feb 27 '18 at 22:50
add a comment |
type commands on diskpart:
- list disk
- select disk x
- clean
The clean command will do the service..
;)
Renato Ricci
answered Feb 27 '18 at 22:19
Renato RicciRenato Ricci
1
3
That cleans the entire disk, which is not what OP is asking. This makes what you are suggesting dangerous because it will fully wipe ALL data from ALL partitions across the ENTIRE disk. Please read questions carefully before answering, and make sure that your answer solves the actual problem.
– music2myear
Feb 27 '18 at 22:50
add a comment |
type commands on diskpart:
- list disk
- select disk x
- clean
The clean command will do the service..
;)
Renato Ricci
answered Feb 27 '18 at 22:19
Renato RicciRenato Ricci
1
type commands on diskpart:
- list disk
- select disk x
- clean
The clean command will do the service..
;)
Renato Ricci
answered Feb 27 '18 at 22:19
Renato RicciRenato Ricci
1
answered Feb 27 '18 at 22:19
Renato RicciRenato Ricci
1
answered Feb 27 '18 at 22:19
Renato RicciRenato Ricci
1
answered Feb 27 '18 at 22:19
Renato RicciRenato Ricci
1
1
3
That cleans the entire disk, which is not what OP is asking. This makes what you are suggesting dangerous because it will fully wipe ALL data from ALL partitions across the ENTIRE disk. Please read questions carefully before answering, and make sure that your answer solves the actual problem.
– music2myear
Feb 27 '18 at 22:50
add a comment |
3
That cleans the entire disk, which is not what OP is asking. This makes what you are suggesting dangerous because it will fully wipe ALL data from ALL partitions across the ENTIRE disk. Please read questions carefully before answering, and make sure that your answer solves the actual problem.
– music2myear
Feb 27 '18 at 22:50
3
3
That cleans the entire disk, which is not what OP is asking. This makes what you are suggesting dangerous because it will fully wipe ALL data from ALL partitions across the ENTIRE disk. Please read questions carefully before answering, and make sure that your answer solves the actual problem.
– music2myear
Feb 27 '18 at 22:50
That cleans the entire disk, which is not what OP is asking. This makes what you are suggesting dangerous because it will fully wipe ALL data from ALL partitions across the ENTIRE disk. Please read questions carefully before answering, and make sure that your answer solves the actual problem.
– music2myear
Feb 27 '18 at 22:50
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1077372%2fdiskpart-cant-delete-a-partition-without-the-force-protected-parameter-set%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
