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
-58Lines changed: 0 additions & 58 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -183,64 +183,6 @@ Other useful tools to troubleshoot Start menu issues:
183
183
184
184
The following list provides information about common errors you might run into with the Start menu, and steps to help you mitigate them.
185
185
186
-
### Symptom: Apps using Office APIs with Office Click-to-Run installed might cause the Start menu and other shell components to fail
187
-
188
-
You might experience various issues related to the Windows Shell on devices that are running Office Click-to-Run, along with some third-party applications that use Office APIs:
189
-
190
-
- Event 1000 is logged in the Application event log. The event log reports that an application crashes for **StartMenuExperienceHost.exe**, **ShellExperienceHost.exe**, **SearchUI.exe**, with an error code 0xc000027b or -1073741189.
191
-
- Errors in the Microsoft-Windows-AppModel-State event log mentioning the following error with various package names:
192
-
193
-
> Triggered repair of state locations because operation SettingsInitialize against package Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy hit error -2147024891.
194
-
195
-
- The Windows Start menu doesn't respond to mouse clicks or the Windows key.
196
-
- Windows Search doesn't respond to mouse clicks on pressing the **Search** button or Windows+S key.
197
-
198
-
#### Cause
199
-
200
-
Affected devices might have damaged registry keys or data which might affect apps using Microsoft Office APIs to integrate with Windows, Microsoft Office, Microsoft Outlook, or Outlook Calendar. This might occur if application packages permissions are being removed from the following registry path:
> Barco has reported to have fixed this issue starting their App version 4.27.2. However, the affected devices might need to follow the steps mentioned in the workaround section.
208
-
>
209
-
> For more information, see [Unresponsive Windows taskbar or user shell folder permissions issues with ClickShare App Calendar integration](https://www.barco.com/en/support/knowledge-base/6077-unresponsive-windows-taskbar-with-clickshare-app).
210
-
211
-
To work around the issue, follow these steps:
212
-
213
-
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
214
-
prevent the issue from re-occurring.
215
-
216
-
2. Open a PowerShell prompt under the affected user identity, and run the following cmdlet:
217
-
218
-
```PowerShell
219
-
.\FixUserShellFolderPermissions.ps1
220
-
```
221
-
222
-
- 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:
223
-
224
-
```powershell
225
-
FixUserShellFolderPermissions.ps1 -allprofiles
226
-
```
227
-
228
-
- If an application doesn't work, you might need to register the shell packages by running the following cmdlet as the affected user:
229
-
230
-
```powershell
231
-
FixUserShellFolderPermissions.ps1 -register
232
-
```
233
-
234
-
#### Prevent the issue from reoccurring
235
-
236
-
- Ensure the ClickShare App is updated to version 4.27.2 or higher.
237
-
- Ensure the Calendar integration is disabled (default disabled as of version 4.27.2).
238
-
- Prevent the applications from running at startup or configure the applications to Start on-demand.
239
-
240
-
#### Status
241
-
242
-
Microsoft is aware of this issue and is working to resolve it in an upcoming Office update. We'll post more information in this article when it becomes available.
243
-
244
186
### Symptom: Start menu doesn't respond on Windows 2012 R2, Windows 10, or Windows 2016
0 commit comments