Hello krytoned,
I'm not sure what you mean. The .reg files currently in this tutorial here only remove the folders from the "This PC" window and navigation pane, and no where else.
Could you post some screenshots showing what you are talking about before and after using the "Desktop" folder option as a test?
Here are my screenshots below using the Desktop folder option to show that it's only removed in This PC.
Hi Brink.
Sure no problem, but somehow I can't replicate this with the Desktop folder.. However, I can repeat this with both the Music and Videos folders (which is what I always removed):
As you can see, the Music folder is removed from both This PC and the user profile. It also doesn't appear in the Open/Save dialog, like in Attachment 34910. Maybe it's some weird combination of registry keys that caused this effect?
Anyway, no sweat since I found howtogeek's suitable alternative. Still, thanks for your help!
Just a warning though, the HowToGeek's method to remove folders from This PC will break those folders listed in Start below.
https://www.tenforums.com/tutorials/3...dows-10-a.html
I'll do some more testing on it to see what I can do, but I'm not sure anything else can be done. :)
Last edited by Brink; 09 Aug 2016 at 14:11.
WORD OF CAUTION! Up until earlier on Saturday the puzzlement of why first after two full months with the Threshold 2 Update 10586 version 1511 and now much sooner with the Redstone 1 Anniversary update 14393.xxx(now 105 with latest cumulative update) version 1607 both RTM type builds using the reg tweaks resulted in disabling the ability not to create "new folder"s but to be able to name them or rename any other existing folder(s) without running into "Folder doesn't exit" type errors despite taking ownership over them and even parent folders.
With the TH2 update that had been replaced by the next available Insider Preview build back in February being the 14251? or 257 at the time which then seemed to clear all that up and continue to see the same results throughout the next several builds until the RS1 once again revealed the exact same problem. At first with the TH2 the MS Community and Answers sites saw this as unsolvable which is why the main desktop here went back onto the Preview builds scheduling. Upong subsequent searches once again for the same this time an explanation as far as the "why" this was being seen had a solution when pointing to the ...
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions"regist y value having been knocked out each time these reg tweaks with the "All Foloers" reg mod for 64bit running into it's own errors and refusal while each of the individual reg tweaks would work with ease these managed to knock out the key element which allows you to name or rename folders. Note these reg tweaks for some unknown reason as found here have no effect on this when running any Windows Insider Preview build which are not RTM but Developer type builds while the general release Retail type are bound to the registry key pointed to.
Once replaced to correct the naming/renaming problem all those folders spring right back at you all over again! In other words you get caught between a rock and a hard place real fast since MS doesn't want you to do nothing else but stare at all those folders in your face or not be able to name things which also may include new files as well as folders like saving a download under a different name not going through?!
If you should find this to be the case once you add or create the key by editing the registry you will need to sign out and then back in to suddenly see all those folders splashed in your face from the start! After spending months of folder free explorer windows "Surprise! We're back!" is what you get when not running an Insider build and using the reg tweaks to dump folders. So far no work around to get past the need to restore the defaults has been found!
I used the 64-bit_Remove_All_user_Folders_in_This_PC.reg, but these folders reappear in the Save As dialog:
Windows 10 Pro, v1607.
Hello creeve4, :)
Is it doing this in all "save as" type dialogs, or only from a specific app?
Did you already restart the computer after merging the .reg file to see if that may help?
Brink,
I experience this or something similar* with most programs.
*Sometimes it is just a single folder that reappears, sometimes it is several, sometimes all of the folders. This behavior depends on the program.
notepad:
Word:
If you open the folder, it'll still show since it's open, but it shouldn't by default.
This can also happen if the last save as location was a user folder causing it to open directly to the folder the next time you open it.
The last time I was able to use the 64bit Remove All Users Folders option here going by date was August 2015 when it simply stopped working on more then one machine with the subsequent Insider builds I opted to go for. So I ended up using the individual folder reg mods for each to clear things up.
The snipping there was dated August 15, 2015. After the TH2 update went on however is when I found that after the first two months I was no longer able to name new or rename existing folders due the FolderDescription reg value missing problem where when just getting the Redstone 1 update suddenly found the same problem appeared.
So far I had to run with defaults since replacing the default value mentioned undoes the changes reverting everything back to avoid the naming problem. Initially once the All Folders mod no longer worked I went with the individual folders until that came up with the RS1 and had to choose the stay with the defaults and all the clutter that comes with it!
Not a very pleasant sight when I had hoped to keep all that cleaned up.Eventually I will be testing one remover at a time followed by a restart for each to create and name new folders in case it turns out to be traced to one or two only as far as the individuals go.
The reg files changed at some point.
Try downloading the ALL file again and compare it to the one you have.
Side note: the feature updates restore the folders, so you have to merge the keys again. At least that's what happened on this machine - I think I noticed the change to the reg file after the 1511 update.
Quote
