After applying the 2019-06 Security Monthly Quality Rollup of Windows Update, programs like Word display a blank image when provided with an EMF file created with InkScape 0.92.

It seems to be related with EMF specification as long as InkScape uses a LogFont object instead of a LogFontExDv object while exporting EMF files.

Is anyone having the same problem?

Could it be fixed?

Welcome to the forum!

Thanks for the heads up. 

(@doctormo, this is why I wanted to make a dedicated board for developers only.  I could simply move this to the developers board.  As it is, who knows when a developer will see it.)

Hopefully it won't be too long before a developer sees this, and can answer.  Personally, I have not heard this problem.

Can you clarify a bit:

• which version of Word, etc. are you using?
• which particular update triggered the issue?
• do you have a source for the LogFont vs LogFontExDv info (i.e. what makes you believe this is the cause?)

Also, can you provide a sample file? I could open an EMF just fine on my machine, but I'm also using Word 2010, so might not be true for newer versions.

I certainly hope Microsoft does not break existing files. If they do, I'd actually consider it a bug on their side.

Hello,

I'm using Inkscape 0.92.4 (5da689c313, 2019-01-14) and Microsoft Word 2016 MSO (16.0.4266.1001) 32 bits on a computer with Microsoft Windows 10 version 1803 (64 bits).

I realized the problem in June 2019 and solved it uninstalling the update KB4503286 (https://www.catalog.update.microsoft.com/Search.aspx?q=KB4503286).

I've been googling a bit and these people seems to have the same problem:

• https://stackoverflow.com/questions/56633434/devemf-output-display-problems-in-ms-word-2010-after-microsoft-update
• https://social.technet.microsoft.com/Forums/en-US/d1c392ec-6d12-444e-93dd-5a27d78a227b/office-365-and-2016-emf-files-not-showing-in-windows-7-after-recent-update?forum=Office2016ITPro
• https://social.msdn.microsoft.com/Forums/en-US/a0af7c55-7f13-4a6a-ac41-3c7a2a09d8f5/emf-graphics-specification-amp-security-patch?forum=os_specifications

Here you have two examples of EMF files: https://1drv.ms/u/s!Atb1I5AIMRMig-8gwqyb4dwEXiAsSg?e=vX3owG

Thanks, that's useful info!

As I understand it it was indeed a bug on Microsoft's end and should be fixed already or with an upcoming update (see answer in thread https://social.msdn.microsoft.com/Forums/en-US/a0af7c55-7f13-4a6a-ac41-3c7a2a09d8f5).

Patrick, thank you for your help.

I hope Microsoft do his job early.