Windows 11 update doesn't skin taskbar or windowframes

from WinCustomize Forums

Just what it says. Turned on my computer just now, and my taskbar and nothing is skinned. 

Windows updated to 25H2 a week and a half ago and everything was working fine until this morning's update. It installed the 2026-03 .NET 8.0.25 Security Update for x64 Client (KB5081277) yesterday and I had no problems; this morning it installed 2026-03 Security Update (KB5079473) (26200.8037) and my customizations are GONE. 

Anybody else have this unpleasant surprise? Do I need to roll back the update? Do something else? 

skin studio skinning help windowblinds 11 taskbar windowframes os customization
9,361 views 4 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. I am the same Windows 11 v25H2 (OS Build 26200.8037) but I don't see the issue with my Windowblinds11 and Start11v2 running. Which Stardock software you have installed that change/customize your taskbar and WindowFrames?

Thank you,
Basj,
Stardock Community Assistant.

Reply #2 from WinCustomize Forums Top

Just Windowblinds 11. UPDATE: turned off my computer to go shopping, came home and my taskbar is back. Yay.  Problem solved itself. 

The Political Machine 2024
Reply #3 from Stardock Forums Top

Quoting jbstory, reply 2

Just Windowblinds 11. UPDATE: turned off my computer to go shopping, came home and my taskbar is back. Yay.  Problem solved itself. 

"Turn it off and then turn it on." is age od support advice for good reason: It allows MS's Wizards to repair things which might have gone awry if you don't reboot often. Also, I run sfc /scannow occasionally from an elevated cmd prompt to fix system files which can get corrupted.

+1 Loading…
Reply #4 from Stardock Forums Top

Quoting jbstory, reply 2

Just Windowblinds 11. UPDATE: turned off my computer to go shopping, came home and my taskbar is back. Yay.  Problem solved itself. 

Great, really glad to hear you have resolved it. Yes, rebooting is one of default way to test issues. Another one is restart Explorer.exe.

Thank you,

Basj,
Stardock Community Assistant