|
|
Post by The Jackal on Oct 23, 2019 8:09:49 GMT -8
it only works on Windows 10 up to build 1803 Uhmm, No. It works on 1903. For every version up to 1803 you can just change the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\FlightedFeatures\ImmesiveContextMenu
from 1 to 0. This way you won't screw up your taskbar. For 1809+ you can use the fix The Jackal described This thread involves crashing and restarting explorer so you can remove theming from the desktop context menus as well as other areas that normally don't revert to a classic appearance when you enable classic theme. Like the 'run as' dialog box, as well Open/Classic Shell's settings menu. That includes the taskbar as well - that's why it get's screwed up, it's an intentional side-effect. The taskbar gets screwed up because it reverts to it's classic look, or should I say what's left of it after MS gutted most of the code. The reason is I've not corrected this thread is two fold - 1. ExplorerContextMenuTweaker is still in alpha. I respect and fully appreciate the author for their work, but I don't think it's safe to call it a reliable fix. I certainly don't recommend it for daily use. 2. ExplorerContextMenuTweaker hooks into Explorer, my "trick" involves crashing and restarting Explorer. See the problem? If someone can confirm this works on W10 beyond 1903, yes even with ExplorerContextMenuTweaker, I'll revise the thread title. |
|
|
|
Post by leet on Oct 23, 2019 14:08:24 GMT -8
I should start actually reading what people say. Sorry for the confusion. It only works up to 1803.
|
|
|
|
Post by leet on Oct 23, 2019 14:17:39 GMT -8
This is actually the next thing on my roadmap for SimpleClassicTheme. After brainstorming I've come up with a concept:
1. Enable classic theme 2. Restart explorer, it will be bugged out 3. Disable classic theme 4. Make taskbar buttons big (programmatically)
5. Make taskbar buttons small again (programmatically)
6. Enable classic theme
This works on ANY version of Windows 10 but I can't seem to find a way to do step 4 and 5 programmatically
|
|
veselcraft
Freshman Member
Posts: 46
OS: Windows 10 LTSB
Theme: Win 2k
|
Post by veselcraft on Jan 28, 2020 12:34:32 GMT -8
This works on ANY version of Windows 10 but I can't seem to find a way to do step 4 and 5 programmatically You can try to catch this process with Process Monitor |
|
veselcraft
Freshman Member
Posts: 46
OS: Windows 10 LTSB
Theme: Win 2k
|
Post by veselcraft on Jan 28, 2020 12:54:10 GMT -8
I modify script from there to restart explorer for "Classic" scheme, and it looks so awesome! {Desktop}  By the way, icons looks like in Windows 2k every when selected {Icon}  |
|
|
|
Post by powerplayer on Jan 29, 2020 11:27:25 GMT -8
there must be a hidden registry setting to add it backclassic win87 clock is back in 1909 i got it to work
|
|
|
|
Post by The Jackal on Oct 3, 2020 12:04:07 GMT -8
Another side-effect to this "trick" is, that Task View (aka Win+Tab) no longer works, which is a shame as this is one of the few features added in to W10 that I actually liked...well it was until they screwed it up in by added in the timeline and making it slow and bloated. Another inconvenience is Virtual Desktops; seeing as Task View no longer works, you can no longer delete a running virtual desktop. Why does this matter? Because if you hit Ctrl+Win+Left/Right you'll switch to a VD without a way to go back. Solution? Disable the hotkeys. Script is attached to this post, add it to startup and you'll no longer have this issue. |
|
|
|
Post by ihatemetro on Oct 3, 2020 16:00:01 GMT -8
there must be a hidden registry setting to add it backclassic win87 clock is back in 1909 i got it to work That's because of StartIsBack++, StartIsBack++ restored the ability to have that clock. |
|
|
|
Post by powerplayer on Oct 5, 2020 4:21:27 GMT -8
there must be a hidden registry setting to add it backclassic win87 clock is back in 1909 i got it to work That's because of StartIsBack++, StartIsBack++ restored the ability to have that clock. Yes but if they did it howcome nobody here did? |
|
|
|
Post by leet on Oct 5, 2020 4:37:09 GMT -8
That's because of StartIsBack++, StartIsBack++ restored the ability to have that clock. Yes but if they did it howcome nobody here did? I’ve tried asking the people behind SIB++ many times. They refused to tell me how they did it, probably because they can sell more copies if there’s no open source solution. |
|
|
|
Post by powerplayer on Oct 6, 2020 15:08:00 GMT -8
Yes but if they did it howcome nobody here did? I’ve tried asking the people behind SIB++ many times. They refused to tell me how they did it, probably because they can sell more copies if there’s no open source solution. They actually forced the registry entry to work with sib which is kinda amazing but given their history they had a win7 explorer for win8 from the start they might have added all sorts of undocumented apis found in win sourcecode lol. |
|
|
|
Post by leet on Oct 11, 2020 3:33:37 GMT -8
I’ve tried asking the people behind SIB++ many times. They refused to tell me how they did it, probably because they can sell more copies if there’s no open source solution. They actually forced the registry entry to work with sib which is kinda amazing but given their history they had a win7 explorer for win8 from the start they might have added all sorts of undocumented apis found in win sourcecode lol. No, it’s not a reg hack. I looked in to it a bit and it seems they catch when the clock is clicked and force explorer to display the old clock. |
|
|
|
Post by powerplayer on Oct 11, 2020 8:05:26 GMT -8
They actually forced the registry entry to work with sib which is kinda amazing but given their history they had a win7 explorer for win8 from the start they might have added all sorts of undocumented apis found in win sourcecode lol. No, it’s not a reg hack. I looked in to it a bit and it seems they catch when the clock is clicked and force explorer to display the old clock. probably because they catch the memory adress via processhacker in older builds and replicate it with the memorycode. |
|
|
|
Post by ihatemetro on Oct 11, 2020 11:32:46 GMT -8
They actually forced the registry entry to work with sib which is kinda amazing but given their history they had a win7 explorer for win8 from the start they might have added all sorts of undocumented apis found in win sourcecode lol. No, it’s not a reg hack. I looked in to it a bit and it seems they catch when the clock is clicked and force explorer to display the old clock. I think you said some information in here: www.winclassic.net/thread/130/port-clock-back-windows-anniversary about the Windows subclassing and all that. |
|
