Update on the Windows 10 Creators Update Linked Font Bug
As I previously posted, on behalf of Adobe and its customers, I officially submitted a bug report to Microsoft with regards to this serious problem.
Working closely with one of their Senior Escalation Engineers in their Windows Support organization, Microsoft was readily able to reproduce the problem exactly as I represented it to them.
Good News – Microsoft now acknowledges that this is a bug and that it will be fixed. Apparently the bug was introduced as part of major changes associated with improved security in the boot process.
Bad News – The permanent fix for the bug will appear in the Windows 10 Creators Fall Update, the exact release date TBD. This fix isn't something that is readily exportable as a patch in one of the upcoming monthly updates.
Good News – There is a very reliable workaround, based on a single registry entry, which forces rebuild of the font cache at bootup. The side effect is slightly increased boot time, but if you have a reasonably robust hardware configuration (SSDs, fast processor, a good amount of memory, etc.), this increased boot time should not be that noticeable. (My systems are particularly well-endowed in terms of such resources and also have close to 2000 typefaces installed. I see no noticeable difference in boot times!)
Unfortunately, this forum doesn't provide for attachments and thus, I cannot provide the .reg files directly for you, but if you copy and paste into files, the following should work like a charm:
Use this file Temp_Fix_Windows_10_Creators_Update_LinkedFont_Bug.reg to install the temporary fix:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\GRE_Initialize]
"DisableFontBootCache"=dword:00000001
Obviously, you will need to reboot your system after having applied this registry change.
Use this file Undo_Temp_Fix_Windows_10_Creators_Update_LinkedFont_Bug.reg to remove the temporary fix (you'll need to use this prior to installing the Windows 10 Creators Fall Update):
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\GRE_Initialize]
"DisableFontBootCache"=-
Microsoft offered a second workaround which I don't recommend - deleting the fontcache file as part of the logoff process. This effectively accomplishes the same thing with the same increased boot time, but quite frankly, if a system crashes or otherwise reboots without logoff, you can't count on this workaround since a logoff script won't be run.
I'll update this thread if and when I get further information from Microsoft confirming that the fix has been made, tested, and included in the Windows 10 Creators Fall Update (or if miraculously, an earlier fix is made available)!
- Dov Isaacs, Principal Scientist, Adobe Systems Incorporated
It sounds like something that could resolve the problem but where should I apply that?
dvo wrote:cmd : stands for command line ( uitvoeren in dutch )
cmd >> regedit look for
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\GRE_Initialize
I'm probably just stupid and doing something wrong but the CMD says that it can't find the folder specified. Sorry for being a dummy hahah
dvo wrote:oke you can get cmd ....
then you type regedit (enter) this will open register ....
after that you look part by part where you should be ....
are you using win 10 or ....?
Yea I'm using win 10, I got everything but not the GRE_Initialize fck me really
edit: Nvm I did the thing but it didn't help.
Last edited by cantarellaa on December 27th, 2017, 6:57 am, edited 1 time in total.
dvo wrote:what version of win 10 ... and what is the update version of the win 10 did you have all updates
btw it's showing on my win 10 fall update mine are working (1% does) still so can't re-create it ...
if you use win 10 home with all the updates i could zip my regs... makes it a bit nicer
They say my version is the 1709 ant that it's up to date.
jckinncik wrote:How do I check the path of the skin folder?
Right click Rainmeter icon in the Notification Area. Click Edit Settings. The Rainmeter.ini opens. In the SkinsPath option of the [Rainmeter] section, you have the path of the Skins folder.
I said to check it because I thought just the illusto skins can be loaded. Those are the default skins of Rainmeter, so if you have set a wrong path for the Skins folder, it sees just the illusto skins.
