Windows 10 AppxPackage Removal For All Existing and Future User Accounts

Question

So I know there are other posts around this question, and I have read through all the ones I found and thought I had this set up correctly, but it still isn't working correctly. I have a post-installation task with a Powershell script to remove all the appxpackage apps except for certain ones we want to keep. The task works great for the local admin account that is added during the OS deployment, but all of the apps still show up for any other accounts that log into the computer after the deployment is finished. Below is the script I'm using. Appreciate any help you all can provide in making this work for all accounts that ever log into the computer.

Get-AppxPackage -AllUsers | where-object {$_.name –notlike "*Microsoft.WindowsStore*"} | where-object {$_.name –notlike "*Microsoft.DesktopAppInstaller*"} | where-object {$_.name –notlike "*Microsoft.HEIFImageExtension*"} | where-object {$_.name –notlike "*Microsoft.MicrosoftStickyNotes*"} | where-object {$_.name –notlike "*Microsoft.MSPaint*"} | where-object {$_.name –notlike "*Microsoft.ScreenSketch*"} | where-object {$_.name –notlike "*Microsoft.StorePurchaseApp*"} | where-object {$_.name –notlike "*Microsoft.VP9VideoExtensions*"} | where-object {$_.name –notlike "*Microsoft.WebMediaExtensions*"} | where-object {$_.name –notlike "*Microsoft.WebpImageExtension*"} | where-object {$_.name –notlike "*Microsoft.Windows.Photos*"} | where-object {$_.name –notlike "*Microsoft.WindowsCalculator*"} | where-object {$_.name –notlike "*Microsoft.WindowsCamera*"} | where-object {$_.name –notlike "*Microsoft.ZuneMusic*"} | where-object {$_.name –notlike "*Microsoft.ZuneVideo*"} | Remove-AppxPackage

Get-AppxProvisionedPackage -Online | where-object {$_.name –notlike "*Microsoft.WindowsStore*"} | where-object {$_.name –notlike "*Microsoft.DesktopAppInstaller*"} | where-object {$_.name –notlike "*Microsoft.HEIFImageExtension*"} | where-object {$_.name –notlike "*Microsoft.MicrosoftStickyNotes*"} | where-object {$_.name –notlike "*Microsoft.MSPaint*"} | where-object {$_.name –notlike "*Microsoft.ScreenSketch*"} | where-object {$_.name –notlike "*Microsoft.StorePurchaseApp*"} | where-object {$_.name –notlike "*Microsoft.VP9VideoExtensions*"} | where-object {$_.name –notlike "*Microsoft.WebMediaExtensions*"} | where-object {$_.name –notlike "*Microsoft.WebpImageExtension*"} | where-object {$_.name –notlike "*Microsoft.Windows.Photos*"} | where-object {$_.name –notlike "*Microsoft.WindowsCalculator*"} | where-object {$_.name –notlike "*Microsoft.WindowsCamera*"} | where-object {$_.name –notlike "*Microsoft.ZuneMusic*"} | where-object {$_.name –notlike "*Microsoft.ZuneVideo*"} | Remove-AppxPackage

Answer

Hi MABrooksWe use the below powershell script to remove all the metro apps and keep the main ones like Calcualtor.Make this a Post Installaiton task on your K2000 or K1000 and it will deploy and remove all the Windows 10 bloatware.https://github.com/Sycnex/Windows10Debloater/blob/master/Windows10Debloater.ps1This will run when deployed and any user that logs on after will have a clean debloated profile.Make sure your full command line is the same as below.powershell -nologo -executionpolicy bypass -noprofile -file Windows10Debloater.ps1Is this the sort of thing your looking for?Kind RegardsLawrence

Answer

I stopped doing scripted installs, they are harder to customize in detail.

For images make sure you use the administrator account to copy to default and never never login with another user on your master. It creates problems removing store apps since another user had the app installed. Remove all the tiles under administrator and place the only what you want everyone to see.

If you do not use a VM for your master (I use a Dell 5050) make sure any apps installed by windows for the audio or video are removed in control panel - programs prior to sysprep

Our golden images for windows 10 (regular and LTSC) are minimal. We have all the browsers and they are configured how we want, we have the base adobe products. Also install things like the VPN then we can put the UNC in so users only need to enter name/password, configure VNC and a few minor programs. Also this gives everyone the same directory structure so programs like Firefox all will have the same path now vs unique per user in the profiles. easier to make changes when all machines are the same.

We do not install office till post the newer versions have some hard paths in the registry so if you install office prior everyone will have pointers to administrator directories in their profile. I copied the office install to a temp directory on my master. It installs post and then deletes the install.

I run a pin.ps1 to pin any tiles post like office after I install it

(New-Object -ComObject shell.application).Namespace('C:\Program Files (x86)\Microsoft Office\Office16\').parsename('excel.exe').invokeverb('pintostartscreen')

(New-Object -ComObject shell.application).Namespace('C:\Program Files (x86)\Microsoft Office\Office16\').parsename('powerpnt.exe').invokeverb('pintostartscreen')

(New-Object -ComObject shell.application).Namespace('C:\Program Files (x86)\Microsoft Office\Office16\').parsename('winword.exe').invokeverb('pintostartscreen')

We use post tasks and the SMA to finish the images.

If you keep the driver feed current a sysprep image will get its drivers just like a scripted image.

You can create your answer files with the tool Kace has https://www.itninja.com/blog/view/sysprep-creator-wizard

or use Microsoft's WSIM to create and validate.

I recommend using the Kace tool to build and the WSIM to validate the file and also encrypt the passwords.

On the Win10 images I have the cleanup.ps1 file that removes the apps we do not want. I run it manually prior to sysprep and also as my first post task when the machine comes out of sysprep. (app paranoia) and poke the registry to stop them re-pushing the commercial apps.

We push the same wim file to all our desktops and laptops without any problem. We have a lot of different models in use, even surface's they all take the image.

The method you choose should be based on skills available and what works best for your organization.

We image because in our classrooms the techs use WOL to wake machines, change boot to pxe with the SMA, cast image automatically from SDA, set bios back to hdd first mid level, never having to touch a machines except the occasional failure. New machines they set the bios and boot to pxe, choose image and walk away. most imaging can be done from a tech station in shop.

On admin they image replacement machine in shop, arranges with customer when they can have an hour to migrate them. take machine to their office, pull mig file to usb drive, remove old machine from domain, put new machine in place give it same name and join to domain and migrate back.

Answer

I used to run my PS1 file just prior to sysprep and copied the user to default so they were not here to begin with.

I also had to set this reg key or they came back for new users after a bit, try adding this to your post prior to running ps.

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\CloudContent" /v DisableWindowsConsumerFeatures /d 00000001 /t REG_DWORD /f

Windows 10 AppxPackage Removal For All Existing and Future User Accounts

Answers (3)

Posted by:

View more:

Related Questions

Related Links

Related Posts

Scripting

Windows 10 AppxPackage Removal For All Existing and Future User Accounts

Answers (3)

Posted by:

Don't be a Stranger!

View more:

Related Questions

Related Links

Related Posts

Share