I just tried to use this to skin my windows to something more classic.

It nearly trashed my machine, nothing would open, and even task manager couldn't open the 'run' dialog to let me get the windows shell or command window open to do anything. I got lucky to find an account that had NOT been opened since the last major windows update, opened that, still the system was black and not responsive but in that case I was able to kill the windows blind service (I couldn't with the other one, the task manager was too messed up) enough to get services to run just long enough to disable the windows blind service and restart then I could uninstall.

So I had to uninstall the app, it apparently is totally broken with the current windows 10.

And dangerous, anyone less determined would have had to reformat the system or do some sort of BIOS recovery option, this program is maybe way too dangerous to use if it can get the computer into that state.

I am sorry to hear you had problems however the current version of WindowBlinds IS compatible with the current version of Windows 10.  That is assuming you are defining current Windows 10 as release build and not an insider release of Windows 10 which we have not performed any compatibility testing with.

The most likely explanation is the version you used of WindowBlinds was considerably older than the current release.  Where and when did you obtain it?

To stop WindowBlinds running you can hold down ctrl at login which will prevent it applying any skins in that user session.

The game "Call of Duty - Black Ops 3" crashes immediately, if WindowBlinds is loaded.

I have a definite and reproducible problem with WindowBlinds 10 on Windows 10 Pro, 1709 [OS Build 16299.98] and Visual Studio (in my case VS2017 15.4.5, but older versions/pre-VS Update also had the same issue). I only have VS2017 on this computer, so I don't have other versions to compare.

If WindowBlinds is enabled, Visual Studio does not launch in a usable way. VS comes up as an empty black window that is completely unusable. I have uninstalled/reinstalled Visual Studio several times. I have reinstalled Windows 10 twice in the past two weeks. VS works fine until I install WindowBlinds 10, at which point it stops being usable.  Before I caved and completely (fresh) reinstalled the Windows 10 OS, VS2017 not only would come up in an unusable black window, it would also crash within about 10 seconds. After reinstalling Windows, VS doesn't crash, but as mentioned above, can't be used if WindowBlinds is loaded.

Adding a "per-application do-not-skin-at-all" exclusion for devenv.exe in WindowBlinds settings does not fix this issue and did not have any perceivable effect even before reinstalling the OS, and still no change after the reformat/reinstall of Windows.

Completely unloading WindowBlinds does fix it so that I can use Visual Studio, but of course, prevents me from being able to use WindowBlinds, which is one of the two main reasons why I pay for the OD subscription; the other is Start10, which does not have any detrimental effect that I have noticed. 

Any ideas on a fix for this? Any special settings, workarounds besides unloading WB?

OS: Windows 10/1709 16299.98

WB: 10.65 (048 - Windows 10 Edition) - 64 bit OS

qBittorrent: 4.0.2 (x64)

QBittorrent has problem with Windowblinds. Problem is quite obvious and reproducible with every skin I tried by resizing qBittorrent main window.

Latest Windows 10 Updates and Visual Studio 2017 Updates and now VS refuses to start unless I shut down WindowsBlinds.

Microsoft have reviewed the mini dumps and say it is an issue with fonts and agree it must be WindowsBlinds.

Can this be fixed pleased as I have to shut WindowsBlinds down everytime I want to use VS now (even with the software added to the exclusion list in advanced settings).

Microsoft response:

The bug seems to stem from a customized font that is shipped with WindowBlinds and used in some of the themes. This font causes a crash in a low-level WPF font API. If WindowBlinds allows you to revert font customizations while keeping the rest of the window chrome, that may help mitigate your issue.

Have you tried using a different theme as it sounds like if it is a 'fonts' issue then it might be a choice of system wide font exposing a bug in VS 2017.  Which theme are you using?

When you say Microsoft have reviewed the minidumps, do you mean a MSVP on public forums or an actual Microsoft developer? 

In testing here we are not having problems with VS2017 and WindowBlinds on the latest Windows 10 with the latest VS 2017 updates.

Could you try uninstalling WindowBlinds, REBOOTING (very important) and then downloading and installing the very latest version of WindowBlinds please.  It may be something went wrong in the upgrade though the usual reason for an app crash when excluded from WB would be a bug in the app itself coping with some system wide metric value (titlebar height, global fonts etc)

I provided their response in the edited post. I also forwarded the email to you.

but tomorrow I will uni stall, reboot and install again.

i am using ansaro 10 but I have tried other default themes.

will update you tomorrow.

I am sorry but I still get a crash.

I HAVE BIG PROBLEM WITH CURSOR FX...

I installed previus version and it crusches everytime when i tired to open it...

so i bought newest version 

and it goes the same way after uninstall previuss version and install the newest 

it didn't even show that something is wrong = just i try to open and nothing happens!

PLEASE HELP!

I checked here with ansaro 10 and it did crash VS 2017.  Oddly since rebooting I have not had a single crash from it though which means I cannot track the cause down any more precisely.

That skin does define custom system wide fonts but the font itself looks to be normal.

WindowBlinds does offer a way to disable the system wide fonts though.  Click on the theme you want to use in WB (but do not apply it yet), click modify style (under the apply button), click fonts and then tick the Do not apply any style system wide fonts option.  You can now apply the skin.

If the issue is a system wide font issue then regrettably there is nothing we can directly do to resolve this other than you not picking a custom font as the bug is not with WB it would be with VS2017.  Windows is told about the new font via the well documented apis specifically for this purpose, so the onus would be on them to fix their bug.

Other themes like Modern (included with WB) do not set any custom system wide fonts so if this is the issue they would work perfectly.

Unfortunately this is the thread for issues with WindowBlinds.  You would need to post this in the CursorFX group for assistance.

I have started to experience problems with Tortoise Git and and when I go to check for changes and click the commit button:

https://www.dropbox.com/s/kzpp4ob90icu16v/TortoiseGit.jpg?dl=0

I am using the latest Tortoise Git and the latest Windows 10.  My skin is Dark Realm 10 Light. But I get this problem with other skins.

When the dialog first displays it looks like the attached. Then if I go to re-size the window it will immediately redraw correctly.

Please advise.

Thanks.

Spotify is driving me bonkers.  I managed to fix up Firefox by restoring the whole thing to default (under Firefox -> Troubleshooting -> Reset) and then excluding it.

However, I cannot find a way to exclude Spotify.  It's a weird app that bends the laws of physics.  I just cannot work it out.

If I find the Spotify .exe under some weird directory (C:\Users\<User>\AppData\Local\Microsoft\WindowsApps\Spotify.exe) and try to exclude it I get the error that "The file cannot be accessed by the system".. eh?

Any help appreciated...