Windows 10 October 2018 Update rollout now paused
-
I moved Docs folder to D: and have this (below image) in settings, I honestly do not understand what it means, if I moved Documents to "D:" would not Document have to be D: also in settings ?
Attachment 207852
So the question is, why redirect your documents folder AFTER the move?
Make the change, save a document, see the redirection is working correctly, then move the files. After all, you moved them for a reason, right?
-
-
So the question is, why redirect your documents folder AFTER the move?
Make the change, save a document, see the redirection is working correctly, then move the files. After all, you moved them for a reason, right?
If I change Documents (KFR) to D:/Documents (and also moved all my docs to D:/Documents of course) would it not be logical that the redirect is also working? Otherwise I honestly do not understand.
-
I moved Docs folder to D: and have this (below image) in settings, I honestly do not understand what it means, if I moved Documents to "D:" would not Document have to be D: also in settings ?
Attachment 207852
as I many times have stated (also being bashed for that) Windows behaviour is random, illogical and untrustworthy.
When I've used KFR to move Documents etc from C: to D: I've then also gone into Settings > System > Storage to "Change where new content is saved".
I've always done this manually, making it a 2-stage process. I just wonder if you only do one of those 2 stages, what happens?
Does Windows just move existing content to D: and expect to store new content in C: or what?
As you say, illogical.
-
-
-
![]()
What I take from that is, if you used KFR to move folders, but did NOT agree to move all the files within the old folders, THAT is when some were left in the original location and some were moved. (That is an option when applying KFR as I recall.)
Then 1809 comes along and deletes any "old" files in the original location.
So, 2 issues, in my admittedly rather confused opinion:
1 Why would the user do half a job? - ie move some folders but not all? To me, it should be all or nothing because otherwise to where does "Documents" point? Old location (C) or new location (wherever the user has chosen)
2 Why would MS offer the option of moving some folders/files but not all? Again "all or nothing" makes more sense.
And if MS is going to offer the option, then they should see it through subsequent releases.
Is it possible that someone in MS thought "nobody is actually going to take the option of only moving some of their documents"? But then I ask again....why offer it?
And...... one of the rules of usability testing is "assume the user will do the stupidest thing imaginable, and test for it"
-
![]()
What I take from that is, if you used KFR to move folders, but did NOT agree to move all the files within the folders, THAT is when some were left in the original location and some were moved.
Then 1809 comes along and deletes any "old" files in the original location.
So, 2 issues, in my admittedly rather confused opinion:
1 Why would the user do half a job? - ie move some folders but not all? To me, it should be all or nothing because otherwise to where does "Documents" point? Old location (C) or new location (wherever the user has chosen)
2 Why would MS offer the option of moving some folders/files but not all? Again "all or nothing" makes more sense.
And if MS is going to offer the option, then they should see it through subsequent releases.
Is it possible that someone in MS thought "nobody is actually going to take the option of only moving some of their documents"?
If there is a particular option (or subset of choices) then yes, someone is going to do exactly that. How well thought out or without thought to consequence is not for any of us to know.
But it seems to me Microsoft should not delete any non-system folders if an upgrade is occurring, especially if they were previously designated as known file storage locations.
-
If there is a particular option (or subset of choices) then yes, someone is going to do exactly that. How well thought out or without thought to consequence is not for any of us to know.
But it seems to me Microsoft should not delete any non-system folders if an upgrade is occurring, especially if they were previously designated as known file storage locations.
Indeed!
We cross-posted there @winactive - glance again at the last line about usability testing in my post.
-
![]()
What I take from that is, if you used KFR to move folders, but did NOT agree to move all the files within the old folders, THAT is when some were left in the original location and some were moved. (That is an option when applying KFR as I recall.)
Then 1809 comes along and deletes any "old" files in the original location.
So, 2 issues, in my admittedly rather confused opinion:
1 Why would the user do half a job? - ie move some folders but not all? To me, it should be all or nothing because otherwise to where does "Documents" point? Old location (C) or new location (wherever the user has chosen)
2 Why would MS offer the option of moving some folders/files but not all? Again "all or nothing" makes more sense.
And if MS is going to offer the option, then they should see it through subsequent releases.
Is it possible that someone in MS thought "nobody is actually going to take the option of only moving some of their documents"? But then I ask again....why offer it?
And...... one of the rules of usability testing is "assume the user will do the stupidest thing imaginable, and test for it"
It's not just that. I think there are some badly designed programs that ignore KFR and will recreate the original to store their output.
-
It's not just that. I think there are some badly designed programs that ignore KFR and will recreate the original to store their output.
This is true. Which is why if you move the location for your files by choice the original should exist. Then there's evidence to beat the other vendor with a stick to fix the issue or to find an alternative that is better coded. If you've moved them to save space and it really is a problem then it should hurry your decision.
-
-
It's not just that. I think there are some badly designed programs that ignore KFR and will recreate the original to store their output.
Yes...when you install some programs and just accept the default settings, output goes to a "hard-wired" location.
As everyone has a C: drive - that's it!
That's why, to me, it's so important to always do "custom" installations. OK for us here but the average user may not even understand the difference. Another reference to my comment about usability testing?
And @winactive.......Yup! After all, it might be neater to delete unused folders, but how much space do a few empty folders take up? Negligible and again, most users won't even know about them.
