Problem after updating Windows to 1703 (Creators update)

c++ / delphi package - dll injection and api hooking
Post Reply
dudul
Posts: 27
Joined: Wed Sep 09, 2015 3:00 pm

Problem after updating Windows to 1703 (Creators update)

Post 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
Attachments
3.png
3.png (48.89 KiB) Viewed 5579 times
2.png
2.png (28.34 KiB) Viewed 5579 times
1.png
1.png (17.91 KiB) Viewed 5579 times
Absolute_Zero
Posts: 39
Joined: Fri Jan 26, 2007 11:12 am

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

Post 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.
madshi
Site Admin
Posts: 10339
Joined: Sun Mar 21, 2004 5:25 pm

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

Post 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.
dudul
Posts: 27
Joined: Wed Sep 09, 2015 3:00 pm

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

Post 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.
madshi
Site Admin
Posts: 10339
Joined: Sun Mar 21, 2004 5:25 pm

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

Post 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)
Post Reply