Classic Shell: Forum

I restarted my machine and I started in the W8 Start screen. I could not click on anything. I have dual monitors. My second monitor showed the task bar. Hovering over this taskbar I got the busy pointer. Clicking on it I got the message that Windows is not responding so I ended it. I was then thrown to the desktop after a few seconds.

Don't know if it's a dual monitor problem or not at this point.


**** this is pretty bad. Doesn't appear to be related to dual monitors.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

Does it happen for every reboot or it happened only once? Open Classic Start Menu settings. On the General Behavior tab, uncheck 'Start automatically for this user'. This will not start the menu when you log in. See if the hanging goes away after doing this. That will confirm if the hanging is being cause by Classic Shell or something else. Then you can turn it on again and prepare a dump.

Also, note that is why this is a beta so please bear with bugs.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

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

It would be great if I can get a crash dump. Get the "procdump" software as shown here: viewtopic.php?f=12&t=6

Reboot so it freezes again. Press Ctrl+Alt+Del and run Task Manager. From there go to File, Run. Enter "cmd". When the command prompt shows up navigate to the procdump location and enter the command "procdump explorer.exe". This should produce a DMP file in the same directory. Do this a couple of times, zip the crash dumps and attach them here.

It appears so far that this problem only happens on a restart of Windows. A complete shutdown of my rig and then a power up works as expected so far.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

It would still be great if you can capture a dump. I have to find out where exactly it is hanging.
Do you have any other start menu software that might interfere?

I have ModernMix.

***** I disabled MM and still had the problem with CSM. I can't get Procdump to run. I guess things are too frozen. All I can do is click on my second monitors taskbar which will give me the message to kill Windows. Once I do that CSM comes to life.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

Does pressing Ctrl+Alt+Del do anything?

it will bring up the menu to run Task Manager. Interestingly I have to had run TM on my second monitor before I do this otherwise the menu doesn't appear. When I run CMD I don't get a DOS box even though I see CMD in TM. Procdump is also in TM but doesn't produce any dump file.

I had to run Procdump from TM's Run option.

Bottom line is no dump.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

I thought the problem might be related to using Faststart. So I deleted my Hibernate file which in affect disables FastStart. Now A power off/power on doesn't work either.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

FWIW, I ran 3.9 on a W8 VM x64 Pro using Vbox and I had no problems.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

It may be possible that the CMD window is behind the Metro screen. See if using Win+arrows will bring it to the other monitor. You can also try blindly typing the command, but you have to be in the right directory with procdump first...

As a last resort you can right-click on Explorer and save a crash dump from there. However those are pretty big. You will have to use some file sharing service to upload it.

To get you unstuck, we can try few things in this order:
1) See if you can run regedit from the Task Manager. If so, go to HKEY_CURRENT_USER\Software\IvoSoft\ClassicStartMenu\Settings and create a new DWORD called "AutoStart". Set it to 0. This should hopefully prevent the auto-start of the menu and let you log in. You can then manually run the start menu by running ClassicStartMenu.exe

2) Run regedit and go to HKCR\CLSID\{ECD4FC4D-521C-11D0-B792-00A0C90312E1}. Rename the sub-key "TreatAs" to something else, like "TreatAs1". Reboot and see of that helps.

3) See if you can launch the installer from the Task Manager. Locate the installer and run it. Select Remove. Hopefully this will uninstall Classic Shell and bring your system back into usable state.

There must be something unique on your system, also judging by your other problem with highlighting. We need to figure out what this is.

From msconfig I set the option to do a Diagnostic Startup and restarted my machine. The problem in this post went away as did the Apps entry always being highlighted. It was highlighted until I ran one of the Apps.

At first I disabled all my non-MS start ups and services. That did not work. The Diagnostic Startup disables MS services and drivers so the problem might be with something MS.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

Is this reversible? If you turn on back "Normal Startup" does the problem come back?
It will be greatly useful to identify the real cause, in case other people experience the same problem.

If you can reproduce it again I will make another build with more logging to pinpoint the part that's failing. However the most useful thing will still be if you can manage to get a dump when Explorer is frozen. I thought of another possible way to run procdump. Put procdump.exe in some easy to find location (like C:\). Create a batch file in the same place that runs "procdump explorer.exe". Run the batch file to make sure it creates a .dmp file correctly. Then you will be able to easily run the batch file from Task Manager if Explorer freezes.

It appears that the problem is caused by Oracle VirtualBox. Specifically the driver \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys.

Disabling this driver of the 4 Vbox drivers fixes the problem. Unfortunately with this driver disabled I have no Internet connection on my machine. I uninstalled VBox and no more problem.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

Great catch! Just to make sure I understand - this is a driver installed on the host machine, not in the VM, right?
Is the host 32-bit or 64-bit? What version of VBox are you using? I will try to repro.

Yes, the driver is on the host machine. Host is W8 Pro 64-bit.

Vbox version is the latest:
April 12th, 2013
VirtualBox 4.2.12

I think when you install VBox it might have an option regarding the network that will install this driver. It's a bridge between host and VM i BELIEVE.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

Well happened to me too. Win8 x64 Professional. I had StartIsBack before Classic Shell, but I completely uninstalled that before installing CS 4.0.
1. I installed Classic Shell 4.0 beta.
2. I've shutdown my laptop.
3. I turned on my laptop.
4. The loading of Windows hang and I could only see the coloured background (the one I chose when installing Windows 8). Ctrl+Alt+Delete and Alt+Tab worked, sort of, but I couldn't see the Task manager's window.
5. I forced shutdown and turned it on again.
6. Now it works.

@lostprophet, you didn't say if you also have VirtualBox installed. You have it installed, right?

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

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

I installed VirtualBox 4.2.12 on Windows 8 Pro 64-bit, but was unable to reproduce the problem. My Windows restarts and shuts down just fine.

Do you mind installing Vbox again to see if the problem reoccurs? If it does, use the Task Manager's Browse button to get to the Classic Shell folder and rename ClassicStartMenu.exe to something else (like ClassicStartMenu2.exe). Reboot and see if Explorer will start this time. Basically launching the start menu has two stages and I'm trying to figure out which one is the problem. Renaming the exe will disable the second stage.

I reinstalled Vbox with all features and have the problem again. I renamed the file to ClassicStartMenu2.exe and rebooted. Everything worked OK except for the fact that there is no CSM start menu.

btw... where the heck do you autostart CSM from? I can't find it in the usual places. Did you use some trickery?

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

Yes, it uses trickery.
However looks like that's not the problem, because the first stage seems to be working for you.

Maybe the problem is the new way I am skipping the metro screen. Other people are having problems with it too: viewtopic.php?f=19&t=772
Try disabling that option and see if rebooting works (rename the exe back of course)

If it still doesn't work, uncheck "Start automatically for this user" and for now launch the start menu manually (just run ClassicStartMenu.exe).

At the moment you are the only one that can reliably reproduce this problem. I would appreciate it if you keep the current state of that machine until we find a solution. I will make a new build in the next 2 days that has more logging and some changes to hopefully fix this.

Skipping the Metro screen didn't work. As a pseudo workaround I placed a shortcut to CSM in my startup folder. Now when I start my machine I get the Metro start screen. Clicking on my Desktop tile I get thrown into the desktop and CSM starts up.

I'll keep Vbox on my system until we fix this. I just discovered Hyper-V and might use that instead of Vbox if it suits my needs.

**** Found a better temporary solution. In addition to adding CSM to my startup folder I ran SkipMetroSuiteUI to bypass the Metro screen. This works fine although CSM takes a little longer to startup compared to how you do it.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

Actually at the moment I'm just shooting in the dark. I have no clue what might be happening.

What would really help narrow down the problem is a crash dump. Can you please try to get procdump to work one more time? Like create a batch file that runs "procdump explorer.exe" and that you can launch from the Task Manager while Explorer is frozen.

As a last resort you can create a dump directly from TaskManager. Right-click on the explorer.exe process and select "Create dump file". These files are big but usually compress about 2:1. If you don't have a place where you can upload it (like dropbox) I will figure something out later. At the moment it is important to create the dump file while the problem is still happening.

Got a dump for you!

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

This was very helpful, thanks!
Looks like a standard "loader lock" issue. Basically I'm doing stuff I shouldn't be doing while my DLL is being loaded.
I will have to redesign my code a bit. I should have a fix in a few days, end of the week the latest.

My Pleasure Ivo.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

No, I don't have Virtualbox installed, but UAC is turned off.

@streetwolf:
Please try the attached file. It contains a replacement for ClassicStartMenu.exe and ClassicStartMenuDLL.dll. You need to exit the start menu and copy these files into the Classic Shell directory (replacing the original files).
Set the start menu to run automatically, and disable the SkipMetroSuite.

This version is an attempt to fix:
the incompatibility with Vbox
the permanent highlight issue
the UAC issue (the popup when UAC is disabled)

Let me know how it works for you.

(Note that this DLL fix is only for 3.9.0 and 64-bit only. Later versions include the fix)

1. The Vbox problem appears to have been fixed. The only difference I see now is the Metro start menu appears for a couple of seconds before I get to my desktop. The previous version without Vbox installed went to the desktop immediately without seeing the Metro start screen.

2. Permanent highlighting seems fixed. I'll monitor this.

3. I have UAC at the lowest setting via the slider. In reality this does not turn UAC off completely in W8. I believe changing a Registry entry is the only way to accomplish a complete disable of UAC. However, this is not recommended by MS. I've never had popups the way I have UAC off. Could it be those that did have popups had UAC completely off via the Registry?

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

Yes, I can confirm, the highlighting issue is fixed. The UAC one I can test after a 32-bit DLL is available.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

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

Actually I see the Metro start screen for no more then a second. I'm pretty sure it didn't even show before.

_________________
i7 Quad 3770K @ 5Ghz|ASUS P8Z77-V Deluxe|Corsair 1050W PSU|Corsair H100 CPU Cooler|16GB RAM|Sapphire Nitro R9 390 8GB|DUAL ASUS PA249Q IPS 24" LCDs|Samsung SSD 830, 840 256GB|2TB Seagate, 4TB WD Black|Windows 10 Pro x64 (v1511)|

I had to switch back to the old method of skipping Metro because the new one (launching the Desktop app) doesn't work when UAC is completely disabled through the registry. Apps don't work without UAC. I've also heard reports that the new method sometimes fails to switch.

why not have both?, maybe nest the option right under the other; and call it "Skip metro Alternate (only check it the above doesn't work)" or something similar
broad spectrum and all, at least until you can find a total solution

By old method, Ivo means sending Win+D keystroke/show desktop command. It still uses COM to skip the Start screen right? It no longer depends on the service like 3.6.x did. Giving two options means supporting both and unnecessary complexity. Plus Windows 8.1 is coming with a native option to boot to desktop in a few months.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

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

Both methods exist in the full beta build and can be selected through a registry key. It was intended as a safety measure if the new method doesn't work. As there are enough reports by now to suggest it doesn't work in many cases, I'd rather remove it. Adding an option with somewhat technical description will be confusing for most users.

And yeah, I want to see what 8.1 has to offer. The //build/ build is supposedly coming up next week.

ah havnt been keeping up with 8.1 , also you should maybe have an 'super advanced' settings .txt file stored within classic shells folder, for all the settings to technical, specific, or menial to make it into the program otherwise . Having it there would ensure only advanced users get there hands on it