This is a weird and particularly annoying problem.

In the past 2 weeks, we’ve had a number of users report that the Start Menu is not working (read: i click on the start button and it does nothing) all across the school. We are running Windows 10 Education and have a mix of 1607 and 1703. Roaming Profiles are not in use, we just redirect folders instead.

Now I’ve managed to establish that it only affects users that have not signed into that computer before. Users who have signed onto that machine before seem to work as normal. I’ve also determined that the problem has something to do with Shell Experience Host as it appears to be missing on problematic accounts.The error i see in the logs is:

Faulting application name:ShellExperienceHost.exe, version 10.0.15063.0 time stamp 0x58ccbd2e
Faulting module name: twinapi.appcore.dll, version: 10.0.15063, time stamp: 0x2f0c1b3c
Exception code: 0xc000027b

As is it affecting so many users (who also have linked email accounts) and as many computers, blowing away and recreating isn’t a viable option. Has anyone seen behavior similar to this and if so how did you fix?

Additional Information:
DC’s - 2016 & 2X 2012R2
SCCM - 1606. SUP installed.
~300PC’s all running Windows 10 1607 or 1703
Mix of Wireless Laptops and Wired Desktops

I would take a look at this fix (was for the TP so I don’t know how relevant it still is) and try doing a sfc scan.

Otherwise, the faulting module appears to be part of the UWP API. Are you using and Remote Apps or having any of the default UWP apps running? There’s not a lot else to go on with just that error.