Classic Shell: Forum

If you can capture a crash dump as instructed here: viewtopic.php?f=12&t=6, the cause of the slowdown/hang or crash can be determined by inspecting the dump.

_________________
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 may have found the solution. You can create short cuts to explorer using certain codes. It's like the code for creating a short cut
for "God Mode" I had a short cut on my desktop, with one of those code going to Windows/Thispc/desktop.

This may have caused conflict with classic shell

This looks like the desktop is referencing itself, causing a infinitely deep nesting.
It should not cause a crash, but it might.

Which causes Explorer.exe to reload after the bad hang I need a answer on this !


Log Name: Microsoft-Windows-DeviceSetupManager/Admin
Source: Microsoft-Windows-DeviceSetupManager
Date: 2/3/2016 10:17:14 AM
Event ID: 131
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: WINDOWS-0B0FK46
Description:
Metadata staging failed, result={1C852A4D-B800-1F08-ABCD-D89D67D762F0} for container '0x80070490'

Log Name: System
Source: Virtual Disk Service
Date: 2/3/2016 10:16:02 AM
Event ID: 9
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WINDOWS-0B0FK46
Description:
Unexpected provider failure. Restarting the service may fix the problem. Error code: 8007001F@02000014


Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2/3/2016 10:50:49 AM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: WINDOWS-0B0FK46\johnlsenchak
Computer: WINDOWS-0B0FK46
Description:
The server {CEFF45EE-C862-41DE-AEE2-A022C81EDA92} did not register with DCOM within the required timeout.

Did removing the shortcut from the desktop fix the problem?

Have you tried capturing the crash dump as instructed in viewtopic.php?f=12&t=6. Try both ways: procdump -e Explorer.exe and if that doesn't capture it then the alternative way in the post below it.

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

Yes the shortcut was removed but apparently no on fixing the issue .It still might be the network share drives slowly down the opening of Explorer. I noticed a few times that the network shares (connected to the network port) take the longest to appear in Explorer which may be causing the time out. This then causes Explorer.exe to restart



I'm on a WIFI network right now, where the Network Shares are not connected via the network port


Usual if I don't open Explorer.exe for a long period of time, then click on it, the hang occurs

I still haven't ruled out uploading files to Facebook. The hang occurred just after uploading files via Chrome


Facebook is well known to cause issues with browsers.


I removed the shortcut but haven't rebooted the computer

Downloaded the program, but haven't done that yet. Can you tell me the benefits here of running that program

It will capture the state of Explorer when it crashes inside a dump file which you can upload here. The dump can be used to analyze and determine what causes the crash.

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

Okay, I have to find time to do that


I also have a network shortcut using "Folder (.{208D2C60-3AEA-1069-A2D7-08002B30309D})" which also could be the issue

Deleted

I just tried opening the File Explorer after some time and their was some lag, but it didn't hang, before removing the above


God mode codes
http://www.thewindowsclub.com/the-secre ... -7-godmode

That is quite likely to be the cause of the slowdown! The Network folder is best not added to the Start Menu as an expanding menu because it takes some time to populate PCs on the network. You could add it as a link that opens in Explorer.

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

Running whoscrashed dump program, I'll get back to you on this

Computer name: WINDOWS-0B0FK46
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: Inspiron 5720, Dell Inc. , 023HTX
CPU: GenuineIntel Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6292516864 bytes total

No dumps

Nothing yet , still have not recreated the hang after removing the network shortcut. You should post on the main site about this issue in the F.A.Q.

The CLSID that you mentioned {208D2C60-3AEA-1069-A2D7-08002B30309D} is the old Network folder which is known to cause Explorer to become unresponsive. It's not there by default in Classic Shell, you must've added it yourself.

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

Yes, it was added by me for easy access to my network share drives. Like I already stated , I thought it was the network drives that where hanging Windows 8.1 but in
actuality it maybe was the reverse via the short cut . This then caused the shortcut, to hang Classic Shell