Unable to delete a file or take ownership on Win7x64












15















I'm a developer and as part of the build process, a Microsoft dll is copied to a certain
folder. That file copy is now failing as the target can't be overwritten.



I decided to delete it by hand (using an admin account but a non-elevated explorer) so browsed to the folder and attempted a delete. This failed (Require permission from the Administrator). The same applies when using an elevated explorer.



So I tried Properties->Security->Advanced->Ownership



The current owner is showing as Unable to display current owner. I can't take ownership (a simple Access Denied message with no elaboration). Elevated Command Prompt/PowerShell don't help either (both give an Access Denied in their own way).



Process explorer shows no open handles on the file.



Eventually, I booted to linux and deleted the file but what I'd like to know is what caused it?



Security Essentials had no issues with the file. It's digitally signed by MS and the signatures match.










share|improve this question

























  • possible duplicate of File I can't take ownership of

    – CharlieRB
    Oct 16 '12 at 14:12











  • @CharlieRB I've read it - but as you can see, my problem isn't removing the file but understanding what the "loss of ownership" is caused by.

    – Basic
    Oct 16 '12 at 14:23











  • You are right. Sorry. Guess I got lost in reading it and misunderstood the question.

    – CharlieRB
    Oct 16 '12 at 14:35











  • In some cases, deleting a file needs to be done externally, e.g. Safe Mode, or as you did booting into another OS. If the file has certain attributes (I'm not exactly sure but I think System affects it), along with the existing SYSTEM permissions, that makes it untouchable in the context of the booted Windows. Obviously once you go away from that context, it becomes irrelevant, but inside Windows 7 (and 8) some files are certainly undeletable.

    – user3463
    Oct 16 '12 at 16:05













  • @RandolphWest Thanks for the answer. Can you explain a little more? I know anything with an open handle can't be modified but suspect that if I deleted everything I could in my windows dir then rebooted, I'd have bricked my machine - so there's no "required for windows" flag set on a lot of files. Pagefile/etc come under the heading of open handles. I just don't see how a DLL buried in a folder on my D drive which has been replaced every few hours for days can suddenly be flagged as undeletable (nor what that "flag" is?)

    – Basic
    Oct 16 '12 at 16:39
















15















I'm a developer and as part of the build process, a Microsoft dll is copied to a certain
folder. That file copy is now failing as the target can't be overwritten.



I decided to delete it by hand (using an admin account but a non-elevated explorer) so browsed to the folder and attempted a delete. This failed (Require permission from the Administrator). The same applies when using an elevated explorer.



So I tried Properties->Security->Advanced->Ownership



The current owner is showing as Unable to display current owner. I can't take ownership (a simple Access Denied message with no elaboration). Elevated Command Prompt/PowerShell don't help either (both give an Access Denied in their own way).



Process explorer shows no open handles on the file.



Eventually, I booted to linux and deleted the file but what I'd like to know is what caused it?



Security Essentials had no issues with the file. It's digitally signed by MS and the signatures match.










share|improve this question

























  • possible duplicate of File I can't take ownership of

    – CharlieRB
    Oct 16 '12 at 14:12











  • @CharlieRB I've read it - but as you can see, my problem isn't removing the file but understanding what the "loss of ownership" is caused by.

    – Basic
    Oct 16 '12 at 14:23











  • You are right. Sorry. Guess I got lost in reading it and misunderstood the question.

    – CharlieRB
    Oct 16 '12 at 14:35











  • In some cases, deleting a file needs to be done externally, e.g. Safe Mode, or as you did booting into another OS. If the file has certain attributes (I'm not exactly sure but I think System affects it), along with the existing SYSTEM permissions, that makes it untouchable in the context of the booted Windows. Obviously once you go away from that context, it becomes irrelevant, but inside Windows 7 (and 8) some files are certainly undeletable.

    – user3463
    Oct 16 '12 at 16:05













  • @RandolphWest Thanks for the answer. Can you explain a little more? I know anything with an open handle can't be modified but suspect that if I deleted everything I could in my windows dir then rebooted, I'd have bricked my machine - so there's no "required for windows" flag set on a lot of files. Pagefile/etc come under the heading of open handles. I just don't see how a DLL buried in a folder on my D drive which has been replaced every few hours for days can suddenly be flagged as undeletable (nor what that "flag" is?)

    – Basic
    Oct 16 '12 at 16:39














15












15








15


5






I'm a developer and as part of the build process, a Microsoft dll is copied to a certain
folder. That file copy is now failing as the target can't be overwritten.



I decided to delete it by hand (using an admin account but a non-elevated explorer) so browsed to the folder and attempted a delete. This failed (Require permission from the Administrator). The same applies when using an elevated explorer.



So I tried Properties->Security->Advanced->Ownership



The current owner is showing as Unable to display current owner. I can't take ownership (a simple Access Denied message with no elaboration). Elevated Command Prompt/PowerShell don't help either (both give an Access Denied in their own way).



Process explorer shows no open handles on the file.



Eventually, I booted to linux and deleted the file but what I'd like to know is what caused it?



Security Essentials had no issues with the file. It's digitally signed by MS and the signatures match.










share|improve this question
















I'm a developer and as part of the build process, a Microsoft dll is copied to a certain
folder. That file copy is now failing as the target can't be overwritten.



I decided to delete it by hand (using an admin account but a non-elevated explorer) so browsed to the folder and attempted a delete. This failed (Require permission from the Administrator). The same applies when using an elevated explorer.



So I tried Properties->Security->Advanced->Ownership



The current owner is showing as Unable to display current owner. I can't take ownership (a simple Access Denied message with no elaboration). Elevated Command Prompt/PowerShell don't help either (both give an Access Denied in their own way).



Process explorer shows no open handles on the file.



Eventually, I booted to linux and deleted the file but what I'd like to know is what caused it?



Security Essentials had no issues with the file. It's digitally signed by MS and the signatures match.







windows-7 security permissions






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 1 '17 at 22:12









Mithrandir

3051314




3051314










asked Oct 16 '12 at 13:56









BasicBasic

65511129




65511129













  • possible duplicate of File I can't take ownership of

    – CharlieRB
    Oct 16 '12 at 14:12











  • @CharlieRB I've read it - but as you can see, my problem isn't removing the file but understanding what the "loss of ownership" is caused by.

    – Basic
    Oct 16 '12 at 14:23











  • You are right. Sorry. Guess I got lost in reading it and misunderstood the question.

    – CharlieRB
    Oct 16 '12 at 14:35











  • In some cases, deleting a file needs to be done externally, e.g. Safe Mode, or as you did booting into another OS. If the file has certain attributes (I'm not exactly sure but I think System affects it), along with the existing SYSTEM permissions, that makes it untouchable in the context of the booted Windows. Obviously once you go away from that context, it becomes irrelevant, but inside Windows 7 (and 8) some files are certainly undeletable.

    – user3463
    Oct 16 '12 at 16:05













  • @RandolphWest Thanks for the answer. Can you explain a little more? I know anything with an open handle can't be modified but suspect that if I deleted everything I could in my windows dir then rebooted, I'd have bricked my machine - so there's no "required for windows" flag set on a lot of files. Pagefile/etc come under the heading of open handles. I just don't see how a DLL buried in a folder on my D drive which has been replaced every few hours for days can suddenly be flagged as undeletable (nor what that "flag" is?)

    – Basic
    Oct 16 '12 at 16:39



















  • possible duplicate of File I can't take ownership of

    – CharlieRB
    Oct 16 '12 at 14:12











  • @CharlieRB I've read it - but as you can see, my problem isn't removing the file but understanding what the "loss of ownership" is caused by.

    – Basic
    Oct 16 '12 at 14:23











  • You are right. Sorry. Guess I got lost in reading it and misunderstood the question.

    – CharlieRB
    Oct 16 '12 at 14:35











  • In some cases, deleting a file needs to be done externally, e.g. Safe Mode, or as you did booting into another OS. If the file has certain attributes (I'm not exactly sure but I think System affects it), along with the existing SYSTEM permissions, that makes it untouchable in the context of the booted Windows. Obviously once you go away from that context, it becomes irrelevant, but inside Windows 7 (and 8) some files are certainly undeletable.

    – user3463
    Oct 16 '12 at 16:05













  • @RandolphWest Thanks for the answer. Can you explain a little more? I know anything with an open handle can't be modified but suspect that if I deleted everything I could in my windows dir then rebooted, I'd have bricked my machine - so there's no "required for windows" flag set on a lot of files. Pagefile/etc come under the heading of open handles. I just don't see how a DLL buried in a folder on my D drive which has been replaced every few hours for days can suddenly be flagged as undeletable (nor what that "flag" is?)

    – Basic
    Oct 16 '12 at 16:39

















possible duplicate of File I can't take ownership of

– CharlieRB
Oct 16 '12 at 14:12





possible duplicate of File I can't take ownership of

– CharlieRB
Oct 16 '12 at 14:12













@CharlieRB I've read it - but as you can see, my problem isn't removing the file but understanding what the "loss of ownership" is caused by.

– Basic
Oct 16 '12 at 14:23





@CharlieRB I've read it - but as you can see, my problem isn't removing the file but understanding what the "loss of ownership" is caused by.

– Basic
Oct 16 '12 at 14:23













You are right. Sorry. Guess I got lost in reading it and misunderstood the question.

– CharlieRB
Oct 16 '12 at 14:35





You are right. Sorry. Guess I got lost in reading it and misunderstood the question.

– CharlieRB
Oct 16 '12 at 14:35













In some cases, deleting a file needs to be done externally, e.g. Safe Mode, or as you did booting into another OS. If the file has certain attributes (I'm not exactly sure but I think System affects it), along with the existing SYSTEM permissions, that makes it untouchable in the context of the booted Windows. Obviously once you go away from that context, it becomes irrelevant, but inside Windows 7 (and 8) some files are certainly undeletable.

– user3463
Oct 16 '12 at 16:05







In some cases, deleting a file needs to be done externally, e.g. Safe Mode, or as you did booting into another OS. If the file has certain attributes (I'm not exactly sure but I think System affects it), along with the existing SYSTEM permissions, that makes it untouchable in the context of the booted Windows. Obviously once you go away from that context, it becomes irrelevant, but inside Windows 7 (and 8) some files are certainly undeletable.

– user3463
Oct 16 '12 at 16:05















@RandolphWest Thanks for the answer. Can you explain a little more? I know anything with an open handle can't be modified but suspect that if I deleted everything I could in my windows dir then rebooted, I'd have bricked my machine - so there's no "required for windows" flag set on a lot of files. Pagefile/etc come under the heading of open handles. I just don't see how a DLL buried in a folder on my D drive which has been replaced every few hours for days can suddenly be flagged as undeletable (nor what that "flag" is?)

– Basic
Oct 16 '12 at 16:39





@RandolphWest Thanks for the answer. Can you explain a little more? I know anything with an open handle can't be modified but suspect that if I deleted everything I could in my windows dir then rebooted, I'd have bricked my machine - so there's no "required for windows" flag set on a lot of files. Pagefile/etc come under the heading of open handles. I just don't see how a DLL buried in a folder on my D drive which has been replaced every few hours for days can suddenly be flagged as undeletable (nor what that "flag" is?)

– Basic
Oct 16 '12 at 16:39










6 Answers
6






active

oldest

votes


















18














I had this issue too for a file I manage with SourceTree ( git client ). This file had no 'Owner'. I just noticed that closing down all application susceptible to use it, removed it magically.
The other option was to remove the file in windows' safe-mode. I don't know why this happened though and I'm curious too as to why this happened.






share|improve this answer



















  • 2





    This happened to me too, which is what brought me to this question. A git checkout created a folder, then afterwards I couldn't do anything with it (and couldn't checkout anything else that would modify it!). Your comment helped me realise I had other git bash windows open; once I closed them all the folder magically deleted :)

    – Tim Malone
    Apr 26 '16 at 0:50



















3














One solution works for me on Windows 7 :



Right click the hard disk drive,
==> Properties / Tools / Check now
....
And then try to delete again, it should work.






share|improve this answer
























  • Warning: You have to reboot and the reboot may take several hours.

    – User
    Dec 8 '16 at 20:53











  • Update: After several hours, it did fix the problem.

    – User
    Dec 9 '16 at 19:05



















1














In my case it was a file I'd used Firefox to download. Couldn't display owner, change ownership or delete the file (though it was readable). Using lockhunter to delete the firefox lock on the file worked.






share|improve this answer
























  • Lockhunter worked for me too. Thanks.

    – Steve Dowling
    Feb 18 '16 at 9:42



















1














I found that a folder with "Unable to display current owner" was locked as a library location (such as Music Library). I removed that as a Location and I could delete folder.






share|improve this answer
























  • That's one hell of a gotcha, I would never have thought of that. Thanks. It wasn't the issue here, but it will definitely help others in future with the same symptoms.

    – Basic
    Oct 30 '16 at 21:33



















0














I had the same issue with some files in the windows directory, most likely caused by a virus.



running sfc /scannow fixed the problem for me






share|improve this answer



















  • 1





    "most likely caused by a virus" xkcd.com/1180

    – Basic
    Dec 10 '14 at 11:51



















-1














Open command prompt with admin rights, then type:



net user administrator - this will display current settings.



Use net user administrator /active:yes to activate if needed.



This is the built-in administrator account for managing the system. It is usually not active.






share|improve this answer



















  • 1





    Thanks for the tip but if it was owned by the local admin account, 1) wouldn't another admin be able to take ownership and 2) wouldn't the security dialog have identified the owner? It was my understanding that only the SYSTEM account had higher permissions than a user in the administrator group

    – Basic
    Oct 16 '12 at 14:27






  • 1





    Your understanding is correct, @Basic.

    – user3463
    Oct 16 '12 at 16:06











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%2f488487%2funable-to-delete-a-file-or-take-ownership-on-win7x64%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























6 Answers
6






active

oldest

votes








6 Answers
6






active

oldest

votes









active

oldest

votes






active

oldest

votes









18














I had this issue too for a file I manage with SourceTree ( git client ). This file had no 'Owner'. I just noticed that closing down all application susceptible to use it, removed it magically.
The other option was to remove the file in windows' safe-mode. I don't know why this happened though and I'm curious too as to why this happened.






share|improve this answer



















  • 2





    This happened to me too, which is what brought me to this question. A git checkout created a folder, then afterwards I couldn't do anything with it (and couldn't checkout anything else that would modify it!). Your comment helped me realise I had other git bash windows open; once I closed them all the folder magically deleted :)

    – Tim Malone
    Apr 26 '16 at 0:50
















18














I had this issue too for a file I manage with SourceTree ( git client ). This file had no 'Owner'. I just noticed that closing down all application susceptible to use it, removed it magically.
The other option was to remove the file in windows' safe-mode. I don't know why this happened though and I'm curious too as to why this happened.






share|improve this answer



















  • 2





    This happened to me too, which is what brought me to this question. A git checkout created a folder, then afterwards I couldn't do anything with it (and couldn't checkout anything else that would modify it!). Your comment helped me realise I had other git bash windows open; once I closed them all the folder magically deleted :)

    – Tim Malone
    Apr 26 '16 at 0:50














18












18








18







I had this issue too for a file I manage with SourceTree ( git client ). This file had no 'Owner'. I just noticed that closing down all application susceptible to use it, removed it magically.
The other option was to remove the file in windows' safe-mode. I don't know why this happened though and I'm curious too as to why this happened.






share|improve this answer













I had this issue too for a file I manage with SourceTree ( git client ). This file had no 'Owner'. I just noticed that closing down all application susceptible to use it, removed it magically.
The other option was to remove the file in windows' safe-mode. I don't know why this happened though and I'm curious too as to why this happened.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 26 '13 at 15:50









DarkUrseDarkUrse

34637




34637








  • 2





    This happened to me too, which is what brought me to this question. A git checkout created a folder, then afterwards I couldn't do anything with it (and couldn't checkout anything else that would modify it!). Your comment helped me realise I had other git bash windows open; once I closed them all the folder magically deleted :)

    – Tim Malone
    Apr 26 '16 at 0:50














  • 2





    This happened to me too, which is what brought me to this question. A git checkout created a folder, then afterwards I couldn't do anything with it (and couldn't checkout anything else that would modify it!). Your comment helped me realise I had other git bash windows open; once I closed them all the folder magically deleted :)

    – Tim Malone
    Apr 26 '16 at 0:50








2




2





This happened to me too, which is what brought me to this question. A git checkout created a folder, then afterwards I couldn't do anything with it (and couldn't checkout anything else that would modify it!). Your comment helped me realise I had other git bash windows open; once I closed them all the folder magically deleted :)

– Tim Malone
Apr 26 '16 at 0:50





This happened to me too, which is what brought me to this question. A git checkout created a folder, then afterwards I couldn't do anything with it (and couldn't checkout anything else that would modify it!). Your comment helped me realise I had other git bash windows open; once I closed them all the folder magically deleted :)

– Tim Malone
Apr 26 '16 at 0:50













3














One solution works for me on Windows 7 :



Right click the hard disk drive,
==> Properties / Tools / Check now
....
And then try to delete again, it should work.






share|improve this answer
























  • Warning: You have to reboot and the reboot may take several hours.

    – User
    Dec 8 '16 at 20:53











  • Update: After several hours, it did fix the problem.

    – User
    Dec 9 '16 at 19:05
















3














One solution works for me on Windows 7 :



Right click the hard disk drive,
==> Properties / Tools / Check now
....
And then try to delete again, it should work.






share|improve this answer
























  • Warning: You have to reboot and the reboot may take several hours.

    – User
    Dec 8 '16 at 20:53











  • Update: After several hours, it did fix the problem.

    – User
    Dec 9 '16 at 19:05














3












3








3







One solution works for me on Windows 7 :



Right click the hard disk drive,
==> Properties / Tools / Check now
....
And then try to delete again, it should work.






share|improve this answer













One solution works for me on Windows 7 :



Right click the hard disk drive,
==> Properties / Tools / Check now
....
And then try to delete again, it should work.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 11 '13 at 16:48









BrunoBruno

392




392













  • Warning: You have to reboot and the reboot may take several hours.

    – User
    Dec 8 '16 at 20:53











  • Update: After several hours, it did fix the problem.

    – User
    Dec 9 '16 at 19:05



















  • Warning: You have to reboot and the reboot may take several hours.

    – User
    Dec 8 '16 at 20:53











  • Update: After several hours, it did fix the problem.

    – User
    Dec 9 '16 at 19:05

















Warning: You have to reboot and the reboot may take several hours.

– User
Dec 8 '16 at 20:53





Warning: You have to reboot and the reboot may take several hours.

– User
Dec 8 '16 at 20:53













Update: After several hours, it did fix the problem.

– User
Dec 9 '16 at 19:05





Update: After several hours, it did fix the problem.

– User
Dec 9 '16 at 19:05











1














In my case it was a file I'd used Firefox to download. Couldn't display owner, change ownership or delete the file (though it was readable). Using lockhunter to delete the firefox lock on the file worked.






share|improve this answer
























  • Lockhunter worked for me too. Thanks.

    – Steve Dowling
    Feb 18 '16 at 9:42
















1














In my case it was a file I'd used Firefox to download. Couldn't display owner, change ownership or delete the file (though it was readable). Using lockhunter to delete the firefox lock on the file worked.






share|improve this answer
























  • Lockhunter worked for me too. Thanks.

    – Steve Dowling
    Feb 18 '16 at 9:42














1












1








1







In my case it was a file I'd used Firefox to download. Couldn't display owner, change ownership or delete the file (though it was readable). Using lockhunter to delete the firefox lock on the file worked.






share|improve this answer













In my case it was a file I'd used Firefox to download. Couldn't display owner, change ownership or delete the file (though it was readable). Using lockhunter to delete the firefox lock on the file worked.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 2 '15 at 15:52









user528821user528821

111




111













  • Lockhunter worked for me too. Thanks.

    – Steve Dowling
    Feb 18 '16 at 9:42



















  • Lockhunter worked for me too. Thanks.

    – Steve Dowling
    Feb 18 '16 at 9:42

















Lockhunter worked for me too. Thanks.

– Steve Dowling
Feb 18 '16 at 9:42





Lockhunter worked for me too. Thanks.

– Steve Dowling
Feb 18 '16 at 9:42











1














I found that a folder with "Unable to display current owner" was locked as a library location (such as Music Library). I removed that as a Location and I could delete folder.






share|improve this answer
























  • That's one hell of a gotcha, I would never have thought of that. Thanks. It wasn't the issue here, but it will definitely help others in future with the same symptoms.

    – Basic
    Oct 30 '16 at 21:33
















1














I found that a folder with "Unable to display current owner" was locked as a library location (such as Music Library). I removed that as a Location and I could delete folder.






share|improve this answer
























  • That's one hell of a gotcha, I would never have thought of that. Thanks. It wasn't the issue here, but it will definitely help others in future with the same symptoms.

    – Basic
    Oct 30 '16 at 21:33














1












1








1







I found that a folder with "Unable to display current owner" was locked as a library location (such as Music Library). I removed that as a Location and I could delete folder.






share|improve this answer













I found that a folder with "Unable to display current owner" was locked as a library location (such as Music Library). I removed that as a Location and I could delete folder.







share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 30 '16 at 18:45









MakMak

111




111













  • That's one hell of a gotcha, I would never have thought of that. Thanks. It wasn't the issue here, but it will definitely help others in future with the same symptoms.

    – Basic
    Oct 30 '16 at 21:33



















  • That's one hell of a gotcha, I would never have thought of that. Thanks. It wasn't the issue here, but it will definitely help others in future with the same symptoms.

    – Basic
    Oct 30 '16 at 21:33

















That's one hell of a gotcha, I would never have thought of that. Thanks. It wasn't the issue here, but it will definitely help others in future with the same symptoms.

– Basic
Oct 30 '16 at 21:33





That's one hell of a gotcha, I would never have thought of that. Thanks. It wasn't the issue here, but it will definitely help others in future with the same symptoms.

– Basic
Oct 30 '16 at 21:33











0














I had the same issue with some files in the windows directory, most likely caused by a virus.



running sfc /scannow fixed the problem for me






share|improve this answer



















  • 1





    "most likely caused by a virus" xkcd.com/1180

    – Basic
    Dec 10 '14 at 11:51
















0














I had the same issue with some files in the windows directory, most likely caused by a virus.



running sfc /scannow fixed the problem for me






share|improve this answer



















  • 1





    "most likely caused by a virus" xkcd.com/1180

    – Basic
    Dec 10 '14 at 11:51














0












0








0







I had the same issue with some files in the windows directory, most likely caused by a virus.



running sfc /scannow fixed the problem for me






share|improve this answer













I had the same issue with some files in the windows directory, most likely caused by a virus.



running sfc /scannow fixed the problem for me







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 10 '14 at 11:26









Dieter CasierDieter Casier

1




1








  • 1





    "most likely caused by a virus" xkcd.com/1180

    – Basic
    Dec 10 '14 at 11:51














  • 1





    "most likely caused by a virus" xkcd.com/1180

    – Basic
    Dec 10 '14 at 11:51








1




1





"most likely caused by a virus" xkcd.com/1180

– Basic
Dec 10 '14 at 11:51





"most likely caused by a virus" xkcd.com/1180

– Basic
Dec 10 '14 at 11:51











-1














Open command prompt with admin rights, then type:



net user administrator - this will display current settings.



Use net user administrator /active:yes to activate if needed.



This is the built-in administrator account for managing the system. It is usually not active.






share|improve this answer



















  • 1





    Thanks for the tip but if it was owned by the local admin account, 1) wouldn't another admin be able to take ownership and 2) wouldn't the security dialog have identified the owner? It was my understanding that only the SYSTEM account had higher permissions than a user in the administrator group

    – Basic
    Oct 16 '12 at 14:27






  • 1





    Your understanding is correct, @Basic.

    – user3463
    Oct 16 '12 at 16:06
















-1














Open command prompt with admin rights, then type:



net user administrator - this will display current settings.



Use net user administrator /active:yes to activate if needed.



This is the built-in administrator account for managing the system. It is usually not active.






share|improve this answer



















  • 1





    Thanks for the tip but if it was owned by the local admin account, 1) wouldn't another admin be able to take ownership and 2) wouldn't the security dialog have identified the owner? It was my understanding that only the SYSTEM account had higher permissions than a user in the administrator group

    – Basic
    Oct 16 '12 at 14:27






  • 1





    Your understanding is correct, @Basic.

    – user3463
    Oct 16 '12 at 16:06














-1












-1








-1







Open command prompt with admin rights, then type:



net user administrator - this will display current settings.



Use net user administrator /active:yes to activate if needed.



This is the built-in administrator account for managing the system. It is usually not active.






share|improve this answer













Open command prompt with admin rights, then type:



net user administrator - this will display current settings.



Use net user administrator /active:yes to activate if needed.



This is the built-in administrator account for managing the system. It is usually not active.







share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 16 '12 at 14:24









snayobsnayob

3,85911018




3,85911018








  • 1





    Thanks for the tip but if it was owned by the local admin account, 1) wouldn't another admin be able to take ownership and 2) wouldn't the security dialog have identified the owner? It was my understanding that only the SYSTEM account had higher permissions than a user in the administrator group

    – Basic
    Oct 16 '12 at 14:27






  • 1





    Your understanding is correct, @Basic.

    – user3463
    Oct 16 '12 at 16:06














  • 1





    Thanks for the tip but if it was owned by the local admin account, 1) wouldn't another admin be able to take ownership and 2) wouldn't the security dialog have identified the owner? It was my understanding that only the SYSTEM account had higher permissions than a user in the administrator group

    – Basic
    Oct 16 '12 at 14:27






  • 1





    Your understanding is correct, @Basic.

    – user3463
    Oct 16 '12 at 16:06








1




1





Thanks for the tip but if it was owned by the local admin account, 1) wouldn't another admin be able to take ownership and 2) wouldn't the security dialog have identified the owner? It was my understanding that only the SYSTEM account had higher permissions than a user in the administrator group

– Basic
Oct 16 '12 at 14:27





Thanks for the tip but if it was owned by the local admin account, 1) wouldn't another admin be able to take ownership and 2) wouldn't the security dialog have identified the owner? It was my understanding that only the SYSTEM account had higher permissions than a user in the administrator group

– Basic
Oct 16 '12 at 14:27




1




1





Your understanding is correct, @Basic.

– user3463
Oct 16 '12 at 16:06





Your understanding is correct, @Basic.

– user3463
Oct 16 '12 at 16:06


















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%2f488487%2funable-to-delete-a-file-or-take-ownership-on-win7x64%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

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

Eduardo VII do Reino Unido