Jump to content

How to get rid of Candy Crush Soda Saga and other Windows 10 Start Menu junk for good!


Recommended Posts

Posted
Use a custom StartLayout, that way you don't have to remove apps from the image. However the apps will still appear in the Start Menu, but you can use AppLocker to prevent users from running them.
That's fine for single user PCs, but on shared devices, every time a user logs in to a machine for the first time it installs all of the unwanted apps which can take a while...
Posted
That's fine for single user PCs, but on shared devices, every time a user logs in to a machine for the first time it installs all of the unwanted apps which can take a while...

We have no perfmance issues and I have all the apps still in and push the StartLayout file to about 400 machines.

  • 2 weeks later...
Posted (edited)
Just having a look as OSDeploy and the command New-OSBuildTask - is there anyway to add apps to be kept instead having to manually select them to be removed via -RemoveAppx Edited by mdrabble
Posted
Just having a look as OSDeploy and the command New-OSBuildTask - is there anyway to add apps to be kept instead having to manually select them to be removed via -RemoveAppx

 

Isn't anything you don't select left in there? I assumed they were - and you choose the ones you want to remove.

 

Gareth

Posted
Use a custom StartLayout, that way you don't have to remove apps from the image. However the apps will still appear in the Start Menu, but you can use AppLocker to prevent users from running them.
Do you have your startlayout set via group policy or via machine install
  • 8 months later...
  • 6 months later...
  • 1 year later...
Posted

Bit of a necrobump, have MS changed how you list the installed packages?

I'm putting together a new image for over the summer and that means updating the package list.

 

(Get-AppXPackage).Name | Sort works just fine and gives me a nice list

The other command I have on file - (Get-AppXProvisionedPackage -Online).DisplayName | Sort - throws a The request is not supported error.

Posted (edited)

Huh, weird. It's 21H2 I'm trying to build and it just does not like it.

 

Edit: Lol looks like it's AppLocker. My bad!

Edited by Garacesh
Posted

Too long for me to edit it, oops. Just dropping this here in case anybody runs into the same issue at any point:

When running Get-AppXProvisionedPackage (and other such tools, like Get-WindowsCapability, I assume this will affect any cmdlet that uses -Online), Windows would try to spawn and execute Appdata\Local\Temp\GUIDGUID-GUID-GUID-GUID-GUIDGUID\DIMSHOST.EXE

 

The solution was an exception for:

Publisher: O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US

Product name: MICROSOFT® WINDOWS® OPERATING SYSTEM

File name: DISMHOST.EXE

Version: * (And above)

  • Thanks 1
  • 1 year later...
  • 1 year later...
  • 2 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...