gcomputzide
Sophomore Member
As gcomputing goes on, it comes to the zide.
Posts: 150 
OS: Windows 10 1909
Theme: Classic Theme (Winamp 3.0)
CPU: Asus K53E: Intel(R) Pentium(R) CPU B950 @ 2.10GHz
RAM: AMD 8 GB, QUMO 4 GB
GPU: Asus K53E: Intel HD Graphics 3000
|
Post by gcomputzide on Aug 28, 2019 10:41:10 GMT -8
:ok_hand:
|
|
rikka0w0
New Member
Posts: 6
OS: Windows 10 x64 1803 & Ubuntu 18.04
Theme: AeroGlass
|
Post by rikka0w0 on Jan 31, 2020 7:55:16 GMT -8
Hi All,  I just switched to 1909 and confirmed that the taskbar context menu tweaker is still working! And I have found an alternative solution for the explorer context menu (system-wide): https://gist.github.com/rikka0w0/971e247871154427d5e62c7b3a7ac1d4 Although it is not the original classic menu, it does look very similar. And in that link I also described how to modify the explorer immersive menu style. |
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Mar 26, 2021 7:31:13 GMT -8
Hi All, I just switched to 1909 and confirmed that the taskbar context menu tweaker is still working! And I have found an alternative solution for the explorer context menu (system-wide): https://gist.github.com/rikka0w0/971e247871154427d5e62c7b3a7ac1d4 Although it is not the original classic menu, it does look very similar. And in that link I also described how to modify the explorer immersive menu style. I tested that solution but still does not display correctly . Tested on 20H2.  |
|
|
|
Post by ihatemetro on Mar 26, 2021 9:03:04 GMT -8
Hi All, I just switched to 1909 and confirmed that the taskbar context menu tweaker is still working! And I have found an alternative solution for the explorer context menu (system-wide): https://gist.github.com/rikka0w0/971e247871154427d5e62c7b3a7ac1d4 Although it is not the original classic menu, it does look very similar. And in that link I also described how to modify the explorer immersive menu style. I tested that solution but still does not display correctly . Tested on 20H2. That just skins the immersive menu, it doesn't restore the classic menu. |
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Mar 26, 2021 9:07:18 GMT -8
I tested that solution but still does not display correctly . Tested on 20H2. That just skins the immersive menu, it doesn't restore the classic menu. I got it. My bad |
|
|
|
Post by randommanonthenet on Dec 17, 2021 21:17:12 GMT -8
It seems that Alsee makes all context menus including its menus to classic, even on 1903 (and maybe 1809). the website is in what looks to be Korean, I can't read that! is there a way to get it in English? (by the way, i am using Firefox, and chrome just REFUSES to open, no error messages, no stuff, just won't open.)
|
|
|
|
Post by anixx on Dec 18, 2021 2:11:02 GMT -8
Just update to Win11+ExplorerPatcher.   |
|
|
|
Post by anixx on Dec 18, 2021 10:36:41 GMT -8
@ʇǝǝๅ ftw Please be polite and civil.
|
|
|
|
Post by leet on Dec 18, 2021 12:52:55 GMT -8
I'm sorry, but I was just telling the truth. I've heard the same complaints from multiple members on ClassicServ (the unofficial discord server). Deleting my post because I disagree with what you do is just straight up admin abuse in my opinion.
That aside, I wasn't even rude, I just pointed something out. I think I brought over the message in a very polite way, considering how much the issue bothers me. So next time you delete my post, be honest about why you are doing so.
EDIT: Context: The post contained a complaint towards anixx about them pushing Windows 11 everywhere on the forum, even when it's irrelevant
|
|
Souper
Freshman Member
Posts: 63
OS: Manjaro | Windows 10 (2021)
Theme: Placeholder | Aero / Luna
|
Post by Souper on Dec 18, 2021 13:15:17 GMT -8
Honestly would look forward to someone backporting this stuff to Win10 as these often already revert the 10 versions of everything after the 11 stuff
Plus, the fixed taskbar is already using the 10 one so it'd be possible.
|
|
|
|
Post by ihatemetro on Dec 19, 2021 7:09:23 GMT -8
Honestly would look forward to someone backporting this stuff to Win10 as these often already revert the 10 versions of everything after the 11 stuff Plus, the fixed taskbar is already using the 10 one so it'd be possible. I agree. Especially older versions since they are more compatible with DWM-off (More control panel items), which would mean being more friendly with classic theme. |
|
|
|
Post by anixx on Dec 19, 2021 11:31:43 GMT -8
May be you guys should ask for this at Explorer Patcher github.
|
|
Ingan121
Sophomore Member
Posts: 104
OS: Windows 10 22H2
Theme: Arc dark
CPU: AMD Ryzen 7 1700 Eight-Core Processor
RAM: 32GB
GPU: NVIDIA GeForce GTX 1050 Ti
Computer Make/Model: VPS-ish thingy (ComViewers)
|
Post by Ingan121 on Dec 20, 2021 3:07:01 GMT -8
It seems that Alsee makes all context menus including its menus to classic, even on 1903 (and maybe 1809). the website is in what looks to be Korean, I can't read that! is there a way to get it in English? (by the way, i am using Firefox, and chrome just REFUSES to open, no error messages, no stuff, just won't open.)
You don't need it now, this was before ExplorerContextMenuTweaker came. That program added a image preview in a context menu, which caused a bug in Windows that makes the context menu classic. Any other program that adds a thumbnail/preview in a right-click menu causes this bug.
|
|
|
|
Post by The Jackal on Jan 11, 2022 8:45:04 GMT -8
Found this whilst browsing Github: github.com/llccd/Shell32PatcherIt says it's for Windows 11, but can someone on a Win 10 build past 1809 try it for me please? I know it's a long shot, but I'd like to confirm where this could be a replacement for ExplorerContextMenuTweaker. Cheers. |
|
AnyKey
Sophomore Member
Posts: 248
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Jan 11, 2022 9:22:30 GMT -8
Found this whilst browsing Github: github.com/llccd/Shell32PatcherIt says it's for Windows 11, but can someone on a Win 10 build past 1809 try it for me please? I know it's a long shot, but I'd like to confirm where this could be a replacement for ExplorerContextMenuTweaker. Cheers. I tried it but it did not do anything. Still displays immersive menu.
Tested on 21H2.
|
|
|
|
Post by The Jackal on Jan 11, 2022 15:57:17 GMT -8
Found this whilst browsing Github: github.com/llccd/Shell32PatcherIt says it's for Windows 11, but can someone on a Win 10 build past 1809 try it for me please? I know it's a long shot, but I'd like to confirm where this could be a replacement for ExplorerContextMenuTweaker. Cheers. I tried it but it did not do anything. Still displays immersive menu.
Tested on 21H2.
Thank you for testing it out for me. Much appreciated. |
|
|
|
Post by anixx on Jan 12, 2022 3:17:55 GMT -8
This program just reverts Win11 menus to Win10 menus (immersive)
|
|
|
|
Post by leet on Jan 12, 2022 8:46:51 GMT -8
Combine this with ExplorerContextMenuTweaker (the hooking of this program and the context menu routine of ECMT) and you have fixed the context menu problem on Windows 10 once and for all
|
|
|
|
Post by anixx on Jan 12, 2022 15:46:49 GMT -8
Combine this with ExplorerContextMenuTweaker (the hooking of this program and the context menu routine of ECMT) and you have fixed the context menu problem on Windows 10 once and for all On Win10 this program simply does nothing. And on Win11 one can use ExplorerPatcher. |
|
|
|
Post by leet on Jan 13, 2022 8:11:12 GMT -8
I was talking about merging the two codebases:
You can use the patching method of Shell32Patcher to overwrite part of the method in Shell32 that creates a context menu, and then use ECMT’s code to create a classic context menu. This can be done by copying ECMT’s code into Explorer's memory, and then overriding the context menu handler to call the code that displays the classic context menu. This probably needs to be done in a new memory section (VirtualAlloc+VirtualProtect?) because the code that creates the classic menu is too big to fit in the available space.
Note: This would be single architecture (IE. 64-bit only) as you have to compile the function that creates the classic context menu into machine code first, and then compile your entire patcher with the machine code you compiled earlier as raw bytes.
|
|
