Script to Clean up Windows 10 Start Menu?
-
There is a decrapifier script that someone posted on ML that I use for both deployment and non-deployment scenarios.
In the case of non-deployment, You need to run this script as the first user on the system, preferably an account that won't actually be used.
https://community.spiceworks.com/user-groups/windows-decrapifier-group
-
@JasGot I have not found a good solution to this yet. We have been just living with it. It hasn't caused any problems I'm aware of but it sure is annoying. I have run scripts for this before but periodically all the settings get reset on every pc. Pretty sure its when Windows updates come through, when things get reset.
-
Here is the link to the actual script (version 1809).
https://gist.github.com/gvlx/b4d4c5681900ca965276fc5c16fe8520
I usually use the switches -allapps and -clearstart. Does a nice job until the OS updates, then it's time to run it again.
edit: changed link. screw sending traffic to shiteworks.
-
https://timothygruber.com/scripts/powershell/win10-crapp-remover-powershell-script-gui/
This one let's you get granular and has a GUI where you can import and export a start menu.
-
@Dashrender said in Script to Clean up Windows 10 Start Menu:
There is a decrapifier script that someone posted on ML that I use for both deployment and non-deployment scenarios.
In the case of non-deployment, You need to run this script as the first user on the system, preferably an account that won't actually be used.
https://community.spiceworks.com/user-groups/windows-decrapifier-group
I checked this out. Lot's of talk about it, mostly about how it is intended to be run prior to sysprep, and how it will not remove anything from the user profile it is being run under.
How are you running it for stand alone and more importantly, the user you are logged in as?
-
@JasGot said in Script to Clean up Windows 10 Start Menu:
@Dashrender said in Script to Clean up Windows 10 Start Menu:
There is a decrapifier script that someone posted on ML that I use for both deployment and non-deployment scenarios.
In the case of non-deployment, You need to run this script as the first user on the system, preferably an account that won't actually be used.
https://community.spiceworks.com/user-groups/windows-decrapifier-group
I checked this out. Lot's of talk about it, mostly about how it is intended to be run prior to sysprep, and how it will not remove anything from the user profile it is being run under.
How are you running it for stand alone and more importantly, the user you are logged in as?
I don't - for standalone I do an audit mode setup pre giving it to the user - then all created uses have the script against the accounts.
If you have an existing machine and aren't willing to wipe and start over with audit mode - looks like some others have posted other options.
-
@JasGot said in Script to Clean up Windows 10 Start Menu:
@Dashrender said in Script to Clean up Windows 10 Start Menu:
There is a decrapifier script that someone posted on ML that I use for both deployment and non-deployment scenarios.
In the case of non-deployment, You need to run this script as the first user on the system, preferably an account that won't actually be used.
https://community.spiceworks.com/user-groups/windows-decrapifier-group
I checked this out. Lot's of talk about it, mostly about how it is intended to be run prior to sysprep, and how it will not remove anything from the user profile it is being run under.
How are you running it for stand alone and more importantly, the user you are logged in as?
I have always run it under my own account, not in audit mode. If you use the -allusers switch, it works on all existing profiles. But the link that @Obsolesce posted looks like a much better solution. I haven't had time to try it out yet.
-
@RojoLoco said in Script to Clean up Windows 10 Start Menu:
@JasGot said in Script to Clean up Windows 10 Start Menu:
@Dashrender said in Script to Clean up Windows 10 Start Menu:
There is a decrapifier script that someone posted on ML that I use for both deployment and non-deployment scenarios.
In the case of non-deployment, You need to run this script as the first user on the system, preferably an account that won't actually be used.
https://community.spiceworks.com/user-groups/windows-decrapifier-group
I checked this out. Lot's of talk about it, mostly about how it is intended to be run prior to sysprep, and how it will not remove anything from the user profile it is being run under.
How are you running it for stand alone and more importantly, the user you are logged in as?
I have always run it under my own account, not in audit mode. If you use the -allusers switch, it works on all existing profiles. But the link that @Obsolesce posted looks like a much better solution. I haven't had time to try it out yet.
And it cleaned out the installed junkware? in the past it did not clean out many things for the account you ran it in (a real account, not the audit account).
-
@Dashrender said in Script to Clean up Windows 10 Start Menu:
@RojoLoco said in Script to Clean up Windows 10 Start Menu:
@JasGot said in Script to Clean up Windows 10 Start Menu:
@Dashrender said in Script to Clean up Windows 10 Start Menu:
There is a decrapifier script that someone posted on ML that I use for both deployment and non-deployment scenarios.
In the case of non-deployment, You need to run this script as the first user on the system, preferably an account that won't actually be used.
https://community.spiceworks.com/user-groups/windows-decrapifier-group
I checked this out. Lot's of talk about it, mostly about how it is intended to be run prior to sysprep, and how it will not remove anything from the user profile it is being run under.
How are you running it for stand alone and more importantly, the user you are logged in as?
I have always run it under my own account, not in audit mode. If you use the -allusers switch, it works on all existing profiles. But the link that @Obsolesce posted looks like a much better solution. I haven't had time to try it out yet.
And it cleaned out the installed junkware? in the past it did not clean out many things for the account you ran it in (a real account, not the audit account).
It sometimes leaves blank icons on the start menu, but it does remove crapware. I bet the whole audit mode thing makes it work better though.
-
@Obsolesce said in Script to Clean up Windows 10 Start Menu:
https://timothygruber.com/scripts/powershell/win10-crapp-remover-powershell-script-gui/
This one let's you get granular and has a GUI where you can import and export a start menu.
I'm checking this out right now. It looks like it has promise. Too bad the author doesn't explain things a bit more.
-
If you just want to clean out the start menu, you can use layoutmodification.xml files to have a "blank" start menu. https://blogs.technet.microsoft.com/deploymentguys/2016/03/07/windows-10-start-layout-customization/
USe the above blog as your starting point. We had to tweak it a bit. Im trying to find my notes becasie when we re-imported the start layout we have to use a different mount path than what is mentioned in the blog.
I'll try and find the other script I used to remove all the bloatware. I foudn one that actually worked; removed all the junk but left what was needed for Windows Update to work -
@Obsolesce said in Script to Clean up Windows 10 Start Menu:
https://timothygruber.com/scripts/powershell/win10-crapp-remover-powershell-script-gui/
This one let's you get granular and has a GUI where you can import and export a start menu.
Well. I had high hopes for this. Or, better yet, my expectations were too high. After testing for two minutes, I've decided the app is not for me. Maybe I'll use it just to clear out the start menu with the Start Menu> Empty Start Menu XML template (I'll try that in a minute...).
The first thing I did was Check All on the Win10 crAPPs page and then Check All on the App & Privacy Settings page. Ran both removers and was left with this:
That's hardly a cleanup.
Oh, and I just tried the Empty Start Menu template....You can only apply it to new users.Darn, I was so excited.
-
I use the xml templates and apply via GPO. https://docs.microsoft.com/en-us/windows/configuration/start-layout-xml-desktop
-
Cleaning up existing users for a script can likely be challenging without making all kinds of assumptions or asking a million questions of the users.
That's why I think you see all of these scripts designed for new setups, not existing ones.
-
Tis blog post points to a PowerShell script you can use to remove most of the built in apps.
https://www.scconfigmgr.com/2018/11/27/remove-built-in-apps-for-windows-10-version-1809/ -
@JasGot said in Script to Clean up Windows 10 Start Menu:
@Obsolesce said in Script to Clean up Windows 10 Start Menu:
https://timothygruber.com/scripts/powershell/win10-crapp-remover-powershell-script-gui/
This one let's you get granular and has a GUI where you can import and export a start menu.
Well. I had high hopes for this. Or, better yet, my expectations were too high. After testing for two minutes, I've decided the app is not for me. Maybe I'll use it just to clear out the start menu with the Start Menu> Empty Start Menu XML template (I'll try that in a minute...).
The first thing I did was Check All on the Win10 crAPPs page and then Check All on the App & Privacy Settings page. Ran both removers and was left with this:
Reboot after you run it. Whatever you are left with after that has to be done in audit mode pre initial user login. That's not a limitation of the script, but a limitation of how Windows does it.
-
@JasGot said in Script to Clean up Windows 10 Start Menu:
That's hardly a cleanup.
Oh, and I just tried the Empty Start Menu template....You can only apply it to new users.
Darn, I was so excited.Start menu layout can only be changed in that way for new users that haven't logged on to the system yet.
Again, not a script limitation, but how Windows makes it.
-
@Obsolesce said in Script to Clean up Windows 10 Start Menu:
@JasGot said in Script to Clean up Windows 10 Start Menu:
That's hardly a cleanup.
Oh, and I just tried the Empty Start Menu template....You can only apply it to new users.
Darn, I was so excited.Start menu layout can only be changed in that way for new users that haven't logged on to the system yet.
Again, not a script limitation, but how Windows makes it.
Pretty sure you can get powershell to tell you all the store installed crap - and then uninstall it, on a user by user basis...
And as mentioned, a reboot might show much of that stuff gone.
-
After three days of exploring this. I'm giving up. I can remove the tiles faster by hand.
I chose to forego all the existing scripts because they either don't work, or they uninstall items. There are too many hooks between too many apps to be confident in uninstalling apps without potential consequences.
With all the failures in modifying Start Menu items coming from Microsoft changes, I just can't take the chance that a production machine won't have an issue later (mostly with updates) because an app was removed.
I have also found that there is either no way (or the process is broke) to use XML to control the Start Menu for an existing user (without GPO).
And to top it all off, it appears the ability to modify the Taskbar is broke in 1803 or only works intermittently. Further, in all of the 100's of posts I've read, no one can actually provide a working example. It seems as though every time someone says "I got it working", some else says "post your XML", and they can't because it suddenly isn't working again.
I had narrowed the choices down to one:
Website: TimothyGruber.com
GitLab: https://gitlab.com/tjgruber/win10crappremover
but I was unable to make it work 100% of the time. I did not check to see if the unreliability was caused by varying levels of updates; I need it to work across all updates, because I need the start menu modification to work after the upgrade to 10 and before all the updates have taken place. I need to be able to go from 7 to 10 with a custom start menu in under an hour. If I have to wait for certain updates to apply, it could take two full days.I'll keep searching for a solution, but for now, the Windows 10 upgrades are on hold.
-
Interesting - I've been using the 1803 version of the script for 9 months now with zero problems. I'll post my script and XML later today.
