Update January 24: Microsoft has confirmed the issue behind Windows Start Menu's unresponsiveness and app launching problems. More info on possible workarounds is available HERE.
Microsoft is investigating an issue causing the Windows taskbar and Start Menu to become unresponsive and triggering Outlook and Teams login problems.
Windows admins have told BleepingComputer that their users have been reporting issues not seeing the Windows Start Menu when clicking, not being able to launch modern apps, and that the Windows Search feature is broken.
Others have also reported encountering issues while trying to log into Azure Active Directory (Azure AD) to activate Office 365 apps.
Similar issues have happened in the past, too, with Microsoft MVP Rudy Ooms linking them in June 2022 with the ClickShare app (a tool that helps share a Windows device's screen wirelessly) corrupting User Shell Folders registry permissions.
However, Microsoft sent a statement two months later acknowledging that its own software was breaking permissions for the affected apps and causing unresponsiveness and connection issues.
"While this initially appeared to be an issue with the 3rd party app, it now appears to be Microsoft code (profapi.dll) which breaks the permissions thinking they need to be recovered," Redmonds told Ooms.
"This may occur when an x32 third-party process (like ClickShare) uses Office APIs on a machine where Office is deployed using Office ClickToRun, because of a bug in AppvIsvSubsystem32.dll registry hooks.
"In this case, profapi.dll will start recovering the ACLs, but after a second failure, it won't write the All Application Packages ACLs, causing issues (crashes & registration failures) with packaged apps."
Script to fix corrupt registry permissions
Today, Barco (ClickShare's developer) has updated an advisory it initially issued in July 2022 to share a helper Diagnostic PowerShell script provided by Microsoft Support that would allow affected users to repair the corrupted User Shell Folders registry permissions.
"Although the app is not causing the problem, we still want to offer our ClickShare App users a possible intermediate solution," Barco said.
"In most cases it has been possible to recover by using the recovery tool from Microsoft: the recovery tool FixUserShellFolderPermissions."
The script can be downloaded from the Downloads section at the end of Barco's recently updated advisory.
If the issue is not addressed after running the helper script, you should manually disable the Calendar Integration feature from ClickShare's Settings dialog.
"Please contact Barco Support for more details on an dedicated APP version (4.25.2) to prevent the issue from happening until a final solution can be offered," the company added.
Issue under investigation
While Microsoft is yet to acknowledge this issue publicly, Barco said that Redmond's Windows team is investigating it and advises affected customers to reach out to Microsoft to file a report of their own.
"The issue is under investigation with Microsoft Windows team but it still is good to take up contact directly with Microsoft Windows team to flag this issue," Barco said.
"Make sure to mention for ticket submission the tittle "unresponsive start menu or task bar" and refer to Microsoft internal bug number: 41322218."
A Microsoft spokesperson was not immediately available for comment when contacted by BleepingComputer earlier today.
H/T Günter Born
Comments
TanyaC - 1 year ago
Good on you Microsoft!
This has been an issue since at least v1809 of Windows 10.
Awesome superfast response. Not.
SoftwareEngineer248 - 1 year ago
I understand why you are frustrated but it does not happen to everyone. I have never seen it for example. My guess is that it only occurs on certain configurations, and it is also an intermittent bug.
These problems are hard to solve because the people fixing the bug (problem, defect, error, etc.) often cannot reproduce the bug on their own system. This means they often have no idea why it's occurring, and they have to guess or rely on telemetry. Guessing often does not fix the bug because most guesses are wrong. Telemetry, user reports and automated error reports can help but it's harder to diagnose and fix a bug using these tools.
If you want to fix your own issue, I would try some basic steps first.
1) Make sure your computer has enough RAM. 8 GB is fine for most users but if you have a lot of web browser tabs open, I would go with 16 GB or 32 GB.
2) Consider removing software you don't use. I would focus on software which always runs processes in the background or which integrates with the operating system or shell. These sorts of things are more likely to cause problems with your computer.
3) If 1 and 2 do not work, consider upgrading to a SSD (Solid State Disk) if you are using a mechanical hard drive (traditional hard drive). It will help your performance a lot.
4) If nothing helps, consider reinstalling Windows or resetting Windows to its original state (https://support.microsoft.com/en-us/windows/recovery-options-in-windows-31ce2444-7de3-818c-d626-e3b5a3024da5#bkmk_reset_pc&WindowsVersion=Windows_11). This is annoying because it means you have to reinstall all of your applications but it has the highest chance of working. Remember to backup your data before you do this.
Dburke225 - 1 year ago
I've been complaining to Microsoft and researching this since the summer. Only got, we cannot help you, from Microsoft.
Only solution we found was disconnect from internet, restart Windows Explorer task, reconnect to internet.
Artolink - 1 year ago
Just had this problem yesterday for two different clients, tried the fix included in the article but didn't work... hope Microsoft comes up with a solution fast.
Can you please notify me if you find the solution?
Bleeping Computer amazing as always!
Thanks!
-Artolink
Dburke225 - 1 year ago
Unplug the ethernet, if Wi-Fi disable it, then press Ctrl Shift Esc, to open the task manager then restart the file explorer task. Usually works for us.
DavidDavid123 - 1 year ago
Same issue here....
Dburke225 - 1 year ago
Unplug the ethernet, if Wi-Fi disable it, then press Ctrl Shift Esc, to open the task manager then restart the file explorer task. Usually works for us.
Holoholo - 1 year ago
Yeah. Yesterday we had a bunch of clients with this issue. All linked to an auto update from Barco ClickShare, Version 4.27.0-b8.
https://www.reddit.com/r/msp/comments/10f9ab6/comment/j4vw3hy/?utm_source=share&utm_medium=web2x&context=3
Artolink - 1 year ago
This is not my case unfortunately
trltrl - 1 year ago
Found a solution that worked for us. Uninstall the ClickShare app and run the following ps-script as the user
$acl1 = Get-Acl "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\"
#$person = [System.Security.Principal.NTAccount]"all application packages" ##S-1-15-2-1
$sid = New-Object System.Security.Principal.SecurityIdentifier ("S-1-15-2-1")
$person_temp = $sid.Translate( [System.Security.Principal.NTAccount])
$person = $person_temp.Value.Split("\")[1]
$access = [System.Security.AccessControl.RegistryRights]"ReadKey"
$inheritance = [System.Security.AccessControl.InheritanceFlags]"ContainerInherit,ObjectInherit"
$propagation = [System.Security.AccessControl.PropagationFlags]"None"
$type = [System.Security.AccessControl.AccessControlType]"Allow"
$rule = New-Object System.Security.AccessControl.RegistryAccessRule($person,$access,$inheritance,$propagation,$type)
$acl1.AddAccessRule($rule)
$acl1 | Set-Acl
if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) { Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown } Get-AppxPackage Microsoft.AAD.BrokerPlugin
sanch2 - 1 year ago
Having the same issue for a Windows 10 22h2. Windows and search button not responding.
Outlook not connecting, asking for password and password prompt disappearing immediately.
Teams also having problem to connect.
User has some Barco software installed.
I resolved the Teams and Outlook problem with the following:
for outlook adding 3 registry key:
KEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity
Create a new DWORD named "EnableADAL" and give it a value 1
Create a new DWORD named "DisableAADWAM" and give it a value 1
Create a new DWORD named "DisableADALatopWAMOverride" and give it a value 1
and reboot
For Teams:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
Reboot
Still haven't resolve the Start and search button. Will log a support ticket.
Edit:
The Start and search button are fixed with the Barco script. But come back after every reboot.
SecurityIsStress - 1 year ago
I've been investigating issues with outlook backend app authentication breaking for a few months now. I'm glad for this article as I think it very well will lead me to understanding and resolving this issue.
IGotChicks - 1 year ago
Here's the solution:
Restoring and installing Clickshare version 4.26 or alternatively disabling the "calendar integration" in Clickshare.
Here you'll find some more details:
https://www.barco.com/en/support/knowledge-base/6077-unresponsive-windows-taskbar-with-clickshare-app
Artolink - 1 year ago
It is not only caused by Clickshare, it happens when some third party software calls some specific MOffice API and profapi.dll is used. We need a definitive solution from Microsoft, or a registry fix from someone when this happens...
SiemNL - 1 year ago
I have the same problems on different Surfaces from different companies. The 3 registry keys from @sanch2 gave me the login for Outlook back. The Teams script does not run (or i am not doing it right).
h_b_s - 1 year ago
There's probably multiple issues behind this. Another person tracked a similar issue with start to crashes from runtimebroker.exe which appears to be related to Microsoft's insistence in spamming the start menu with web search junk no one asked for nor wants. There's a well written article detailing the person's investigation into why he was encountering application launch lag from the Win 11 start menu. You can find it here:
https://randomascii.wordpress.com/2023/01/17/no-start-menu-for-you/
The work-around is listed at the end of the article. Turn off start menu web search. Or, you know, don't use Windows, which isn't an option for some I know. Please note, as the article points out, his research isn't definitive, nor is it necessarily the only reason people may encounter issues with the start menu or starting applications.
At this point, I'm only using Windows when I need to. My daily drivers are a combination of MacOS, iOS, and Linux because I'm fed up with Windows 10 and (especially) 11 bugs and intrusive, purposely distracting UX. If it weren't for a couple of games and one particular Windows-only program I need a couple of times a month and doesn't run well on Wine, I'd wipe the Windows drive clean and be done with it for good.
sanch2 - 1 year ago
Microsoft has release an article about it:
https://learn.microsoft.com/en-us/troubleshoot/windows-client/shell-experience/troubleshoot-start-menu-errors
henrikuhaja - 1 year ago
Hi Everyone,
These PowerShell commands have fixed it 30 times for me. Please open Powershell as admin, and run this:
#$acl1 = Get-Acl "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\"
#$person = [System.Security.Principal.NTAccount]"all application packages" ##S-1-15-2-1
$sid = New-Object System.Security.Principal.SecurityIdentifier ("S-1-15-2-1")
$person_temp = $sid.Translate( [System.Security.Principal.NTAccount])
$person = $person_temp.Value.Split("\")[1]
$access = [System.Security.AccessControl.RegistryRights]"ReadKey"
$inheritance = [System.Security.AccessControl.InheritanceFlags]"ContainerInherit,ObjectInherit"
$propagation = [System.Security.AccessControl.PropagationFlags]"None"
$type = [System.Security.AccessControl.AccessControlType]"Allow"
$rule = New-Object System.Security.AccessControl.RegistryAccessRule($person,$access,$inheritance,$propagation,$type)
#$acl1.AddAccessRule($rule)
#$acl1 | Set-Acl $folder = 'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders'
$acl = Get-Acl $folder
try {
$acl.AddAccessRule($rule)
$acl |Set-Acl
} catch { } $folder = 'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer'
$acl = Get-Acl $folder
try {
$acl.AddAccessRule($rule)
$acl |Set-Acl
} catch { }
Get-AppXPackage *Microsoft.Windows.Search* | ForEach-Object {Add-AppxPackage -DisableDevelopmentMode -ForceApplicationShutdown -Register "$($_.InstallLocation)\AppXManifest.xml"}
Get-AppXPackage *MicrosoftWindows.Client.CBS* | ForEach-Object {Add-AppxPackage -DisableDevelopmentMode -ForceApplicationShutdown -Register "$($_.InstallLocation)\AppXManifest.xml"}
Get-AppXPackage *Microsoft.Windows.ShellExperienceHost* | ForEach-Object {Add-AppxPackage -DisableDevelopmentMode -ForceApplicationShutdown -Register "$($_.InstallLocation)\AppXManifest.xml"}
if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) { Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown } Get-AppxPackage Microsoft.AAD.BrokerPlugin
Get-AppXPackage *Microsoft.AccountsControl* | ForEach-Object {Add-AppxPackage -DisableDevelopmentMode -ForceApplicationShutdown -Register "$($_.InstallLocation)\AppXManifest.xml"}
Get-AppXPackage *Microsoft.Windows.CloudExperienceHost* | ForEach-Object {Add-AppxPackage -DisableDevelopmentMode -ForceApplicationShutdown -Register "$($_.InstallLocation)\AppXManifest.xml"}
After that, you should be able to add your O365 account as a work account in windows settings.
SiemNL - 1 year ago
@henrikuhaja when i run that i get an error om the line
$acl1 = Get-Acl $folder
Error on line 1 car 16. That's the Dollar sign from folder.
Dburke225 - 1 year ago
I have been looking up this issue for months now. Has happened since the summer, the only solution was to unplug the ethernet and turn off wifi, then Restart Windows Explorer in the Task Manager.
Is this finally going to be fixed, hasn't happened for a while but still annoying when it does come up.