12

Fresh Windows 10 install. Somehow the MSN Weather app became corrupted. (Unable to launch) I removed the app with the following Powershell command:

Remove-AppxPackage -Package Microsoft.BingWeather_4.7.118.0_x86__8wekyb3d8bbwe

However, when running

Get-Appxpackage –Allusers

the package is still present. When I attempt to reinstall the app via the Windows Store, the download is skipped and the same corrupted package is installed.

I've tried restarting (many times) and using WSReset to no avail.

What can I do? Thank you!

  • 1
    you have to use Remove-AppxProvisionedPackage to remove buildin apps: Remove-AppXProvisionedPackage -Online -PackageName <PackageName> – magicandre1981 Dec 21 '15 at 5:17
  • I'm getting "the system cannot find the file specified". – GiantDuck Dec 22 '15 at 0:28
  • DId you try running the command as Administrator from the powershell console? – Smeerpijp Dec 29 '15 at 10:06
6

On Windows 10 1709 :

Get-AppxPackage -all *NAME_OF_THE_APPX* | Remove-AppxPackage -AllUsers
|improve this answer|||||
  • Theoretically it worked (I saw something happened, and Get-AppxPackage -all *CandyCrush* now shows empty), but unfortunately I still see gigabytes of CandyCrush & similar crap in the WindowsApps folder :( not a complaint to you, just to Microsoft I suppose :/ – akavel May 6 '19 at 14:45
2

As of v1709 (Fall Creator's Update), there is a new "-AllUsers" flag for Remove-AppxPackage.

|improve this answer|||||
1

This will work in windows 10 1809:

get-appxpackage *pattern* | remove-appxpackage -AllUsers

or

remove-appxpackage -AllUsers -Package somepackagefullname

This is currently not working:

remove-appxpackage -User somesid -Package somepackagefullname

Piping anything to remove-appxpackage with no options will only remove the packages of the current user.

|improve this answer|||||
1

The Remove-AppxPackage only removes store applications for the logged in user, even if you pipe it from Get-AppxPackage -AllUsers

I've had trouble updating apps in the past because another user had logged in and the app had been updated in their profile, it's also a known issue when using sysprep.

You can identify if that is the case using this script:

Get-AppxPackage -AllUsers | Format-List -Property PackageFullName,PackageUserInformation.

In the output of this last cmdlet, check the users for whom the package is showing up as Installed. Delete these user accounts from the reference computer, or log on to the computer by using these user accounts & remove the Appx package, as you have been:

Remove-AppxPackage -Package Microsoft.BingWeather_4.7.118.0_x86__8wekyb3d8bbwe

If that still doesn't work, you could try removing the provisioning and installing it again from the Store.

Remove-AppxProvisionedPackage -Online -PackageName Microsoft.BingWeather_4.7.118.0_x86__8wekyb3d8bbwe
|improve this answer|||||
  • Careful to users removing store from provisioning, it can be a real hassle after reinstall; see here to get store back, if you make this mistake! – Under A Tree Jun 16 '19 at 8:13
-1

Best bet is to remove the apps from the image. Weather is a provisioned app, meaning it will install a fresh copy for each user if present. This holds true for new version releases as well. Check out Michael's article on removing them via task sequence, it's a great reference you can adapt for your particular methods. https://blogs.technet.microsoft.com/mniehaus/2015/11/11/removing-windows-10-in-box-apps-during-a-task-sequence/

TL;DR - You have to remove it from the image if you want it to stay gone, else it will eventually reinstall for someone.

|improve this answer|||||
  • 1
    would you care to include the instructions from the link into your answer? – flolilo Jan 3 '18 at 13:02
  • Basically, you'd use powershell and run get-startapps | format-list | out-file C:\users\username\desktop\startapps.txt to isolate the target packages , and run the supplied script in the link after modifying the $AppsList variable definition. Of course, replace username in the get-startapps cmdlet with your username. You'll want to use format-list in the cmdlet to prevent truncation of package names. I strongly advise picking through a few articles before doing this. There are provisioned and non-provisioned applications. Not enough room to type it all out. – Charlie C Jan 4 '18 at 18:20
  • Removing a non-provisioned package in the image can cause serious functionality loss. For example, removing Cortana components can cause SearchUI to break, since it is nested in Cortana's package for efficiency. – Charlie C Jan 4 '18 at 18:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.