How to fix corrupt or missing os system fonts in high sierra
I did a clean install of my mac from a usb key. Following that, everything worked perfectly in high sierra. Then, i used migration assistant to restore from my latest time machine backup. Following the restore, all of my fonts on not only the login screen, but also everything on the desktop and finder have become question marks with boxes around them. My question is, how do i restore the system fonts to get my fonts back into human readable form? See the screenshots below.
time-machine high-sierra font migration-assistant font-book
asked Jan 5 at 17:00
DanRanDanRan
1486
add a comment |
I did a clean install of my mac from a usb key. Following that, everything worked perfectly in high sierra. Then, i used migration assistant to restore from my latest time machine backup. Following the restore, all of my fonts on not only the login screen, but also everything on the desktop and finder have become question marks with boxes around them. My question is, how do i restore the system fonts to get my fonts back into human readable form? See the screenshots below.
time-machine high-sierra font migration-assistant font-book
asked Jan 5 at 17:00
DanRanDanRan
1486
Also, when you do a clean install, looking at /var/log/install.log sometimes will explain any issues or errors your offline installer encountered. What CPU and hardware are you running?
– bmike♦
2 days ago
add a comment |
I did a clean install of my mac from a usb key. Following that, everything worked perfectly in high sierra. Then, i used migration assistant to restore from my latest time machine backup. Following the restore, all of my fonts on not only the login screen, but also everything on the desktop and finder have become question marks with boxes around them. My question is, how do i restore the system fonts to get my fonts back into human readable form? See the screenshots below.
time-machine high-sierra font migration-assistant font-book
asked Jan 5 at 17:00
DanRanDanRan
1486
I did a clean install of my mac from a usb key. Following that, everything worked perfectly in high sierra. Then, i used migration assistant to restore from my latest time machine backup. Following the restore, all of my fonts on not only the login screen, but also everything on the desktop and finder have become question marks with boxes around them. My question is, how do i restore the system fonts to get my fonts back into human readable form? See the screenshots below.
time-machine high-sierra font migration-assistant font-book
time-machine high-sierra font migration-assistant font-book
asked Jan 5 at 17:00
DanRanDanRan
1486
asked Jan 5 at 17:00
DanRanDanRan
1486
asked Jan 5 at 17:00
DanRanDanRan
1486
asked Jan 5 at 17:00
DanRanDanRan
1486
asked Jan 5 at 17:00
DanRanDanRan
1486
1486
Also, when you do a clean install, looking at /var/log/install.log sometimes will explain any issues or errors your offline installer encountered. What CPU and hardware are you running?
– bmike♦
2 days ago
add a comment |
Also, when you do a clean install, looking at /var/log/install.log sometimes will explain any issues or errors your offline installer encountered. What CPU and hardware are you running?
– bmike♦
2 days ago
Also, when you do a clean install, looking at /var/log/install.log sometimes will explain any issues or errors your offline installer encountered. What CPU and hardware are you running?
– bmike♦
2 days ago
Also, when you do a clean install, looking at /var/log/install.log sometimes will explain any issues or errors your offline installer encountered. What CPU and hardware are you running?
– bmike♦
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
I’ll assume you have already tried a safe boot to rebuild the font cache and you legitimately have a system level corruption where the font database cannot retrieve even a system font.
- Boot to internet recovery if you can and verify that Disk Utility gives the boot volume a clean bill of health. A failing storage device would explain why a good backup on a good system would end up with corrupt fonts.
- Boot to internet recovery (or local recovery) and connect to the internet and download a fresh copy of macOS to reinstall over the top of the data.
Once that’s done, you can be sure you have a good install and then go back to isolating how the user account got corrupted.
- Boot to single user mode (or recovery) and mount the files stem as read/write and remove
/var/db/.AppleSetupDonefile so you can make a brand new admin account.
If this new admin account is also corrupt, you’ll need to perform a full erase install and/or seek hardware service since known good OS can’t be installed on an erased drive.
If this new admin account is fine with fonts, now you know the user account you migrated has the issue so you would decide to pick apart the font database / library for that user and re-enable all fonts in FontBook app - remove any third party font management tools. Or you could hand migrate that user’s files to a clean working account and walk away from the user corruption.
Sorry for so many if / then / else, but this isn’t a simple - press this one button to restore the fonts when you’re migrating user data to a system that’s not sure it’s working.
answered Jan 5 at 18:00
bmike♦bmike
157k46283611
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "118"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f347645%2fhow-to-fix-corrupt-or-missing-os-system-fonts-in-high-sierra%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I’ll assume you have already tried a safe boot to rebuild the font cache and you legitimately have a system level corruption where the font database cannot retrieve even a system font.
- Boot to internet recovery if you can and verify that Disk Utility gives the boot volume a clean bill of health. A failing storage device would explain why a good backup on a good system would end up with corrupt fonts.
- Boot to internet recovery (or local recovery) and connect to the internet and download a fresh copy of macOS to reinstall over the top of the data.
Once that’s done, you can be sure you have a good install and then go back to isolating how the user account got corrupted.
- Boot to single user mode (or recovery) and mount the files stem as read/write and remove
/var/db/.AppleSetupDonefile so you can make a brand new admin account.
If this new admin account is also corrupt, you’ll need to perform a full erase install and/or seek hardware service since known good OS can’t be installed on an erased drive.
If this new admin account is fine with fonts, now you know the user account you migrated has the issue so you would decide to pick apart the font database / library for that user and re-enable all fonts in FontBook app - remove any third party font management tools. Or you could hand migrate that user’s files to a clean working account and walk away from the user corruption.
Sorry for so many if / then / else, but this isn’t a simple - press this one button to restore the fonts when you’re migrating user data to a system that’s not sure it’s working.
answered Jan 5 at 18:00
bmike♦bmike
157k46283611
add a comment |
I’ll assume you have already tried a safe boot to rebuild the font cache and you legitimately have a system level corruption where the font database cannot retrieve even a system font.
- Boot to internet recovery if you can and verify that Disk Utility gives the boot volume a clean bill of health. A failing storage device would explain why a good backup on a good system would end up with corrupt fonts.
- Boot to internet recovery (or local recovery) and connect to the internet and download a fresh copy of macOS to reinstall over the top of the data.
Once that’s done, you can be sure you have a good install and then go back to isolating how the user account got corrupted.
- Boot to single user mode (or recovery) and mount the files stem as read/write and remove
/var/db/.AppleSetupDonefile so you can make a brand new admin account.
If this new admin account is also corrupt, you’ll need to perform a full erase install and/or seek hardware service since known good OS can’t be installed on an erased drive.
If this new admin account is fine with fonts, now you know the user account you migrated has the issue so you would decide to pick apart the font database / library for that user and re-enable all fonts in FontBook app - remove any third party font management tools. Or you could hand migrate that user’s files to a clean working account and walk away from the user corruption.
Sorry for so many if / then / else, but this isn’t a simple - press this one button to restore the fonts when you’re migrating user data to a system that’s not sure it’s working.
answered Jan 5 at 18:00
bmike♦bmike
157k46283611
add a comment |
I’ll assume you have already tried a safe boot to rebuild the font cache and you legitimately have a system level corruption where the font database cannot retrieve even a system font.
- Boot to internet recovery if you can and verify that Disk Utility gives the boot volume a clean bill of health. A failing storage device would explain why a good backup on a good system would end up with corrupt fonts.
- Boot to internet recovery (or local recovery) and connect to the internet and download a fresh copy of macOS to reinstall over the top of the data.
Once that’s done, you can be sure you have a good install and then go back to isolating how the user account got corrupted.
- Boot to single user mode (or recovery) and mount the files stem as read/write and remove
/var/db/.AppleSetupDonefile so you can make a brand new admin account.
If this new admin account is also corrupt, you’ll need to perform a full erase install and/or seek hardware service since known good OS can’t be installed on an erased drive.
If this new admin account is fine with fonts, now you know the user account you migrated has the issue so you would decide to pick apart the font database / library for that user and re-enable all fonts in FontBook app - remove any third party font management tools. Or you could hand migrate that user’s files to a clean working account and walk away from the user corruption.
Sorry for so many if / then / else, but this isn’t a simple - press this one button to restore the fonts when you’re migrating user data to a system that’s not sure it’s working.
answered Jan 5 at 18:00
bmike♦bmike
157k46283611
I’ll assume you have already tried a safe boot to rebuild the font cache and you legitimately have a system level corruption where the font database cannot retrieve even a system font.
- Boot to internet recovery if you can and verify that Disk Utility gives the boot volume a clean bill of health. A failing storage device would explain why a good backup on a good system would end up with corrupt fonts.
- Boot to internet recovery (or local recovery) and connect to the internet and download a fresh copy of macOS to reinstall over the top of the data.
Once that’s done, you can be sure you have a good install and then go back to isolating how the user account got corrupted.
- Boot to single user mode (or recovery) and mount the files stem as read/write and remove
/var/db/.AppleSetupDonefile so you can make a brand new admin account.
If this new admin account is also corrupt, you’ll need to perform a full erase install and/or seek hardware service since known good OS can’t be installed on an erased drive.
If this new admin account is fine with fonts, now you know the user account you migrated has the issue so you would decide to pick apart the font database / library for that user and re-enable all fonts in FontBook app - remove any third party font management tools. Or you could hand migrate that user’s files to a clean working account and walk away from the user corruption.
Sorry for so many if / then / else, but this isn’t a simple - press this one button to restore the fonts when you’re migrating user data to a system that’s not sure it’s working.
answered Jan 5 at 18:00
bmike♦bmike
157k46283611
answered Jan 5 at 18:00
bmike♦bmike
157k46283611
answered Jan 5 at 18:00
bmike♦bmike
157k46283611
answered Jan 5 at 18:00
bmike♦bmike
157k46283611
157k46283611
add a comment |
add a comment |
Thanks for contributing an answer to Ask Different!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f347645%2fhow-to-fix-corrupt-or-missing-os-system-fonts-in-high-sierra%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Also, when you do a clean install, looking at /var/log/install.log sometimes will explain any issues or errors your offline installer encountered. What CPU and hardware are you running?
– bmike♦
2 days ago