Classic Shell: Forum

Rename the installer and install it. Or wait for an updated release which will be out soon.

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

There is a new version 4.2.6 beta that should work just fine with the Insider builds.

Thanks for the new version.
It must be inconvenient to keep up with all these insider builds, but it seems to be the new "reality", so thanks again for allowing us to test them, without having to miss out on our beloved Classic Start Menu!!

Woops, spoke too soon, installed 4.2.6 on clean 14342edu32, things are not working correctly: the screen keeps flickering, looks like ClassicShell is continually restarting or something...

Can you capture a crash dump? Instructions are at the top of this page.

I used the "HKLM" method to make the dumps, from the zip info it looks like all the dumps are identical, not sure if they're something useful in there...
Please let me know if you want me to try other stuff, I have plenty of test laptops around.

Tested with 14342 x86 Enterprise as well now, exactly the same problem: Constant explorer restarts/ flashing screen (looks like CS gets killed as soon as it appears).
Has nobody else tested this? EDIT: 4.2.5 is fine (after renaming the installer, of course).

Yes, there appears to be a problem on 32-bit Windows 10. How did you manage to recover? I want to post instructions for other people affected by this.

Well, I like to play around with PE, disk imagers, automatic postinstall, software testing etc., so for me it was a "fun" (ahem) project, but of course it's too bad that there is a problem with the new beta.

My first "recovery" was a quick restore of a disk image, but then in a later test I tried to recover from the flashing (and somewhat entertaining) explorer crashes by hitting ctrl-sh-esc and trying to kill the ClassicStartmenu process fast enough before a new entry appeared in the list, and/or the task manager lost focus. In this case it was a good thing I tested on a slow computer...

Seriously, not a very practical way of "recovery", so I really hope you can find the problem soon.

I am still a very happy ClassicShell user, so hopefully on to the next beta soon!

I found the problem. There was a wrong calling convention for some Windows function that only causes problems on 32-bit Windows 10.
Try this new installer: http://www.mediafire.com/download/7hvdd ... _4_2_7.exe

Wow, that was fast...
Good thing I kept the disk image (14342ent32), I could test within a few minutes. Looking good, problem gone!!!
Now I will replace 4.2.5 with 4.2.7 in my PostInst and test that, so one more image restore and this whole thing was fixed in just one day!
You are a genuis, sir...

Yep, I could also remove the "if build >=14316, rename installer" part from my PostInstall thingy, so looking pretty good!!!
Really like the easy taskbar color change option!!