Windows 10: Cannot remove apps using Appx after Fall Creator Update

I do not know if others have come across this problem, but it seems that remove-appxpackage no longer works to remove the UWP downloaded by the system.

The command runs thru with its usual error message about being unable to remove some, but these aren't in that list.
Also get-appxpackage -allusers | remove-appxpackage no longer seems to work. Or at least it doesnt remove the apps from all users any longer.

:)

 

Windows Reopens applications after Shutdown.

Microsoft may change this 'feature' in the spring update.

But see
this link on superuser.

After Windows 10 Fall Creators Update recent used app will launch on startup

 

Windows Reopens applications after Shutdown.

Yup this will work until MS gets it fixed!

 

I tried your code and it removed some apps, but it didn't remove other things like "Bubble Witch 3 Saga", "Disney Magic Kingdoms", etc. Is that what you mean?

I have found that "Remove-AppXPackage" works best when used before installing Windows. Either in sysprep Audit Mode, or editing the offline wim directly. This is the command I use to remove apps from a mounted image:
Code: Get-AppXProvisionedPackage -Path "C:\Mount" | Where-Object {$_.PackageName -NotLike "*Microsoft.WindowsStore*"} | Where-Object {$_.PackageName -NotLike "*Microsoft.WindowsCalculator*"} | Where-Object {$_.PackageName -NotLike "*Microsoft.MicrosoftStickyNotes*"} | Remove-AppXProvisionedPackage[/quote]
This also has to be used in conjunction with the "Turn off Microsoft consumer experiences" computer policy. For servicing an offline wim, it can be translated as a reg value like this:
Code: REG ADD "HKLM\%MountedSoftwareHive%\Policies\Microsoft\Windows\CloudContent" /v "DisableWindowsConsumerFeatures" /t REG_DWORD /d "1" /f[/quote]
If that part isn't there, "Candy Crush" or whatever is still going to install itself within a few minutes of connecting to the internet. I am normally doing this with an Enterprise image in a domain environment that includes lots of other modifications. I tried it today with an x64 Pro ISO downloaded from the Media Creation Tool. Besides having to convert "install.esd" to "install.wim", it appears to work the same. When I first signed into my test machine, the Start menu looks like below. After over an hour there are still no new apps installing themselves.

 

OK. I dont know what I was doing wrong, but the command started working again.

Thanks for that info. I will definitely do that on the next image.