Skip to content

Commit be47852

Browse files
authored
updates
1 parent 93372cf commit be47852

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

support/windows-client/shell-experience/troubleshoot-start-menu-errors.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Categories of issues with the Start menu:
1717

1818
- Issues related to deployment or installation
1919
- 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)
2121
- Other issues
2222

2323
## Basic troubleshooting
@@ -211,19 +211,19 @@ To work around the issue, follow these steps:
211211
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
212212
prevent the issue from re-occurring.
213213

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:
215215

216216
```PowerShell
217217
.\FixUserShellFolderPermissions.ps1
218218
```
219219
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:
221221
222222
```powershell
223223
FixUserShellFolderPermissions.ps1 -allprofiles
224224
```
225225
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:
227227
228228
```powershell
229229
FixUserShellFolderPermissions.ps1 -register

0 commit comments

Comments
 (0)