-
-
Notifications
You must be signed in to change notification settings - Fork 57
Can't apply any of the OS theme options (for example Windows 7/8.1) on Windows 10 (Error) #212
Comments
Open each Windows aspect and make the toggles enabled then press on 'Load into current preferences', and re-apply the theme and finally tell me if it worked. |
Sadly it didn't. Still experiencing the same errors. |
I have the same issue. Trying to apply Windows Switcher changes after downloading WinPaletter today, but it says it's disabled along with most (if not all) of the other features. Deleting the registry key and starting over didn't seem to change anything. |
|
@Jonhhn17818 I misunderstood you before. It's not feasible to apply Windows 7/8.1 themes on Windows 10. I've developed an OS switch feature in WinPaletter, allowing users to create a single theme file that's compatible across various operating systems, from Windows XP to 11. When switching the OS in WinPaletter, the preview changes accordingly, enabling users to visualize how their theme file would appear on different operating systems. When applying a theme file in Windows 11, it will implement the colors and theme specific to Windows 11. Similarly, if you're using Windows 7, it will adopt the theme elements pertinent to Windows 7, and the same principle applies to other operating systems accordingly. |
After some rest I realized that there may have been a conflict with another program I have used for years called Regardless, I have exported the registry below using version |
I tried to reproduce this issue after importing your registry, enabled all aspects toggles (except for Windows Terminal Stable 🔴 ), and found some aspects skipped:
There is another issue that is simmilar to this (for Metrics and Fonts only) and I can't reproduce it too: #218 (comment) If these are the aspects not being applied for you, let me know and I'll fix it. If not, try using WinPaletter |
My apologies, I wasn't exceptionally clear in my last post. Both WinPaletter |
No problem! I am fixing now small issues in applying process. |
I'll add a warning at WinPaletter startup about potential third-party program conflicts too, as another issue happened before due to a conflict with ExplorerPatcher. |
I've tried to put the Windows Vista theme on Windows 10, but I can't since it just says that most of the stuff are disabled!
Here's the log it gives me!
[info] WinPaletter will apply theme from Windows 10's section
[info] 20:30:11: Applying started
[apply] 20:30:11: Saving theme info into registry
[time] It took 0,002 seconds
[skip] 20:30:11: Skipping WinPaletter application theme as it is disabled
[time] It took 0,038 seconds
[skip] 20:30:11: Skipping Wallpaper as it is disabled
[apply] 20:30:11: Applying Windows 10 scheme
[time] It took 0,004 seconds
[apply] 20:30:11: Applying Windows 10 LogonUI
[time] It took 0,002 seconds
[apply] 20:30:11: Applying Classic Colors
[time] It took 0,039 seconds
[apply] 20:30:11: Applying Windows Effects
[time] It took 0,007 seconds
[skip] 20:30:11: Skipping Windows Metrics and Fonts as they are disabled
[skip] 20:30:11: Skipping Windows Switcher (Alt+Tab) Appearance as it is disabled
[time] It took 0,001 seconds
[apply] 20:30:11: Applying Wallpaper Tone
[time] It took 0,004 seconds
[skip] 20:30:11: Skipping Command Prompt as it is disabled
[skip] 20:30:11: Skipping PowerShell x86 as it is disabled
[skip] 20:30:11: Skipping PowerShell x64 as it is disabled
[skip] 20:30:11: Skipping Windows Terminal Stable & Preview as they are disabled
[apply] 20:30:11: Applying Screen Saver
[time] It took 0,002 seconds
[apply] 20:30:11: Applying Sounds
[time] It took 0,22 seconds
[info] 20:30:11: Saving Windows Cursors Colors to registry
[time] It took 0,014 seconds
[apply] 20:30:11: Rendering Windows Cursors
[time] It took 0,154 seconds
[apply] 20:30:11: Applying Windows Cursors
[time] It took 0,023 seconds
[time] Total applying Windows cursors took 0,204 seconds
[success] 20:30:11: Applying theme done. It took 0,601 seconds
[info] 20:30:11: All operations are done
I did also did the thing which removes the Microsoft Defender detection and still nothing changed!
The text was updated successfully, but these errors were encountered: