Hey!

I'm not sure how much of 11 is customizable given how many things are hard coded these days. It's a shame.

Hey!

The parts in the Basic section aren't used in Windows 8 onwards except for MDI windows. You can open mmc.exe and click the restore button of the MDI window to see the basic window frame and controls in an MDI window.

https://www.mediafire.com/file/2qlrw6vlo8ehlaq/Skyrim_Cold_Steel_V2_1903-22H2_updated.zip/file
this one is failling also

https://www.mediafire.com/file/nb8obhzrnvssuhc/Rockstar+Orange+Black.msstyles/file
But this one works just fine

https://prnt.sc/E-ZNLJ4-XBPI
My version of windows 10

I was able to get the Skyrim theme to test, though it took a couple of tries:

https://prnt.sc/VJ1q6AGiG4WN
Why is this like this?

It's been so long I can't remember, but it may be the hack to have aero blur behind the programs list in Vista/7, or something else. I had done it as well in my theme.

Which version of WSB are you using? For me it's been intermittent as to whether testing would work or not.

Open ANY 10 0r 11 msstyle in WSB and it will show as 8.1 in the title bar. Always been like that.

I'm suddenly getting the same error message as you on a msstyle that was testing fine a week ago. For some reason a shell folder keeps appearing in the Program Data Testing folder that shouldn't be there. I've tried every trick I know to fix this but nothing works including saving first, replacing the shellstyle etc.

The latest beta will show Windows 10 or Windows 11 unless the theme has been modified in a way that causes the version check to get confused. Can you send me the theme that used to work but doesn't work anymore so I can see why it may be failing?

In the titlebar it states that it's a Windows 8.1 theme. Windows 8.1 themes are only supported on 8.1 and not any other version of Windows. I will be attempting to add the ability to port 8.1 themes to Windows 10 and 11 in a later release.

By default when opening WSB it loads the default Aero theme. You can just start modifying it right there.

For what to edit or what certain sections do you can refer to the maps located in the Maps subforum https://www.vistastylebuilder.com/forum/index.php?board=18.40
Do note however, that certain items may be different depending on which version of Windows you're running however.

For StartIsBack (or StartAllBack for Windows 11) you can make a copy of one of the themes it installs with located in C:\Program Files\StartAllBack\Styles

From there you'll want to just focus on the 'Start Menu' and 'Taskbar & System Tray' locations to modify those sections. For SIB/SAB themes they have to be applied from within SIB/SAB and don't require a UXTheme patcher.

You can start with the default Aero theme in Windows, personally I find that to be the best method.

A UXTheme patcher will be needed, as for StartAllBack (which is the Windows 11 version of StartIsBack) I'm not sure of its capabilities since I haven't used it since Windows 8, however back then it did support theming by modifying the msstyles file. I think the current versions may include their own mini msstyles files containing just the startmenu and taskbar resources, however I'm not sure if those need to be edited separately or not.

One thing to note about WSB and Windows 11 is that it can't theme the start menu, taskbar, new context menus and more because they are not a part of the .msstyles file. You can grab the latest beta which is able to modify the Windows 11 msstyles file, however since so many parts now use xaml/WinUI you can't really change as much as you used to on previous versions of Windows.

Latest beta can be found here: https://www.vistastylebuilder.com/forum/index.php?topic=2615.0

I haven't been on Insider builds for a while. When 1703 releases I'll take a look at it.

This is amazing, thanks so much.  Should be stickied in the forum!

Cheers!

Stickied

I think the caption text is controlled by Windows itself as it'll change from black to white depending on the background color, I'm not sure if you can change it from the msstyles or not.

I doubt GDIPlus is related to the msstyles directly. Do you use GDI++ or WindowBlinds/WindowFX (I believe these override some stuff in gdiplus though I could be wrong)

I'll see if I can update WSB to allow custom DWM mapping here soon. The problem is that for 8 and onwards I was just using some old porting code which hardcoded the DWM property maps to the newer states. So it was like part x = part y. I should be able to use XML like the other half of the conversion process to make porting easier.

Make sure that no properties are missing under the DWMWindow (Windows & Caption Buttons > Aero > DWM Window) class when comparing your theme to the default Aero. If any properties there are missing, DWM will crash.

I'm not entirely sure if this would be caused by 1.5.6.3 or not since those metrics are just normal properties. You can try changing the caption metrics in Fonts, Colors, & System Metrics > Fonts & System Metrics or change the content margins in the various states under Windows & Caption Buttons > Aero > DWM Window > Controls > Captions > Window

Be careful, most blackscreens are caused by the DWM classes being different. That's why in the beta you can't change them.

I don't think it's possible.

255, 255, 255
#FFFFFF

The color search has to have all three components.

Actually you should be able to do so with a StyleScript:

Code:

<stylescript>
	<remove>
		<class class="SIB_StartPanelPriv"/>
		<class class="SIB_StartPanelComposited::StartPanelPriv"/>
	</remove>
</stylescript>

Save that as SIBClassRemove.xml in your WSB\Data\StyleScripts folder and then hold Shift and click Import Stylehack and select SIBClassRemove then click Apply StyleScript.

If you manually remove it from the CMAP WSB will remove the properties on compile. Editing the CMAP requires hex editing though.

What was the error message?

Thank you,
It is no longer possible to modify the Taskbar in Windows 10 final version?

I haven't tried to customize 10 but as far as I know you can't.

They're created using the beta; http://vistastylebuilder.com/forum/index.php?topic=2130.0

It doesn't really support Win10 but it still works.

Editing XAML is easy if you're making your own application, but if you're wanting to customize the built in apps it's probably not going to be easy.

can we expect VSB support for windows 10

the UI is far to white for my liking

will need to be extensivly modded before i can use as a daily driver

What do you mean by Win10 support? To my knowledge the current version works with 10.

Also the UI uses the same parameters as all other Win32 apps, you can change it in Fonts, Colors, & System Metrics > Fonts & System Metrics

I hate those dark jumplists and context menus. Should only be dark if you are using a dark theme.

Microsoft doesn't do consistency.

I feel that may be optimistic, windows controls have been predominately blue for years already anyway.

I'm surprised you can even still change the background of the taskbar to be honest.

One of those might be a mask. I believe in 8 there was the bitmap and then a mask over it for the color animation.

Does this happen with all menus, or just that program?

What was the last property you copy/pasted?

Is UxTheme patched? If you're using UxStyle as a patcher try restarting the UxStyle service.

I'm pretty sure this was in Vista.

The next build isn't going to have a timebomb, it was only there so it would kind of force everyone to be on the same version so I could make sure bugs weren't reoccurring in newer builds. I last spoke to Ave some time ago and he stated that he would create a COM component for creating the msstyles, that would allow me to use .NET to program WSB which would be a lot easier as I have more experience with it. This is also the primary reason I haven't put out a new build in some time.

Are those last two specific to 8?