Tutorial: Use of Windows Classic theme with Windows 10, Windows 11 and Explorer Patcher

[Anixx]

Here is a tutorial on how to use Windows Classic theme and classic workflow on Windows 11. Thanks to Explorer Patcher, the Windows 11 shell is now compatible with Classic theme.

To enable the Windows Classic theme (which is more properly should be called the absence of themes) you would need a program that can switch the Classic theme from a command line, such as ClassicThemeTray or equivalent.

1. Install classic Task Manager

!Note! Instead of points 2,3,4,5,6 you can use these Windhawk mods together:

https://windhawk.net/mods/classic-theme-enable

https://windhawk.net/mods/classic-uwp-fix

You will need to enable injecting into system processes in Windhawk properties.

2. Put ClassicThemeTray.exe into C:\Classic

3. Create in task sheduler a task named "Classic" with elevated rights with the following commands in it:

C:\Windows\System32\schtasks.exe /run /tn Apps
C:\Classic\ClassicThemeTray.exe /enable
C:\Windows\System32\schtasks.exe /run /tn Classic2

Make sure it is set to run at any power source.

4. Create another task named "Classic2" with normal rights with the following command:
C:\Windows\System32\cmd.exe /c start userinit.exe

Make sure it is set to run at any power source.

5. Create a third task named "Apps", with normal rights and the following command:
C:\Windows\System32\cmd.exe /c start C:\Windows\System32\ApplicationFrameHost.exe

Make sure it is set to run at any power source.

6. Import the following reg file (under elevated command prompt):

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"Userinit"=C:\Windows\System32\schtasks.exe /run /tn "Classic"

(!) This does not always get successfully imported, so a manual editing of registry may be needed. (!)

7. Install Explorer Patcher. Then import the following reg file:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\ExplorerPatcher]
"OldTaskbar"=dword:00000001
"SkinMenus"=dword:00000000
"ToolbarSeparators"=dword:00000001
"DisableImmersiveContextMenu"=dword:00000001
"ClassicThemeMitigations"=dword:00000001
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"TaskbarGlomLevel"=dword:00000002
"MMTaskbarGlomLevel"=dword:00000002
"TaskbarSmallIcons"=dword:00000001
"TaskbarAl"=dword:00000000
"TaskbarSD"=dword:00000000
[-HKEY_CURRENT_USER\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32]
@=""
[-HKEY_CURRENT_USER\Software\Classes\CLSID\{1eeb5b5a-06fb-4732-96b3-975c0194eb39}\InprocServer32]
@=""
[-HKEY_CURRENT_USER\Software\Classes\CLSID\{1d64637d-31e9-4b06-9124-e83fb178ac6e}\TreatAs]
@="{64bc32b5-4eec-4de7-972d-bd8bd0324537}"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ImmersiveShell]
"UseWin32BatteryFlyout"=dword:00000001
[-HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{D17F1E1A-5919-4427-8F89-A1A8503CA3EB}\InprocServer32]
@="{64bc32b5-4eec-4de7-972d-bd8bd0324537}"

8. Install OpenShell and import the following reg file:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\OpenShell\StartMenu\Settings]
"StartButtonType"="ClasicButton"
"CustomTaskbar"=dword:00000001
"TaskbarLook"="Opaque"
"TaskbarColor"=dword:00000000
"SkinC1"="Classic skin"
"SkinOptionsC1"=hex(7):43,00,41,00,50,00,54,00,49,00,4f,00,4e,00,3d,00,30,00,\
  00,00,55,00,53,00,45,00,52,00,5f,00,49,00,4d,00,41,00,47,00,45,00,3d,00,30,\
  00,00,00,55,00,53,00,45,00,52,00,5f,00,4e,00,41,00,4d,00,45,00,3d,00,30,00,\
  00,00,43,00,45,00,4e,00,54,00,45,00,52,00,5f,00,4e,00,41,00,4d,00,45,00,3d,\
  00,30,00,00,00,53,00,4d,00,41,00,4c,00,4c,00,5f,00,49,00,43,00,4f,00,4e,00,\
  53,00,3d,00,30,00,00,00,54,00,48,00,49,00,43,00,4b,00,5f,00,42,00,4f,00,52,\
  00,44,00,45,00,52,00,3d,00,31,00,00,00,53,00,4f,00,4c,00,49,00,44,00,5f,00,\
  53,00,45,00,4c,00,45,00,43,00,54,00,49,00,4f,00,4e,00,3d,00,31,00,00,00,00,\
  00

[HKEY_CURRENT_USER\Software\OpenShell\ClassicExplorer\Settings]
"StatusBarFont"=""
"ShowStatusBar"=dword:00000001
"UseBigButtons"=dword:00000000
"TreeItemSpacing"=dword:fffffffe
"NoFadeButtons"=dword:00000001
"FullIndent"=dword:00000001

If you want the start menu icon to be Windows logo, add the following lines:

[HKEY_CURRENT_USER\Software\OpenShell\StartMenu\Settings]
"StartButtonIcon"="%SystemRoot%\System32\slui.exe, 2"

9. Put the patched file StartMenuDLL for OpenShell 4.4.160 or StartMenuDLL for OpenShell 4.4.169 beta or
StartMenuDLL for OpenShell 4.4.190
into the Open Shell folder, replacing the existing one. Or install the patched version of OpenShell4.4.191. For patching instructions, see the post by @valinet below.

10. You would need a modified desk.cpl either from Windows NT or Windows 2000 to choose and adjust color schemes. (Modification instructions)

11. Delete or rename this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\DefaultColors\Standard
It prevents color scheme change after pressing Ctrl+Alt+Del or going to the logon screen and back.

12. If you want the 3D borders in menus, import the following reg file:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Control Panel\Desktop]
"UserPreferencesMask"=hex:9E,1E,05,80,12,01,00,00

13. If you dislike the ribbon interface, merge the following in the registry, which will have ExplorerPatcher enable the Windows 7 command bar in Explorer windows instead of the ribbon:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\ExplorerPatcher]
"Virtualized_{D17F1E1A-5919-4427-8F89-A1A8503CA3EB}_FileExplorerCommandUI"=dword:00000002

14. If you prefer the 3D-looking taskbar buttons, install a pre-release (1.1.7.6 or above) version of TaskBowFree Explorer extension. Be warned, it is quite buggy. Update: as a better solution, install this Windhawk mod.

15. Install 7+ Taskbar Tweaker if you want additional taskbar fixes, such as setting the interval between the tray icons to 2px as in classic versions of Windows or classic taskbar context menus.
Reg file for 7+TT:

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\7 Taskbar Tweaker\OptionsEx]
"tray_icons_padding"=dword:00000002
"disable_taskbar_transparency"=dword:00000001
[HKEY_CURRENT_USER\Software\7 Taskbar Tweaker\Options]
"1318069356"=dword:00000001
"1318069660"=dword:00000001
"1318069999"=dword:00000003
"1318070012"=dword:00000001
"1321056220"=dword:00000001

16. Install other Windhawk mods related to Classic Theme at your choice, such as https://windhawk.net/mods/classic-theme-transparency-fix, https://windhawk.net/mods/classic-browser-fix, https://windhawk.net/mods/dwm-ghost-mods, https://windhawk.net/mods/classic-maximized-windows-fix, https://windhawk.net/mods/clientedge-in-apps.

[Gaurav-Original-ClassicShellTester]

Thank you and awesome! Truly appreciated.

[valinet]

Niceee. Thanks for the writeup. Btw, in the spirit of this project and working in the open and publishing the source, here is the patch diff file for the changes made to OpenShell (you need Open-Shell-Menu-4.4.160.zip for this patch specifically, but the idea should work on all versions) to generate that custom DLL version. The edits are not huge (described in reverse order as they appear in the source code):

• Disabled OpenShell's DrawThemeTextEx IAT hook because it was useless since themes are disabled and interfered with ExplorerPatcher's own hook for that which is required to fix the taskbar buttons text under classic theme
• There is some code that applied a taskbar color (via a taskbar texture) but it was enabled only for Windows versions less than 10; enabled that on all versions and made sure the color is GetSysColor(COLOR_BTNFACE)
• There is a check whether themes are enabled, and only then taskbar textures are drawn; removed that check, since themes are disabled when using the classic theme, but we wanted that texture so the above point worked
• I added a call to update the taskbar texture when WM_SETTINGCHANGE is received; that happens in various circumstances, including when you change the color scheme - thus, applying a new color scheme using deskn.cpl, for example, does not require an Explorer restart

I am glad that this saw the light of day. It is a great addition to the functionalities of EP, indeed. Truth be told, the classic theme looks nice and with it you get a consistency level that modern versions of Windows struggle to get by.

Thanks

StartMenuDLL_diff.txt

[roytam1]

I wonder if you will create a PR to OpenShell for this patch? or did upstream merge this?

[Anixx]

I made a request for this patch to be merged. Open-Shell/Open-Shell-Menu#889

[roytam1]

I made a request for this patch to be merged. Open-Shell/Open-Shell-Menu#889

maybe better creating a real PR, and their side may want these changes be configurable.

[Anixx]

Please, do it.

[OrthodoxWindows]

I just made the Pull Request : Open-Shell/Open-Shell-Menu#1642

[l0oo]

WOW! Simply awesome!
TYVM Anixx & valinet!

[Biliskn3r]

I hate that we have to do this - every Windows version they try to "upgrade" the themes but just end up f00king it all up. Sigh. Are you listening M$ Devs?

[Anixx]

Valentin! I have forgot one important step in setting up the classic theme: one has to delete (or rename) the Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\DefaultColors

If not done, then after pressing Ctrl+Alt+Del and returning from that screen, the color scheme will change. This has been the case since Windows 8.1. Can you please add this fix to the "Classic Theme Mitigations" set?

[valinet]

No, because it's in HKLM, and Explorer runs unelevated. Does it have to run every time or once is enough? If once is enough, mention it in the tutorial and that should be it. If it's not enough, some scheduled task or something like that, I can't do anything from Explorer that involves admin without triggering a UAC prompt.

[Anixx]

Once is enough.

[Anixx]

Added to the tutorial.

[Anixx]

Valentin, since you inject all programs with open/save dialogs, and maybe others (such as console apps?), would you mind to include in the patcher a part of my AHK script that adds 3D border to the Notepad and Cmd windows?

When in AHK it does not work perfectly because it needs to resize the window after applying the style. As you can see in the tutorial above, I use the following commands:

if (WinClass = "Notepad") {
Control, ExStyle, +0x200, Edit1, ahk_id %lParam%
WinGetPos, , , , h, ahk_id %lParam%
WinMove, ahk_id %lParam%,,,,,h-1
WinMove, ahk_id %lParam%,,,,,h
}

If (WinClass = "ConsoleWindowClass") {
WinSet, ExStyle, +0x200, ahk_id %lParam%
WinGetPos, , , , h, ahk_id %lParam%
WinMove, ahk_id %lParam%,,,,,h-1
WinMove, ahk_id %lParam%,,,,,h
}

If added to the Patcher, I think it would work better. I do not think, a separate option is needed for this, just an addition to the "Classic theme mitigations". If you also add this to the Mathematica's notebook class, this would be wonderful:

if (WinClass = "NotebookFrame") {
Control, ExStyle, +0x200, NotebookContent1, ahk_id %lParam%
WinGetPos, , , , h, ahk_id %lParam%
WinMove, ahk_id %lParam%,,,,,h-1
WinMove, ahk_id %lParam%,,,,,h
}

[jailbird777]

@Anixx Is the binary version of the patched StartMenuDLL.dll for the old OpenShell 4.4.160 or the slightly newer 4.4.169-beta, which seems to correlate to the 'master' branch?

If I can get a build environment setup, I'm going to see if I can produce one for 4.4.169-beta

[valinet]

More details about the patched StartMenuDLL.dll here as well: #167 (comment)

[jailbird777]

Thanks for the pointers! I'm mostly an *IX guy, but I managed to somewhat find my way around VS to get it to poop out a new .DLL.

And ouch, that reboot experience sounds like a total pain :(.

[valinet]

Yeah, it's not that difficult, I spend my fair share of days in GNU/Linux too, for example. Yeah, idk, that's how it was for me in a VM I tested that, idk what was causing it exactly, but I eventually did that and realized my builds weren't broken, they just did not work properly without rebooting. Anyway, not a pain unless you plan on doing active development on OpenShell. When you get a working DLL, maybe share it here as well, some people might find it interesting, idk. Thanks.

[jailbird777]

Open-Shell 4.4.169 .DLL if anybody wants to give it a shot: StartMenuDLL.dll

[Anixx]

I have updated the guide, the script, all.

[HitAnyKey]

Almost fine but the taskbar is glitchy.

[Anixx]

It should just work. Did you put the dll into c:\windows?

[HitAnyKey]

Sorry for late reply.
Yes, I placed DLLs into there. But now I've got a proper taskbar by enabling Customize Taskbar in Open-Shell Settings.

And I have another issue now.
Restarting explorer makes some task tray icons unusable. (They does not responds to right/left clicking)

[Anixx]

I've got a proper taskbar by enabling Customize Taskbar in Open-Shell Settings.

Thanks for pointing this out, I had missed that reg key. Added it to the tutorial now.

[l0oo]

Wow! HitAnyKey - your taskbar looks perfect now. My is more like on Anixx screenshot.
How do you get such 3D effect (for taskbar's active/inactive window)?

[Anixx]

Read the tutorial, p.14

[l0oo]

TBH I didn't get effect as on Anixx' screenshot too. :(
Was trying to reproduce all steps carefully but no luck. :/
Dunno what trigger to use in task sheduler... Taskbar don't have quick launch nor 3D frame at tray etc... :/

As for Explorer Patcher - dunno if we need to use dxgi.dll too? Win+X for settings not working anyway...
I used as per Annix tutorial:
7. Install Explorer Patcher by copying its DLLs into C:\Windows AND registering them using the regsvr32 method (registering as shell extension is only needed for effect on file open/save dialogs).

But acc. to https://github.com/valinet/ExplorerPatcher/blob/master/CHANGELOG.md we need to use just one dll to be registered:
Info about experimental 22000.282.31 feature:
To enable this, put the 2 DLLs (ExplorerPatcher.amd64.dll and ExplorerPatcher.IA-32.dll) in a secure folder (for example, C:\Program Files\ExplorerPatcher). Then, in that folder, run this command: regsvr32 ExplorerPatcher.amd64.dll. After elevation, a message will display informing you of the operation outcome, and if it went well, Explorer will restart displaying the old taskbar.

I am little lost... :(
It is shame that we lose energy to bring back features which in fact still exist inside Windows. :(

[Anixx]

Is Explorer Patcher running at all? If yes, you should always have the ability to add a quick Launch toolbar.

Is the following option checked?

[Anixx]

You should put the Explorer Patcher DLLs into C:\Windows. If you want the open/save dialogs affected, you should additionally register the DLL.

[Anixx]

Dunno what trigger to use in task sheduler...

You should not specify any trigger.

[HitAnyKey]

No need to specify the trigger?
However it does not do anything without trigger.

[Anixx]

It is getting run by this part:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"Userinit"=C:\Windows\System32\schtasks.exe /run /tn "Classic"

So, you do not need to specify a trigger, it replaces userinit process.

[l0oo]

Thank you for the answer! Will try again from scratch. :)
BTW: Wouldn't be great if MS could just bring back classic interface? :)

[BraINstinct0]

I hope so too(no, not really - they'll mess up something more in the process...)

[kjm8368889]

How do I create a "classic" task in task scheduler with elevated privileges with the following command?

[HitAnyKey]

You need to edit Userinit.
Double click Userinit and type this in given dialog.

C:\Windows\System32\schtasks.exe /run /tn "Classic"

And then restart your computer.

[l0oo]

6. Import the following reg file (under elevated command prompt)

Maybe this is the problem? Users rights are not enough for such important entry... And people just click *.reg as normal users.

[kjm8368889]

yes this seems to be the problem.
Once I entered the properties in the task scheduler and deleted it from the start position (option) (T) in the action properties in the action, it started running.

[kjm8368889]

First, I manually turned on ClassicThemeTray, but the method is a bit inconvenient...
This is my windows 11 classic theme.

[kjm8368889]

+Open Shell

[HitAnyKey]

That AHK script adds weird vertical bar (this happens when in multi-monitor setup and any one of the windows is maximized) and replaces transparent with dark side.
Vertical bar image (External site because it's too large)

[Anixx]

That AHK script adds weird vertical bar

I did not face with it. Does it depend on whether the shadows enabled?

and replaces transparent with dark side.

This is expected. A workaround (if it bothers you) is to use Classic theme over a light high-contrast theme. But I did not use it on Windows 11, on Win8.1 such theme would also bring a light-grey background on the logon screen.

[HitAnyKey]

Sorry for super late reply.

This is expected. A workaround (if it bothers you) is to use Classic theme over a light high-contrast theme. But I did not use it on Windows 11, on Win8.1 such theme would also bring a light-grey background on the logon screen.

OK, I live with it now

I did not face with it. Does it depend on whether the shadows enabled?

I did not check about the windows shadows but the transparency fix seems to add it.
As of now, I'm using DwmUnExtendFrame.exe instead.
And then, weird bar has been disappeared.

[Anixx]

With contrast theme the dialogs appear correct but other issues emerge:

[novatiberium]

Am I doing this properly?

I'm using RetroBar because the OG taskbar looks ugly (maybe if there's a way to fix it more then I will stop Retrobar)

The problem here is - the Classic Theme (despite the fact that in this photo it's already running) - I set on Task Scheduler and configured it to start, but it doesn't start properly at log on. And even after starting the tasks - the Windows File Explorer opens. Am I doing this all wrong?

[Anixx]

Did you do all other steps or only this?

[novatiberium]

I did do all other steps

[Anixx]

What is OG taskbar, btw?

[l0oo]

OG = Original, W10 taskbar.
In fact TaskBowFree'ed taskbar and RetroBar, both look better, but are limited (change order of opened windows in 1st + using T-Clock on 2nd).

@novatiberium
look here: #167 (comment)

[solstice-r]

can this be easily reverted?

[Anixx]

Classic theme? Yes, by restoring

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"Userinit"=C:\Windows\System32\userinit.exe

After this, uncheck "Classic theme adjustments" option in Explorer Patcher.

[umbrella-k]

When I did this, the taskbar became buggy.

There appear to be mysterious blank spaces on either side of the icons of applications that are not open.
Is there any way to solve this?

[Anixx]

If you meant pinned items, it works correctly here:

[jonhermansen]

FYI, ClassicThemeTray is detected by Windows Defender as a threat: Trojan:Script/Phonzy.A!ml

https://www.virustotal.com/gui/url/3c6ff7663f7dd9181fb2f818a5904b83f09d5dfe56d456327482ea7508057e78/details

[Anixx]

Windows Defender detects all hacking tools as viruses.

[valinet]

Exactly, fuck Windows Defender.

[NDevDiscord]

Hello, good work!
Also, im maded a tutorial how to run 16-bit apps in windows 10, can you add it?

[LoneCrusader2002]

I've followed the tutorial, but I can't seem to end up with the same results. While things are close, there are still some glitches. Maybe I missed some minor detail?

Tried adding some other "Classic" related Windhawk mods, but at least one made things worse and messed up the side caption of the Start Menu. This is with only the 3 shown enabled plus Classic Conhost enabled.

The taskbar is slightly too large and covers the bottom edge of the Open Shell Menu; the Task buttons are not properly aligned; the System Tray has no borders; the Quick Launch and Taskbar handles are different (not necessarily a bad look, but not correct); and the "line" between the Quick Launch Bar and Taskbar is more noticeable than it should be.

Also noted that if I open a Command Prompt, it is originally skinned like a Classic window should be, but after a few seconds it transforms into a Windows 7-type window with larger borders and buttons.

[Anixx]

When you did the steps 2-6 method, the Apps task starts ApplicationFrameHost before Classic Theme. So, the UWP apps work but ApplicationFrameHost resides in memory. A better method is to enable the ClassicUWPFix mod and remove the Apps task as unneeded (also, the context menu of the UWP windows will become classic-themed).
The 3D Buttons mod is definitely preferred to TaskBowFree in all cases. You also can use taskbar with flat buttons, in which case you have the progress indicator on buttons, which is not visible on 3D buttons.

[Anixx]

No-one reported a problem like yours with the Windhawk mod.

[pyrates999]

Using OpenShell.

have you checked to see if there is an update to OpenShell? Latest is 4.4.191.

[Anixx]

Try this variant of the Windhawk mod, does it work better?

https://winclassic.net/thread/2409/massive-update-classic-theme-proposed?page=1

[LoneCrusader2002]

Unfortunately it doesn't work either, same behavior as the previous version. I tested on a clean setup using the same method/order I outlined above. Tested under both User-Administrator and Built-In-Administrator (switched IU to BA) accounts.

It's weird that no one else seems to encounter this.

[NDevDiscord]

Hello, i cant find the openshell start menu skin

[Anixx]

You should use Classic skin, shipped with OpenShell.

[NDevDiscord]

You should use Classic skin, shipped with OpenShell.

now looks like from classic windows 7 but i wanted from windows 2000

[oep42]

Thanks a lot for the tutorial. Suggestion to improve the tutorial:

These links to Windhawk mods do not work for me:
https://winclassic.boards.net/thread/2030/windhawk-enabling-classic-closing-handle
https://winclassic.boards.net/thread/2058/classic-uwp-fix
https://winclassic.net/thread/1889/classic-taskbar-fix

The "Classic Taskbar Fix" mod seems to have been replaced by the "Classic Task bar 3D buttons Lite" mod.

I would suggest to replace the above links to Windhawk mods by these:
https://windhawk.net/mods/classic-theme-enable
https://windhawk.net/mods/classic-uwp-fix
https://windhawk.net/mods/classic-taskbar-buttons-lite

[oep42]

Three other suggestions for improvement of the tutorial:

It is not immediately obvious, that "ClassicThemeTray" is not needed when skipping points 2, 3, 4, 5, and 6. So I would suggest to move the sentence "To enable the Windows Classic theme (which is more properly should be called the absence of themes) you would need a program that can switch the Classic theme from a command line, such as ClassicThemeTray or equivalent." to the beginning of point 2.

I would suggest to add something like this to point 1:
Windows Classic theme is not compatible with Windows 10/11 Task Manager. Before enabling the Windows Classic theme, install the Classic Task Manager.

When using OpenShell 4.4.191, it does not make sense to first install its unpatched version in point 8 of the tutorial, and after that install its patched version in point 9. Then just install its patched version in point 8. It would be helpful to mention this in point 8.

[oep42]

Concering point 10 of the tutorial: Using Desktop Architect under Windows 11 to choose and adjust color schemes.

I tried to run desk2k.cpl from point 10 of the tutorial in Windows 11 (22H2). It worked a few times, and after that, it didn't work anymore.

When I tried the Desktop Architect utility as an alternative for it (mentioned here), I found out that it isn't possible to install this under Windows 11 (22H2). As a solution for this, I installed Desktop Architect on a Windows 8.1 system, and then copied its installed files to Windows 11. In this way, it is possible to use Desktop Architect under Windows 11.

The attached file contains these files of Desktop Architect for those who encounter the same problem.
Desktop Architect 2.11 Files.zip

[Anixx]

As the tutorial says, you should run Desktop Architect's installer in compatibility mode. Properties->Compatibility->WindowsXP

[oep42]

I tried to install Desktop Architect in these compatibility modes, which all failed: "Windows XP (Service Pack 2)"; "Windows XP (Service Pack 3)"; "Windows 98 / Windows Me". I tried it with and without a check mark at "Run this program as an administrator". Below is an image of a first and second try. With the second try (and next ones), a different error message appears; it seems to fail earlier.

[oep42]

I did not succeed to get the Classic Theme and the 3D Taskbar Buttons using the tutorial.

I skipped points 2, 3, 4, 5, 6, 13 and 16 of the tutorial. I installed Classic Task Manager, non-portable Windhawk 1.4.1, Explorer Patcher 22621.3527.65.5, the patched version of Openshell 4.4.191, and 7+ Taskbar Tweaker 5.15.1. Instead of the program of point 10, I installed Desktop Architect 2.11, but did not use it to change anything. I followed the points in the tuturial in the same order as in the tutorial. I added things to the registry as instructed in the tutorial. (I changed the start menu icon and some settings in 7+ Taskbar Tweaker. I did not try any alternative or additional mods.)

[oep42]

I did restart the PC many times to no avail. The problem seems to be that mods that are enabled in the Windhawk user interface, do not work. The skipped steps are not related to this problem. Any suggestions for a solution for a mod that is enabled in the Windhawk user interface but does not work?

Additional question:
I may have to start again from scratch and only enable the mod "Enable Classic Theme by handle method", to find out a way to get this mod to work. I could only redo the beginning of the tutorial, by just installing the Classic Task Manager and then installing the "Enable Classic Theme by handle method" mod. If only this mod would be working, would this then be visible because of a different looking Windows user interface? (If so, I could concentrate on just getting this mod to work.)

[Anixx]

1. The clssic theme enabler may fail to start in time for Explorer but it always affects the programs that start after.
2. The 3d taskbar buttons mod works always after being enabled. We do not know instances where it does not work. It starts instantly and does not require explorer restart.
   If these mods do not work, this means your Windhawk installation is broken.

[levitation]

@oep42 Did you get your problem solved? If not, would you like to try an updated classic theme enable mod I have just published? One of the updates in this mod is handling certain cases where the old mod would have failed to activate classic theme.

The readme of this mod contains also updated version of instructions, which is partially based on instructions here, but there are also various details I have updated or added.

https://windhawk.net/mods/classic-theme-enable-with-extended-compatibility

[oep42]

@levitation I was unable to solve my problem and gave up on the Classic Theme for the time being.

Thank you for creating the "Classic Theme Enable with extended compatibility" mod and its extensive documentation, which looks very promising.

When I have time, I will try to install the Classic Theme again using your mod and its documentation. I will report here if it works for me.

[oep42]

@levitation I tried the Classic Theme Enable with extended compatibility mod and it works very well. This is what it looks like:

I give some more feedback here.

[vault-thirteen]

Hello there.

I have read about Windhawk mod mentioned in the first message of this thread and it says that the mod requires to install many other mods while it breaks a lot of things ... Moreover, I see that task bar in the screenshot of the first (top) message is not a good old task bar from Windows 2000/XP, while it looks like a modified Windows 10 task bar.

My question is following. Is there any simple solution that looks like real Windows 2000/XP, does not break anything and is as easy as clicking one button ?

Thank you.

[Anixx]

@Anixx Thanks, I didn't know. Was this discovered recently?

As I understand it, the main quest was to have DWM off but still having 3D acceleration working in games and other apps. This is quite complicated to do. If you do not need the 3D acceleration at all, you can easily switch off DWM by disabling the video driver.

[OrthodoxWindows]

That is all speculation because you do not have the source code, where as the bugs found while classic theme is enabled is not speculation. And the few who want classic theme may not be worth the money to spend on their programmers time to fix those bugs.

What you are referring to? What bugs? If we are not considering third-party software, the only things by MS not compatible with Classic theme were a few of Control Panel pages, but they are deprecated anyway now, in favor of the Settings app, which works in Classic theme just well. The taskbar while was imcompatible out of the box, can be fixed by a Windhawk mod (and it is also deprecated now).

Indeed, bugs concerning Win32 compatible elements (usually XAML) are very few in number. There are just:

• Buttons too thin in dialog boxes (solved with a Windhawk mod)
• Some control panel pages, and the task manager that do not open (solved by editing resources)
• Incompatible taskbar (solved with a Windhawk mods)

All other bugs, it seems to me, are related to modernUI type elements, sometimes inserted in the explorer.

[Anixx]

Buttons too thin in dialog boxes (solved with a Windhawk mod)

This is not related to classic theme at all, it exists in all themes.

All other bugs, it seems to me, are related to modernUI type elements, sometimes inserted in the explorer.

What are you referring to? What other bugs?

[OrthodoxWindows]

Buttons too thin in dialog boxes (solved with a Windhawk mod)

This is not related to classic theme at all, it exists in all themes.

Is the issue is fixed by this Windhawk mod: https://windhawk.net/mods/classic-taskdlg-fix

[OrthodoxWindows]

All other bugs, it seems to me, are related to modernUI type elements, sometimes inserted in the explorer.

What are you referring to? What other bugs?

I'm thinking, for example, of the bug where the immersive context menu disappears in the explorer and the taskbar.
But this kind of bug is not only a issue for the classic theme, but also for custom visual styles.