You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/windows-client/application-management/modern-apps-application-packages-reported-vulnerable.md
+36-33Lines changed: 36 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,75 +11,78 @@ ms.custom: sap:Windows Desktop and Shell Experience\Modern, Inbox and Microsoft
11
11
---
12
12
# Modern apps or application packages are reported as vulnerable due to multiple versions
13
13
14
-
This article provides troubleshooting suggestions when there are multiple versions of one modern app (also known as application package) on a computer. The app could be reported as vulnerable by system vulnerability scanning and can't be resolved by updating to the latest version.
14
+
This article provides troubleshooting suggestions when there are multiple versions of a modern app or application package on a computer. The app might be reported as vulnerable by system vulnerability scanning and can't be resolved by updating to the latest version.
15
15
16
16
*Original KB number:* 5011324
17
17
18
-
## Issue symptoms
18
+
## Symptoms
19
19
20
-
On recent Windows versions, several parts of the shell are moved to modern apps. Those apps are brought as .msix or .appx files and need to be registered per-user at every first user sign-in to Windows or after an app update.
20
+
In recent Windows versions, several parts of the shell have been moved to modern apps. Those apps are introduced as *.msix* or *.appx* files and need to be registered peruser each time a user signs in to Windows for the first time or after an app update.
21
21
22
-
Those apps might be **SystemApps** (such as **StartMenuExperienceHost**, **ShellExperienceHost** and so on) brought within Windows Cumulative Updates, or **WindowsApps** which are updated through Windows Update connecting to Windows Store endpoints.
22
+
Those modern apps might be **SystemApps** (such as **StartMenuExperienceHost** and **ShellExperienceHost**) introduced within Windows Cumulative Updates or **WindowsApps** updated through Windows Update connecting to Windows Store endpoints.
23
23
24
24
Because of this inherent design, you might encounter one of the following issues:
25
25
26
26
### Multiple app folders in the system
27
27
28
-
If there are multiple user profiles in the system, Apps installed per users might create multiple app folders because of the different versions. The folders are in the *C:\\Program Files\\WindowsApps* hidden folder.
28
+
If there are multiple user profiles in the system, apps installed per user might create multiple app folders because of the different versions. The folders are in the *C:\\Program Files\\WindowsApps* hidden folder.
29
29
30
30
### Multiple app versions in the system
31
31
32
32
Consider the following scenarios:
33
33
34
-
- Several users are signed in at the same time and Microsoft Store is enabled. One user is using the app during a Microsoft Store background update.
35
-
- Some users don't sign in frequently and Microsoft Store is disabled. The system administrator updates the app manually.
34
+
- Several users are signed in at the same time, and Microsoft Store is enabled. One user is using the app during a Microsoft Store background update.
35
+
- Some users don't sign in frequently, and Microsoft Store is disabled. The system administrator updates the app manually.
36
36
37
-
In these scenarios, there are multiple versions of the app per users in the system, which doesn't affect users. However, the app is reported as vulnerable if the app isn't updated for all users.
37
+
In these scenarios, there are multiple versions of the app per user in the system, which doesn't affect users. However, the app is reported as vulnerable if the app isn't updated for all users.
38
38
39
39
## Update the app for all users or remove the old packages
40
40
41
41
To resolve this issue, use one or more of the following methods:
42
42
43
-
1. Ensure that the app is updated for all users in the system by reconnecting to the machine with user profiles.
43
+
### Method 1: Ensure that the app is updated for all users in the system by reconnecting to the machine with user profiles.
44
44
45
-
1. Identify the user profiles in which the old Appx version package is installed by using the Appx cmdlet [Get-AppxPackage](/powershell/module/appx/get-appxpackage) from an elevated PowerShell window.
45
+
1. Identify the user profiles in which the old Appx version package is installed by using the Appx cmdlet [Get-AppxPackage](/powershell/module/appx/get-appxpackage) from an elevated PowerShell window:
46
46
47
-
```powershell
48
-
Get-AppxPackage <app_name> -AllUsers
49
-
```
47
+
```powershell
48
+
Get-AppxPackage <Application Name> -AllUsers
49
+
```
50
50
51
-
2. Reconnect to the machine with the identified user.
51
+
2. Reconnect to the machine with the identified user.
52
52
53
-
2. Remove the old packages (.appx)
53
+
### Method 2: Remove the old packages (*.appx*).
54
54
55
-
1. Identify the User Profiles in which the Appx package is installed with Appx cmdlet [Get-AppxPackage](/powershell/module/appx/get-appxpackage) from an elevated PowerShell prompt.
55
+
1. Identify the user profiles in which the Appx package is installed with the Appx cmdlet [Get-AppxPackage](/powershell/module/appx/get-appxpackage) from an elevated PowerShell prompt:
56
56
57
-
```powershell
58
-
Get-AppxPackage <app_name> -AllUsers
59
-
```
57
+
```powershell
58
+
Get-AppxPackage <Application Name> -AllUsers
59
+
```
60
60
61
-
2. Identify if the app is provisioned. To get a list of all provisioned apps, use [Get-AppxProvisionedPackage](/powershell/module/dism/get-appxprovisionedpackage).
61
+
2. Identify if the app is provisioned. To get a list of all provisioned apps, use [Get-AppxProvisionedPackage](/powershell/module/dism/get-appxprovisionedpackage):
3. Delete the user profiles pointing to the old version of the app. To do so, see the following articles:
82
-
[Delete a user profile in Windows](../../windows-server/user-profiles-and-logon/delete-user-profile.md)
83
-
[Using Group Policy/CSP](/windows/client-management/mdm/policy-csp-admx-userprofiles#cleanupprofiles)
81
+
### Method 3: Delete the user profiles pointing to the old version of the app.
84
82
85
-
To confirm that the app is updated for all users and the old packages are removed, scan again or check the *C:\\Program Files\\WindowsApps* folder. If you don't have the permission to check the folder, create a copy in another location and check inside.
83
+
To do so, see the following articles:
84
+
85
+
-[Delete a user profile in Windows](../../windows-server/user-profiles-and-logon/delete-user-profile.md)
86
+
-[Using Group Policy/CSP](/windows/client-management/mdm/policy-csp-admx-userprofiles#cleanupprofiles)
87
+
88
+
To confirm that the App is updated for all users and the old packages are removed, scan again or check the *C:\\Program Files\\WindowsApps* folder. If you don't have permission to check the folder, create a copy in another location and check inside.
0 commit comments