Now that I'm a subscriber again I wanted to see if there was any changes to WB. Unfortunately the top of the Microsoft Store being cut off is still a problem. With all skins as far as I'm aware. Same for maximised window; I made the window small for the sake of the screenshot.

I am currently getting this (See Picture Below) in Fences (4.0.7.2). I have to go to the "Per Application" option and enable "Total Exclusion" for it to go back to normal. I am currently using a pre-install theme that came with WindowBlinds 11.

WindowBlinds info:

Windows 11 Core 22H2 (22621.ni_release.220506-1250)

WindowBlinds 11.00 BETA (009 x64 - Windows 11 Edition) - 64 bit OS

Window titlebar blur features are enabled on this operating system

        Wblind.dll                2022/11/07 08:44:23

        Wblind64.dll              2022/11/07 08:44:46

        Wbsrv.dll                2022/11/07 08:44:52

        WB11Config.exe            2022/11/07 08:44:25

        Wbload.dll                2022/11/07 08:45:38

        Screen10.exe              2022/11/07 08:44:45

MagikGimp

reply 348

Now that I'm a subscriber again I wanted to see if there was any changes to WB. Unfortunately the top of the Microsoft Store being cut off is still a problem. With all skins as far as I'm aware. Same for maximised window; I made the window small for the sake of the screenshot.

Reduced 81%

Original 1022 x 799

You will have to exclude the Microsoft Store from the theming when using WindowBlinds 10/11. I haven't been able to figure a way to get it to work. It seems to have a custom theme separate from windows. Its been this way since Microsoft updated Microsoft Store.

Incompatible with StartAllBack (probably all start-menu enhancements besides start11) would love an option to be able to not theme taskbar+start menu, I think it would probably solve those issues.

Adlice UCheck is wonky in wb 11..  was wonky in wb10 too...

using windows 10 2h22 19045.2251 and windowblinds 11 '011 - windows 10 edition' (i just installed wb 11 yesterday)

messed up;

and the way it should look;

since installing wb11 i have removed many apps from exclude... was worth the upgrade.. esp if i can report broken apps for future fixes

Missing window buttons (minimize, maximize, and close buttons) in UltraEdit and UltraCompare AFTER switching back to Default Theme in WB11.

The issue even persists after restarting WB11 service, uninstall WB11, and even purging it (https://support.stardock.com/space/SS/1349058584/WindowBlinds+purging+and+re-installing).

In addition, I have ESET Internet Security installed, but already have HIPS (Host Intrusion Prevention System) disabled.

Windows 11 Professional 22H2 (22621.ni_release.220506-1250)

WindowBlinds 11.00 (011 x64 - Windows 11 Edition) - 64 bit OS

Window titlebar blur features are enabled on this operating system

        Wblind.dll                2022/11/30 00:26:37

        Wblind64.dll              2022/11/30 00:26:20

        Wbsrv.dll                2022/11/30 00:26:33

        WB11Config.exe            2022/11/30 00:26:29

        Wbload.dll                2022/11/30 00:27:38

        Screen10.exe              2022/11/30 00:26:45

m4h4r4

reply 353

Missing window buttons (minimize, maximize, and close buttons) in UltraEdit and UltraCompare AFTER switching back to Default Theme in WB11.

Reduced 83%

Original 1005 x 1080

Reduced 51%

Original 1622 x 1080

The issue even persists after restarting WB11 service, uninstall WB11, and even purging it (https://support.stardock.com/space/SS/1349058584/WindowBlinds+purging+and+re-installing).

In addition, I have ESET Internet Security installed, but already have HIPS (Host Intrusion Prevention System) disabled.

 

Windows 11 Professional 22H2 (22621.ni_release.220506-1250)

WindowBlinds 11.00 (011 x64 - Windows 11 Edition) - 64 bit OS

Window titlebar blur features are enabled on this operating system

        Wblind.dll                2022/11/30 00:26:37

        Wblind64.dll              2022/11/30 00:26:20

        Wbsrv.dll                2022/11/30 00:26:33

        WB11Config.exe            2022/11/30 00:26:29

        Wbload.dll                2022/11/30 00:27:38

        Screen10.exe              2022/11/30 00:26:45

 

 

Do you mean this continues even when WindowBlinds is uninstalled after a reboot?  If so thats probably not WB at fault given it isn't installed.

If this is just having had a skin applied and then switching back to Default whilst those apps are open then I would imagine closing and reopening them would resolve that.

> Do you mean this continues even when WindowBlinds is uninstalled after a reboot? If so thats probably not WB at fault given it isn't installed.

Yes. But that could make sense.

It seems to me the Default Theme of WB11 could possibly leave any leftover theme settings within Windows itself that aren't properly cleaned up after uninstallation, or even purging.

That came to my mind as after I excluded UltraEdit executable file (uedit64.exe) from WB11, and then I switched to any other non-default themes, those window buttons were properly shown using Window 11 default window theme (as expected).

Only after I switched back to WB11 Default Theme, those buttons disappeared again, like shown in the screenshots above.

I've also tried reinstalling UltraEdit, but the issue persists.

So for now, I'm assuming there's an issue caused by WB11 Default Theme, specifically, that trigger this unexpected behavior.

I can recreate this problem too (with a different skin).

文件资源管理器有问题，呈现错误

Which skin is this, please? I'll test it with an English locale.

请问这是什么皮肤？ 我将使用英语语言环境对其进行测试。

Microsoft Paint: Quick Access Toolbar does not show above Ribbon. Does appear when selected to show below it though.

So is the compatibility better with Window Blinds 11? Is it worth an update, or is it better to wait?

Im running the latest version of WB11 and windows is updated fully. For some reason the taskbar wont skin no matter what

Windowblinds blocks the Reolink client 

Using client version "v7.2.2.33" the client starts

Using the latest client version "8.8.5" the client refuses to start.

After unloading Windowblinds the latest Reolink client starts normaly...

I already asked Reolink to look at the problem, they proposed to use the older

client and till now they didn't solve the problem. Maybe the problem lies in the

Windowblinds program ?

Using : Windows 10 Version 21H2 (Build 19044.2846)