With the WindowBlinds 11 Public Beta 2 release, we are creating this thread so that users can report any observed issues.
Obtaining WindowBlinds Beta 2
Object Desktop members can get the release from within Object Desktop Manager
Individual purchases (as well as Object Desktop Members) can also be obtained from your account page: https://store.stardock.com/myaccount/products
For guest check-out purchase (no account), from this link: http://www.stardock.com/support/productkeyretrieval
Reporting an issue
Please include the following for anything found:
Thank you for your interest and any time you put into making WindowBlinds a better product.
Sean DrohanStardock Support Manager
Why?Sean DrohanStardock Product Lifecycle Manager
Sorry Sean, it's because I see way too many negative comments and as a WB Skinner I don't want to install software that may interfere with that in any way. I will wait until all software is out of Beta and continue to design on Windows 10 using WB 10, Start 10 and SKS 10 until that time. I will however test my skins on Windows 11 though when I get that computer fully configured using the Beta 1 release of Windowblinds.
FF latest update works ok here mind you I'm running wb beta 1
I second that is that beta 2?
Or
I only see 11.0.1 in individual download is that Beta 2?
I second that is that beta 2?OrI only see 11.0.1 in individual download is that Beta 2?
Yes
A number of us internally have tried to reproduce this but could not:https://cdn.stardock.us/support/uploads/explorer_2022-11-09_12-15-21.mp4If you restart Windows Explorer, does that resolve it?If you do a clean boot, under a new Windows Administrator account as directed, does it still do it?https://forums.stardock.com/486023/windowblinds-support-faq#cleanbootSean DrohanStardock Product Lifecycle Manager
Seems to be just my user profile. To much of a hassle to migrate over to a new profile as I have many apps installed that are quite annoying to reinstall due to the nature of how the keys work be able to use them and where the point to. So I will just have to deal with the flashing buttons issue for now. Honestly Im not quite sure I will be using windows much longer. These limitations you guys say w11 has are really meh. If 3rd party devs can get them working with whats already still inside windows I cant see why you guys cant. Im about ready to just switch to linux and be done with this.
ODM continues to tell me to update WB11. Irritating.
I tried to install Windowblinds 11 to my Windows 11 rig. There is an issue keeping it from functioning. .....
Edition Windows 11 ProVersion 21H2Installed on 11/9/2022OS build 22000.1219Experience Windows Feature Experience Pack 1000.22000.1219.0
Device name ASUSProcessor AMD FX(tm)-6300 Six-Core Processor 3.51 GHzInstalled RAM 16.0 GB (15.9 GB usable)Device ID 8BFAB7EE-E882-4D81-B010-79E4DF790B46Product ID 00330-80000-00000-AA580System type 64-bit operating system, x64-based processorPen and touch No pen or touch input is available for this display
-- Ace --
Edition Windows 11 ProVersion 21H2Installed on 11/9/2022OS build 22000.1219Experience Windows Feature Experience Pack 1000.22000.1219.0 Device name ASUSProcessor AMD FX(tm)-6300 Six-Core Processor 3.51 GHzInstalled RAM 16.0 GB (15.9 GB usable)Device ID 8BFAB7EE-E882-4D81-B010-79E4DF790B46Product ID 00330-80000-00000-AA580System type 64-bit operating system, x64-based processorPen and touch No pen or touch input is available for this display -- Ace --
Hello,Sorry to hear you are having issues. Please try purge and reinstall steps as mention here : [Link]. Just make sure to redownload the latest version from your account page. Reboot after the purge. Reinstall and reboot again after the installation. Retest and report back here.
Thank you,Basj,Stardock Community Assistant.
Be honest I'm not that impressed it's really not that much of a change from beta 1 to Beta 2 right now. But then again it's. 0.1 different. I was just expecting a little more positive changes. It's still fights with start 11, it overrides start 11 really needs an option to don't override start 11 settings. I use start 11 to customize my start bar and menu and window blinds just throws that all away and does what it wants to do. It's still a work in progress I've never used Windows 10 I probably should just start using that with window blinds 10. If I get time perhaps I will play with that it's just a little busy this time of the year for me so I don't have time to play with the program as I would like.
I still can't get the titlebars on control panel and settings app with WB11 beta 2
Works fine for me.
Have to fully agree with you LightStar. I really thought i would jump on WB11 as soon as possible, then i read comment after comment about how it is fecking up peeps setups in one shape or form, i understand this is still a Beta and these issues can be expected, Hell, i have even commissioned two Bespoke Windowblind creations as i thought "These Will Be Ready To Go" when WB11 hits, but due to the Beta, these Commissions are still untested in WB11, and will not be until we have a more Stable platform. Yes i am going to still purchase WB11 when it is ready as Stardock has been central to my customising needs. I will stick to Themes right now, and even after we have a Final WB11, i will create a balance between the two methods to change the look of my Desktops.
Hi SimplexDesigns,
Thank you for taking the time to test and confirm that the issue does not exist on a new user profile. It is much appreciated!
Paul ScrogginsAssociate Technical Support Analyst
ODM is in need of an update and is something we are progressing with.
Sean DrohanStardock Product Lifecycle Manager
I can give a roadmap on this
1. If you run on an hdr enabled device you will probably have some bugs regardless.
2. If you have hdr disabled Beta 1 should work fine on you device
3. If you want hdr enabled you will need beta 2. BUT..... If you have an AMD graphics card you may experience some of the listed issues.
Therefore,
If you need hdr AND have AMD graphics then you should wait until beta 3 drops
If you are like me and have something along the lines of an NVida card then you will have a stable build of Windowblinds 11 with beta 2.
For me personally my biggest grip with Windowblinds 11 right now is more of the lack of support for explorer tabs more then software issues. I could disable explorer tabs but once I tried out the skin "7 for 10" by 2of3 I then decided it looked really good on Windows 11. I believe this skin really showcases how Windows 11 is supposed to be skinned. Too bad the explorer command bar can't be skinned as that would fix a lot of skins in itself, for now we have to rely on artists.
A minor issue: After applying many skins, taskbar buttons get corrupted when hovering over them (see screenshot). The problem goes away after a short while.
Classy & Rhythm by Lightstar
Windows 10 Home 22H2 19045.2251I'm also running Start 11 v1.31 & Fences v4.0.7.2
I can give a roadmap on this1. If you run on an hdr enabled device you will probably have some bugs regardless.2. If you have hdr disabled Beta 1 should work fine on you device3. If you want hdr enabled you will need beta 2. BUT..... If you have an AMD graphics card you may experience some of the listed issues.Therefore,If you need hdr AND have AMD graphics then you should wait until beta 3 dropsIf you are like me and have something along the lines of an NVida card then you will have a stable build of Windowblinds 11 with beta 2.For me personally my biggest grip with Windowblinds 11 right now is more of the lack of support for explorer tabs more then software issues. I could disable explorer tabs but once I tried out the skin "7 for 10" by 2of3 I then decided it looked really good on Windows 11. I believe this skin really showcases how Windows 11 is supposed to be skinned. Too bad the explorer command bar can't be skinned as that would fix a lot of skins in itself, for now we have to rely on artists.
Hello Phoenix, really hope you are doing well mate, Thankyou for your road map bud but to keep with that metaphor, That is just too many Red Lights as i was hoping for a more Open Road if you get my meaning.
I really thought i would be up for this, but as it has been so long without WBs, and this is the killer, I Have learnt to live without it, (never thought i would ever say that) and brought my skillset of using and Porting Themes for use on current Operating Systems up to date. It has been a long year waiting for a working WB and a person like me who can not use there PC for long hours each day without customisation, Had to find other ways, Themes gave me what i needed and filled the hole left by No WB for Win 11. I am still going to buy WB 11, but only when it is a Final Release, and even then it will be just another customising tool in the box, were as in the past, it was central to my needs.
I do have and use hdr , and i do use Nvidia graphics cards too. Reading through the forum issues connected to WB11, peeps are having issues all over the place and not restricted to the 3 options you pointed out, Do not get me wrong mate, i am chuffed to bits the WB11 beta 2 is stable for you and others, but right now, it seems like too much work to make it work as required for me reading all the comments. I could just install another SSD and work through all the issues until i am happy, but my setup is complex enough already, giving me everything i need and more, So Why Feck With It If It Is Not Broken, and besides , that is what the Devs are paid to do, so i say let them get on with it and earn their money in the best way they know how. Brilliant to hear from you though bud.
Win10 v 21H2 (OS Build 19044.2251)
This is the SkinStudio installer I have installed, it should be the current:
The "Text" tab / "Text light/dark" field doesn't seem to be reporting the color setting, it just reports "OS Default". It does write changes to the file. I've looked at a few sections (taskbar buttons, pp window captions, popup menus item) and a few states in a few skins and it seems to be consistent. This is Lantana's Horizontal Taskbar Buttons section:
When I first go into it, I see this:
Then I can pick a different color and I see this:
Then when I go back to the Text tab, I see this:
Thanks.
Win10 v 21H2 (OS Build 19044.2251)2nd (Current) WBBeta
The "Per application" option "Only skin this applications titlebar" does not appear to be working. I tried it on a few programs, even tried re-booting once after setting the option. The programs were not running when I set the option. ("Ignore this application and do not skin it" is working.) This is Notepad++ :
Is beta three out yet? Because Beta 2 isn't making it.
Before beta 3 is released. Can you please add in an option to not skin any parts of the taskbar & startmenu under windowblinds settings.
******************************************
WTF why was this entire section of my post nuked! I was showing the issues I had with WB11 with startallback enabled. Not cool Stardock!
I am afraid this is not something thats technically viable from our end as it isn't quite that simple. The start menu and taskbar are both part of explorer and the only simple solution there would be to exclude the entire of explorer as there is overlap between those and other areas in how WB does things. Worth noting that Start10/11 are both designed to cooperate with WB in order to prevent such issues.
That said I believe you could use Start11 with explorer patcher if you really liked the Win10 taskbar as WindowBlinds will see that as Windows 10 (or will do in beta 2 and above)
I hope the winrar issue will be addressed in beta 3
It was addressed in Beta 2.
There are many great features available to you once you register, including:
Sign in or Create Account
