Highlighted
Zepfanman
1 Nickel

How to fix left-click of Start Menu, taskbar icons, and search bar in Windows 10

This problem is affecting ***ALL USERS*** on a new computer I'm setting up in a corporate environment. I thought I'd share my experience in detail in case anyone else is looking for some specific keywords. I've tried as many suggestions from a Microsoft Answers thread as well a post on BT called "Has your Windows 10 Start menu stopped working? Here are four ways to fix it," including suggestions in the comments there.

***NOTHING HAS WORKED SO FAR.***

We have received a shipment of Dell OptiPlex 7040 desktops with Windows 10 Pro built in (Express Settings setup). DisplayPort monitor; 3 USB connections to keyboard, mouse, and speakers; wired LAN; no antivirus except Defender.

I set up the first machine and let the Windows Updates install. I'm not sure if that was the issue, but once I rebooted, I could not open the Start Menu. Nor could I use Cortana or left-click on ANY icon in the taskbar.

Here are the steps that I've tried (that I can remember), starting simple to more complex:

(1) Reinstall Windows apps in Administrator PowerShell: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

(2) Ran sfc /scannow 3 times, rebooting after each. You can see from log file snippets below that the scan detects the same errors every time, but cannot fix them.

(3) Restarted with msconfig "Safe boot" (Safe Mode).

(4) Ran built-in Dell Command Update and installed the latest video driver. Latest BIOS is already installed.

(5) Manually ran Windows Update to make sure all are installed.

(6) Windows System Restore, rolled back to earliest point (initial install).

(7) Reset this PC option in Troubleshooting mode, doing a "Remove everything" rebuild. Start Menu works on first login, but then will not open after the first reboot.

(8) Installed Windows 10 Pro out of the box. Worked fine until installing a huge build update - I did not write down the number and can't find an update history.

Here are a few system and application event logs that seem relevant, followed by snippets from the sfc /scannow log file:

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          6/2/2016 8:40:36 AM
Event ID:      10010
Task Category: None
Level:         Error
Keywords:      Classic
User:          GJ1_D10_7040\admin
Computer:      GJ1_D10_7040.cao30.lan
Description:
The server CortanaUI.AppXfbn8w4s0jbk3tjevpcn9kaxerc6rby8k.mca did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns="schemas.microsoft.com/.../event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10010</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-02T12:40:36.312141200Z" />
    <EventRecordID>5245</EventRecordID>
    <Correlation />
    <Execution ProcessID="928" ThreadID="980" />
    <Channel>System</Channel>
    <Computer>GJ1_D10_7040.cao30.lan</Computer>
    <Security UserID="S-1-5-21-257392508-3664685258-3270622264-1001" />
  </System>
  <EventData>
    <Data Name="param1">CortanaUI.AppXfbn8w4s0jbk3tjevpcn9kaxerc6rby8k.mca</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          6/2/2016 8:40:31 AM
Event ID:      10010
Task Category: None
Level:         Error
Keywords:      Classic
User:          GJ1_D10_7040\admin
Computer:      GJ1_D10_7040.cao30.lan
Description:
The server CompanionApp.App.AppXd70q285y9yf126fg7srgst0m5akck63d.mca did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns="schemas.microsoft.com/.../event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10010</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-02T12:40:31.311771700Z" />
    <EventRecordID>5236</EventRecordID>
    <Correlation />
    <Execution ProcessID="928" ThreadID="976" />
    <Channel>System</Channel>
    <Computer>GJ1_D10_7040.cao30.lan</Computer>
    <Security UserID="S-1-5-21-257392508-3664685258-3270622264-1001" />
  </System>
  <EventData>
    <Data Name="param1">CompanionApp.App.AppXd70q285y9yf126fg7srgst0m5akck63d.mca</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Microsoft-Windows-Immersive-Shell
Date:          6/2/2016 8:46:06 AM
Event ID:      5973
Task Category: (5973)
Level:         Error
Keywords:     
User:          GJ1_D10_7040\admin
Computer:      GJ1_D10_7040.cao30.lan
Description:
Activation of app Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App failed with error: The app didn't start. See the Microsoft-Windows-TWinUI/Operational log for additional information.
Event Xml:
<Event xmlns="schemas.microsoft.com/.../event">
  <System>
    <Provider Name="Microsoft-Windows-Immersive-Shell" Guid="{315A8872-923E-4EA2-9889-33CD4754BF64}" />
    <EventID>5973</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>5973</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-02T12:46:06.164375000Z" />
    <EventRecordID>6322</EventRecordID>
    <Correlation ActivityID="{2A1697F5-BCCA-0000-399B-162ACABCD101}" />
    <Execution ProcessID="5048" ThreadID="4916" />
    <Channel>Application</Channel>
    <Computer>GJ1_D10_7040.cao30.lan</Computer>
    <Security UserID="S-1-5-21-257392508-3664685258-3270622264-1001" />
  </System>
  <EventData>
    <Data Name="AppId">Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App</Data>
    <Data Name="ErrorCode">-2144927141</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Application Error
Date:          6/2/2016 8:46:05 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GJ1_D10_7040.cao30.lan
Description:
Faulting application name: ShellExperienceHost.exe, version: 10.0.10586.306, time stamp: 0x571afaa5
Faulting module name: ShellExperienceHost.exe, version: 10.0.10586.306, time stamp: 0x571afaa5
Exception code: 0xc000027b
Fault offset: 0x0000000000085831
Faulting process id: 0x1018
Faulting application start time: 0x01d1bcccba275e0c
Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Faulting module path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Report Id: 26b0f047-71e6-47c2-952d-e668a7afcaba
Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.10586.0_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="schemas.microsoft.com/.../event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-02T12:46:05.321093700Z" />
    <EventRecordID>6320</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GJ1_D10_7040.cao30.lan</Computer>
    <Security />
  </System>
  <EventData>
    <Data>ShellExperienceHost.exe</Data>
    <Data>10.0.10586.306</Data>
    <Data>571afaa5</Data>
    <Data>ShellExperienceHost.exe</Data>
    <Data>10.0.10586.306</Data>
    <Data>571afaa5</Data>
    <Data>c000027b</Data>
    <Data>0000000000085831</Data>
    <Data>1018</Data>
    <Data>01d1bcccba275e0c</Data>
    <Data>C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe</Data>
    <Data>C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe</Data>
    <Data>26b0f047-71e6-47c2-952d-e668a7afcaba</Data>
    <Data>Microsoft.Windows.ShellExperienceHost_10.0.10586.0_neutral_neutral_cw5n1h2txyewy</Data>
    <Data>App</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Microsoft-Windows-Immersive-Shell
Date:          6/2/2016 8:40:36 AM
Event ID:      5973
Task Category: (5973)
Level:         Error
Keywords:     
User:          GJ1_D10_7040\admin
Computer:      GJ1_D10_7040.cao30.lan
Description:
Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The app didn't start. See the Microsoft-Windows-TWinUI/Operational log for additional information.
Event Xml:
<Event xmlns="schemas.microsoft.com/.../event">
  <System>
    <Provider Name="Microsoft-Windows-Immersive-Shell" Guid="{315A8872-923E-4EA2-9889-33CD4754BF64}" />
    <EventID>5973</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>5973</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-02T12:40:36.328796400Z" />
    <EventRecordID>6262</EventRecordID>
    <Correlation />
    <Execution ProcessID="5048" ThreadID="5100" />
    <Channel>Application</Channel>
    <Computer>GJ1_D10_7040.cao30.lan</Computer>
    <Security UserID="S-1-5-21-257392508-3664685258-3270622264-1001" />
  </System>
  <EventData>
    <Data Name="AppId">Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI</Data>
    <Data Name="ErrorCode">-2144927141</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Microsoft-Windows-LoadPerf
Date:          6/2/2016 8:26:43 AM
Event ID:      3009
Task Category: None
Level:         Error
Keywords:     
User:          GJ1_D10_7040\admin
Computer:      GJ1_D10_7040.cao30.lan
Description:
Installing the performance counter strings for service WSearchIdxPi () failed. The first DWORD in the Data section contains the error code.
Event Xml:
<Event xmlns='schemas.microsoft.com/.../event'><System><Provider Name='Microsoft-Windows-LoadPerf' Guid='{122EE297-BB47-41AE-B265-1CA8D1886D40}'/><EventID>3009</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime='2016-06-02T12:26:43.495003500Z'/><EventRecordID>6183</EventRecordID><Correlation/><Execution ProcessID='4876' ThreadID='6440'/><Channel>Application</Channel><Computer>GJ1_D10_7040.cao30.lan</Computer><Security UserID='S-1-5-21-257392508-3664685258-3270622264-1001'/></System><UserData><EventXML xmlns='LoadPerf'><param1>WSearchIdxPi</param1><param2></param2><binaryDataSize>2</binaryDataSize><binaryData>9F0F</binaryData></EventXML></UserData></Event>


C:\Windows\Logs\CBS\CBS.log after sfc /scannow
2016-06-01 16:33:54, Info                  CSI    0000a7d8 [SR] Verify complete
2016-06-01 16:33:54, Info                  CSI    0000a7d9 [SR] Repairing 1 components
2016-06-01 16:33:54, Info                  CSI    0000a7da [SR] Beginning Verify and Repair transaction
2016-06-01 16:33:54, Info                  CSI    0000a7db Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-06-01 16:33:54, Info                  CSI    0000a7dc [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-06-01 16:33:54, Info                  CSI    0000a7dd@2016/6/1:20:33:54.041 Primitive installers committed for repair
2016-06-01 16:33:54, Info                  CSI    0000a7de Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-06-01 16:33:54, Info                  CSI    0000a7df [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-06-01 16:33:54, Info                  CSI    0000a7e0 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-06-01 16:33:54, Info                  CSI    0000a7e1 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-06-01 16:33:54, Info                  CSI    0000a7e2 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-06-01 16:33:54, Info                  CSI    0000a7e3 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-06-01 16:33:54, Info                  CSI    0000a7e4@2016/6/1:20:33:54.057 Primitive installers committed for repair
2016-06-01 16:33:54, Info                  CSI    0000a7e5 [SR] Repair complete
2016-06-01 16:33:54, Info                  CSI    0000a7e6 [SR] Committing transaction
2016-06-01 16:33:54, Info                  CSI    0000a7e7 Creating NT transaction (seq 3), objectname "(null)"
2016-06-01 16:33:54, Info                  CSI    0000a7e8 Created NT transaction (seq 3) result 0x00000000, handle @0x1d70
2016-06-01 16:33:54, Info                  CSI    0000a7e9@2016/6/1:20:33:54.072 Beginning NT transaction commit...
2016-06-01 16:33:54, Info                  CSI    0000a7ea@2016/6/1:20:33:54.182 CSI perf trace:
CSIPERF:TXCOMMIT;108426
2016-06-01 16:33:54, Info                  CSI    0000a7eb [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

2016-06-02 08:52:51, Info                  CSI    0000547c [SR] Verify complete
2016-06-02 08:52:51, Info                  CSI    0000547d [SR] Repairing 1 components
2016-06-02 08:52:51, Info                  CSI    0000547e [SR] Beginning Verify and Repair transaction
2016-06-02 08:52:51, Info                  CSI    0000547f Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-06-02 08:52:51, Info                  CSI    00005480 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-06-02 08:52:51, Info                  CSI    00005481@2016/6/2:12:52:51.308 Primitive installers committed for repair
2016-06-02 08:52:51, Info                  CSI    00005482 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-06-02 08:52:51, Info                  CSI    00005483 [SR] Cannot repair member file [l:10]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-06-02 08:52:51, Info                  CSI    00005484 [SR] This component was referenced by [l:125]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys"
2016-06-02 08:52:51, Info                  CSI    00005485 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-06-02 08:52:51, Info                  CSI    00005486 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 g2VAunZ6/2J1G3oL7kf9fjInPUA9VYeiJcl9VKgizaY=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-06-02 08:52:51, Info                  CSI    00005487 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-06-02 08:52:51, Info                  CSI    00005488@2016/6/2:12:52:51.339 Primitive installers committed for repair
2016-06-02 08:52:51, Info                  CSI    00005489 [SR] Repair complete
2016-06-02 08:52:51, Info                  CSI    0000548a [SR] Committing transaction
2016-06-02 08:52:51, Info                  CSI    0000548b Creating NT transaction (seq 2), objectname "(null)"
2016-06-02 08:52:51, Info                  CSI    0000548c Created NT transaction (seq 2) result 0x00000000, handle @0x440
2016-06-02 08:52:51, Info                  CSI    0000548d@2016/6/2:12:52:51.386 Beginning NT transaction commit...
2016-06-02 08:52:51, Info                  CSI    0000548e@2016/6/2:12:52:51.497 CSI perf trace:
CSIPERF:TXCOMMIT;102931
2016-06-02 08:52:51, Info                  CSI    0000548f [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

3 Replies
Zepfanman
1 Nickel

RE: How to fix left-click of Start Menu, taskbar icons, and search bar in Windows 10

Update: The problem appears to be related to some Group Policies we have on our domain. It's only when we add the machine to our work OU in Active Directory that the Start Menu problem begins. By the way, I failed to mention that Edge does not open, either, when we're having the Start Menu problem.

I'll post another reply when we find out which GP is the problem...

0 Kudos
saitohas
1 Copper

RE: How to fix left-click of Start Menu, taskbar icons, and search bar in Windows 10

News?

0 Kudos
tchristin
1 Copper

RE: How to fix left-click of Start Menu, taskbar icons, and search bar in Windows 10

Hi, check the Auditing object access policy in AD.

It must be not configured or no auditing to let the start menu work.

Reboot needed to apply change.

Cheers,

Tim.

0 Kudos