using junctions and moving the Recycle Bin to the right partition
I have got two partitions on a PC running Windows XP:
C: system partition
D: data partition
Usually every user has got his user profile on
C:Documents and Settings<user>
But I have moved the user profiles to the D: partition and linked them to the old locations using the junction tool from sysinternals:
D:<user>
junction "D:<user>" "C:Documents and Settings<user>"
Everything works great, but the only annoying thing is the Recycle Bin:
When a user deletes a file (which physically is located somewhere in D:user), the file is moved to the Recycle Bin on the C: drive, which actually makes sense because Windows still thinks that it is somewhere in "C:Documents and Settingsuser". But this means that deleting files can take very long time.
So how can I tell Windows to use the Recycler on the D: partition instead?
I hope that you can understand the problem.
windows symbolic-link user-profiles recycle-bin junction
asked Sep 29 '10 at 16:50
DucDuc
211
add a comment |
I have got two partitions on a PC running Windows XP:
C: system partition
D: data partition
Usually every user has got his user profile on
C:Documents and Settings<user>
But I have moved the user profiles to the D: partition and linked them to the old locations using the junction tool from sysinternals:
D:<user>
junction "D:<user>" "C:Documents and Settings<user>"
Everything works great, but the only annoying thing is the Recycle Bin:
When a user deletes a file (which physically is located somewhere in D:user), the file is moved to the Recycle Bin on the C: drive, which actually makes sense because Windows still thinks that it is somewhere in "C:Documents and Settingsuser". But this means that deleting files can take very long time.
So how can I tell Windows to use the Recycler on the D: partition instead?
I hope that you can understand the problem.
windows symbolic-link user-profiles recycle-bin junction
asked Sep 29 '10 at 16:50
DucDuc
211
add a comment |
I have got two partitions on a PC running Windows XP:
C: system partition
D: data partition
Usually every user has got his user profile on
C:Documents and Settings<user>
But I have moved the user profiles to the D: partition and linked them to the old locations using the junction tool from sysinternals:
D:<user>
junction "D:<user>" "C:Documents and Settings<user>"
Everything works great, but the only annoying thing is the Recycle Bin:
When a user deletes a file (which physically is located somewhere in D:user), the file is moved to the Recycle Bin on the C: drive, which actually makes sense because Windows still thinks that it is somewhere in "C:Documents and Settingsuser". But this means that deleting files can take very long time.
So how can I tell Windows to use the Recycler on the D: partition instead?
I hope that you can understand the problem.
windows symbolic-link user-profiles recycle-bin junction
asked Sep 29 '10 at 16:50
DucDuc
211
I have got two partitions on a PC running Windows XP:
C: system partition
D: data partition
Usually every user has got his user profile on
C:Documents and Settings<user>
But I have moved the user profiles to the D: partition and linked them to the old locations using the junction tool from sysinternals:
D:<user>
junction "D:<user>" "C:Documents and Settings<user>"
Everything works great, but the only annoying thing is the Recycle Bin:
When a user deletes a file (which physically is located somewhere in D:user), the file is moved to the Recycle Bin on the C: drive, which actually makes sense because Windows still thinks that it is somewhere in "C:Documents and Settingsuser". But this means that deleting files can take very long time.
So how can I tell Windows to use the Recycler on the D: partition instead?
I hope that you can understand the problem.
windows symbolic-link user-profiles recycle-bin junction
windows symbolic-link user-profiles recycle-bin junction
asked Sep 29 '10 at 16:50
DucDuc
211
asked Sep 29 '10 at 16:50
DucDuc
211
asked Sep 29 '10 at 16:50
DucDuc
211
asked Sep 29 '10 at 16:50
DucDuc
211
asked Sep 29 '10 at 16:50
DucDuc
211
211
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Moving the Recycle Bin is not possible.
Plus there are some unfavorable consequences to performance to moving the Recycling bin to another drive.
answered Jan 4 '12 at 20:26
surfasbsurfasb
20.7k34270
add a comment |
I had a similar problem (on Win10): SSD system drive, HDD data drive, junctions worked, deleting to the recycle bin was no problem, but restoring stuff from the recycle bin resulted in a copy operation when deletion was triggered from inside the symlinked path (e.g. C:Usersmejunction-to-dfoo).
This problem can be circumvented by going into the Disk Management Console, removing the drive letter (D:) and adding a mount point (e.g. C:data). Just adding a mount point is not enough, the partition is not allowed to have a drive letter at all.
Why this happens: The recycle bin view has a column Original Location and also knows where the file is really located (drive letter). If the drive letter and Original Location are different (e.g. because a file was deleted from inside a symlink/junction), the restore operation will perform a copy operation. If a partition is only accessed via a mount point on the system drive, there is no conflict and the usual quick restore is performed.
TL;DR: Completely abandoning D: for C:d-drive solves the problem and has the additional benefit of making Windows slightly more Unix-y by not having to switch drive letters in the console and such.
Edit: And that's why we can't have nice things... no file indexing support for anything without a drive letter. Indexing across a mount point in windows
answered Jan 1 at 7:04
T NierathT Nierath
35419
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%2f194108%2fusing-junctions-and-moving-the-recycle-bin-to-the-right-partition%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Moving the Recycle Bin is not possible.
Plus there are some unfavorable consequences to performance to moving the Recycling bin to another drive.
answered Jan 4 '12 at 20:26
surfasbsurfasb
20.7k34270
add a comment |
Moving the Recycle Bin is not possible.
Plus there are some unfavorable consequences to performance to moving the Recycling bin to another drive.
answered Jan 4 '12 at 20:26
surfasbsurfasb
20.7k34270
add a comment |
Moving the Recycle Bin is not possible.
Plus there are some unfavorable consequences to performance to moving the Recycling bin to another drive.
answered Jan 4 '12 at 20:26
surfasbsurfasb
20.7k34270
Moving the Recycle Bin is not possible.
Plus there are some unfavorable consequences to performance to moving the Recycling bin to another drive.
answered Jan 4 '12 at 20:26
surfasbsurfasb
20.7k34270
answered Jan 4 '12 at 20:26
surfasbsurfasb
20.7k34270
answered Jan 4 '12 at 20:26
surfasbsurfasb
20.7k34270
answered Jan 4 '12 at 20:26
surfasbsurfasb
20.7k34270
20.7k34270
add a comment |
add a comment |
I had a similar problem (on Win10): SSD system drive, HDD data drive, junctions worked, deleting to the recycle bin was no problem, but restoring stuff from the recycle bin resulted in a copy operation when deletion was triggered from inside the symlinked path (e.g. C:Usersmejunction-to-dfoo).
This problem can be circumvented by going into the Disk Management Console, removing the drive letter (D:) and adding a mount point (e.g. C:data). Just adding a mount point is not enough, the partition is not allowed to have a drive letter at all.
Why this happens: The recycle bin view has a column Original Location and also knows where the file is really located (drive letter). If the drive letter and Original Location are different (e.g. because a file was deleted from inside a symlink/junction), the restore operation will perform a copy operation. If a partition is only accessed via a mount point on the system drive, there is no conflict and the usual quick restore is performed.
TL;DR: Completely abandoning D: for C:d-drive solves the problem and has the additional benefit of making Windows slightly more Unix-y by not having to switch drive letters in the console and such.
Edit: And that's why we can't have nice things... no file indexing support for anything without a drive letter. Indexing across a mount point in windows
answered Jan 1 at 7:04
T NierathT Nierath
35419
add a comment |
I had a similar problem (on Win10): SSD system drive, HDD data drive, junctions worked, deleting to the recycle bin was no problem, but restoring stuff from the recycle bin resulted in a copy operation when deletion was triggered from inside the symlinked path (e.g. C:Usersmejunction-to-dfoo).
This problem can be circumvented by going into the Disk Management Console, removing the drive letter (D:) and adding a mount point (e.g. C:data). Just adding a mount point is not enough, the partition is not allowed to have a drive letter at all.
Why this happens: The recycle bin view has a column Original Location and also knows where the file is really located (drive letter). If the drive letter and Original Location are different (e.g. because a file was deleted from inside a symlink/junction), the restore operation will perform a copy operation. If a partition is only accessed via a mount point on the system drive, there is no conflict and the usual quick restore is performed.
TL;DR: Completely abandoning D: for C:d-drive solves the problem and has the additional benefit of making Windows slightly more Unix-y by not having to switch drive letters in the console and such.
Edit: And that's why we can't have nice things... no file indexing support for anything without a drive letter. Indexing across a mount point in windows
answered Jan 1 at 7:04
T NierathT Nierath
35419
add a comment |
I had a similar problem (on Win10): SSD system drive, HDD data drive, junctions worked, deleting to the recycle bin was no problem, but restoring stuff from the recycle bin resulted in a copy operation when deletion was triggered from inside the symlinked path (e.g. C:Usersmejunction-to-dfoo).
This problem can be circumvented by going into the Disk Management Console, removing the drive letter (D:) and adding a mount point (e.g. C:data). Just adding a mount point is not enough, the partition is not allowed to have a drive letter at all.
Why this happens: The recycle bin view has a column Original Location and also knows where the file is really located (drive letter). If the drive letter and Original Location are different (e.g. because a file was deleted from inside a symlink/junction), the restore operation will perform a copy operation. If a partition is only accessed via a mount point on the system drive, there is no conflict and the usual quick restore is performed.
TL;DR: Completely abandoning D: for C:d-drive solves the problem and has the additional benefit of making Windows slightly more Unix-y by not having to switch drive letters in the console and such.
Edit: And that's why we can't have nice things... no file indexing support for anything without a drive letter. Indexing across a mount point in windows
answered Jan 1 at 7:04
T NierathT Nierath
35419
I had a similar problem (on Win10): SSD system drive, HDD data drive, junctions worked, deleting to the recycle bin was no problem, but restoring stuff from the recycle bin resulted in a copy operation when deletion was triggered from inside the symlinked path (e.g. C:Usersmejunction-to-dfoo).
This problem can be circumvented by going into the Disk Management Console, removing the drive letter (D:) and adding a mount point (e.g. C:data). Just adding a mount point is not enough, the partition is not allowed to have a drive letter at all.
Why this happens: The recycle bin view has a column Original Location and also knows where the file is really located (drive letter). If the drive letter and Original Location are different (e.g. because a file was deleted from inside a symlink/junction), the restore operation will perform a copy operation. If a partition is only accessed via a mount point on the system drive, there is no conflict and the usual quick restore is performed.
TL;DR: Completely abandoning D: for C:d-drive solves the problem and has the additional benefit of making Windows slightly more Unix-y by not having to switch drive letters in the console and such.
Edit: And that's why we can't have nice things... no file indexing support for anything without a drive letter. Indexing across a mount point in windows
answered Jan 1 at 7:04
T NierathT Nierath
35419
edited 19 hours ago
answered Jan 1 at 7:04
T NierathT Nierath
35419
answered Jan 1 at 7:04
T NierathT Nierath
35419
answered Jan 1 at 7:04
T NierathT Nierath
35419
35419
add a comment |
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%2f194108%2fusing-junctions-and-moving-the-recycle-bin-to-the-right-partition%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
