[quote who="sdrohan" reply="16" id="3905171"] Quoting banditt76, reply 15 After installing the Windows 11 23H2 update my tray icons are much bigger than normal. Is this a known issue that is being fixed? Seems to always happen with a new Windows feature release version, and maybe other version updates as well. </div
Windowblinds 11 (WB11) now paints the taskbar, but the WB11 tray icon is missing and Firefox and Edge title bars are not painted by WB11. WB11 does not cause screen hanging on my system.
As of Windows 11 22631.2715, the taskbar is being painted by Windowblinds 11 (WB11). But the WB11 tray icon is missing and now I'm seeing that WB11 is not painting the Firefox title bar as of Firefox v120.0.
The currently "general availability channel" build for Windows 11 (as of November, 2023) is 22631.2715. I have good news and bad news about this build. The good news is that Windows 11 is now painting the taskbar! The bad news is that Windowblinds 11 still doesn't provide a tray icon. This started with the release of 22631. The workaround for this is to create a Windowblinds icon on the desktop and then pin the icon to the taskbar. The following graphic s
[quote who="Envisaged0ne" reply="12" id="3904899"] I'm using the latest 23h2 version 22631.2338 and WB11 works perfectly fine [/quote] You're using an "Insider Preview" version, which may receive updates from the General Availability update channel. 22631.2338 may be the most recent update for an Insider Preview ISO install. If you install a standard ISO of Windows 11 (not an Insider Preview version), you'll be in the General Availability update channel and the most
[quote who="cajelevado" reply="11" id="3904897"] @r_pinkard: But does WB 11 still work on 23H2? I'm thinking of getting WB 11, but I'm also currently in Release Preview. [/quote] Windowblinds still works in 22631, but there is just no icon in the taskbar. The workaround is to create a Windowblinds shortcut on the desktop and pin it to the taskbar. I was on 226 2 1.2361 and the Enablement Package (EP) changed that to 226<span s
After applying the 23H2 enablement package to Windows 11, the Windowblinds tray icon no longer appears in the tray. In other words, the following Windowblinds feature no longer works: "Show icon in the system tray for easy access to WindowBlinds settings" Uninstalling/Reinstalling Windowblinds 11 causes the Windowblinds tray icon to appear for a few boots. But then it disappears again. I'm in the Release Preview update channel, but I don't see why that shou
[quote who="Robert84MK" reply="155" id="3818667"] Quoting r_pinkard, reply 154 I don't have verification that your statements are true. Open Shell v4.4.16X works fine with Windows 10, Start10/11 + Window Blinds = correct. <img src="https://cdn.stardock.us/forums/36/36/3636747/d075267b-b46
[quote who="Robert84MK" reply="153" id="3818614"] Quoting r_pinkard, reply 152 Open Shell v4.4.169 appears to be available Open Shell and Start10/11 doesn't work correct on Window Blinds. Start orb has not correct position. On Open Shell work only Start orbs from Vista/7/8/10 but XP doesn't and in Start10
[quote who="Derell Licht" reply="151" id="3818520"] Quoting Und3rsc0r3, reply 2 I don't know if this is 100% true, but I have heard if you use open shell or classic shell while using windowsblinds it can cause big problems. I suggest making a popup in the installer warn the user. nyet, current beta versio
[quote who="LightStar" reply="142" id="3817383"] The hardware requirements for Windows 11 are different. Are you sure your computer will run Windows 11? Sadly, mine won't and I am having to buy a new laptop and desktop computer.... Your computer must also be TPM 2.0 compatible... [/quote] At this point, MSFT is relaxing the hardware requirements for Windows 11. You can install Windows 11 on almost any PC as long as you have drivers that are compatible wi
I have also collected WindowBlinds styles over the last 20+ years. I was an avid user of WindowBlinds, and then transitioned to using 3rd party themes for Windows (msstyle mods) and stopped using WindowBlinds for several years. But then I came back to WindowBlinds because it was versatile, and you could use WindowBlinds with several different versions of Windows. When I came back to using WindowBlinds, several styles disappeared from prior years (2000-2015). I al
[quote who="Robert84MK" reply="115" id="3812005"] Quoting don5318, reply 111 First you say it's the same (Win 10/Win 11), now you say it's "almost the same OS", make up your mind, In first post its shortcut. Quoting r_pinkard, reply
[quote who="fictitiousfellow" reply="116" id="3812013"] Quoting r_pinkard, reply 113 EDIT: If you are running Windows 11, and you are using a Windows 10 version of explorer.exe, then be sure to revert back to the Windows 11 version of explorer.exe before applying updates to Windows 11. Otherwise, Windows
As of yesterday (7/15/2021), MSFT released Windows 10 19044.1147 in the Release-Preview update channel for users who don't deploy a UEFI, Secure Boot, or active TPM configuration. Windowblinds v10.89 continues to function with 19044 as it did with 19041, 19042, and 19043 versions. Windows 11 insider preview 22000.71 was released in the DEV update channel and Windowblinds continues to not paint the taskbar as with prior versions of Windows 11. I am presuming that Stardock i
Windows 11 is Windows 10 with a smaller footprint and a new user interface that is designed to steer the consumer into buying a "new and improved" touch screen PC. The fact that it runs with the same drivers as Windows 10 is a dead-giveaway that it's an alternate build of Windows 10. Some users are referring to it as a "Fake OS" because they think it is just Windows 10 with a Windows 11 mask on it. One of MSFT's biggest mistakes is that they release new versi
[quote who="Robert84MK" reply="99" id="3810301"] Quoting r_pinkard, reply 98 I don't want to spoil things for people who think they must buy new hardware to run a new version of Windows. <img src="https://bpccdn.fra1.digitaloceanspaces.com/original/3X/d/e/de34131ccc4418cb70e492e5448122cf
[quote who="Envisaged0ne" reply="97" id="3810005"] I'd just like to see Windowblinds work on Windows 11. I know it's probably to early to think that far ahead, but that's the one wish I have [/quote] Windowblinds 10 seems to work with the current Windows 11 leaked version (21996.1). It just doesn't skin the taskbar or start button. The taskbar is locked anyway by default, but the other Window frames get skinned. The entire atmosphere surrounding Win
So is the latest release 10.8.9.1 or is it 10.8.9.0? This thread lists 10.8.9.1.
Please be sure that you are running the latest graphics adapter driver with Windows 10 v2004. With some upgrades to new versions of Windows, the graphics adapter driver also needs to be updated. Switchable graphics on laptops can be quite temperamental as we migrate to newer versions of windows. You can quickly access device manager by pressing the Windows + R key and entering devmgmt.msc to open the device manager. Click on the plus sign next to "display adapt
I've had Windowblinds running on v1909 and have transitioned to v2004 (19041.208) and it runs perfectly for me. Windowblinds works fine. However, there are numerous issues with v2004, but none of them affected the way Windowblinds ran.
It's one of three variants of Lantana and you can get the latest one here: https://www.wincustomize.com/explore/screenshots/27013/ ~Roger
[quote who="Frogboy" reply="22" id="3764517"] WindowBlinds is definitely not going away any time soon. As Neil explained, the biggest obstacles we have faced in the past several years are: Apps that (wrongly) try to skin their own title bars to look like the OS rather than using what's built into the OS. Apps that are trying to block external DLLs from hooking onto their process. Hopefully we can work with the major parties to s
However, what was different about Windowblinds v10.82 that enabled it to paint the titlebar of Firefox v70.0.1 while v10.83 does not? It seems like the change is not with Firefox, but with Windowblinds.
Perhaps Mozilla needs some feedback. Thanks for the explanation.