Windows 10 Start Menu Icons inactive/unclickable on first logon.

[jmcdermott]

Not a question, just a quick statement because this issue has been causing me a headache for a little while now, and the answer did not seem to appear any where on the web.

 

Some background:

We are now using Windows 10 education.

We have a redirected start menu to a folder in netlogon.

Our students do not have roaming profiles.

 

The Issue:

When a student logs on to a workstation for the first time some start menu items are unclickable. If the student logs off then logs on again to the same workstation the issue goes away.

 

The Fix:

The issue seems to be with the default profile created on the my netlogon folder. Following instructions online I created my default profile and deleted the Appdata\Local and the Appdata\Locallow folders as they are not required normaly for windows to work, this was my error, windows seems to store a database for the start menu in a folder called AppData\Local\TileDataLayer\Database. Once I copied the the jrs files and jfm file and edb file from a working profile into the default profile folder structure the issue was fixed.

 

I am sure this will be of no interest to anyone but at least if it is out there it might help someone one day.

[KK20]

Ironically, I think this hasn't affected me because I stripped the default profile of ALL databases when I copied to netlogon - I figured that they are recreated on first logon anyway so why copy them across? I also strip the webcache, onedrive install - pretty much MOST of appdata/local (if the directory was over 5mb then I looked into it to see what it was) but I DIDNT strip the tiledatalayer and didn't delete everything.

 

Nice to see someone else has posted so we can piece together the mess that is default profile...

[jmcdermott]

Just to add an extra quick note

 

After a few days of this working I have noticed that a few windows 10 workstations Start Menu had stopped working completely, on closer inspection it seems all the faulty machines were an old build of the x86 version of windows 10, where as the database files I have used are from a x64 version, quick install of x64 version fixes the issue.

[Garacesh]

Ye olde necrobump, but did anyone ever find out anything about what causes this and how to prevent it?

 

We get it here occasionally with our staff, W10Ent x64 1511, start menu redirected to network share via GPO, local profiles.

Strangely never seems to happen with the kids. Or maybe I just never get told about it when it does..

 

A reboot always fixes it, but our users never seem to try that for some reason

[BOOT]

Tried running tdlrecover.exe?