C:Windows.old has a phantom permission, how do I rid myself of it?












-2















I just used Clean Install to reinstall on Windows 10 1809 (big mistake, I know). It's the official refreshed version, but it grants ALL APPLICATION PACKAGES permission to C:Windows.old.



This is relevant because inheritance is sticking to all of the files, even in server mode. Any attempt to remove it looks as though it succeeds, but nothing happens.



These are all of my personal files and documents, appdata, etc, going back many years, so the relevant portion is about 200GB, so copying (which resets the modified date anyway) isn't really feasible.



I need to either




  • move the files and break the inheritance chain; tried this using old PowerShell trick (move file, reset inheritance via SetAccessRuleProtection; the phantom permission sticks from "Parent Object" which this normally negates),

  • remove the phantom permission before moving files.


I've already taken ownership of the folder, that's not helping any. To be clear, I want to remove the ALL APPLICATION PACKAGES permission from C:Windows.old so my files aren't tainted with a bad security permission.



Screenshot of ALL APPLICATION PACKAGES, removing it "succeeds", but it's still there:



screenshot










share|improve this question

























  • Let us continue this discussion in chat.

    – TheGoddessInari
    Dec 13 '18 at 3:54











  • This is usually a driver package. Removing the driver clears the lock. This question has been asked and answered here before. Did you check the other questions about windows.old?

    – music2myear
    Dec 13 '18 at 4:40













  • I checked other questions, there isn't a driver involved that I'm aware unless Microsoft is being stupid with one. Things aren't locked, there is no permission denied, removing "ALL APPLICATION PACKAGES" iterates through all of the files like usual, no errors, but the phantom permission stays. Same with cacls, icacls, powershell set-acl, etc.

    – TheGoddessInari
    Dec 13 '18 at 4:45











  • Another point: A "clean reinstall" typically involves formatting your hard drive prior to or during the installation process. If "Windows.old" still exists, that means you did not run a "clean reinstall". Could you clarify the precise method and steps you used to update your computer to build 1809?

    – music2myear
    Dec 13 '18 at 17:03











  • And finally, what are you actually trying to accomplish: Are you just trying to remove the All Application Packages permission entry from your own files (what the body of the question seems to say) or are you trying to delete Windows.old and you believe this permission is preventing you from doing so, or something else entirely? Please EDIT your question to make this more clear.

    – music2myear
    Dec 13 '18 at 17:04
















-2















I just used Clean Install to reinstall on Windows 10 1809 (big mistake, I know). It's the official refreshed version, but it grants ALL APPLICATION PACKAGES permission to C:Windows.old.



This is relevant because inheritance is sticking to all of the files, even in server mode. Any attempt to remove it looks as though it succeeds, but nothing happens.



These are all of my personal files and documents, appdata, etc, going back many years, so the relevant portion is about 200GB, so copying (which resets the modified date anyway) isn't really feasible.



I need to either




  • move the files and break the inheritance chain; tried this using old PowerShell trick (move file, reset inheritance via SetAccessRuleProtection; the phantom permission sticks from "Parent Object" which this normally negates),

  • remove the phantom permission before moving files.


I've already taken ownership of the folder, that's not helping any. To be clear, I want to remove the ALL APPLICATION PACKAGES permission from C:Windows.old so my files aren't tainted with a bad security permission.



Screenshot of ALL APPLICATION PACKAGES, removing it "succeeds", but it's still there:



screenshot










share|improve this question

























  • Let us continue this discussion in chat.

    – TheGoddessInari
    Dec 13 '18 at 3:54











  • This is usually a driver package. Removing the driver clears the lock. This question has been asked and answered here before. Did you check the other questions about windows.old?

    – music2myear
    Dec 13 '18 at 4:40













  • I checked other questions, there isn't a driver involved that I'm aware unless Microsoft is being stupid with one. Things aren't locked, there is no permission denied, removing "ALL APPLICATION PACKAGES" iterates through all of the files like usual, no errors, but the phantom permission stays. Same with cacls, icacls, powershell set-acl, etc.

    – TheGoddessInari
    Dec 13 '18 at 4:45











  • Another point: A "clean reinstall" typically involves formatting your hard drive prior to or during the installation process. If "Windows.old" still exists, that means you did not run a "clean reinstall". Could you clarify the precise method and steps you used to update your computer to build 1809?

    – music2myear
    Dec 13 '18 at 17:03











  • And finally, what are you actually trying to accomplish: Are you just trying to remove the All Application Packages permission entry from your own files (what the body of the question seems to say) or are you trying to delete Windows.old and you believe this permission is preventing you from doing so, or something else entirely? Please EDIT your question to make this more clear.

    – music2myear
    Dec 13 '18 at 17:04














-2












-2








-2








I just used Clean Install to reinstall on Windows 10 1809 (big mistake, I know). It's the official refreshed version, but it grants ALL APPLICATION PACKAGES permission to C:Windows.old.



This is relevant because inheritance is sticking to all of the files, even in server mode. Any attempt to remove it looks as though it succeeds, but nothing happens.



These are all of my personal files and documents, appdata, etc, going back many years, so the relevant portion is about 200GB, so copying (which resets the modified date anyway) isn't really feasible.



I need to either




  • move the files and break the inheritance chain; tried this using old PowerShell trick (move file, reset inheritance via SetAccessRuleProtection; the phantom permission sticks from "Parent Object" which this normally negates),

  • remove the phantom permission before moving files.


I've already taken ownership of the folder, that's not helping any. To be clear, I want to remove the ALL APPLICATION PACKAGES permission from C:Windows.old so my files aren't tainted with a bad security permission.



Screenshot of ALL APPLICATION PACKAGES, removing it "succeeds", but it's still there:



screenshot










share|improve this question
















I just used Clean Install to reinstall on Windows 10 1809 (big mistake, I know). It's the official refreshed version, but it grants ALL APPLICATION PACKAGES permission to C:Windows.old.



This is relevant because inheritance is sticking to all of the files, even in server mode. Any attempt to remove it looks as though it succeeds, but nothing happens.



These are all of my personal files and documents, appdata, etc, going back many years, so the relevant portion is about 200GB, so copying (which resets the modified date anyway) isn't really feasible.



I need to either




  • move the files and break the inheritance chain; tried this using old PowerShell trick (move file, reset inheritance via SetAccessRuleProtection; the phantom permission sticks from "Parent Object" which this normally negates),

  • remove the phantom permission before moving files.


I've already taken ownership of the folder, that's not helping any. To be clear, I want to remove the ALL APPLICATION PACKAGES permission from C:Windows.old so my files aren't tainted with a bad security permission.



Screenshot of ALL APPLICATION PACKAGES, removing it "succeeds", but it's still there:



screenshot







windows windows-10 permissions ntfs






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 14 '18 at 22:53







TheGoddessInari

















asked Dec 13 '18 at 2:48









TheGoddessInariTheGoddessInari

13




13













  • Let us continue this discussion in chat.

    – TheGoddessInari
    Dec 13 '18 at 3:54











  • This is usually a driver package. Removing the driver clears the lock. This question has been asked and answered here before. Did you check the other questions about windows.old?

    – music2myear
    Dec 13 '18 at 4:40













  • I checked other questions, there isn't a driver involved that I'm aware unless Microsoft is being stupid with one. Things aren't locked, there is no permission denied, removing "ALL APPLICATION PACKAGES" iterates through all of the files like usual, no errors, but the phantom permission stays. Same with cacls, icacls, powershell set-acl, etc.

    – TheGoddessInari
    Dec 13 '18 at 4:45











  • Another point: A "clean reinstall" typically involves formatting your hard drive prior to or during the installation process. If "Windows.old" still exists, that means you did not run a "clean reinstall". Could you clarify the precise method and steps you used to update your computer to build 1809?

    – music2myear
    Dec 13 '18 at 17:03











  • And finally, what are you actually trying to accomplish: Are you just trying to remove the All Application Packages permission entry from your own files (what the body of the question seems to say) or are you trying to delete Windows.old and you believe this permission is preventing you from doing so, or something else entirely? Please EDIT your question to make this more clear.

    – music2myear
    Dec 13 '18 at 17:04



















  • Let us continue this discussion in chat.

    – TheGoddessInari
    Dec 13 '18 at 3:54











  • This is usually a driver package. Removing the driver clears the lock. This question has been asked and answered here before. Did you check the other questions about windows.old?

    – music2myear
    Dec 13 '18 at 4:40













  • I checked other questions, there isn't a driver involved that I'm aware unless Microsoft is being stupid with one. Things aren't locked, there is no permission denied, removing "ALL APPLICATION PACKAGES" iterates through all of the files like usual, no errors, but the phantom permission stays. Same with cacls, icacls, powershell set-acl, etc.

    – TheGoddessInari
    Dec 13 '18 at 4:45











  • Another point: A "clean reinstall" typically involves formatting your hard drive prior to or during the installation process. If "Windows.old" still exists, that means you did not run a "clean reinstall". Could you clarify the precise method and steps you used to update your computer to build 1809?

    – music2myear
    Dec 13 '18 at 17:03











  • And finally, what are you actually trying to accomplish: Are you just trying to remove the All Application Packages permission entry from your own files (what the body of the question seems to say) or are you trying to delete Windows.old and you believe this permission is preventing you from doing so, or something else entirely? Please EDIT your question to make this more clear.

    – music2myear
    Dec 13 '18 at 17:04

















Let us continue this discussion in chat.

– TheGoddessInari
Dec 13 '18 at 3:54





Let us continue this discussion in chat.

– TheGoddessInari
Dec 13 '18 at 3:54













This is usually a driver package. Removing the driver clears the lock. This question has been asked and answered here before. Did you check the other questions about windows.old?

– music2myear
Dec 13 '18 at 4:40







This is usually a driver package. Removing the driver clears the lock. This question has been asked and answered here before. Did you check the other questions about windows.old?

– music2myear
Dec 13 '18 at 4:40















I checked other questions, there isn't a driver involved that I'm aware unless Microsoft is being stupid with one. Things aren't locked, there is no permission denied, removing "ALL APPLICATION PACKAGES" iterates through all of the files like usual, no errors, but the phantom permission stays. Same with cacls, icacls, powershell set-acl, etc.

– TheGoddessInari
Dec 13 '18 at 4:45





I checked other questions, there isn't a driver involved that I'm aware unless Microsoft is being stupid with one. Things aren't locked, there is no permission denied, removing "ALL APPLICATION PACKAGES" iterates through all of the files like usual, no errors, but the phantom permission stays. Same with cacls, icacls, powershell set-acl, etc.

– TheGoddessInari
Dec 13 '18 at 4:45













Another point: A "clean reinstall" typically involves formatting your hard drive prior to or during the installation process. If "Windows.old" still exists, that means you did not run a "clean reinstall". Could you clarify the precise method and steps you used to update your computer to build 1809?

– music2myear
Dec 13 '18 at 17:03





Another point: A "clean reinstall" typically involves formatting your hard drive prior to or during the installation process. If "Windows.old" still exists, that means you did not run a "clean reinstall". Could you clarify the precise method and steps you used to update your computer to build 1809?

– music2myear
Dec 13 '18 at 17:03













And finally, what are you actually trying to accomplish: Are you just trying to remove the All Application Packages permission entry from your own files (what the body of the question seems to say) or are you trying to delete Windows.old and you believe this permission is preventing you from doing so, or something else entirely? Please EDIT your question to make this more clear.

– music2myear
Dec 13 '18 at 17:04





And finally, what are you actually trying to accomplish: Are you just trying to remove the All Application Packages permission entry from your own files (what the body of the question seems to say) or are you trying to delete Windows.old and you believe this permission is preventing you from doing so, or something else entirely? Please EDIT your question to make this more clear.

– music2myear
Dec 13 '18 at 17:04










1 Answer
1






active

oldest

votes


















-1














You can follow the below steps for deleting the Windows.Old folder by login as administrator.




  1. Press the Windows + R keys to open the Run dialog, type cleanmgr,
    and click/tap on OK to open Disk Cleanup.

  2. If you have more than one drive or partition on your PC, then select the Windows C: drive, and click/tap on OK.

  3. Click/tap on the Cleanup system files button.

  4. If prompted by UAC, click/tap on Yes.

  5. Repeat step 2 above.

  6. Check the Previous Windows installation(s) box, and click/tap on OK.

  7. Click/tap on Delete Files to confirm.

  8. When Disk Cleanup finishes, the C:Windows.old folder will be deleted.


Update: If you want to move the files from the Windows.Old folder, you may need to take ownership and grant full permissions to your account. This can be done by using the freeware TakeOwnershipPro.






share|improve this answer


























  • I really obviously don't want to delete all of my personal files and documents, nor would that at-all help with the issue.

    – TheGoddessInari
    Dec 13 '18 at 3:09













  • @TheGoddessInari I've updated my answer. To solve the permission issue, you need to change the ownership of all files inside C:Windows.old.

    – E.Swaff
    Dec 13 '18 at 3:23











  • That was the first thing I tried. It's not about permission denied, or any other error, but a bad phantom permission that persists regardless of trying to remove it.

    – TheGoddessInari
    Dec 13 '18 at 3:34











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383171%2fc-windows-old-has-a-phantom-permission-how-do-i-rid-myself-of-it%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









-1














You can follow the below steps for deleting the Windows.Old folder by login as administrator.




  1. Press the Windows + R keys to open the Run dialog, type cleanmgr,
    and click/tap on OK to open Disk Cleanup.

  2. If you have more than one drive or partition on your PC, then select the Windows C: drive, and click/tap on OK.

  3. Click/tap on the Cleanup system files button.

  4. If prompted by UAC, click/tap on Yes.

  5. Repeat step 2 above.

  6. Check the Previous Windows installation(s) box, and click/tap on OK.

  7. Click/tap on Delete Files to confirm.

  8. When Disk Cleanup finishes, the C:Windows.old folder will be deleted.


Update: If you want to move the files from the Windows.Old folder, you may need to take ownership and grant full permissions to your account. This can be done by using the freeware TakeOwnershipPro.






share|improve this answer


























  • I really obviously don't want to delete all of my personal files and documents, nor would that at-all help with the issue.

    – TheGoddessInari
    Dec 13 '18 at 3:09













  • @TheGoddessInari I've updated my answer. To solve the permission issue, you need to change the ownership of all files inside C:Windows.old.

    – E.Swaff
    Dec 13 '18 at 3:23











  • That was the first thing I tried. It's not about permission denied, or any other error, but a bad phantom permission that persists regardless of trying to remove it.

    – TheGoddessInari
    Dec 13 '18 at 3:34
















-1














You can follow the below steps for deleting the Windows.Old folder by login as administrator.




  1. Press the Windows + R keys to open the Run dialog, type cleanmgr,
    and click/tap on OK to open Disk Cleanup.

  2. If you have more than one drive or partition on your PC, then select the Windows C: drive, and click/tap on OK.

  3. Click/tap on the Cleanup system files button.

  4. If prompted by UAC, click/tap on Yes.

  5. Repeat step 2 above.

  6. Check the Previous Windows installation(s) box, and click/tap on OK.

  7. Click/tap on Delete Files to confirm.

  8. When Disk Cleanup finishes, the C:Windows.old folder will be deleted.


Update: If you want to move the files from the Windows.Old folder, you may need to take ownership and grant full permissions to your account. This can be done by using the freeware TakeOwnershipPro.






share|improve this answer


























  • I really obviously don't want to delete all of my personal files and documents, nor would that at-all help with the issue.

    – TheGoddessInari
    Dec 13 '18 at 3:09













  • @TheGoddessInari I've updated my answer. To solve the permission issue, you need to change the ownership of all files inside C:Windows.old.

    – E.Swaff
    Dec 13 '18 at 3:23











  • That was the first thing I tried. It's not about permission denied, or any other error, but a bad phantom permission that persists regardless of trying to remove it.

    – TheGoddessInari
    Dec 13 '18 at 3:34














-1












-1








-1







You can follow the below steps for deleting the Windows.Old folder by login as administrator.




  1. Press the Windows + R keys to open the Run dialog, type cleanmgr,
    and click/tap on OK to open Disk Cleanup.

  2. If you have more than one drive or partition on your PC, then select the Windows C: drive, and click/tap on OK.

  3. Click/tap on the Cleanup system files button.

  4. If prompted by UAC, click/tap on Yes.

  5. Repeat step 2 above.

  6. Check the Previous Windows installation(s) box, and click/tap on OK.

  7. Click/tap on Delete Files to confirm.

  8. When Disk Cleanup finishes, the C:Windows.old folder will be deleted.


Update: If you want to move the files from the Windows.Old folder, you may need to take ownership and grant full permissions to your account. This can be done by using the freeware TakeOwnershipPro.






share|improve this answer















You can follow the below steps for deleting the Windows.Old folder by login as administrator.




  1. Press the Windows + R keys to open the Run dialog, type cleanmgr,
    and click/tap on OK to open Disk Cleanup.

  2. If you have more than one drive or partition on your PC, then select the Windows C: drive, and click/tap on OK.

  3. Click/tap on the Cleanup system files button.

  4. If prompted by UAC, click/tap on Yes.

  5. Repeat step 2 above.

  6. Check the Previous Windows installation(s) box, and click/tap on OK.

  7. Click/tap on Delete Files to confirm.

  8. When Disk Cleanup finishes, the C:Windows.old folder will be deleted.


Update: If you want to move the files from the Windows.Old folder, you may need to take ownership and grant full permissions to your account. This can be done by using the freeware TakeOwnershipPro.







share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 13 '18 at 3:21

























answered Dec 13 '18 at 3:00









E.SwaffE.Swaff

12




12













  • I really obviously don't want to delete all of my personal files and documents, nor would that at-all help with the issue.

    – TheGoddessInari
    Dec 13 '18 at 3:09













  • @TheGoddessInari I've updated my answer. To solve the permission issue, you need to change the ownership of all files inside C:Windows.old.

    – E.Swaff
    Dec 13 '18 at 3:23











  • That was the first thing I tried. It's not about permission denied, or any other error, but a bad phantom permission that persists regardless of trying to remove it.

    – TheGoddessInari
    Dec 13 '18 at 3:34



















  • I really obviously don't want to delete all of my personal files and documents, nor would that at-all help with the issue.

    – TheGoddessInari
    Dec 13 '18 at 3:09













  • @TheGoddessInari I've updated my answer. To solve the permission issue, you need to change the ownership of all files inside C:Windows.old.

    – E.Swaff
    Dec 13 '18 at 3:23











  • That was the first thing I tried. It's not about permission denied, or any other error, but a bad phantom permission that persists regardless of trying to remove it.

    – TheGoddessInari
    Dec 13 '18 at 3:34

















I really obviously don't want to delete all of my personal files and documents, nor would that at-all help with the issue.

– TheGoddessInari
Dec 13 '18 at 3:09







I really obviously don't want to delete all of my personal files and documents, nor would that at-all help with the issue.

– TheGoddessInari
Dec 13 '18 at 3:09















@TheGoddessInari I've updated my answer. To solve the permission issue, you need to change the ownership of all files inside C:Windows.old.

– E.Swaff
Dec 13 '18 at 3:23





@TheGoddessInari I've updated my answer. To solve the permission issue, you need to change the ownership of all files inside C:Windows.old.

– E.Swaff
Dec 13 '18 at 3:23













That was the first thing I tried. It's not about permission denied, or any other error, but a bad phantom permission that persists regardless of trying to remove it.

– TheGoddessInari
Dec 13 '18 at 3:34





That was the first thing I tried. It's not about permission denied, or any other error, but a bad phantom permission that persists regardless of trying to remove it.

– TheGoddessInari
Dec 13 '18 at 3:34


















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1383171%2fc-windows-old-has-a-phantom-permission-how-do-i-rid-myself-of-it%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Список кардиналов, возведённых папой римским Каликстом III

Deduzione

Mysql.sock missing - “Can't connect to local MySQL server through socket”