none
Windows 10 Start Menu Broken RRS feed

  • Question

  • Hello hopefully someone call help me.

    Problem:

    Windows 10 LTSB - I image a machine and it is added to the domain with no group policies.

    The start menu now no longer allows left click, only right click.

    It does the same under the local administrator account.

    It would imply a computer group policy is at fault.

    However if I move the object to the computers container that has no policies linked it does the same.

    This happens to every machine consistantly.

    It is almost identical to the problem listed here

    https://social.technet.microsoft.com/Forums/en-US/764d3fec-a7f4-4108-9dce-c0a8b6ed734f/after-windows-10-build-10240-installation-start-menu-taskbar-ms-settings-not-working-and-some?forum=win10itprosetup

    I feel like from what I have read, this command should solve it:

    Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

    However when I run this I do not get a series of processing strings, it just drops to the next line for a further command input and notihing is written to the eventlogs, if I put the wrong syntax in on purpose it complains....

    This is a local admin command windows ran as administrator with powershell typed before hand.

    Other steps Tried:

    Removed my anti-virus

    Ensured the firewall service is running and it is turned on for domains

    Ran the windows start menu repair tool, which advises me that "microsoft.windows.shellexperiencehost and microsoft.windows.cortana applications need to be installed correctly"
    This could be because I am on Windows LTSB and it is expecitng a different version because LTSB does not have cortana ?
    Tried Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “\appxmetadata\appxbundlemanifest.xml”)}

    Application identity service is started

    No plugins are present to renamed using ren %windir%\System32\AppLocker\Plugin*.* *.bak

    sfc /scannow results in two files it can not repair:

    1)


    2016-07-28 10:24:49, Info                  CSI    00002d7c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft.secureboot.commands_31bf3856ad364e35_10.0.10240.16384_none_403a7ad0be73724c\SecureBoot.psd1 do not match actual file [l:30{15}]"SecureBoot.psd1" :
      Found: {l:32 b:YWau4NnklUW5jmmmg4hWPlwi5hQY4Za36qJrJVn7TW4=} Expected: {l:32 b:6ZX9lf8ZOhwvGQXeS6039CpLdi6PYjngUHMOKLPtUwg=}
    2016-07-28 10:24:49, Info                  CSI    00002d7d [SR] Cannot repair member file [l:30{15}]"SecureBoot.psd1" of Microsoft.SecureBoot.Commands, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-07-28 10:24:49, Info                  CSI    00002d7e [SR] This component was referenced by [l:334{167}]"Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-Package-AutoMerged-base-Deployment"
    2016-07-28 10:24:49, Info                  CSI    00002d7f Hashes for file member \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\SecureBoot\SecureBoot.psd1 do not match actual file [l:30{15}]"SecureBoot.psd1" :
      Found: {l:32 b:YWau4NnklUW5jmmmg4hWPlwi5hQY4Za36qJrJVn7TW4=} Expected: {l:32 b:6ZX9lf8ZOhwvGQXeS6039CpLdi6PYjngUHMOKLPtUwg=}
    2016-07-28 10:24:49, Info                  CSI    00002d80 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft.secureboot.commands_31bf3856ad364e35_10.0.10240.16384_none_403a7ad0be73724c\SecureBoot.psd1 do not match actual file [l:30{15}]"SecureBoot.psd1" :
      Found: {l:32 b:YWau4NnklUW5jmmmg4hWPlwi5hQY4Za36qJrJVn7TW4=} Expected: {l:32 b:6ZX9lf8ZOhwvGQXeS6039CpLdi6PYjngUHMOKLPtUwg=}
    2016-07-28 10:24:49, Info                  CSI    00002d81 [SR] Could not reproject corrupted file [ml:132{66},l:130{65}]"\??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\SecureBoot"\[l:30{15}]"SecureBoot.psd1"; source file in store is also corrupted

    2)

    016-07-28 10:27:38, Info                  CSI    000051eb [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2016-07-28 10:27:38, Info                  CSI    000051ec [SR] This component was referenced by [l:258{129}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.RemoteFX clientVM and UMTS files and regkeys"
    2016-07-28 10:27:39, Info                  CSI    000051ed Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:aUERXVKSAEJD5gSpXsaCAkjG9qYxmG88cuMbCteoVog=} Expected: {l:32 b:3nQy34XEqrcTm+le3PyhNMbyrGuxiT2D5+L7RJQKKgM=}
    2016-07-28 10:27:39, Info                  CSI    000051ee Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10240.16384_none_b928dea146e73395\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:aUERXVKSAEJD5gSpXsaCAkjG9qYxmG88cuMbCteoVog=} Expected: {l:32 b:3nQy34XEqrcTm+le3PyhNMbyrGuxiT2D5+L7RJQKKgM=}
    2016-07-28 10:27:39, Info                  CSI    000051ef [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted


    I am not sure if these are related and if they are how they can be repaired.


    These articles are others I have referenced:

    http://www.urtech.ca/2016/06/solved-fix-windows-10-start-button-problems-with-start-menu-repair-tool/
    http://www.urtech.ca/2015/05/solved-windows-10-start-menu-and-modern-apps-do-not-function/
    https://social.technet.microsoft.com/Forums/en-US/8b263e44-3e18-4025-a47c-b2e990f3c9ab/windows-10-start-menu-problem-after-joining-domain?forum=win10itprosetup


    Tried fully updating with MS updates but I cant get to settings due to menu being unavailable on left click.

    Tried to run "start ms-settings:windowsupdate" and it results in a install failed. please contact your software vendor. message followed by an access is denied from the command line once clicking ok (exactly the same as the other guy reports with his problem)

    Thursday, July 28, 2016 10:16 AM

Answers

  • Hello,

    The solution was I had no package app rules in applocker.

    Once they where created the start menu worked OK

    When I was denying the applocker policy it did not seem to remove the enforcement of it.

    Only through building a machine with no policys and adding allow on each policy at a time could I see it was applocker

    Because my estate is still mainly 2008 servers I missed that packaged app rules was a new section only viewable on 2012 server to amend.

    • Marked as answer by Mikey-Gee Thursday, August 11, 2016 12:19 PM
    Thursday, August 11, 2016 12:19 PM

All replies

  • Hi,

    It seems that this issue is related to permission.

    We need to try following tool to find the root cause:

    Process Monitor v3.05
    http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

    Find the access denied errors and try to fix them:

    Solving Access Denied Errors Using Process Monitor
    http://improve.dk/solving-access-denied-errors-using-process-monitor/


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Sunday, July 31, 2016 3:58 PM
    Owner
  • Hi, 

    Was your issue resolved? 

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 5, 2016 8:10 AM
    Owner
  • Hello,

    The solution was I had no package app rules in applocker.

    Once they where created the start menu worked OK

    When I was denying the applocker policy it did not seem to remove the enforcement of it.

    Only through building a machine with no policys and adding allow on each policy at a time could I see it was applocker

    Because my estate is still mainly 2008 servers I missed that packaged app rules was a new section only viewable on 2012 server to amend.

    • Marked as answer by Mikey-Gee Thursday, August 11, 2016 12:19 PM
    Thursday, August 11, 2016 12:19 PM