Classic Shell: Forum

Hello,

I have implemented Classic Start Menu on a Windows Server 2016 Terminal Server.
Classic Start Menu has been setup through Group Policy. (ADMX-Template)

I start a session through RDP and as soon as the session is loaded and I have control, I click the start-button and the start menu opens.
I think there are still some windows logon tasks running, which take over the focus, and the start menu closes. I have to press the start-button again and the start menu opens.
Again some tasks are running and the start menu closes. After some seconds everything is loaded and then everything is fine.

I think this is normal behavior and everybody has this issue, but I still wanted to ask, if there is a possibility to improve the user experience?

Thank you

If the remote computer has many tasks set to run at logon or startup, I think it's normal if some of them are stealing focus as you just log in to your session. Just wait for a few seconds.

If you can identify which apps or tasks are doing this and they are not necessary, you can disable them. SysInternals AutoRuns would be the best tool to show you everything in detail: https://docs.microsoft.com/en-us/sysint ... s/autoruns

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and did Classic Shell's testing and usability/UX feedback.

Hello,

thank you for the answer.

Well, I know that.
I thought about settings like:

- Auto-start delay (http://getadmx.com/?Category=ClassicShell&Policy=IvoSoft.Policies.ClassicStartMenu::CSM_AutoStartDelay&Language=en-en)
- Delay loading of icons (http://getadmx.com/?Category=ClassicShell&Policy=IvoSoft.Policies.ClassicStartMenu::CSM_DelayIcons&Language=en-en)

I wanted to know, if they would be suitable for the mentioned issue.
Perhaps anybody could share some experience.

At least the delevoper should know, why he has implemented these settings ...

Thank you