Page 1 of 1

Problem after updating Windows to 1703 (Creators update)

Posted: Tue May 16, 2017 3:41 pm
by dudul
Hi,
I'm working with version 3.1.15 and it works fine until now.
After updating Windows 10 Pro Education X86 to the latest creators update (1703) the windows start to acting strange, mostly missing strings on open windows and menus.
Please take a look at the attached screenshots.

My hook start by windows service.

It only happened on Win 10 x86, the x64 version works fine.

Any idea?

Thanks

Re: Problem after updating Windows to 1703 (Creators update)

Posted: Tue May 16, 2017 4:14 pm
by Absolute_Zero
Been there, fixed/worked-around that... or something very similar. Hopefully you too.

Add fontdrvhost.exe to your exclusion mask.

Edit to add: I saw this problem on *some* x64 systems. I wasn't able to determine the difference between "working" and "not working" x64 installs. Appart from the non-display of text issue, I found some apps crashed when the "MS Shell Dlg 2" font was used on a #32770 common dialog.

Re: Problem after updating Windows to 1703 (Creators update)

Posted: Tue May 16, 2017 8:44 pm
by madshi
Yes, injection into fontdrvhost.exe seems to "sometimes" be problematic atm. I'm not exactly sure why yet. I'm working on a new injection method which I hope may fix the issue.

Re: Problem after updating Windows to 1703 (Creators update)

Posted: Wed May 17, 2017 10:34 am
by dudul
Absolute_Zero wrote:Been there, fixed/worked-around that... or something very similar. Hopefully you too.

Add fontdrvhost.exe to your exclusion mask.

Edit to add: I saw this problem on *some* x64 systems. I wasn't able to determine the difference between "working" and "not working" x64 installs. Appart from the non-display of text issue, I found some apps crashed when the "MS Shell Dlg 2" font was used on a #32770 common dialog.
Thanks, worked for me too.

Re: Problem after updating Windows to 1703 (Creators update)

Posted: Thu Jul 13, 2017 12:02 pm
by madshi
Since I've not been able to reproduce this problem myself, could you kindly double check if this new build fixes the problem without needing fontdrvhost.exe to be excluded from injection?

http://madshi.net/madCollectionBeta.exe (installer 2.8.2.13)