Font issues - Boxed Question Marks

We had the same issue, as Microsoft released the 16.9 Office version on february. We could solve this issue by reset the font cache with this commands:

atsutil databases -remove
atsutil databases -removeUser

Do you have a policy with a maintenance payload running with " Flush System Caches Flush caches from /Library/Caches/ and /System/Library/Caches/, except for any com.apple.LaunchServices caches

Flush User Caches Flush caches from ~/Library/Caches/, ~/.jpi_cache/, and ~/Library/Preferences/Microsoft/Office version #/Office Font Cache " checked? We had this issue for along time and turning them off solved the problem.

anverhousseini
Thanks - so in the script I have as the "temporary" fix, I already include:

atsutil databases -remove

Which already includes the current user in the command.

Chris.Tavenner
Thanks for your response! We have the Maintenance Policy available in Self Service ONLY. It's not a policy that triggers on a check-in basis. You have to manually use it however, the specific cache policies you mentioned are indeed active. Most folks at our company don't really use Self Service all that much though which is why I'm doubtful that would have caused it. I will disable them as a precaution.

Sorry for reviving a dead thread here...but I'm curious if anyone else has seen this issue or been able to completely resolve it? This is wide spread across our district and we are in the same exact boat as amohammed.

I updated my laptop to Mojave 10.14, and I see this on that laptop. I would suspect that if this was happening across campus, the phone would be ringing of the hook, so I guess it's only me.

Sounds like there are some conflicting fonts in there.

where are fonts usually stored? when we deployed corporate fonts, we package them into the /Library/Fonts/NewFonts path.
I know some companies have licenses for fonts similar to those of the macOS font (Helvetica, etc), I would double check those conflicts and try to resolve them.

We are not currently pushing any custom fonts or anything like that. Everything font related is default. We've attempted everything amohammed put in his original post (including font validation and fixing errors/duplicates through FontBook) and as he said, it resolves it for the time being, but it always seems to come back. I originally thought this was in place upgrade related, as a number of the machines it started happening on were running Yosemite and were in place upgraded to High Sierra, but we've also seen this happen on fresh Macbook Airs from this summer that were shipped with High Sierra already installed. We also found a payload doing what Chris.Tavenner spoke on, but that has been fixed for months now, yet the issue is still wide spread.

We're also seeing this on a fresh image of 10.14.1

Running these commands as current logged in user:

Edit: The test system is actually "OK" now after these commands (unable to replicate the ???? issue anymore).

sudo atsutil databases -remove
atsutil server -shutdown
atsutil server -ping
sudo killall -HUP WindowServer

You have to run the -shutdown and -ping commands as the current logged in user, -remove as root.

Can't see anything in the 10.14.2 release notes to suggest this has been fixed by Apple...

Only consistency so far is it occurs after the OS is put to sleep for an X period of time. e.g If users go home for the evening (close the lid of their MacBook or put it to sleep. iMacs same thing).

We've had reports that an end user downloaded a heap of fonts in Word for Mac v 16.19 and this resolved the issue for them. We haven't had a chance to find out which fonts were downloaded to fix the issue, nor if this can be looked at for fleet deployment yet.

Any particular security apps installed in your environment? We were suspect of a few of ours, but this seems to be a long-running issue. We've only seen it since Mojave was released though.

Ticket with Apple provided the same recommendation as above from @Chris.Tavenner ; disable any ongoing policies which flush caches:
https://www.jamf.com/jamf-nation/discussions/27532/font-issues-boxed-question-marks#responseChild162938

@merc_support Thanks for your post, that did the trick perfectly! :)

@Vegaz We put a variant of that script into Self Service - to flush font caches. Main difference is rather than HUP the WindowServer, we force a restart.

#!/bin/sh
# Credit to Brian LaShomb via Jamf Nation
# Removes all user and system font caches
atsutil databases -remove
# Removes all user caches
atsutil databases -removeUser
# Stops the Font service
atsutil server -shutdown
# Wait 5 seconds
Sleep 5
# Starts the Font service
atsutil server -ping
exit

There's a thread you may want to check out where there's a lot of discussion about implementing various maintenance tools into Self Service.
https://www.jamf.com/jamf-nation/discussions/30872/what-scripts-and-helpdesk-tools-do-you-use-with-self-service

@KSchroeder are these the ones you mean?

The problem can be hard drives formatted as APFS encrypted or could JAMF.

Are there any other suggestions? This issue has not resolved my problems.

I used to run the full script @Wildfrog mentioned, but now it's a one liner and a force restart

I also have it as a self service policy, with a picture of the corrupt font icon; question mark in box, as if self service fonts get corrupt, you can't read the policy name ;-)

sudo atsutil databases -remove

It began when all sites wouldn't load anymore and only fixed after a full shut down and reset of the computer and I had to compare the options to click the restart as all the options turned to that boxed question marks if it got worse I don't know if I would be able to fix it however when I saw the condition of everything I knew to act quick but I am afraid of what would happen if I waited longer.

Hi all , did anyone find the root cause to this issue in the end?