Can't delete Foxit Reader directory, not even as Administrator, on Windows 8
I tried to upgrade Foxit Reader and it left the directory in an unreadable state. I can't view the directory, nor even delete it, not even as Administrator. How do I get rid of it so I can re-install?
C:Program Files (x86)Foxit Software>takeown /f "Foxit Reader"
ERROR: Access is denied.
C:Program Files (x86)Foxit Software>takeown /a /f "Foxit Reader"
ERROR: Access is denied.
C:Program Files (x86)Foxit Software>icacls "Foxit Reader" /setowner Administrator
Foxit Reader: Access is denied.
Successfully processed 0 files; Failed processing 1 files
Even ran chkdsk, which found no problem:
C:Program Files (x86)Foxit Software>chkdsk
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
643840 file records processed.
File verification completed.
7590 large file records processed.
0 bad file records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
819780 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
87971 data files processed.
CHKDSK is verifying Usn Journal...
36537832 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
961180671 KB total disk space.
283748976 KB in 547635 files.
271996 KB in 87972 indexes.
0 KB in bad sectors.
778755 KB in use by the system.
65536 KB occupied by the log file.
676380944 KB available on disk.
4096 bytes in each allocation unit.
240295167 total allocation units on disk.
169095236 allocation units available on disk.
windows-8 file-permissions foxit-reader
add a comment |
I tried to upgrade Foxit Reader and it left the directory in an unreadable state. I can't view the directory, nor even delete it, not even as Administrator. How do I get rid of it so I can re-install?
C:Program Files (x86)Foxit Software>takeown /f "Foxit Reader"
ERROR: Access is denied.
C:Program Files (x86)Foxit Software>takeown /a /f "Foxit Reader"
ERROR: Access is denied.
C:Program Files (x86)Foxit Software>icacls "Foxit Reader" /setowner Administrator
Foxit Reader: Access is denied.
Successfully processed 0 files; Failed processing 1 files
Even ran chkdsk, which found no problem:
C:Program Files (x86)Foxit Software>chkdsk
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
643840 file records processed.
File verification completed.
7590 large file records processed.
0 bad file records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
819780 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
87971 data files processed.
CHKDSK is verifying Usn Journal...
36537832 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
961180671 KB total disk space.
283748976 KB in 547635 files.
271996 KB in 87972 indexes.
0 KB in bad sectors.
778755 KB in use by the system.
65536 KB occupied by the log file.
676380944 KB available on disk.
4096 bytes in each allocation unit.
240295167 total allocation units on disk.
169095236 allocation units available on disk.
windows-8 file-permissions foxit-reader
1
Try to find out if any process has a file handle on it, among others you can use sysinternals process explorer.
– Martin
Jun 6 '13 at 20:08
add a comment |
I tried to upgrade Foxit Reader and it left the directory in an unreadable state. I can't view the directory, nor even delete it, not even as Administrator. How do I get rid of it so I can re-install?
C:Program Files (x86)Foxit Software>takeown /f "Foxit Reader"
ERROR: Access is denied.
C:Program Files (x86)Foxit Software>takeown /a /f "Foxit Reader"
ERROR: Access is denied.
C:Program Files (x86)Foxit Software>icacls "Foxit Reader" /setowner Administrator
Foxit Reader: Access is denied.
Successfully processed 0 files; Failed processing 1 files
Even ran chkdsk, which found no problem:
C:Program Files (x86)Foxit Software>chkdsk
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
643840 file records processed.
File verification completed.
7590 large file records processed.
0 bad file records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
819780 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
87971 data files processed.
CHKDSK is verifying Usn Journal...
36537832 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
961180671 KB total disk space.
283748976 KB in 547635 files.
271996 KB in 87972 indexes.
0 KB in bad sectors.
778755 KB in use by the system.
65536 KB occupied by the log file.
676380944 KB available on disk.
4096 bytes in each allocation unit.
240295167 total allocation units on disk.
169095236 allocation units available on disk.
windows-8 file-permissions foxit-reader
I tried to upgrade Foxit Reader and it left the directory in an unreadable state. I can't view the directory, nor even delete it, not even as Administrator. How do I get rid of it so I can re-install?
C:Program Files (x86)Foxit Software>takeown /f "Foxit Reader"
ERROR: Access is denied.
C:Program Files (x86)Foxit Software>takeown /a /f "Foxit Reader"
ERROR: Access is denied.
C:Program Files (x86)Foxit Software>icacls "Foxit Reader" /setowner Administrator
Foxit Reader: Access is denied.
Successfully processed 0 files; Failed processing 1 files
Even ran chkdsk, which found no problem:
C:Program Files (x86)Foxit Software>chkdsk
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
643840 file records processed.
File verification completed.
7590 large file records processed.
0 bad file records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
819780 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
87971 data files processed.
CHKDSK is verifying Usn Journal...
36537832 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
961180671 KB total disk space.
283748976 KB in 547635 files.
271996 KB in 87972 indexes.
0 KB in bad sectors.
778755 KB in use by the system.
65536 KB occupied by the log file.
676380944 KB available on disk.
4096 bytes in each allocation unit.
240295167 total allocation units on disk.
169095236 allocation units available on disk.
windows-8 file-permissions foxit-reader
windows-8 file-permissions foxit-reader
edited Apr 23 '17 at 20:25
djsmiley2k
4,90912335
4,90912335
asked Jun 6 '13 at 19:52
Chloe
2,421123976
2,421123976
1
Try to find out if any process has a file handle on it, among others you can use sysinternals process explorer.
– Martin
Jun 6 '13 at 20:08
add a comment |
1
Try to find out if any process has a file handle on it, among others you can use sysinternals process explorer.
– Martin
Jun 6 '13 at 20:08
1
1
Try to find out if any process has a file handle on it, among others you can use sysinternals process explorer.
– Martin
Jun 6 '13 at 20:08
Try to find out if any process has a file handle on it, among others you can use sysinternals process explorer.
– Martin
Jun 6 '13 at 20:08
add a comment |
1 Answer
1
active
oldest
votes
The problem was Brother Control Center had a lock on the file. I don't know why Brother Control Center was running - I did not run it, it does not start at boot - but it had a lock. I killed the process and the directory disappeared. I found the lock with 'Process Explorer' and searched for 'Foxit Reader'. There were two locks for the same process, 'BrCtrlCntr.exe'.
2
You just made my morning. Thank you.
– hwilbanks
Sep 27 '13 at 11:59
1
Cool, I ran into this problem again when trying to upgrade Oracle Virtual Box. Luckily I wrote it down! Also 'handle' by SysInternals is good for finding the locked file handle.
– Chloe
Mar 21 '14 at 18:17
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%2f604644%2fcant-delete-foxit-reader-directory-not-even-as-administrator-on-windows-8%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
The problem was Brother Control Center had a lock on the file. I don't know why Brother Control Center was running - I did not run it, it does not start at boot - but it had a lock. I killed the process and the directory disappeared. I found the lock with 'Process Explorer' and searched for 'Foxit Reader'. There were two locks for the same process, 'BrCtrlCntr.exe'.
2
You just made my morning. Thank you.
– hwilbanks
Sep 27 '13 at 11:59
1
Cool, I ran into this problem again when trying to upgrade Oracle Virtual Box. Luckily I wrote it down! Also 'handle' by SysInternals is good for finding the locked file handle.
– Chloe
Mar 21 '14 at 18:17
add a comment |
The problem was Brother Control Center had a lock on the file. I don't know why Brother Control Center was running - I did not run it, it does not start at boot - but it had a lock. I killed the process and the directory disappeared. I found the lock with 'Process Explorer' and searched for 'Foxit Reader'. There were two locks for the same process, 'BrCtrlCntr.exe'.
2
You just made my morning. Thank you.
– hwilbanks
Sep 27 '13 at 11:59
1
Cool, I ran into this problem again when trying to upgrade Oracle Virtual Box. Luckily I wrote it down! Also 'handle' by SysInternals is good for finding the locked file handle.
– Chloe
Mar 21 '14 at 18:17
add a comment |
The problem was Brother Control Center had a lock on the file. I don't know why Brother Control Center was running - I did not run it, it does not start at boot - but it had a lock. I killed the process and the directory disappeared. I found the lock with 'Process Explorer' and searched for 'Foxit Reader'. There were two locks for the same process, 'BrCtrlCntr.exe'.
The problem was Brother Control Center had a lock on the file. I don't know why Brother Control Center was running - I did not run it, it does not start at boot - but it had a lock. I killed the process and the directory disappeared. I found the lock with 'Process Explorer' and searched for 'Foxit Reader'. There were two locks for the same process, 'BrCtrlCntr.exe'.
answered Jun 6 '13 at 20:09
Chloe
2,421123976
2,421123976
2
You just made my morning. Thank you.
– hwilbanks
Sep 27 '13 at 11:59
1
Cool, I ran into this problem again when trying to upgrade Oracle Virtual Box. Luckily I wrote it down! Also 'handle' by SysInternals is good for finding the locked file handle.
– Chloe
Mar 21 '14 at 18:17
add a comment |
2
You just made my morning. Thank you.
– hwilbanks
Sep 27 '13 at 11:59
1
Cool, I ran into this problem again when trying to upgrade Oracle Virtual Box. Luckily I wrote it down! Also 'handle' by SysInternals is good for finding the locked file handle.
– Chloe
Mar 21 '14 at 18:17
2
2
You just made my morning. Thank you.
– hwilbanks
Sep 27 '13 at 11:59
You just made my morning. Thank you.
– hwilbanks
Sep 27 '13 at 11:59
1
1
Cool, I ran into this problem again when trying to upgrade Oracle Virtual Box. Luckily I wrote it down! Also 'handle' by SysInternals is good for finding the locked file handle.
– Chloe
Mar 21 '14 at 18:17
Cool, I ran into this problem again when trying to upgrade Oracle Virtual Box. Luckily I wrote it down! Also 'handle' by SysInternals is good for finding the locked file handle.
– Chloe
Mar 21 '14 at 18:17
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f604644%2fcant-delete-foxit-reader-directory-not-even-as-administrator-on-windows-8%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
1
Try to find out if any process has a file handle on it, among others you can use sysinternals process explorer.
– Martin
Jun 6 '13 at 20:08