Classic Shell: Forum

Hey, first up, thanks for Classic Start Menu. It's fabulous!

We having been running it from an early date with much success, but recently i've noticed delays in the start menu popping up. Sometimes as much as 30 seconds from clicking.

Whilst i suspect it's a network issue rather than a bug in classic start menu, i don't know how to troubleshoot the dmp files generated by procdump.

Would someone be able to either take a look or give me some guidance to take a look myself? (I tried opening in VS Express, but that just lists DLL's).

I uploaded the zip file to your mediafire location with a name starting "bodger".

Environment is:
Classic Start Menu 4.3.0
Windows 10 Edu x64 (v1607)
Network installation with multiple DC's, DNS etc.

We have done some server work recently, so i'm hoping it's some reference to an old dc (as i saw in another post), but i can't work out how to get more info out of the dmp files!

Thanks in advance!

Matt

The slowdown seems to be caused by the file C:\Program Files (x86)\NSL\NSCommonHook64.dll.
It is probably trying to access a network location and waiting for a response.
Possibly related to the user profile being on a remote machine.

Hey Ivo,

Thanks for the response and appologies for taking a while to come back. The DLL in question is part of a management suite called NetSupport which was a reasonable candidate for causing the slowdown, but i've since taken it off my machine (a different PC to the one i used in the last test) and i'm still getting a noticeable pause when loading Classic Start Menu.

The pause is not experienced when loading the regular start menu (via shift / start).


Appdata is based on server, but LocalAppdata is not redirected (and remains local)... Network is enterprise level with 10Gbps between switches and 1Gbps. It normally servers 500+ simultaneous users, but today, just about 30 as it's a training day, so high spec, low use.

Any further advice with the new logs available here?
New logs: https://drive.google.com/open?id=0B5lh1 ... V9UTWF0R1k
The start menu click was between logfile 1 and 2 (possibly 3).


Thanks again for your time here, would love to get this nailed down!

Cheers,
Matt

In this case the menu is trying to get the timestamp for a shortcut in the start menu to see if it has changed. That shortcut is probably on a remote machine.
See if disabling the settings "Highlight newly installed programs" makes a difference for you.

Thanks again for the advice on this Ivo.

Rather than disable the "Highlight newly installed programs", i figured i'd take the opportunity to do a bit of an audit. There were 6 or 7 old windows 8 shortcuts being distributed which no longer pointed to valid exe's (running from a mixture of local and server shares).

Removing these appears to have solved it.

Tested both machines and accounts from this thread and it appears to be much more responsive! (even with NetSupport running).

Cheers very much for getting me on the right track!
Matt

Can you ZIP those shortcut files and upload them here so Ivo can take a look what kind of shortcuts? Dead shortcuts causing Start Menu slowdown means there is a problem.

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