|
|
Post by OrthodoxWin32 on Jul 1, 2022 15:04:51 GMT -8
The purpose of ThemeSwitcherScript and to be able to allow the user to patch his system with the addition of many customization tools at once, then to be able to apply themes natively supporting several customization tools. Finally, ThemeSwitcherScripts should facilitate the automation of Windows themes, which is currently impossible.
For creators, this means writing scripts on a defined template, which allows the user to apply their theme/visual style very easily. The goal is to remove the confusion between customization tools, and potentially some misunderstandings created by this confusion.
Supported tools are :
- Switching to Basic and Classic themes, using the ClassicThemeTray and BasicThemer5 tools. Credit to Spitfire_x86 and Alcatel (and Ingan121 for the original tool)
- Change of theme (for classic elements) via WinClassicThemeConfig. Credit to Franco Tortoriello.
- The change of .theme file (supported natively by Windows), with the WinaeroThemeSwitcher tool. Credit to Sergey Tkachenko.
- Automatic Windhawks mod toggle DISABLE-DWM-EXTENDED-FRAMES, useful for Basic and Classic themes. Credit to Taniko Yamamoto for the mods, and of course to Ramen Software, the creator of Windhawks.
- Big credit to anixx for the ideas of scheduled task foractivate the classic theme on startup.
In the future, the following tools will be supported :
- WinPaletter, to allow more advanced theme switching
- Toggle other Windhawk mods
- The toggle of some Explorer customization tools
And the following features will be added in the future :
- The switching of certain registry keys
- The support of automatic planning for the themes
A guide for theme makers, and maybe an ordering system to come. For now, only Windows 10 themes are included by default. Windows 11 themes will be included in the future.
Installation :
- Check your installation. ThemeSwitcherScripts can work on all versions of Windows 10 and 11, but currently works best in the latest versions of Windows 10. If you are using an older version of Windows 10, you will need to install Curl first. Curl is included by default from Windows 10 1803/Windows Server 2019.
- Run INSTALL.EXE, and follow the instructions.
- If your system contains several users, execute C:\TSS\INSTALL_ANOTHERS_USER.EXE after the installation for the 1st user, in the concerned session.
- Install Windhawks mods "Disable DWM Extended Frames", "Non Immersive Taskbar Context Menu" and "Disable Immersive Context Menus". "Disable DWM Extended Frames" is not included in the Windhawks store, so you have to install it by clicking on "Create a new mod" in Windhawks, then copy and paste the text from the "DISABLE-DWM-EXTENDED-FRAMES.C" file into the editor. Next, compile the mod.
Enjoy !
Limitations :
- ThemeSwitcherScript supports multi-user systems, but with one limitation: avoid using multiple user sessions simultaneously. This exposes you to a black screen on login, and it disrupts Windhawks, which runs in single-user mode. Additionally, it is important that all user accounts have administrative privileges. ThemeSwitcherScript is therefore currently not usable on public posts such as cybercafés or media libraries. This may be fixed in the future.
- The Basic and Classic themes are no longer officially supported by Microsoft, the display of certain programs may not be correct. Most of these problems can be easily fixed, search this forum for answers.
- If you use custom visual styles (.msstyle), use a patcher like UltraUxThemePatcher. SecureUXTheme does not work with ThemeSwitcherScript.
The current version is a pre-release, I cannot guarantee stability, use is at your own risk !
Latest Release :
|
|
|
|
Post by anixx on Jul 1, 2022 15:11:00 GMT -8
What does it basically do?
When using ClassicThemeTray, DWM is still running, by the way...
|
|
|
|
Post by OrthodoxWin32 on Jul 1, 2022 15:16:19 GMT -8
What does it basically do? When using ClassicThemeTray, DWM is still running, by the way... This facilitates automation; right now I have to manually change a lot of settings to change this or that UI element. The goal is also to be able to easily switch from a classic theme to a basic/DWM theme and vice versa.
For running DWM on ClassicThemeTray, I know. I just called "DWM" the "aero" themes because I didn't know what to name them.
EDIT: More simply, my goal is to make it easier to administer the look and feel of the Windows UI. Of course, this is just the beginning. |
|
|
|
Post by OrthodoxWin32 on Jul 3, 2022 15:29:52 GMT -8
Another potential use of these scripts; the problem of users unable to revert to the original configuration after trying the classic theme. If I can write a script properly to help bring back to the initial theme, that should partially solve the problem.
|
|
|
|
Post by OrthodoxWin32 on Jul 15, 2022 16:21:00 GMT -8
First Release - 1.0
- Compiled version of Windows visual style types switcher scripts - DWM-Effects/Basic/Classic - x64 and x86 versions - EN and FR versions - Compiled version of the test script for installing the programs necessary for ThemeSwitcherScript. If everything is installed correctly (programs, scheduled tasks and registry entries) the change in visual style must be taken into account at the reopening of the session. I am in no way responsible for any computer problem related to the use of ThemeSwitcherScript.
|
|
|
|
Post by OrthodoxWin32 on Jul 17, 2022 4:05:10 GMT -8
|
|
|
|
Post by OrthodoxWin32 on Jul 24, 2022 15:04:16 GMT -8
I found a way to add support for multiple user accounts with the classic theme  . This is an alternative way to start the scheduled task of classicthemetray and userinit, by checking the "start at logon" box rather than going through the userinit registry key. I will post this change soon. |
|
|
|
Post by OrthodoxWin32 on Jul 26, 2022 3:01:32 GMT -8
So here is the way to add multi-user support to ThemeSwitcherScript. That is, the ability to simultaneously run, for example, the DWM-styled theme (default theme) on User A, the Basic theme on User B, and the Classic theme on User C. Thanks to anixx for the original idea of the classic theme by scheduled tasks ( www.winclassic.net/thread/990/windows-classic-theme-on-1903 ). 1. move basicthemer2.exe to %userprofile%\TSS\basic2. move classicthemetray.exe to %userprofile%\TSS\classic
3. Repeat copying basicthemer2.exe to %userprofile%\TSS\basic and classicthemetray.exe to %userprofile%\TSS\classic for all other user accounts
4. In the task scheduler, create a scheduled task named basic, with this command : %userprofile%\TSS\basic\basicthemer2.exe, as a trigger for all users to login, and the BUILTIN\Users group for task execution. Check the Run with maximum permissions box case 5. Create a scheduled task named classic, with the following commands: C:\Windows\System32\schtasks.exe /run /tn Apps, %userprofile%\TSS\classic\classicthemetray.exe / enable, C:\Windows\System32\schtasks.exe /run /tn classic2 as the trigger for all user login, and the BUILTIN\Users group for task execution. Check the Run with maximum permissions box case 6. Create a task named classic2, with the command C:\Windows\System32\cmd.exe /c start userinit.exe, with the group BUILTIN\Users for the execution of the task, and select in the parameters of the task the rule If the task is already running, the following rule applies : Do not start a new instance7. Create a task named Apps, with command C:\Windows\System32\cmd.exe /c start C:\Windows\System32\ApplicationFrameHost.exe, with group BUILTIN\Users for task execution
8. Make sure all tasks are configured to run on any power mode.
9. Import this registry file (  WARNING, it is important to save the previous key before modifying ) :
It works on my system, but nothing tells me that it will work on other systems. It is therefore important to test it by taking maximum precautions. Please let me know if it works or not. When I'm sure it works, I could write an automatic installation script.
For the moment, it is impossible to install ThemeSwitcherScripts on part of the user accounts. It must be installed on all visible accounts (invisible accounts do not count).
WARNING : The BUILTIN\Users group depends on the system language ; for example, on my system, the group is named BUILTIN\Utilisateurs.
|
|
|
|
Post by OrthodoxWin32 on Jul 25, 2023 10:16:44 GMT -8
Changes and novelties: - Added a installer/uninstaller
- Added support for themes, with simultaneous change of .theme file, WinClassicThemeConfig schemes, Windhwawks Disable-DWM-Extended-Frames mod and theme type (Classic, Basic, DWM)
By default, the following themes are supported :
Windows (Windows 10 Aero)
Windows Light (Windows 10 Aero)
Flowers (Windows 10 Aero)
Windows 10 (Windows 10 Aero)
Windows Basic (Windows 10 Aero - Basic)
Windows Aerolite (Windows 10 Aerolite)
Windows Aerolite Autolorization (Windows 10 Aerolite)
Windows Aerolite Basic (Windows Aerolite - Basic)
Windows Classic (Windows Classic Theme)
Windows Standard (Windows Classic Theme)
High Contrast #1 (Windows Aerolite - HC)
High Contrast #2 (Windows Aerolite - HC)
High Contrast Black (Windows Aerolite - HC)
High Contrast White (Windows Aerolite - HC)
High Contrast #1 Classic (Windows Classic Theme)
High Contrast #2 Classic (Windows Classic Theme)
High Contrast Black Classic (Windows Classic Theme)
High Contrast White Classic (Windows Classic Theme)
It is of course possible to add other themes, the possibilities are endless.
|
|
|
|
Post by OrthodoxWin32 on Mar 22, 2024 4:36:11 GMT -8
Added support for Windhawk, and other settings stored in the registry. ThemeSwticherScript now installs its own reg keys.
Before releasing the new version, I need to speed up the theme change, and add support for switching other settings (including OpenShell).
Currently support is only for Windows 10, but I plan to add support for Windows 11.
Note: The demonstration is carried out on my main machine, which proves the stability on a real machine. This is also why the appearance is personalized on other levels (presence of PowerPro, no address bar in the explorer...).
The main issue for ThemeSwitcherScripts that I can't seem to resolve is automating the installation of Windhawk mods; I haven't found a solution for this, the user still has to manually install the mods after installing ThemeSwitcherScripts.
|
|
![[Win9x]](http://storage.proboards.com/6513581/images/ShYyDgYIKMJjewIFxpoY.png)
. This is an alternative way to start the scheduled task of classicthemetray and userinit, by checking the "start at logon" box rather than going through the userinit registry key. I will post this change soon.