Start Menu Greyed out

[Tillthewheelsfalloff]

Hi!

We're having an issue with the Start Menu where upon first opening it's completely grayed out, the users can't click on anything. However, if you close the Start Menu and re-open it, it works OK.

We have Windows 10 1803 machines, on a domain. The main start menu is done via redirect and the tiles are set from an XML file on GPO. I've tried changing some of the GPO's on that section but nothing seems to have worked and I don't want to play around too much as I'm still fairly new to Group Policy.

Has anybody had this or a similar issue before?

Thank you,

Alex

[jthompson]

We have that is the Cortana search executable is restricted from running by SRP/AppLocker. When your Start menu is no longer greyed out, does any searching work (results appearing when typing)?

[Tillthewheelsfalloff]

No, it doesn't. How would I change this?

 

Although, we are a school so we want Cortana disabled, can we do this and still have the Start Menu working okay?

[Arthur]

we are a school so we want Cortana disabled, can we do this and still have the Start Menu working okay?

Disable Cortana through Group Policy instead of AppLocker/SRP.

 

https://gpsearch.azurewebsites.net/#10992

[Tillthewheelsfalloff]

How would I check if its blocked via Applocker/SRP? I've not dealt with that in the past.

Thank you!

[jthompson]

The Group Policy option to disable Cortana will turn off the digital assistant features and web searches, but the basic local search functionality will remain in place, surfacing apps and local files just like pre-Cortana editions of Windows did. Disabling that involves blocking the execution of a particular exe file within the Cortana app, which in turn creates the greyed out Start menu behaviour.

 

I don't know if there's anything else that might cause the same behaviour. If you look in the Event Viewer, you can see if it's the search exe is being blocked. Would need to look up the details of what to check for.

[mrwoberts]

we want Cortana disabled

 

Do you know how it got disabled in the first place? Was it through GPO, or baked into the initial image?

 

With my initial tweaking around with Windows 10 I stopped the Cortana app being provisioned for each new user, but that rather smug look on my face as the boot time decreased soon disappeared when I had the same 'two click start menu' effect. As a fun little project I actually created a Autohotkey app that would do the double clicking for you as soon as you logged in - the automation was often unnoticeable, but I just lumped with having Cortana provisioned and disabled it through GPO (as above). Shame Microsoft don't give us more granular controls over what is/isn't installed for new users; I'm sure we could half our login times

[Arthur]

the basic local search functionality will remain in place, surfacing apps and local files just like pre-Cortana editions of Windows did.

Surely not an issue if users do not have the rights to access apps and files they shouldn't?

[jthompson]

Surely not an issue if users do not have the rights to access apps and files they shouldn't?

 

This is certainly true, but it's been discussed in other threads and those who fully block search are also doing it as a way to prevent things going on on screen that might be interpreted by teaching staff as misuse (i.e. for a quieter helpdesk). So more about UX than security, I suppose you could say.

[Tillthewheelsfalloff]

Do you know how it got disabled in the first place?

 

Sadly not, we had some people in who set up the image for us but they haven't left very good documentation and we've struggled to get back in contact with them. It looks as though it was built into the original image.

How would I go about creating the double click Autohotkey app if I can't get this fixed?

[jthompson]

Scripting a coupl of Ctrl+Esc keystrokes would simulate opening then closing the Start menu. We found that timing was difficult to work out for that, though. It's easy to go too early, and too quickly, during login. THe later you leave it, the more likely users will be trying to use the Start menu by then anyway.

[mrwoberts]

How would I go about creating the double click Autohotkey app if I can't get this fixed?

 

Install the Autohotkey tool, then your script can be as basic as the following, which just simulates the (CTRL)+(ESC) keys pressed twice

 

#NoTrayIcon
Send ^{Esc}
Sleep 50
Send ^{Esc}

 

Convert that to an exe, place it in the (default profile, or programdata) startup folder and you're good to go. Just try it out first.

Edited November 5, 2018 by mrwoberts

[mrwoberts]

Interestingly, this can be done with VB Script with similar code - no need for autohotkey, just create your .vbs file with these lines...

 

Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.SendKeys "^{ESCAPE}"
WScript.Sleep 100
WshShell.SendKeys "^{ESCAPE}"

[Warwick_Tech]

We never found a fix for this, but you're all right it is caused by Cortana in Applocker - The GPO we found does little to disable Cortana's 'search' function which gives them access to a host of 'features'

 

Another school created GPO's to lock these down, but I don't know how far they ever got with it - Until such time as we have a proper fix I just get them to open the menu twice, it soon becomes second nature; Unless anyone has a fix now?

 

Regards,

[HelpImAnAdmin]

Hi all, my 2 cents towards this. I have been playing with this for a week or so now. I first tried 1803 and blocked cortana via app locker. This seemed to work except for the double click nuisance. After deployment to machines I had the full screen greyed out issue ( you can navigate via tab key though if you have noticed )

My tinkering with applocker eventually broke my test machine which would eventually not even boot. I have now gone to Windows 10 2019 LTSC which strips all the apps and used user based SRP to block Cortana & the security center notification ( you can use GPO to hide a lot of the security center )

This "so far" has seemed to work on 2 test machines.. We need search function disabled as students can browse UNC paths although NTFS permissions will deny them but I do not like the fact that they can browse SYSVOL and attempt to make a connection to servers by just typing in \\hostname and run System32 commands from the search ( e.g gpupdate , cscript ) although access to the C drive is blocked via other GPO.

I may further this by using SRP to disallow most system32 commands as the old create a shortcut hack is still viable for the kids who know what they are doing..

[Garacesh]

Interestingly, this can be done with VB Script with similar code - no need for autohotkey, just create your .vbs file with these lines...

 

Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.SendKeys "^{ESCAPE}"
WScript.Sleep 100
WshShell.SendKeys "^{ESCAPE}"

 

Doesn't seem to be doing anything for me..

 

I've tried both pointing the logon GPO directly at the script, and also using WSCRIPT.EXE with parameters \\...\netlogon\flickerstartmenu.vbs, neither works, first manual open is always grey.

_{Also sorry for necrobump}

 

Still, seems like a bit of a kludge.. Is there no other way to ditch Cortana/SearchUI that doesn't trigger this? Any way to strip it from the .wim, for example?

Edited April 29, 2019 by Garacesh

[Arthur]

Is there no other way to ditch Cortana/SearchUI that doesn't trigger this?

In theory the Start Menu shouldn't turn grey in Windows 10 v1903 since it's now in its own process (StartMenuExperienceHost.exe) which never gets suspended.

 

 

https://blogs.windows.com/windowsexperience/2019/01/16/announcing-windows-10-insider-preview-build-18317

 

The next step in improving Start reliability

As some of you may already know, up until now Start in Windows 10 has been hosted by something called ShellExperienceHost.exe. In order to provide you the best possible Start experience, we’re separating it into its own process, called StartMenuExperienceHost.exe. This has a number of benefits, including simplifying debugging and insulating Start from potential issues impacting other surfaces. This has been running as an experiment for a few weeks now and we’ve seen measurable improvements in the reliability amongst those that have the change, so we’re rolling it out to everyone.

 

We’re also making a change so that Start no longer suspends, which improves launch time.

[Garacesh]

In theory the Start Menu shouldn't turn grey in Windows 10 v1903 since it's now in its own process (StartMenuExperienceHost.exe) which never gets suspended.

 

 

https://blogs.windows.com/windowsexperience/2019/01/16/announcing-windows-10-insider-preview-build-18317

 

Bummer..

LTSC 2019, which is based on 1809

Maybe it's time for me to give Edu a try.

[itdoesthatsometimes]

Hi Guys,

 

1903 fixes this issue for me ....

 

I just upgraded from Ent 1809 to 1903 and the start menu works from first click. I understand that 1903 start menu has its own process now, so hopefully might be more reliable????....

 

I cant find the new 1903 policy definitions yet, but so far I haven't had any problems (with any of it...........................................................................Y.... E....T..!)

 

And i'm off for two weeks from today ... yipee