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/shell-experience/troubleshoot-start-menu-errors.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Categories of issues with the Start menu:
17
17
18
18
- Issues related to deployment or installation
19
19
- Application termination or crash
20
-
- Issues related to the Start menu customization or other policies/configuration service provider (CSPs)
20
+
- Issues related to the Start menu customization or other policies/configuration service providers (CSPs)
21
21
- Other issues
22
22
23
23
## Basic troubleshooting
@@ -211,19 +211,19 @@ To work around the issue, follow these steps:
211
211
1. Download the [scripts](https://cesdiagtools.blob.core.windows.net/windows/FixUserShellFolderPermissions.zip) to fix the issue when it happens, though the scripts can't
212
212
prevent the issue from re-occurring.
213
213
214
-
2. Open a PowerShell prompt under the affected user identity, and run the following command:
214
+
2. Open a PowerShell prompt under the affected user identity, and run the following cmdlet:
215
215
216
216
```PowerShell
217
217
.\FixUserShellFolderPermissions.ps1
218
218
```
219
219
220
-
- If the script can't access the registry key because the registry permissions are wiped out, open an elevated PowerShell prompt and run the following command:
220
+
- If the script can't access the registry key because the registry permissions are wiped out, open an elevated PowerShell prompt and run the following cmdlet:
221
221
222
222
```powershell
223
223
FixUserShellFolderPermissions.ps1 -allprofiles
224
224
```
225
225
226
-
- If an application doesn't work, you might need to register the shell packages by running the following command as the affected user:
226
+
- If an application doesn't work, you might need to register the shell packages by running the following cmdlet as the affected user:
0 commit comments