Dear Shiv,
Launching explorer.exe from within a custom shell no longer restores the full desktop experience (taskbar, Start menu, desktop icons). Instead, it opens a standalone File Explorer window. This behavior is expected in Shell Launcher environments, as the system suppresses the standard shell components unless explicitly configured otherwise.
Here are Recommended approach:
To temporarily switch back to the full Windows shell experience, you’ll need to programmatically change the shell back to explorer.exe and restart the user session. Here’s how you can approach it:
- Use Shell Launcher APIs or PowerShell to switch shell You can use
Set-AssignedAccessor Shell Launcher v2 configuration to reassign the shell toexplorer.exe. - Trigger a logoff/logon cycle After changing the shell, the user session must be restarted for the change to take effect. This can be done via script or user prompt.
- Design your “Run Windows” option to automate this flow
- Behind the scenes, your app can: Update the shell assignment to
explorer.exePrompt the user to save work Log off the session Upon next login, the full Windows shell will be active
- Behind the scenes, your app can: Update the shell assignment to
Simply launching explorer.exe from within a custom shell won’t restore the full desktop environment, as the system doesn’t treat it as the shell unless it’s assigned at session start.
If this guidance proves helpful, feel free to click “Accept Answer” so we know we’re heading in the right direction 😊. And of course, I’m here if you need further clarification or support. T&B, Domic Vo