I am pleased to say we have finally located the root cause of the issue with VS 2017/2015 on later versions of the OS and a fix will be included in the next WB update. 

I am sorry it took so long, but unfortunately it was not a simple issue to resolve as it had nothing to do with VS2017 at all (other than an OS bug feeding it bad data) which means we had to track down where the breaking behaviour happened with a great deal of trial and error.  The breakthrough was when we found MS Paint triggered it at will thus saving us a huge amount of time in the testing.

As those having the issue are technical, the root issue turned out to be the GetSystemMetricsForDpi call is able to break the current session until OS metrics change.  In rare circumstances WB passed in a value of 1 for dpi rather than 96/ other valid dpi.  This seems to return valid values, but causes the OS to go completely mad and return bad data for VS2017 (a process launched later on without WB even doing anything inside it) which gets it in a muddle for fonts.

I am unsure why a get call in one process should impact anything else and that's a question for Microsoft as we plan to file it as a bug as that should never happen.

So in short, make an app that just does this (obviously WB didn't have a 1 there, it was a variable) :

GetSystemMetricsForDpi(SM_CYCAPTION, 1);

and after then no copy of VS 2017/2015 will load up in your user session until you reapply system metrics or sign out and in again.

Thanks. 

When can we have the new version? Thanks.

Glad I found this thread, Was just starting a "Repair" of Visual Studio thinking something went wonky in the install (just installed WindowBlinds last night after renewing my subscription) 

Running 10.65(048 Windows 10 Edition) on Windows 10 Enterprise (17134.rs4_release.180410-1804) 
Windows 10 Enterprise (17134.rs4_release.180410-1804)
WindowBlinds 10.65 (048 - Windows 10 Edition) - 64 bit OS
Window titlebar blur features are enabled on this operating system

        Wblind.dll                2017/09/05 07:42:33

        Wblind64.dll              2017/09/05 07:42:00

        Wbsrv.dll                 2017/03/28 06:53:46

        WB10Config.exe            2017/09/05 07:42:09

        Wbload.dll                2017/09/14 13:51:13

        Screen10.exe              2017/03/28 06:53:17

VisualStudio.15.Release/15.8.8+28010.2048

Microsoft .NET Framework Version 4.7.03056

Installed Version: Professional

Application Insights Tools for Visual Studio Package   8.13.10627.1

ASP.NET and Web Tools 2017   15.8.05085.0

ASP.NET Core Razor Language Services   15.8.31590

ASP.NET Web Frameworks and Tools 2017   5.2.60618.0

Azure App Service Tools v3.0.0   15.8.05023.0

Azure Functions and Web Jobs Tools   15.9.02046.0

C# Tools   2.9.0-beta8-63208-01

Extensibility Message Bus   1.1.49 (remotes/origin/d15-8@ee674f3)

JavaScript Language Service   2.0

Microsoft Azure Tools   2.9

Microsoft Continuous Delivery Tools for Visual Studio   0.4

Microsoft JVM Debugger   1.0

Microsoft Library Manager   1.0

Microsoft MI-Based Debugger   1.0

Microsoft Visual Studio Tools for Containers   1.1

Mono Debugging for Visual Studio   4.11.11-pre (8fb558f)

NuGet Package Manager   4.6.0

ProjectServicesPackage Extension   1.0

ResourcePackage Extension   1.0

ResourcePackage Extension   1.0

SQL Server Data Tools   15.1.61808.07020

TypeScript Tools   15.8.20822.2001

Visual Basic Tools   2.9.0-beta8-63208-01

Visual F# Tools 10.2 for F# 4.5   15.8.0.0.  Commit Hash: 55a3dc3231c95c77f81ee53f7d29152029da7408.

Visual Studio Code Debug Adapter Host Package   1.0

Visual Studio Tools for Containers   1.0

VisualStudio.Mac   1.0

Xamarin   4.11.0.776 (d15-8@1ae9b59d7)

Xamarin Designer   4.15.9 (d000f568b)

Xamarin Templates   1.1.116 (9619170)

Xamarin.Android SDK   9.0.0.19 (HEAD/a8a3b0ec7)

Xamarin.iOS and Xamarin.Mac SDK   12.0.0.15 (84552a4)

It works for me at the moment. No crashing.