Issues with right clicking start menu.

Page 1 of 2 12 LastLast

  1. Posts : 17
    Win 10 pro
       #1

    Issues with right clicking start menu.


    Prior to upgrading to build 1511 a few days ago I could right click on the start menu and all the icons works. Could run as an administrator with no issue. However for the last few days clicking on any icon from the right click start menu does nothing. Level three at Microsoft has not found an answer. I have tried most of the fixes including running powershell and "getting app." to no avail.

    Any thoughts or suggestions?

    Thanks

    Bob
      My Computer


  2. Posts : 42,734
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hello, could you be a little more precise if possible...
    Prior to upgrading to 1511 (released last November) were you running Win 10? Or did you upgrade from Win 8 to build 1511?
    Just after upgrading to 1511, did rt click on the start menu work, and then stop?
    What is your current build level? (Open a command prompt, type Winver <return>)

    Did you install any programs around the time this happened?

    If you look at your update history, can you see any updates which were installed around the time this happened?

    Have you tried uninstalling those updates?

    What happens if you press the Windows key and X together?

    Please see this:
    Solved Start Menu button right click menu fails - Windows 10 Forums
    and advise if anything helps ro can provide further info.
      My Computers


  3. Posts : 17
    Win 10 pro
    Thread Starter
       #3

    I was running win 10 pro at the time. We, microsoft and I, could not do any updates. That was fixed with a change to the registry. There were no updates when that happened. There was a security update after the fact. Yes it partially worked and then stopped completely. I'm running sfc /scannow now.

    I did not install any programs nor to my knowledge were any updates installed for other programs.

    Build 10586.218

    I think I may have some other issues however. I did an install from a mounted iso file. Two hours ago scannow showed no integrity issues. Now it shows corrupt files that it can't fix. This is the third time for this same pattern. I've run Dism probably 30 times over the last week. it has only found the source files once. Using the same exact command and it won't find the source files.

    I'm old 77 and if I still had hair I'd pull it out. Level three has not been of much help

    fyi here is the dism command I'm running Dism /Online /cleanup-image /restorehealth /Source:wim:l:\sources\install.wim:1 /limitaccess

    This time, make that the 2nd out of 30 that it says it worked.

    Sorry to be screwing up my own thread but I ran scannow after Dism said it repaired the component store. Scannow reports that there are corrupt files that it can't fix.

    Does any part of win10 work?
      My Computer


  4. Posts : 42,734
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #4

    Thanks, sympathies.

    Here's the pattern I think see... correct me if the assumptions I've made are wrong.

    1. You were running build 10240
    2. Rt click start menu was then working (I assume)
    3. You had not been prompted to upgrade to 1511 - I assume that 'cos it seems you did that manually with an iso (I assume that's what the iso was for).
    4. That suggests that windows update had not been working up to then (possibly consistent with you saying Windows update did not work after upgrading to 1511).
    4a. rt clicking the start menu worked partially (? which means?)
    5. MS helped you fix Windows updates
    6. You have now received Windows updates and are up to date.

    Comments:
    SFC /Scannow can report failures for reasons to do with
    a. opencl.dll (Nvidia) - no problem. MS is supposed to be fixing this.
    b. some audio files
    Knowing whether SFC /Scannow has really really failed means scanning the CBS.LOG file - which should not be the case of course.

    What does Windows key + X do?

    From the thread I quoted note this - see instructions below:
    UPDATE: I have disabled all shell extensions except MS's and the menu now works. Next I will try to isolate the culprit.

    Thank you all for your comments. I will try them all if my current thought fails.

    FOLLOW UP: The problem was an old ShellExtension that wasn't compatible with Win10. I uninstalled it and the menu now works fine.

    Action
    Download Shellexview (free)
    Run it, hide all MS shell extensions.
    Disable all others
    Try rt clicking the start button

    Post the result.
      My Computers


  5. Posts : 17
    Win 10 pro
    Thread Starter
       #5

    Window K +x brings up the same menu that right clicking the windows key does. Clicking on the icons does nothing.

    Your assumptions

    1. I assume so, don't know
    2 Yes with no issues
    3 I had been prompted but because of the registry error the update told us that this machine could not run Windows 10. It already was
    4. Correct
    4A Yes control panel, taskmanager. That was about all
    5. yes
    6 yes

    With the last two installs from an iso file I'm getting most of my default files reset.

    Dism worked here about 5 minutes ago. I have not been rebooting. Should I be doing so?

    Thanks.
      My Computer


  6. Posts : 17
    Win 10 pro
    Thread Starter
       #6

    I don't know what this means or how to fix it. I post in the hopes that some of you do. Thanks Bob

    2016-05-06 14:28:18, Info CSI 000053bf Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_10.0.10586.122_none_84cfe03d038f5931\Windows Journal.lnk do not match actual file [l:19]"Windows Journal.lnk" :
    Found: {l:32 w39qCkJdOj5fkruH9r4Hcs0OtR4PiSqtB5oZZsKtUEU=} Expected: {l:32 MZg2KqMnHh+iyhodplgMB7y35LaRMt4yIz1PaJqPuwo=}
    2016-05-06 14:28:18, Info CSI 000053c0 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-05-06 14:28:18, Info CSI 000053c1@2016/5/6:20:28:18.209 Primitive installers committed for repair
    2016-05-06 14:28:18, Info CSI 000053c2 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_10.0.10586.122_none_84cfe03d038f5931\Windows Journal.lnk do not match actual file [l:19]"Windows Journal.lnk" :
    Found: {l:32 w39qCkJdOj5fkruH9r4Hcs0OtR4PiSqtB5oZZsKtUEU=} Expected: {l:32 MZg2KqMnHh+iyhodplgMB7y35LaRMt4yIz1PaJqPuwo=}
    2016-05-06 14:28:18, Info CSI 000053c3 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-05-06 14:28:18, Info CSI 000053c4 [SR] This component was referenced by [l:80]"Package_1683_for_KB3147458~31bf3856ad364e35~amd64~~10.0.1.4.3147458-3978_neutral"
    2016-05-06 14:28:18, Info CSI 000053c5 Hashes for file member \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC\Windows Journal.lnk do not match actual file [l:19]"Windows Journal.lnk" :
    Found: {l:32 w39qCkJdOj5fkruH9r4Hcs0OtR4PiSqtB5oZZsKtUEU=} Expected: {l:32 MZg2KqMnHh+iyhodplgMB7y35LaRMt4yIz1PaJqPuwo=}
    2016-05-06 14:28:18, Info CSI 000053c6 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_10.0.10586.122_none_84cfe03d038f5931\Windows Journal.lnk do not match actual file [l:19]"Windows Journal.lnk" :
    Found: {l:32 w39qCkJdOj5fkruH9r4Hcs0OtR4PiSqtB5oZZsKtUEU=} Expected: {l:32 MZg2KqMnHh+iyhodplgMB7y35LaRMt4yIz1PaJqPuwo=}
    2016-05-06 14:28:18, Info CSI 000053c7 [SR] Could not reproject corrupted file [l:78 ml:79]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC"\[l:19]"Windows Journal.lnk"; source file in store is also corrupted
    2016-05-06 14:28:18, Info CSI 000053c8@2016/5/6:20:28:18.332 Primitive installers committed for repair
    2016-05-06 14:28:18, Info CSI 000053c9 [SR] Repair complete
    201
      My Computer


  7. Posts : 42,734
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #7

    Hi, if those are the only fault reports in CBS.LOG, that appears to be about just one app. Are you sure there are no other occurrences of 'corrupt' or 'fail' - just search CBS.log using e.g. Notepad.

    And note this:
    Error sfc /scannow
    - could be another MS inconsistency they've created.
    I have a reference to it on my laptop; it appears under Windows accessories/Tablet-PC/ in my start menu - Windows Journal.

    Try what I suggested under 'Action'.

    If that doesn't help, then I would normally suggest an in-place upgrade repair install - which would seem a bit strange after having just done an upgrade.
      My Computers


  8. Posts : 18,424
    Windows 11 Pro
       #8

    Create a new local user account. Change the account type to administrator. Log into the newly created account. See if the problem exists in the new user account.
      My Computer


  9. Posts : 17
    Win 10 pro
    Thread Starter
       #9

    synergy1 said:
    I don't know what this means or how to fix it. I post in the hopes that some of you do. Thanks Bob

    2016-05-06 14:28:18, Info CSI 000053bf Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_10.0.10586.122_none_84cfe03d038f5931\Windows Journal.lnk do not match actual file [l:19]"Windows Journal.lnk" :
    Found: {l:32 w39qCkJdOj5fkruH9r4Hcs0OtR4PiSqtB5oZZsKtUEU=} Expected: {l:32 MZg2KqMnHh+iyhodplgMB7y35LaRMt4yIz1PaJqPuwo=}
    2016-05-06 14:28:18, Info CSI 000053c0 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-05-06 14:28:18, Info CSI 000053c1@2016/5/6:20:28:18.209 Primitive installers committed for repair
    2016-05-06 14:28:18, Info CSI 000053c2 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_10.0.10586.122_none_84cfe03d038f5931\Windows Journal.lnk do not match actual file [l:19]"Windows Journal.lnk" :
    Found: {l:32 w39qCkJdOj5fkruH9r4Hcs0OtR4PiSqtB5oZZsKtUEU=} Expected: {l:32 MZg2KqMnHh+iyhodplgMB7y35LaRMt4yIz1PaJqPuwo=}
    2016-05-06 14:28:18, Info CSI 000053c3 [SR] Cannot repair member file [l:19]"Windows Journal.lnk" of Microsoft-Windows-TabletPC-Journal, version 10.0.10586.122, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-05-06 14:28:18, Info CSI 000053c4 [SR] This component was referenced by [l:80]"Package_1683_for_KB3147458~31bf3856ad364e35~amd64~~10.0.1.4.3147458-3978_neutral"
    2016-05-06 14:28:18, Info CSI 000053c5 Hashes for file member \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC\Windows Journal.lnk do not match actual file [l:19]"Windows Journal.lnk" :
    Found: {l:32 w39qCkJdOj5fkruH9r4Hcs0OtR4PiSqtB5oZZsKtUEU=} Expected: {l:32 MZg2KqMnHh+iyhodplgMB7y35LaRMt4yIz1PaJqPuwo=}
    2016-05-06 14:28:18, Info CSI 000053c6 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_10.0.10586.122_none_84cfe03d038f5931\Windows Journal.lnk do not match actual file [l:19]"Windows Journal.lnk" :
    Found: {l:32 w39qCkJdOj5fkruH9r4Hcs0OtR4PiSqtB5oZZsKtUEU=} Expected: {l:32 MZg2KqMnHh+iyhodplgMB7y35LaRMt4yIz1PaJqPuwo=}
    2016-05-06 14:28:18, Info CSI 000053c7 [SR] Could not reproject corrupted file [l:78 ml:79]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Tablet PC"\[l:19]"Windows Journal.lnk"; source file in store is also corrupted
    2016-05-06 14:28:18, Info CSI 000053c8@2016/5/6:20:28:18.332 Primitive installers committed for repair
    2016-05-06 14:28:18, Info CSI 000053c9 [SR] Repair complete
    201
    I believe these are the only ones from this scan but I will check. If I find more do you want me to paste them here?
      My Computer


  10. Posts : 17
    Win 10 pro
    Thread Starter
       #10

    dalchina said:
    Thanks, sympathies.

    Here's the pattern I think see... correct me if the assumptions I've made are wrong.

    1. You were running build 10240
    2. Rt click start menu was then working (I assume)
    3. You had not been prompted to upgrade to 1511 - I assume that 'cos it seems you did that manually with an iso (I assume that's what the iso was for).
    4. That suggests that windows update had not been working up to then (possibly consistent with you saying Windows update did not work after upgrading to 1511).
    4a. rt clicking the start menu worked partially (? which means?)
    5. MS helped you fix Windows updates
    6. You have now received Windows updates and are up to date.

    Comments:
    SFC /Scannow can report failures for reasons to do with
    a. opencl.dll (Nvidia) - no problem. MS is supposed to be fixing this.
    b. some audio files
    Knowing whether SFC /Scannow has really really failed means scanning the CBS.LOG file - which should not be the case of course.

    What does Windows key + X do?

    From the thread I quoted note this - see instructions below:
    UPDATE: I have disabled all shell extensions except MS's and the menu now works. Next I will try to isolate the culprit.

    Thank you all for your comments. I will try them all if my current thought fails.

    FOLLOW UP: The problem was an old ShellExtension that wasn't compatible with Win10. I uninstalled it and the menu now works fine.

    Action
    Download Shellexview (free)
    Run it, hide all MS shell extensions.
    Disable all others
    Try rt clicking the start button

    Post the result.
    Ran as requested. Made no change
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:35.
Find Us




Windows 10 Forums