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 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.