All geek questions in one place

The font file is held by the system process.

In my environment, the system.exe file is supported by the TTF file (font file).
I can’t understand why this is happening.
I tried to unregister (delete) the font and still the system process is holding it.
My problem is when, when I update a package using a ttf file, it requires a system reboot, because the file is replaced during its storage.
Does anyone have any suggestions why it is used by the system process and what can be done?
Thanks

+5
source share
1 answer

This behavior was introduced with a security update that was released in August 2014 (see Security Bulletin MS14-045 for details ) and applies to any font file that is not installed in the default font directory.

Although KB article for MS14-045 lists this as a "known issue", it is now documented as expected behavior. See Add or Remove Fonts on MSDN:

A font installed from a location other than the% windir% \ fonts folder cannot be changed during loading in any active session, including session 0. [...]

Persistent fonts remain after reboot and are loaded by all created sessions.

This means that if it is not allowed to restart the computer when updating the font, the font file must be installed in the default font directory. (I believe that has always been a recommended practice anyway.)

+4
source

Source: https://habr.com/ru/post/1209991/

More articles:


All Articles