SilverSage

Reply to Bringing a Windows Classic theme to Windows 11 in Stardock Blog Stardock Forums

Fair enough, and it cuts both ways. You are paying 0Patch to hold on to the thing you never gave up. I pay a subscription to get the look of it back. Neither of us got out of this for free, we just picked different bills. The Win10 VM sitting on a Win7 host is the part I did not see coming. Every setup like this I have run into goes the other way, old OS in the box, current one underneath. And the honest limit of my route is that a skin gives me the borders and the bevels back

Reply to Bringing a Windows Classic theme to Windows 11 in Stardock Blog Stardock Forums

Fair. The licence was in the price of the machine, and calling it free was sloppy of me. Point taken from both of you. What I was reaching for is a different thing, and it is not really about money. Classic was never a theme. Under 95 through 2000 that look was just the system metrics: border widths, title bar height, the 3D colours, all of it sitting in Display Properties for anyone who fancied lilac window frames. XP put the visual style engine on top, and "Windows Classic" in XP wa

Reply to Bringing a Windows Classic theme to Windows 11 in Stardock Blog Stardock Forums

The theme itself was not the thing with a price on it. The post says Windows Classic shipped as a default style at no additional cost, so if you already had WindowBlinds it turned up in an update. What costs money is WindowBlinds. Which is a fair thing to be annoyed about and I will not pretend otherwise. Microsoft dropped the Classic option after Windows 7, and the only route back is a third party skinning engine, so you end up paying to restore something you used to have for nothing.