View Single Post
Old 03-15-2024, 11:00 PM   #38
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 36,041
Karma: 145735366
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by KevinH View Post
See this link:

https://learn.microsoft.com/en-us/tr...ntrusted-fonts

Make sure your Windows is not blocking woff fonts as untrusted.
That article has some issues. If you use Group Policy editor in a Pro or higher version of Windows 10/11, it has a MitigationOptions item under Computer Configuration => Administrative Templates => System => Mitigation Options. In that section, there is a Untrusted Font Blocking item. Enabling it and setting it to Do Not Block Untrusted Fonts creates an item in the same place as the Microsoft article above but it is a REG_BINARY instead of a REG_QWORD value.
Attached Thumbnails
Click image for larger version

Name:	group_policy_font_blocking.png
Views:	43
Size:	101.8 KB
ID:	206922   Click image for larger version

Name:	regedit_mitigation_options.png
Views:	35
Size:	89.6 KB
ID:	206923  
DNSB is offline   Reply With Quote