Classic Shell: Forum

We have recently rolled out 6 RDServers to one of our clients, as they have moved on to a full TS solution. These servers are running Windows 2012R2, and have Classic Shell installed to simulate a startmenu, instead of the metro screen.

Since migrating everyone on to these servers, we have found a real slowness in Classic Shell opening the startmenu when clicked - this can take between 5seconds and 30seconds.

I ran a procdump while testing this slowness (files attached), and had a long freeze up between the last 4-5 dump files.

My inkling tells me this could be down to looking for the location of certain libraries, as they are all handled by folder redirection, but there is a 10GB link between the servers and the storage, so I would really hope that is enough to handle it.

Would really appriciate some help on this one!

Thanks in advance.

I don't see anything happening in those dumps. The main Explorer thread and the Classic Shell worker threads are doing nothing at the time. They are just waiting for user action.
Maybe the dumps are not captured at the right time? Or maybe the slowdown is not related to the start menu?
You can try using Process Monitor to see what files or registry keys are being accessed by Explorer during that time. Also make sure you close all Explorer windows to reduce the noise.

Is it possible that your entire appdata folder (%username%\Appdata, not %appdata%) is redirected using folder redirection?

_________________
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.