It is currently Fri Dec 15, 2017 2:39 pm

All times are UTC - 8 hours [ DST ]




Post new topic Reply to topic  [ 24 posts ] 
Author Message
 Post subject: Big trouble of 4.2.7 !!!
PostPosted: Sun May 22, 2016 4:24 pm 
Offline

Joined: Thu Dec 17, 2015 6:00 am
Posts: 10
After the install of newest 4.2.7, the start button became NO response, but other functions seem working!
Please check and release new one as soon as possible!!!


Top
 Profile  
Reply with quote  
PostPosted: Sun May 22, 2016 4:30 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5310
Please provide more information. What version of Windows do you have? What other functions are working? Have you tried restarting?


Top
 Profile  
Reply with quote  
PostPosted: Sun May 22, 2016 4:53 pm 
Offline

Joined: Thu Dec 17, 2015 6:00 am
Posts: 10
My Windows 10 is 10586.318 (Pro 64bit).
Yestreday I installed the previoue 4.2.6, and it worked normally.
But this morning I found new 4.2.7 and installed it, but the start button became no response!!!
I went back to 4.2.6, the start button became OK!


Top
 Profile  
Reply with quote  
PostPosted: Sun May 22, 2016 5:47 pm 
Offline
User avatar

Joined: Sun Jan 06, 2013 1:44 pm
Posts: 1847
For most the new version works OK, so we need more Information to find out why it broke on your pc so we can fix the issue


Top
 Profile  
Reply with quote  
PostPosted: Sun May 22, 2016 5:52 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5310
Download the Classic Shell Utility from here: http://www.classicshell.net/downloads/
Run it, use the first button to save a system log, and send the log to me.


Top
 Profile  
Reply with quote  
PostPosted: Sun May 22, 2016 6:00 pm 
Offline

Joined: Thu Dec 17, 2015 6:00 am
Posts: 10
I already went back to 4.2.6!
Please confirm this problem on your test macines!
I saw this error on my two 4.2.7 machines, so I thik you can re-creste this error and confirm!


Top
 Profile  
Reply with quote  
PostPosted: Sun May 22, 2016 6:18 pm 
Offline
User avatar

Joined: Sun Jan 06, 2013 1:44 pm
Posts: 1847
If you simply wish to remain on 4.2.6 that is fine.. but unless we can narrow it down, its going to be hard to reproduce.. Just because the issue crops up on both of your test systems, doesn't mean its a common issue. it just means whatever is causing the issue, is likely installed, or tweaked on both of your test system. I have personally tested it on 2 separate physical machines. and knowing IVO, he probably tested it in a variety of configurations/OS's.

We are happy to troubleshoot and find the issue, but we need people who have the issue, and are willing to work with us. You are under no obligation to do so, but until someone does step forward, the issue might not be resolved.


Top
 Profile  
Reply with quote  
PostPosted: Sun May 22, 2016 6:40 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5310
I have verified that version 4.2.7 works fine here on 64-bit build 10586, 64-bit build 14342 and 32-bit build 10240!!
The problem must be related to something specific to your setup. The utility will collect information about the specifics!!!

Versions 4.2.6 and 4.2.7 differ by only one thing, which should only make a difference on 32-bit Windows.

And BTW, I meant to say - install version 4.2.7, reboot, confirm that it still doesn't work, and then run the utility to create the log file!!!!


Top
 Profile  
Reply with quote  
PostPosted: Sun May 22, 2016 7:43 pm 
Offline

Joined: Thu Dec 17, 2015 6:00 am
Posts: 10
I re-installed 4.2.7 after uninstalling 4.2.6, and finally 4.2.7 works normally!
I think I observe this for a while.
Thanks for your supports.


Top
 Profile  
Reply with quote  
PostPosted: Mon May 23, 2016 6:04 pm 
Offline

Joined: Thu Dec 17, 2015 6:00 am
Posts: 10
After 4.2.7 install for my 2 PCs, the same error occured as follows;

1) desktop PC (syslog1.txt) Windows10 64bit
2) laptop pc (syslog2.txt) Windows10 64bit (surface 3 pro)

On desktop pc, this error occured once just after Classic shell install, but on laptop pc, it occured very frequently (mailnly just after power on startup).
The click for start button is no response for it, but the right click operation for setting it works!
So I went back to 4.2.5c for laptop pc, it become OK as previous 4.2.5!

I attached the system log for these errors;

syslog1 ... for desktop pc ( only once occurence)
syslog2 ... for laptop pc (occured on startup)


Attachments:
syslog.zip [47.94 KiB]
Downloaded 86 times
Top
 Profile  
Reply with quote  
PostPosted: Mon May 23, 2016 6:48 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5310
So basically you are saying that the Windows 10 menu frequently doesn't show when you click on the start button?
Does the Classic menu show up correctly every time when you Shift+click the start button?


Top
 Profile  
Reply with quote  
PostPosted: Mon May 23, 2016 9:35 pm 
Offline

Joined: Thu Dec 17, 2015 6:00 am
Posts: 10
Shift+click the start button does also not work when normal click is unavailable, but the right click works!
(Now I re installed 4.2.7 on my laptop pc for the collection of data relating to this error, and so please ask me to do any operation and collect data for this error. Now my laptop pc installed 4.2.7 and this error can be recreated easily)


Top
 Profile  
Reply with quote  
PostPosted: Wed May 25, 2016 8:41 am 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5310
Sorry, I can't reproduce this problem. Please try a few tests to narrow it down:
1) Try with the "Replace start button" setting and without it
2) Try using the default controls, where the Win key and the mouse click open the Classic start menu, and Shift+Win and Shift+Click open the Windows start menu
3) When the problem starts happening, right-click on the start button, select Exit, and try to open the Windows menu again


Top
 Profile  
Reply with quote  
PostPosted: Wed May 25, 2016 4:09 pm 
Offline

Joined: Thu Dec 17, 2015 6:00 am
Posts: 10
The followins are the results for this error;

1)When this error occurs, the click of Classic shell start button and the start button without setting (Windows 10 native button) both does not work (no response for left-click). Win-key opens start menu normally.
By terminating the classic start menu, the start button (Windows 10 default) works normally.
2)Using default setting, the same error occurs.
3)By exiting classic shell after error, the native windows 10 start button works.

When this error occured, it sometime becomes normal after restarting or power-up (but not always), but becomes to the same error after another restart!
On my laptop pc, this error occurs after install (most of times), and by going back to 4.2.5c, the classic shell becomes normal!


Attachments:
syslog.zip [22.53 KiB]
Downloaded 91 times
Top
 Profile  
Reply with quote  
PostPosted: Sat Jun 11, 2016 3:13 pm 
Offline

Joined: Sat Jun 11, 2016 3:07 pm
Posts: 5
matsuda0707 is right, version 4.2.7 does somehow crash or stop the windows 10 default start menu from working as he has described. im on the latest version of windows 10 x64 and i have had similar issues. it don't happen every time and my fix is to restart the explorer which gets it all working as it should. there's defo a major bug in 4.2.7 beta i've not tried 4.2.6, where can i download it guys as its anoying not to be able to get to the OS menu if you need too. ps uninstalling classic shell fixes the problem with the windows shell - thankfully.

hope this info helps track down the bug, well done matsuda0707!


Top
 Profile  
Reply with quote  
PostPosted: Sat Jun 11, 2016 4:09 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5310
Which exact version of Windows do you have? Is it 32-bit or 64-bit?
Do you have multiple monitors?
Do you use the Windows start button or the one from Classic shell?
And how are you opening the start menu - Win key, Shift+Win, mouse click, or Shift+click?


Top
 Profile  
Reply with quote  
PostPosted: Sat Jun 11, 2016 7:38 pm 
Offline

Joined: Sat Jun 11, 2016 3:07 pm
Posts: 5
Windows 10 64bit, laptop single monitor, neither the start button nor the button in classic shell work when the bug kicks in, no matter how i try to open it but when it's working i tend to use a mouse click, version 4.2.6 seems ok so far...


Top
 Profile  
Reply with quote  
PostPosted: Sat Jun 11, 2016 7:51 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5310
But which build do you use - 10240, 10586, 14342 or the latest 14361?

The only difference between 4.2.6 and 4.2.7 is a single bug that only affects 32-bit Windows. There is no way they work differently for you.
Most likely the problem occurs sporadically, and it just hasn't happened yet with 4.2.6.

I suspect the problem is that sometimes the code thinks incorrectly that the menu is already open, and doesn't open it. I am changing how I check if the menu is open, and I'm adding more logging.
In the next few days I hope to post a test version for you to try.


Top
 Profile  
Reply with quote  
PostPosted: Sun Jun 12, 2016 10:21 am 
Offline

Joined: Sat Jun 11, 2016 3:07 pm
Posts: 5
Yep is the latest build, and not seen it yet in 4.2.6 but am expecting to given what you say about the code being largly identical, the problem is sporadic and when it occurs it seems that somehow classic shell is stopping the windows explorer from loading at startup, it don't happen on restarts and it don't happen when i maunally start the explorer when the clash occurs, yeah it feels like sometimes classic shell and explorer clash and the explorer gets blocked from loading - all aspects of the explorer don't work, left click and right click advanced menu both not available. other than that classic shell works really well and is a credit to your programming skills.


Top
 Profile  
Reply with quote  
PostPosted: Sun Jun 12, 2016 8:33 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5310
Please try the attached file.
Right-click on the start button and select Exit. Then go to the Classic Shell folder, and replace the file ClassicStartMenuDLL.dll with the one that is attached. It is compatible with 64-bit version of Classic Shell 4.2.7, but it should probably work with 4.2.6 as well. Run ClassicStartMenu.exe to restart the menu, or simply log off.

If you don't see any problems for the next couple of days, then most likely the problem is fixed. Report that here.

If the problem happens again, follow these instructions, VERY CAREFULLY:
1) Go to the folder %LOCALAPPDATA%\ClassicShell in Explorer. Delete the file WinMenuLog.txt. Don't close the Explorer window
2) Open the start menu settings and go to the Controls tab. Make sure that the mouse click, Shift+click, the Win key and Shift+Win are all set to open the Windows start menu. Don't close the settings
3) Try to open the Windows start menu 4 times in the following order - the mouse click, Shift+click, the Win key and Shift+Win. After each try wait 5 seconds. If the attempt was successful, close the start menu by pressing Escape or clicking on the desktop. DO NOT use the Win key or the start button to close the menu
4) Make a copy of the WinMenuLog.txt file immediately
5) Click Cancel on the start menu settings. This will revert any changes you made to the controls and will go back to your previous settings
6) Post the results here - include the text file, and report which of the 4 attempts to open the start menu was successful

Note that the attached file is only for Classic Shell 4.2.7. If you have a later version of Classic Shell installed, it may not fix your issue and this fix below is most probably already included in versions of Classic Shell after 4.2.7.


Attachments:
ClassicStartMenuDLL.zip [1.46 MiB]
Downloaded 92 times
Top
 Profile  
Reply with quote  
PostPosted: Mon Jun 13, 2016 1:54 pm 
Offline

Joined: Sat Jun 11, 2016 3:07 pm
Posts: 5
Hi mate, did exactly as you said, same bug occured as soon as i shut down the lappy waited 10 secs and restarted, for your info the windows key and shift plus windows worked ok, the mouse click and shift click did not. Heres the complete winmenulog.txt generated:

478921 2452 StartMenu DLL: TASKLIST WSMM
478921 2452 StartMenu DLL: OpenStartScreen ImmersiveShell=0, monitor=0000000000010001
526687 2452 StartMenu DLL: OPEN_WINDOWS
546140 2452 StartMenu DLL: TASKLIST WSMK

good luck fixing it mate.


Top
 Profile  
Reply with quote  
PostPosted: Mon Jun 13, 2016 10:36 pm 
Offline
Site Admin
User avatar

Joined: Wed Jan 02, 2013 11:38 pm
Posts: 5310
Thanks. That was very helpful. The part that says "ImmersiveShell=0" is a good clue.

Let's try this one more time, with the new file.


Attachments:
ClassicStartMenuDLL.zip [1.46 MiB]
Downloaded 104 times
Top
 Profile  
Reply with quote  
PostPosted: Tue Jun 14, 2016 8:12 am 
Offline

Joined: Thu Dec 17, 2015 6:00 am
Posts: 10
Thanks, Mer.shelluser!
You just made clear that this problem is not specific to my PCs!

I just installed 4.2.7 and replaced ClassicStartMenuDLL.dll taht was released by Ivo.
Now the problem looks disappear! It works OK.


Top
 Profile  
Reply with quote  
PostPosted: Thu Jun 16, 2016 5:12 pm 
Offline

Joined: Sat Jun 11, 2016 3:07 pm
Posts: 5
You are welcome matsuda0707


I can confirm that the latest dll posted above works sweet and has fixed the bug!!

Well done mate!!


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 24 posts ] 

All times are UTC - 8 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group, Almsamim WYSIWYG Classic Shell © 2010-2016, Ivo Beltchev.
All right reserved.