johndk

I uninstalled, rebooted, and installed again (again with just the Windows Classic style), and this time the problem did not occur. I wonder if it was related to me getting the " WindowBlinds has detected a problem with core files. Please contact support with error message -7 " error during my first install, although that seemed to be otherwise fixed by rebooting. May be worth someone testing with a comp

Win10x64 22H2, build 19045.2364 It's not really a problem for me - just wanted to let you guys know since I assume some other people will run into it also.

I did a clean Win10 install of WB 11 with just the Windows Classic style (which, BTW, I was disappointed with - it's less authentic than the True Classic style). With that configuration, I wasn't able to get any other styles to work. I'd install them and choose to Apply Style, but nothing would happen, and the new styles would not appear on the Style page of the settings window. I then installed again with all styles selected (without uninstalling first), and then all of the sty

Testing with a clean install of WB 11 and the Windows Classic theme, the problem happens even without maximizing the window first. (Chrome is configured to have hardware acceleration.)

Thanks! Rebooting fixed the error, although before rebooting (and while still getting the error), I didn't see any error in the Digital Signatures.

I'm considering upgrading to WindowBlinds 11, just for the new Windows Classic skin (currently using True Classic, but maybe the "official" skin will be better). But before I install that or any other software on my real machine, I want to test it in a VM. So I'm trying to install WB 11 on Win10x64 in VMware Workstation, fully updated to 22H2. But multiple times during installation, and when trying to launch WB, it fails with the following error: <

Sorry, I should have been more clear. I meant the main terminal window in Putty, not the Configuration window. Instructions to test this using a public Telnet server: Start Putty and go to the Session category. For the Host Name and Port, use: rainmaker.wunderground.com 3000 For the Connection type, choose Telnet. Click on Open. After it connects, just hit Enter enough times so that a vertical scrollba

When using a non-default theme with WindowBlinds on Win 10 (tested builds 2004 (19041.746) and 20H2 (19042.804)), the vertical scrollbar is missing or broken in the application "PuTTY" (or any of the variations of it, such as PuTTY NG or KiTTY). This is an extremely common SSH client. Download: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html Depending on the theme, the scrollbar will be completely invisible, or may overlap the right window border

Windows 10. I tested builds 2004 (19041.746) and 20H2 (19042.804). Using the latest versions of Chrome and WindowBlinds. I also tested in a VM with new installs of everything to confirm it wasn't just some other setting on my laptop. Several themes tested: "The Captain", "True Classic", "Windows Classic Theme" (and some others I forget). I don't think it matters - just has to be some non-default theme. 100% monitor scaling, and tested various

1.) Have any (I tested a few) non-default theme set with WindowBlinds. 2.) Launch Chrome with the --disable-windows10-custom-titlebar parameter. 3.) Maximize the window. So far so good - the titlebar is still there. 4.) Restore the window. Bug: The titlebar is now transparent, and the only fix is to close and reopen the window. This makes the --disable-windows10-custom-titlebar basically unusable in combination with a Window

Why is WindowBlinds not listed on the forum page? Is it being killed off? Curtains is terrible in comparison, so I hope that's not supposed to be a replacement.