Based on the information we have we believe this to be a bug in the Microsoft product with handling system wide fonts.

Microsoft would need to resolve the issue.  For now you could avoid the issue by using themes which do not set system wide fonts, or using the feature built into WB to disable the use of system wide fonts on a theme.  This can be done by clicking Modify style and then on Fonts and then clicking Do not apply any style system wide fonts.

This is good to know for Windowblinds skin maker too...

I can confirm quoted post. Until resolved I decided to not use WindowBlinds.

I applied "Do not apply any style system wide fonts" and VS still crashes on start. It didn't do it right after I did the update but after a while started doing it again.

It does not seem a system wide fonts issue, because the Visual Studio crash is reproducible once per user session login, or that is what it seems for me. The things are like this:

After you boot the PC, log in your user account and set a style "for first time" in your current user session, and then try to run visual studio, it will crash.

But If you ran Visual Studio before setting any style in your current user session, then you can set any style and any current Visual Studio instance will not crash, and if you close Visual Studio, the next time you run it (in the current user session) it will NOT crash, regardless of the active theme.

For those reasons for me it seems a WindowBlinds bug more than a theme issue..

I'm facing this issue serious months ago...

Come on Stardock, you should attend this annonying issue that affects programmer users. Solve this bug in some way... soon. thanks.

I initially got feedback about this issue and then all my requests have not been answered. I face this too for some months now. I appreciate that the company might be a one man team and if he is poorly .... who knows. We are all only human.

But yes, I woudl liek a fix because it is annoying to constantly unload WB just to use VS.

Andy

We are aware of this issue and are looking into it. Thank you for reporting.

As everyone can see, they speak, promise, and say things like: "We are aware of this issue and are looking into it", but at the end Stardock do nothing after more than eight months suffering this issue... probably they are still "looking into it"... sure they will use more similar empty words like that to excuse their incompetence or just because any excuse is better than saying: "we don't care about this problem" to avoid damaging their commercial image.

How to fight this?, just uninstall the product since it is bugged and the company will do nothing to fix it because probablly we are a minority of programming users. I just will stop suggesting other potential customers to buy and confide to Sardock.

Thanks for read.

I can confirm the supposed solution in the commentary above is NOT working for the next system configuration:

• Microsoft Windows 10 1709.16299.15 (x64) a.k.a 'Fall Creators Update' with public release at October 1, 2017.
• Microsoft Visual Studio 2017 15.7.2 Professional Edition with public release at May 21, 2018.
• Stardock WindowBlinds 10.65.0.

...I feel like I am wasting my time writting specs. (again) for a company that does not seem to want to support this problem.

For that do have an issue, reapplying the WB theme will resolve it.

Unfortunately whilst we are able to reproduce it now at will, we have yet to be able to track down what it is unhappy about or why it suddenly becomes unhappy when it isn't if you launch VS directly after login.  Something triggers it and once that something happens a theme reapply will fix it.  BUT if the issue has yet to happen a theme reapply does not stop it happening later.  Clearly something triggers this and as yet we are unable to see what that thing is.

We can assure you we are still looking into it.

Stopped using Windows Blinds a while ago due to this issue. Getting used to Windows 10 theme. Ugly but doesn't crash.