If a Store app is non-responsive or misbehaving, you can force close it. Here’re different ways to terminate Microsoft store apps.
The Microsoft Store provides the easiest way to install and uninstall apps from Windows 10. In fact, that is one of its best features as it removes the necessity of going through the installation and uninstallation wizards. In addition to that, the apps are also updated silently in the background so that you don’t have to deal with an upgrade or update prompts.
Just like other applications, even after closing some Store apps like Mail, Facebook, Calendar, etc. will silently run in the background. Since the apps are constantly running in the background, they can show notifications, update information, and provide services specific to that app. For example, the Mail app can show new email notification whenever you receive a new email.
As good as it is, as long as the app is running in the background, it uses system resources. This may not be a problem for the most part. However, if the app is misbehaving, not working as it should, or not responding, you have to manually terminate Microsoft Store apps to fully close it. In case you are wondering, terminating is nothing but forcefully closing the application.
So, in this quick tutorial let me show different ways you can stop or terminate any Microsoft Store app in Windows 10.
1] Terminate Microsoft Store Apps from Settings
Every Microsoft Store app has its own master settings page. From that page, you can reset the app, change permissions, terminate, and uninstall the app.
1. First, open the PC Settings app by pressing the Win + I keyboard shortcut. You can also search for it in the start menu or click on the “All Settings” button in the Action Center.
2. After opening the Settings app, go to the “Apps → Apps & Features” page. On the right panel, you will see all the installed applications. Find the app you want to terminate either by scrolling down by using the available search bar.
3. Once you found the app, click on it and then click on the “Advanced Options” link.
Note: The Advanced Options link will only appear for Microsoft Store apps. For regular win32 apps, you will not see that link.
4. In the Advanced Options page, click on the “Terminate” button under the Terminate section.
As soon as you click on the button, the application will be forcefully closed. Keep in mind that it might start automatically. If you don’t want that to happen, on the same page, toggle the switch under “Background” to OFF position.
2] From Task Manager (Alternative Method)
As an alternative, you can also terminate a Microsoft Store app from the Task Manager too. This is particularly useful if you cannot access the Settings app or if the Terminate button is not working.
1. Right-click on the taskbar and select the “Task Manager” option to open it.
2. In the task manager, go to the “Processes” tab, find the app you want to terminate from the list. If the app is actively running, you can find it directly under the “Apps” section on the top.
3. Once you found the app, select it and click on the “End Task” button.
That is it. As soon as you click on the button, the app will be force closed. Just like with the first method, the app might restart itself even after you terminate it. If you don’t want that behavior, revoke background running permission as shown in the last paragraph of the first method.
I hope that helps. If you are stuck or need some help, comment below and I will try to help as much as possible.
A quick tip: If needed, you can also reset Windows 10 Settings app if it is not behaving properly.
Nope! Killing the process using Task Manager does NOT absolutely terminate the application in the way the Terminate option does in Settings.
Actually this was why I started googling, looking for the right way to do it.
In my case I am talking about the Deezer app. The app was showing weird behaviour once agein (it often does), even after killing it using Task Manager and reopening.
Only the Terminate button helped to get it run normal again without the need for rebooting Windows.
Possible explanations might be other related processes running(?) or the correct removal of used caches(?) when terminating the app in the official way.