How to force Windows not create public files?

[newtekie1]

I checked a couple other computers here and I found a few files under a couple subfolders under that Public folder. So for a test, I decided to copy those files to a safe place, then delete them from those folders to see if anything broke.

So far, as far as I can tell, everything still works fine.

Still, I see no reason to worry about them. This is especially true if your computer has more than one user. When you install a program that prompts to install for "Just you" or "All users", this folder is often used with the "All users" option. And as noted above, if access is needed from other computers on your local network.

Watch the freakout the next time you install a program that tries to create shortcuts for "All Users" or "Anyone that uses this computer". Since the public folders is where those shortcuts are created.

I guess i have no choice, but to leave that Public folder.

They've been there since at least Windows 2000. Why do they bother you now?

 

[Bill_Bright]

Watch the freakout the next time you install a program that tries to create shortcuts for "All Users" or "Anyone that uses this computer".

No, doesn't seem to be. For example, I have CCleaner set to install for all users and I just looked again - there are no CCleaner shortcuts (or anything belonging to CCleaner or Piriform under the Public folder. So not sure how it works with that folder.

 

[Valantar]

No, doesn't seem to be. For example, I have CCleaner set to install for all users and I just looked again - there are no CCleaner shortcuts (or anything belonging to CCleaner or Piriform under the Public folder. So not sure how it works with that folder.

There is a Public Desktop folder at least, and it seems that some things (like anything installed through Origin) uses that for desktop shortcuts. But no public Start Menu, and no public Appdata folder, so mostly I'd assume there are separate shortcuts created for each user.

 

[Bill_Bright]

There is a Public Desktop folder at least

Yeah - I have the folders - they just aren't full of stuff.

I will say my machines only have one user account on them. Perhaps where several users share the same computer, these folders will be more populated. IDK.

 

[Valantar]

Yeah - I have the folders - they just aren't full of stuff.

I will say my machines only have one user account on them. Perhaps where several users share the same computer, these folders will be more populated. IDK.

Mine only has one as well, and as I said, Origin does seem to place its shortcuts there, and only there.

 

[Bill_Bright]

I see Foxit Reader put some in mine too. Apparently, there's no standard. I personally wish programs would ALL their files under one primary installation folder, either under Program Files , Program Files (x86) or where the user designates should they decide to do a custom install and select their own folder. I think when programs put files all over the place, that's when orphaned bits get left behind on drives, and as entries in the Registry.

 

[newtekie1]

I see Foxit Reader put some in mine too. Apparently, there's no standard. I personally wish programs would ALL their files under one primary installation folder, either under Program Files , Program Files (x86) or where the user designates should they decide to do a custom install and select their own folder. I think when programs put files all over the place, that's when orphaned bits get left behind on drives, and as entries in the Registry.

The "all user" start menu items used to be stored under the public/start menu folder. But at some point they moved those to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\. So at least that is in a somewhat standard place and not under a profile directory. However, the "all user" desktop icons are still installed under public\desktop and there are definitely programs that will freak out if they try to create an icon there and they can't access the folder for some reason. Adobe did this when installing Reader for the longest time. If it couldn't create the desktop icon under public it would abort and reverse the entire installation(though I think they have fixed that now). But that's just one example, I've encountered several. I do wish they would move the shared desktop space to ProgramData too though.

 

[Bill_Bright]

However, the "all user" desktop icons are still installed under public\desktop

Well, like I said, I installed CCleaner for all users and there are no icons in there for it so its use certainly is not consistent.

 

[Valantar]

Well, like I said, I installed CCleaner for all users and there are no icons in there for it so its use certainly is not consistent.

Given the amount of legacy APIs in Windows - and how open the system is to begin with - there are no doubt dozens of variations on this. Heck, some apps still ask if I want to add an icon to Quick Launch, which hasn't been a thing since ... XP? Maybe Vista?

 

[newtekie1]

Well, like I said, I installed CCleaner for all users and there are no icons in there for it so its use certainly is not consistent.

Did you select the option for CCleaner to create a desktop icon? If so, where did it create that desktop icon so it appeared on every user's desktop?

 

[Vayra86]

Is there registry fix so that Windows would not create any Public folders in ''C:/Users/Public''? Just seeing them annoys me.

Shortcut your way around them. The user folder isn't really in any sort of place that you need to ever go, as in, drop files at or pass by.

But I share your pain having just seen them again since five years or so
But really, even the libraries that Windows offers on your user account are straight into merged folders of 'stuff'. Your documents for example are already inside the User folder and they also appear as quick access in explorer.

Another quick fix: HIDE them. All it needs is an Admin OK and poof, gone. I mean look, I just did it for good measure. Glorious

 

[Bill_Bright]

Heck, some apps still ask if I want to add an icon to Quick Launch, which hasn't been a thing since ... XP? Maybe Vista?

I beg to differ. Not only is the Quick Launch toolbar still available in W10, it is one of the first things I enable on my own systems.

Did you select the option for CCleaner to create a desktop icon? If so, where did it create that desktop icon so it appeared on every user's desktop?

Hmmmm, good point. Probably the first time I install CCleaner after a new build, I have it put the icon on the desktop. But then I drag it to the aforementioned Quick Launch toolbar and never select installing it on the desktop again.

I don't like a busy desktop so don't have many icons on it. And most are links to sites or folders - not programs. But I do have a couple. Pandorian is one. But I don't see an icon for it in the public folder. The .ico file for it is under Program Files (x86) > Pandorian. Just searching through the registry of pandorian and everything seems to point to that same Program Files (x86) folder.

 

[newtekie1]

I don't like a busy desktop so don't have many icons on it. And most are links to sites or folders - not programs. But I do have a couple. Pandorian is one. But I don't see an icon for it in the public folder. The .ico file for it is under Program Files (x86) > Pandorian. Just searching through the registry of pandorian and everything seems to point to that same Program Files (x86) folder.

Do you understand what "All Users" program means? Pandorian is not an "All User" program. Hence it will not put an icon in the public/desktop folder. It doesn't even put an icon on the desktop during the installer, only the start menu. And it puts it's start menu entries under the individual user account.

 

[lexluthermiester]

The OP has made his final statement and this topic looks like it's heading south. /thread

 

[Bill_Bright]

Do you understand what "All Users" program means?

Yes, I understand what all users mean. Frankly, I'm not interested in this so I admit, I have not put much effort in doing my homework on it beyond learning there is nothing malicious (or resource hogging) about those folders. All I can do is say what I have been saying - my public folder has not freaked out and is not full of icons.

As for Pandorian (not to be confused with Pandora), I was just explaining to you that it is my only "program" icon on my desktop (all others are in my Quick Launch toolbar, or Start Menu). I previously said "a couple", but I was wrong. It is only Pandorian.

So because this does not interest me, and because, from the little research I did do, I see no reason to delete or worry about those public folders. Therefore, I concede, you are right.

Now I will take lexluthermiester's hint and move on.

****

Totally OT side note, if you like to stream/listen to music while using your computer, I highly recommend Pandorian. It turns Pandora from a mediocre music streaming service to a, if not the top-notch one. No ads and costs a whopping $0.00.

 

[Valantar]

I beg to differ. Not only is the Quick Launch toolbar still available in W10, it is one of the first things I enable on my own systems.

If it requires custom-adding a toolbar and gaming the system by placing the self-made folder where installer scripts expects the legacy Quick Launch toolbar to be, I wouldn't call it "available". IMO it just serves as an illustration of the layers of legacy functionality I mentioned above.

Seems to me that the Public folders, if anything, are a severely underutilized feature of Windows. Too bad, really. If they were easily available somehow, it would be very easy to share files between users even for novice users not familiar or comfortable with just creating folders themselves (which is a surprisingly high amount of PC users).

 

[Bill_Bright]

If it requires custom-adding a toolbar

"Custom adding? Not sure what that means. My point is, the Quick Launch tool bar definitely is "available" in W10. You just have to enable it. While true, adding it back to the Toolbars options menu is not a one-click process, it is still easy and a one-time process. You don't need to edit the Registry, for example, or create folders or the Quick Launch folder itself. Why? Because it is already in there, and "available" to be added to the Toolbar options menu.

And no, you don't have to put a "self-made" folder anywhere. Did you follow that link I provided? The folder is already there. You are just telling the system where it is. Here is another tutorial to show you it is easy to enable it.

And it is not about dealing with installer scripts since most current programs don't attempt to install shortcuts to Quick Launch. Once the Quick Launch tool bar is enabled, the user can simply drag and drop any shortcut to it.

What I might do, for example, is create a new shortcut to TPU on my desktop. Then simply drag that shortcut to Quick Launch and viola! I have a shortcut to TPU on Quick Launch that is NOT cluttering up my desktop. Piece of cake.

So yes, it does illustrate one of those "legacy functions". But it does it by already being available. Just because Microsoft has severed the direct connections (menu options) to it, that does not mean it is not available, or that it cannot easily be reconnected and added back to the menu.

 

[Valantar]

"Custom adding? Not sure what that means. My point is, the Quick Launch tool bar definitely is "available" in W10. You just have to enable it. While true, adding it back to the Toolbars options menu is not a one-click process, it is still easy and a one-time process. You don't need to edit the Registry, for example, or create folders or the Quick Launch folder itself. Why? Because it is already in there, and "available" to be added to the Toolbar options menu.

And no, you don't have to put a "self-made" folder anywhere. Did you follow that link I provided? The folder is already there. You are just telling the system where it is. Here is another tutorial to show you it is easy to enable it.

And it is not about dealing with installer scripts since most current programs don't attempt to install shortcuts to Quick Launch. Once the Quick Launch tool bar is enabled, the user can simply drag and drop any shortcut to it.

What I might do, for example, is create a new shortcut to TPU on my desktop. Then simply drag that shortcut to Quick Launch and viola! I have a shortcut to TPU on Quick Launch that is NOT cluttering up my desktop. Piece of cake.

So yes, it does illustrate one of those "legacy functions". But it does it by already being available. Just because Microsoft has severed the direct connections (menu options) to it, that does not mean it is not available, or that it cannot easily be reconnected and added back to the menu.

"Adding it back"? If you're adding a toolbar that doesn't exist (it's not one of the three default options), potentially creating the folder yourself (depending whether the system or some app has created it before you), then you're just adding a custom toolbar. Period. It's no different than creating any other custom toolbar pointing to any other folder - this one just happens to step into the shoes of a legacy function that is called on by certain installers. Remember, the function you're pointing to can create a toolbar pointing to literally any folder!

As for what I said about installers, that was actually on topic for this thread! Unlike this nonsense discussion. I was pointing out how the public folders and how some applications seem to create their desktop shortcuts there and others not is likely due to various generations of APIs and installer systems having different defaults and different preferences.

As for your definition of any function that you can potentially add through system menus being "available" ... well, that's on you. That definition is so broad as to be utterly and completely useless. My entire point was the difference between actually active current functionality in Windows and the huge amounts of stuff that exists in a disabled or dormant state for reasons of compatibility and similar considerations. Quick Launch is not a feature of Windows 10. It is a legacy feature that you can add to Windows 10 if you like. There's a difference.

 

[Bill_Bright]

"Adding it back"? If you're adding a toolbar that doesn't exist

Why do keep saying stuff like this? That's just dumb. It does exist. Just because a feature is disabled or not visible by default, that does not mean it doesn't exist. There are lots of features and options in W10 that are disabled by default. That does not mean they don't exist. For example, there are many right-click menu options that are not enabled or visible by default. But you can easily "tweak" Windows and add them.

There is no "creating the folder".

If it NOT a custom Toolbar. User can customize it (just like they can the default Taskbar, Start Menu or Desktop) by adding icons to it. But it is not a custom Toolbar.

Unlike this nonsense discussion.

Then stop making nonsensical and untrue statements about it. Remember, you started this nonsense by claiming Quick Launch "hasn't been a thing since ... XP". That's just false - no matter how badly you want to deny it, or obfuscate the issue with nonsense about it being a "custom" Toolbar, "creating folders" or that it doesn't even exist!

OMG! What's that I see under my Taskbar and Address Toolbar? Why, it is the nonexistant Quick Launch Toolbar!

 

[Valantar]

Why do keep saying stuff like this? That's just dumb. It does exist. Just because a feature is disabled or not visible by default, that does not mean it doesn't exist. There are lots of features and options in W10 that are disabled by default. That does not mean they don't exist. For example, there are many right-click menu options that are not enabled or visible by default. But you can easily "tweak" Windows and add them.

There is no "creating the folder".

If it NOT a custom Toolbar. User can customize it (just like they can the default Taskbar, Start Menu or Desktop) by adding icons to it. But it is not a custom Toolbar.

Then stop making nonsensical and untrue statements about it. Remember, you started this nonsense by claiming Quick Launch "hasn't been a thing since ... XP". That's just false - no matter how badly you want to deny it, or obfuscate the issue with nonsense about it being a "custom" Toolbar, "creating folders" or that it doesn't even exist!

View attachment 200113

OMG! What's that I see under my Taskbar and Address Toolbar? Why, it is the nonexistant Quick Launch Toolbar!

Well, it's good to see you're back to your old habits of twisting people's words. That sentence that you conveniently failed to actually quote, and instead presented as if it were a factual statement actually reads

which hasn't been a thing since ... XP? Maybe Vista?

I.e. a rhetorical point framed as a question. I have no clue, as I haven't used Quick Launch since the introduction of large taskbar icons in W7 made it obsolete - but at least I'm sure it wasn't enabled by default in W7. I'd appreciate if you could at least try to stick to good-faith arguments, rather than this garbage.

As for whether it's a custom toolbar: you're literally clicking a button labeled "New toolbar" to create it. You are creating the toolbar. Hence it is a custom toolbar - bespoke, made precisely to your specification. Period. Unless you create it, the only trace of its existence is a hidden folder nested under a long Appdata folder tree where inadvertently placed shortcuts go to... die from boredom and underuse, I guess? It doesn't matter that an identical toolbar has existed in previous versions of Windows, whether the one you are creating points to the same folder, and thus also enables the same functionality (including installers auto-adding shortcuts there) - it's still a custom toolbar. Recreating something is still creating it. If this was a dormant feature enabled by, say, tweaking a registry entry, I would agree that you weren't creating it (in that case you would be enabling it), but in this case you definitely are. That the W10 taskbar has a general function for custom toolbars does not mean that recreating the legacy Quick Launch toolbar in it is somehow less custom than if you label it "Llama farts" and point it to your any arbitrary folder.

As for making "nonsense points": I made an off-the-cuff reference to a dead legacy Windows feature as an illustration of an overall point of the amount of various legacy functions and options that are still exposed in Windows in various ways. Installers compiled in 2021 for Windows 10 including a function to add a shortcut in a toolbar that doesn't exist in Windows 10 (and to my knowledge hasn't existed since before W7) unless you explicitly create it yourself (and thereby instead placing the shortcuts in a hidden folder that the user will literally never see) is indeed an apt illustration of that point. You're the one insisting on making a discussion out of what was a) an off-the-cuff remark, and b) actually fitting, given that said function (including the ability to manually recreate it) still illustrates the point. Now please, pretty please, can we stop having this nonsense discussion?

 

[newtekie1]

Technically, the Quick Launch Toolbar has been removed from Windows. The Quick Launch Folder is what is still in Windows(for compatibility).

 

[Bill_Bright]

It has not been removed! If that were true, we would have to re-install it to put it back. And we don't. It has been included (embedded!) in EVERY version of Windows since XP. Just because it is not enabled by default, or visible by default, that in no way means it does not exist, or that it has been removed.

 

[Valantar]

It has not been removed! If that were true, we would have to re-install it to put it back. And we don't. It has been included (embedded!) in EVERY version of Windows since XP. Just because it is not enabled by default, or visible by default, that in no way means it does not exist, or that it has been removed.

Again, no. There exists a function to create custom toolbars beyond the standard ones. You are using that to create a stand-in for the legacy Quick Launch toolbar. Given that the functionality of this previous toolbar is entirely encompassed by the functionality of these custom toolbars, your custom replacement is indistinguishable as long as the target folder is the legacy one. Being able to seamlessly replace a specific legacy function through a generic current function does not mean the legacy function hasn't been removed.

 

[Bill_Bright]

Gee whiz, this has gone from stupid to absurd and beyond.

Look it up Valantar. Do your damn homework. Enabling the Quick Launch Toolbar is not creating anything. It is simply enabling it as ANY ONE who is not so incensed with the desire to be right and prove others wrong can plainly see.

When you pull your head out of the sand, I will reply.

 

[Valantar]

Gee whiz, this has gone from stupid to absurd and beyond.

Look it up Valantar. Do your damn homework. Enabling the Quick Launch Toolbar is not creating anything. It is simply enabling it as ANY ONE who is not so incensed with the desire to be right and prove others wrong can plainly see.

When you pull your head out of the sand, I will reply.

Tell me, how is what you are describing different from creating literally any other toolbar using the same menus? Yet this is somehow "enabling" a hidden function? You are the one needing some perspective here - no matter if the various sites describing this process use the word "enable" (SEO is a thing, you know) rather than "recreate", the latter is what is happening and not the former. Period. A custom toolbar made with a function for creating custom toolbars is a custom toolbar whether it's called Quick Launch, l33t h4xX0r t00lz or Reginald, and whether it points to a folder kept for legacy compatibility reasons or the void beyond the universe (though the latter might give some weird errors).