deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merged PR 8127: Edits to removing provisioned apps article

Browse Source 
- Corrected version info, clarified this doesn't apply to 1803.
- Added note clarifying feature update.
- Fixed formatting for example registry key.
This commit is contained in:
Heidi Lohr 2018-05-10 23:25:09 +00:00
commit 53ac5187a4
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
windows/application-management/remove-provisioned-apps-during-update.md
View File

@ -6,16 +6,17 @@ ms.mktglfcycl: deploy
ms.sitesec: library ms.sitesec: library
ms.author: helohr ms.author: helohr
author: HeidiLohr author: HeidiLohr
ms.date: 05/09/2018 ms.date: 05/10/2018
--- ---
# How to keep apps removed from Windows 10 from returning during an update # How to keep apps removed from Windows 10 from returning during an update
>Applies to: Windows 10, version 1703; Windows 10 version 1709; Windows 10, version 1803 >Applies to: Windows 10 (Semi-Annual Channel)
When you update a computer running Windows 10, version 1703 or 1709, you might see provisioned apps that you previously removed return post-update. This can happen if the computer was offline when you removed the apps. When you update a computer running Windows 10, version 1703 or 1709, you might see provisioned apps that you previously removed return post-update. This can happen if the computer was offline when you removed the apps. This issue was fixed in Windows 10, version 1803.
>[!NOTE] >[!NOTE]
>This only applies to first-party apps that shipped with Windows 10. This doesn't apply to third-party apps, Microsoft Store apps, or LOB apps. >* This issue only occurs after a feature update (from one version to the next), not monthly updates or security-related updates.
>* This only applies to first-party apps that shipped with Windows 10. This doesn't apply to third-party apps, Microsoft Store apps, or LOB apps.
To remove a provisioned app, you need to remove the provisioning package. The apps might reappear if you removed the packages in one of the following ways: To remove a provisioned app, you need to remove the provisioning package. The apps might reappear if you removed the packages in one of the following ways:
@ -36,7 +37,10 @@ Use the following steps to create a registry key:
1. Identify any provisioned apps you want removed. Record the package name for each app. 1. Identify any provisioned apps you want removed. Record the package name for each app.
2. Create a .reg file to generate a registry key for each app. Use [this list of Windows 10, version 1709 registry keys](#registry-keys-for-provisioned-apps) as your starting point. 2. Create a .reg file to generate a registry key for each app. Use [this list of Windows 10, version 1709 registry keys](#registry-keys-for-provisioned-apps) as your starting point.
1. Paste the list of registry keys into Notepad (or a text editor). 1. Paste the list of registry keys into Notepad (or a text editor).
2. Remove the registry keys belonging to the apps you want to keep. For example, if you want to keep the Bing Weather app, delete this registry key: `[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Deprovisioned\Microsoft.BingWeather_8wekyb3d8 bbwe]` 2. Remove the registry keys belonging to the apps you want to keep. For example, if you want to keep the Bing Weather app, delete this registry key:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\A ppxAllUserStore\Deprovisioned\Microsoft.BingWeather_8wekyb3d8bbwe]
```
3. Save the file with a .txt extension, then right-click the file and change the extension to .reg. 3. Save the file with a .txt extension, then right-click the file and change the extension to .reg.
3. Double-click the .reg file to create the registry keys. You can see the new keys in HKLM\\path-to-reg-keys. 3. Double-click the .reg file to create the registry keys. You can see the new keys in HKLM\\path-to-reg-keys.