My feeling is no. That's a byproduct of first-time logon.
Whenever I play around with Desktop settings that require a logout to take effect, and instead do:
taskkill /f /im explorer.exe && start explorer
Every few instances, or every time if you've modified specific reg keys, StartMenuExperienceHost will magically open.
What I believe is happening: Windows has to start Explorer first, otherwise you have no desktop. But it must add other first-time settings which require waiting for something else. So it restarts the desktop, and Start Menu appears.
Thanks for the quick reply, got around this by writing a small python code to add a restart into the RunOnce registry after the initial login. It reboots twice but got the job done
That's a restriction for NETBIOS compatibility. If you don't care about it, 63 characters is the limit.
But network shares will truncate the host path to the first 15 characters.
I'm sure it's possible to add an override to NTLCompName.vbs, where you have to acknowledge your reckless abandon.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.