Classic Shell: Forum

I confirm that this issue exist and I don't have any files linked to a network address. Everything is handled locally.

Please capture a crash dump when it stops working as per these instructions: viewtopic.php?f=12&t=6

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

I see that this issue has been reported over and over. While I'm not going to take the time to create crash dumps and count threads like other have already done, I am going to add my experience in hope that it helps.

I have been using Classicshell since the first time I setup a Windows 8 PC. I have used it countless times for Windows 8, 8.1 and Server 2012. It works flawlessly in those instances. Recently I have done 3 or 4 network installs and upgrades. Server 2016 and Windows 10 are the typical installs. Using Classicshell on all of them results in the same experience. Server 2016 has explorer lockup and crashing issues. All the new workstations with Windows 10 and Classicshell also experience the same. This is on all users and servers regardless of installation process, new or upgraded systems.

Classicshell is a life saver but I'm being forced to look at alternative programs now due to the problems explained in this thread. I hope the powers at be figure it out and fix it as this is the most advanced shell program and I hate having to abandon it for a less capable program. Thanks and I look forward to the next version that address this.

There are countless reasons for Explorer to crash or stop working. As such, every crash dump helps.