-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove explorer bloat #2398
Comments
For the gallery this one is a revertable option, by setting it to 1/0:
For the home I found this way (.reg file): Remove:
Add:
so both would be revertable options |
@MyDrift-user |
Worth adding for sure (my thought). The question is add it as new or add it to an existing one? |
I would lean towards creating a new tweak and not adding it into something already there, because the tweaks are already convoluted and unclear enough in regards to what they actually do. |
@Marterich I agree with you. Also I would put it in the "Advanced Tweaks" section. |
I generally agree, but winutil is currently not designed to have that many tweaks as seen that the applications tab is a bit bloated rn. |
Fair, but seeing that winutil will likely only grow in the future, I think we should rather fix or rework the UI like @og-mrk is doing right now instead of compromising the functionality itself. |
Is your feature request related to a problem? Please describe.
A few Windows 11 updates ago Microsoft added "Start" and "Gallery" in the file explorer sidebar. They aren't really useful and waste space. It would be nice to be able to hide them.
Describe the solution you'd like
Maybe some registry tweak? As revertable as possible, so no destructive tweak.
I found this on the Microsoft forum (https://answers.microsoft.com/en-us/windows/forum/all/how-to-remove-gallery-folder-from-file-explorer/e065f58f-c752-4acd-a2a5-46438c5b7996):
Although deleting is pretty destructive.
I'm not too familiar with developing solutions to these kinds of problems so that's how much I can say.
Additional context
The text was updated successfully, but these errors were encountered: