![]() ![]() ![]() If that is not applicable at this time, there are other ways to resolve the issue: if the issue is happening in a controlled environment, apps can be excluded from the mitigation policy, as described in the Block untrusted font documentation ( ). The best way to resolve the issue would be to upgrade to that version, or if a newer is available. Looking at the blog post I've referenced earlier - it seems that the policy was made available with the first release of Windows 10 (v1507) is no longer applied with the so called Creators Update (v1703), which is available since August 17th, 2017.įrom the clarifications in the comments it also seems that the policy applies to IE 11 only, so another option would be to use Edge browser (comes with all windows 10 installations).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |