This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have just built a fresh installation on LTSC 2019 and enabled the custom shell.
For users that should seen the "standard" Explorer desktop it instead loads File Explorer at Documents.
We have previously tested custom shell on LSC 2021 without issue.
What is the question?
How did you setup Shell Launcher?
There is a GUI and command line utilities that can show the setup of shell launcher: https://www.annabooks.com/SW_SLUtility.html. What are the results?
It seems a Windows Update "breaks" the behaviour. I am working my way through each monthly update, so far up to May 2022.
I know it is one of the updates in May to July 2022 when the behaviour first occurs. As I already tried an update fron August 2022.
Away for a couple of days, so not sure when I will get back to it.
What exactly is the issue?
The offending update appears to be
May 24, 2022—KB5014022 (OS Build 17763.2989) Preview
I am using a config similar to ShellLauncherSid.xml
After this updates users who previously were presented with the standard Windows desktop, after login, are now presented with 
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 30%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
It's a bug introduced with build 10.0.17763.2989 / KB5014022, since that time when explorer.exe is called via CustomShellHost.exe ( Shell Launcher v2 ) it's added during startup/logon phase the parameter "/NoShellRegistrationCheck", that's why you see just the explorer instead the desktop shell. They promise to fix that in a new build...
Thanks Ruben, you seem to have more knowledge of the issue.
Hopefully that can be resolved soon. Most of our existing devices are using Windows 10 IoT Enterprise LTSC 2019 (and likely to be using until at least 2029).
We are preparing to move production over to LTSC 2021, which doesn't have the problem, but won't be field upgrading existing devices from LTSC 2019.
Well,1809 is more or less End of Support, so they will only fix issues which are really security related...(in terms of the LTSC Support ), we have reported that close to a year back and never seen a real fix, we finally found some internal workaround, but I understand that it's annoying.
Used to being ignored, as the little guy. So the IoT and LTSC is a bit of a joke.
MS introduced a bug in a KB released after the End of Support; but have no obligation to fix it.