I get this error message when applying WinPaletter changes:

note that the only change made through the app compared to the Windows settings is the color of the status bar.

Windows 11 22H2 stable
Skin: bliss OS
Skin mod: SecureUXTheme
WinPaletter 1.0.6.3

Files
colors settings.zip

Feature Requests:

#4
Needs more definement to find. The User who posted & myself had to look around. I actully did know, then forgot.
Reason the hover mode fooled us.
Add to your main page https://github.com/Abdelrhman-AK/WinPaletter.
Need Directions or screenshot with new labeling. Reason: your pictures can't show the hover name.
So the reason for a re-design to replace the mouse hover hidden.
Relabeling:
Currently says "Create New Theme (Palette) File.
Sugest the name has "Default Reset" added into it. Or a seperate labled Default button, for easy changes, reset & indefication.
Reason for lableing return to default button easily seen.
The file "Save Theme File" perhaps add Export/Import to name.

Main Window, ability to get into to see current Hex/RGB assigned color. Then you can write them down or screenshot, with #'s.
Your choice how/where, if you would assign the # into each line. If only one # fits comfortbly, add a expand to see both RGB & Hex. Need at leat one Number.
Code the line color number, when Windows Default color is on next to the RGB/Hex # show the word Default or D; Then when changed to a custom the "Default or D" disapears.
Having the exact # ability you can immediately know if your color is slightly off, or was changed, bumped, etc.
Knowing the true Windows Default RGB/Hex #'s, helpful, for customizing.
Particularly if you have multiple units you could pick assign different Hex/RGB for units, as a watchdog, or units needing attention are colored a particular color till fixed, then changed to another color or back to default. Also particular users or units in general, could be given a particlar color.
Abilty to say, Check if a unit has true default, with a easily seen Default On or Off, Custom Mode.
Windows Default Set &/or Custom Set, on main window. Having easy ideficataion you know if anyone has touched, experimented the unit.

Zip compress the .exe release. Then when unzipped, you see the true Date/Time released. Currently when downloaded becomes the Date/Time of download. Eliminates confusion for those that save & backup every file, & those getting the correct download, you know immediately which is which, by Real Time/Date.

Is it possible in Windows 10/11 to customize the scrollbars?
So far, I haven't been able to do so.

I just discovered the new functionality of WinPaletter, it's impressive, congratulations !

On the other hand, I have a remark to make: as indicated on the screenshot (as well as in a few other places), the PowerShell instances of the console are separate from the Command Prompt instances of the console and from the other instances of the console (External).
Yet PowerShell consoles are just instances of conhost.exe, like the Command Prompt and the externals.

I therefore propose to create a large "Console" category with three sub-categories: Command Prompt, PowerShell and Externals.

For instance, Window Metrics allows to make the window caption buttons rectangular in Windows Classic mode.

The current configuration makes it so that the volume indicator follows the accent "Active titlebar".As the title says it would be nice to have an option to customize it with a different accent color

hi, After resetting from the menu , my desktop blinks indefinitely, i had to reboot Windows to recover my desktop

I saw the warning but what are the issues?

Here the Windows Classic is chosen but the preview is not Windows Classic.

Also, I suggest to implement Windows Classic as a separate mode (along with Windows 8.1, etc) because its settings are common for all windows versions.

Here is the issue, in notepad the color is blue, in the preview it is grey. The same grey color remains under all color schemes. The menu item highlight color is also wrong:

The pictograms on the window buttons (such as the [X]) also seem to be of the wrong size.

After clean installing Windows 11 22H2 build 22622.590, and making sure all apps and frameworks are updated, when I try to launch WinPaletter, there are many NET Framework issues that occur when I use the app. This did not happen in previous versions. These issues occur when launching, when attempting to change settings, and even when closing the app.

The "Menu bar" item works only when flat menus are enabled. So, I suggest renaming the item to
"Menu bar (only for flat menus)"

I think (I'm not very experienced in programming, so I'm not sure), the function is quite similar to Win32 colors (GetSysColor), it's SystemParametersInfoA (https://docs.microsoft.com /en-us/windows/win32/api/winuser/nf-winuser-systemparametersinfoa). More precisely, I found SPI_GETFLATMENU 0x1022/
SPI_SETFLATMENU 0x1023 and SPI_GETGRADIENTCAPTIONS 0x1008/SPI_SETGRADIENTCAPTIONS 0x1009

The 3D menus are displayed perfectly in the previewer, except for an interior bar which does not display at all. This is a bar with the same colors on each side; this color is that of the 3D-Face setting.

In the picture it is the light gray line.
This issue is my fault, I forgot to tell you this in the past.

i want Windows settings background to remain white with only Apps background changing to black ,is that possible ?

Default Windows 2000:
Themeui.dll, -854

High-contrast white:
Themeui.dll, -853

High-contrast black:
-850, -851, -852

I think it would be a good idea to also offer the default Win95 scheme, as well as those stored in registry at \HKEY_CURRENT_USER\Control Panel\Appearance\Schemes.

I mean, this:

In the previewer the scrollbar does not reflect the "checkers" pattern that many classic color schemes (for instance, Windows 2000/XP scheme) show. This is because the pattern is defined by two different colors, not one.

Also, notice that

• the scrollbar in the previewer has some vertical border on the right, 1px thick that the real scrollbar lacks.

• the menu border (even in 3D menus mode) is thinner in the previewer, it is 1px thick, while in real menus it is 2px thick and those of different colors:
  

• The 3D windows border in the previewer (of Programs Container, Active Window and MessageBox but not of Inactive Window) has a grey 1px frame that does not change color with color scheme (that is, invariable):

Also, the fonts in the previewer do not use the systemwide font smoothing settings and the window control elements (the [X], [_]) have too small font size.

Obviously, it's possible to colorize the taskbar independently of the rest by setting the "ColorPrevalence" key to 2 :

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Personalize]
"ColorPrevalence"=dword:00000002

https://www.askvg.com/tweak-colorization-settings-for-titlebar-taskbar-and-start-menu-in-windows-10/

It works on Windows 10 (except on 2015 versions). On Windows 11, it works almost safely with Windows 10 taskbar and Windows 10 start menu enabled with ExplorerPatcher. With the Windows 11 taskbar, I have absolutely no idea.

Even by selecting 000000, the screen shows as gray.

v1.0.3.0
Build 19044.1862

hello
I am a fan of Windows 8.1 and Windows 7 and I use them on some of my devices
Is there a version of your software that works on Windows 7 and Windows 8.1
Thanks

Are there any plans to implement Window Metrics support (button size, window frame size, etc)?

The 1-px column in the inactive titlebar in the left-hand end is painted with right-hand gradient color.

Also, the menu's lower end is 1 px shorter than the window preview behind it, it is not technically a bug but may create wrong impression of appearance so I suggest to make the "active window" preview a few pixels shorter vertically or a few pixels longer so that the border to be fully visible:

Nothing works ; the fonts are displayed incorrectly (as indicated in the preview), the sizes selected are not the correct ones, WinPaletter cannot detect the previous settings, and it is not possible to apply the changes: either the police go back to "Consolas", or nothing happens.

I'm using the enhanced console/terminal (but I think the problem is the same in the legacy version, since the Raster fonts rendering method hasn't changed).

I think the selection box for Raster fonts should be different than for TrueType (vector) fonts, because each size represents a different raster font.
I'm not very familiar with the subject, but I found Microsoft documentation on fonts : https://learn.microsoft.com/en-us/windows/win32/gdi/raster--vector--truetype--and-opentype-fonts

For example, when setting the title bar to black, apps like mspaint are unable to display any text on the title bar due to the title text color conflict, ie same title text color as title bar color.

Being able to set the text color to something else would solve this issue.

Cursor colors not taking effect, despite enabling the toggle and activating automatic apply custom cursors in settings

In the previewer, the selected button uses the 3D-DarkShadow color, when it should use the WindowFrame color. Also, WindowFrame's color is named FrameButton (After Click) when it should be named FrameButton (Selected and After Click), since the border of the selected button uses the WindowFrame color.

Previewer :

System:

In both cases, the selected button is the OK button.

ExplorerPatcher is a personalization program for Windows 10 and Windows 11 that restores many Windows 10 user interface elements in Windows 11, including the taskbar, start menu, and system tray flyouts (wifi networks, clock, sound, battery and language bar). It also disables rounded corners (however, it cannot restore Windows 10 notification center). My suggestion is therefore to take into account the parameters in question in the accent color previewer, and in the accent color picker (ie, adapt the terms used according to the parameters activated in ExplorerPatcher).
I don't have Windows 11, so I can't test. It is however possible that I install it in a virtual machine in the future. Here is the ExplorerPatcher documentation : https://github.com/valinet/ExplorerPatcher/wiki/All-features
The developer has closed the discussion area, but it is possible to contact him on this thread : https://www.elevenforum.com/t/new-version-of-explorerpatcher.1991/page-43

On Win11 22h2 (build 22621.521), Winpaletter will not start, regardless if I run as admin or not.
Report.zip

If i start this above version i get:

`Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei WinPaletter.RescueBoxdlg.Timer1_Tick(Object sender, EventArgs e)
bei System.Windows.Forms.Timer.OnTick(EventArgs e)
bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4515.0 built by: NET48REL1LAST_C.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.

WinPaletter
Assembly-Version: 1.0.3.0.
Win32-Version: 1.0.3.0.
CodeBase: file:///C:/Optik/WinPaletter/WinPaletter.exe.

Microsoft.VisualBasic
Assembly-Version: 10.0.0.0.
Win32-Version: 14.8.4161.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.

System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4488.0 built by: NET48REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.

System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4515.0 built by: NET48REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.

System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4395.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.

System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4515.0 built by: NET48REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.

System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4341.0 built by: NET48REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.

System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4161.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.

System.Runtime.Remoting
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4161.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.

Animator
Assembly-Version: 1.0.3.0.
Win32-Version: 1.0.3.0.
CodeBase: file:///C:/Optik/WinPaletter/WinPaletter.exe.

ColorThief.Desktop.v46
Assembly-Version: 1.1.0.1.
Win32-Version: 1.0.3.0.
CodeBase: file:///C:/Optik/WinPaletter/WinPaletter.exe.

Cyotek.Windows.Forms.ColorPicker
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.3.0.
CodeBase: file:///C:/Optik/WinPaletter/WinPaletter.exe.

System.Management
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4435.0 built by: NET48REL1LAST_C.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll.

Accessibility
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4161.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll.

mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4161.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.

System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4161.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
`

In default Windows schemes, the font in the active title is bold. This is configurable but in Win Standard scheme and others it is the case.

My friend is on Win11 and when he turned off blur to test it and pressed apply, explorer restarted and he couldn't use the start button or widgets, and when he tried to open Notepad it says Class not registered.. When he tried to turn blur back on explorer closed but never reopened and the app froze.

When navigating between Win32 color schemes, I noticed that the HotTrackingColor and 3DDarkShadow settings are always the same in each color scheme. However, if I click on "Current applied one" or on "Default Windows 10/11" these parameters are correctly modified.

When pressing this button only a few elements are affected while other remain colored as the current scheme, creating a mixed scheme.

изображение

Maybe this button is not necessary as there is already a set of preset schemes? Or maybe it should apply one of the preset schemes fully.

Also, since it is functionally similar to the button "Default Wondows 10/11", should not they be put together?
Or maybe just add the "Default Windows 10/11" to the list of preset schemes?

This is the line normally supported by 3D-DarkShadow. When manually changing the 3D-DarkShadow parameter, the line (botton ClientEdge line) is displayed correctly.

Here is the line :

After I upgraded from 25227 to 25231, WinPaletter's styles were no longer working on my system. I tried relaunching the app to see if it would allow me to change the colors again, but I found the app was not able to launch itself.

This happens for all chosen themes.

It's the same visual style, except for a few differences in the title bar buttons.

On recent versions of Windows 10 and on Windows 11, this visual style can create problems with dark App Mode, a warning message on the subject can be added.

See title. This appears to occur with any palette change I've attached my .wpth file.
https://drive.google.com/file/d/1DI6BWsl4ld12lSMNFm98xXWLeBcEWf-v/view?usp=sharing
Edit: For some reason, the UAC text and the volume slider color are both determined by the active titlebar color. Please make this more clear.

There is "Windows Classic" scheme in WinPaletter, but it is not the same as to Windows 2000 / XP classic scheme, the button face color, for instance is different.

I hereby add the Windows 2000 /XP scheme reg file.
Win2000.zip

Also, the schemes were usually stored in registry at
HKEY_CURRENT_USER\Control Panel\Appearance\Schemes

Currently WinPaletter does not load or store schemes to/from this place.

The high contrast mode is a mode introduced in Windows 8, to compensate for the discontinuation of support for the classic theme for visually impaired users. For Win32 programs, it uses the Aero Lite visual style in a particular mode (much like Aero's "Dark" mode), which forces rendering by Win32 color settings. In UWP/WinUI apps, it forces the use of Win32 color settings, which is the only way, since UWP apps don't work with the classic theme. The parameters used are only certain colors, less than with the classic theme. Tomorrow I will post the links to the Microsoft documentation on this subject, as well as the research I have done on the parameters used, and the results on the Win32 and UWP type elements and for the Windows 10 taskbar and start menu (I don't is not sought for Windows 8 and 11).

It seems to me that the result Win32 programs are almost between Windows 8/10/11, but much less the UWP type elements.

On Win10 21h2 (2009 build 19044) Winpaletter v1.0.6.1 does not start.
The details of the JIT Debugging error are not displayed.

• Date of report: 13 ноября 2022 г. - 21:19:21
• OS: Майкрософт Windows 11 Корпоративная - 10.0.22623.885 - 64-bit
• WinPaletter Version: 1.0.6.2

• Error Message:
Ссылка на объект не указывает на экземпляр объекта.

• Stack Trace:
в WinPaletter.Localizer.Populate(List`1 PopCtrlList, Form Form)
в WinPaletter.Localizer.LoadLanguageFromFile(String File, Form _Form)
в WinPaletter.My.MyApplication.MyApplication_Startup(Object sender, StartupEventArgs e)
в Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnStartup(StartupEventArgs eventArgs)
в Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

First of all, thank you for your great project, which allows you to add some order to the mess that modern Windows represents with regard to personalization.

In the Win32 controls configuration window (Win32UI), indicate that changing these colors requires a session restart. Indeed, it is; but there are many older win32 control color changing programs that support changing colors directly, just by clicking the apply button (without having to restart the session). This has been possible since the very first version of Windows (so I guess it shouldn't be very complicated to implement).

So my suggestion/request is to add support for directly changing the color of win32 controls, with no logout/login required.

There are many older tools with similar functionality; however, some parameters (such as menubar or menuhilight) were added later, so the old tools do not change all colors.
If you want examples, I can give you the links (however, I have only a few open-source examples, and none in VisualBasic.NET).

As you probably already know, Windows contains .theme files to automatically change the appearance of the system. .theme files are able to change colors (win32), mouse pointers, system sounds, wallpaper, screen saver, window metrics, visual styles from Windows XP, and accent colors from Windows Vista.
All of this still exists on Windows 10/11 (except for the windows metric which no longer works in .theme files). https://docs.microsoft.com/en-us/windows/win32/controls/themesfileformat-overview

However, some elements are not supported:

• the precise DWM\UWP accent color settings (.theme files only support settings present in the settings app)
• The visual effects settings (in particular those of the UserPreferenceMask key, such as Flat/3D menus)
• Other visual settings scattered here and there in the registry

As you can see, some of these settings are supported through WinPaletter (in addition, WinPaletter supports colorization of the mouse pointers).

So my idea is to add command line support for applying a .wpth theme (like WinPaletter.exe apply aero.wpth), and ideally some settings individually (however, the important thing is especially the possibility of applying a .wpth theme on the command line).

For examples, I have the Remetric/NoMeiroUI example, which contains both the ability to apply a full scheme and settings individually.
https://github.com/Tatsu-syo/ReMetrics
https://github.com/Tatsu-syo/noMeiryoUI

The "Gradient titlebar for classic apps" and "Enable flat menus" both affect the User Preference Mask registry key.

Yet, they are placed separatly and even have tifferent switch appearance ("Gradient titlebar for classic apps" has possibly not intended black background).

Would not it be more logical to place them next to each other and in the same style?

Hello! This is a great tool!

But Win32UI tab does not have a preview. Is it possible to add a preview for this set of customizations?

Some people still use Windows Classic, and some apps just do not use theming at all, defaulting to Windows Classic (for instance, CPU-Z and Winevdm).