To be fair to Naroon, I don't think his methods are actually illicit either. The stardock software user base has quite a bit of Windows tinkerers... Sure there are programs such as explorerpatcher, for example, that might not be recommended because it can sometimes break certain functions during a windows update. But, realistically there are a lot of users here that use start 11 that have also used explorerpatcher. This is because we all desire to modify Windows in some way even though we do not always agree as to how we want to do that. It can be through windowblinds or start 11 reg edits or even a themepatcher; at the end of the day we are all the same group of people wanting to modify windows.

Phoenix1, let's get one thing straight: What I stated was that there was a time here when using and/or advocating for software which altered system files and discussing it was not tolerated, and went on to explain that altering system files voided one's OS warranty.

Take a look here about what I'm referring to: System file security cracking software altering uxtheme.dll security, and Brad's pov regarding it.

I also stated that changing or "hacking" registry keys is not hacking in the sense of breaking into a computer system for nefarious purposes, nor is it "ethical hacking" to reveal weaknesses which need repair for the general good: Refer to Neil's statement.

Nowhere did I accuse naroon1 of doing anything illicit, so I will repeat my warning regarding not putting words in my mouth.

We all may wish to alter the appearance of Windows, however, all those methods are not equivalent. Stardock uses methods which do not alter system files. Other software euphemistically termed "patcher" software does.

A bit farther afield, look at how the patchers and other customizing software cause problems with SD software and where those folks come for help, thinking the SD software is the problem. Where are those other software companies when their "patching", etc. software causes problems?

Dr, I agree fully with Brad's point. It is well stated.

I do know I have been around quite often with helping navigate the explorerpatcher breaking on a windows update issue. It is both true and unfortunate that people do not know what they are getting into with these methods.

Realistically, right now the path of Windows customization is a bit muddy between these two methods. Even if we take windowblinds 11 as the safer method versus themepatcher, which it is, you also have to take into consideration the state windowblind themes are going right now. On Windows 11, 9 times out of 10, for a theme to look right the explorer tabs need to be removed with a program such as winhawk or explorerpatcher for the theme to look right. This is the artistic direction right now. I know it is not the intention of development but it is very much the state of Windows theming right now.

Personally, I am more of an advocate to migrating towards the Windows 11 parts. But it is not what is popular right now. The patcher method is pretty dominant with Windows 11 themes.

I do and I accept "less than perfect" appearance over the compromise of system security: Whether system files are altered, or whether signature verification is suspended, system security is compromised. For me, that and warranty voiding are the  'line in the sand' issues. When you suspend/void the signature verification, the end result can be far reaching and not good.

Even supposedly safe "Windhawk" carries a warning before choosing to install it, as gHacks points out: "A click on install displays a warning that modifications may damage the system, violate privacy or do other harm. Select "accept risk and install" to go ahead with the installation, or cancel to stop it.

Real [original] OS Customizing simply had an entire replacement of the OS Shell [there were many] and Explorer.exe simply was never loaded at all.

There was no reverse engineering of anything....you just had someone like LoneRunnr code Litestep from 'scratch' and configure it to be a text-edit for anyone to design their own interfaces.

Stardock's software was designed specifically to work with Microsoft's Shell and was entirely legitimate being formal 'Partners' with MS.

The UXTheme 'patcher' was a reverse-engineered [and thus illegal] MS dll that evolved at the time of WinXP.  Because it was unsanctioned MS had no interest in maintaining its functioning and pretty much 'broke' it with every OS update.

Yes, people will explore all sorts of ways to alter a system, but when they do...and their system breaks...they cannot go crying to Microsoft.

Same applies with un-sanctioned mods affecting Stardock's software.  You cannot ever expect Stardock to bend over backwards to solve problems you initiate through ignorance.

The promoting of unsanctioned hacks isn't desirable as it will invariably lead to the naive coming to Stardock claiming Stardock's software doesn't work [or similar], when it was never intended to work on an altered OS. 

BTW...the 'error' you got if/when Litestep went wrong was often "Shell not found.  You must reinstall Windows".

You didn't...you simply had to point the OS to Litestep again.

BTW...the windows in Litestep skinned correctly with Windowblinds...simply because no actual MS files were altered by the Different Shell use...;)

I think sometimes I get curious if I can think of a way to get theming to work better on Windows 11. I actually do agree that these patching methods aren't very good. However, for a theming enthusiast I am not sure where else they can go. The problem isn't how a theme looks on windows 11, the problem is that the themes that are being created are not being designed for windows 11 parts. A true windows 11 theme actually does look good without all the hacks.

This curiosity sometimes makes me wonder if windowblinds can continue to be carried on to the next OS or if it will fade away with Windows 10 in time.

A clever developer may figure out a way to get those explorer tabs looking better with the themes that are being created and I think that is what I am trying to advocate. 

Or...come up with a better (viz SD) app which skins without any problems which probably won't happen because of the already crowded field of Explorer replacements. There are >100 such replacement apps.

I use Directory Opus because of its media player, etc. There are however free ones as well: https://www.makeuseof.com/tag/best-windows-file-explorer-replacements/

or, https://alternativeto.net/software/windows-explorer/

You are not Wrong Phoenix, The Devs who work with Themes Have already come up with "A Way To Get Explorer Tabs Looking Better With Themes" Win 11 is no longer an Issue To Theme Users and has not been for a while now. Its my pleasure to work with some talented people in The Theme World, One in particular Has written several ExplorerPatchers and works closely With Others who create The Competitor for Win 11, hence why i have no issues moving from were we are now, with Win 11, into a Windows 12 World, using Themes to Fully Customise my PC. No longer do peeps who use Themes, need to Patch there system at all(although the name still sticks somewhat), 

This thread has run its course.