Install Issue: TSplicedFont failed creating descriptor...

Well... i do have the same problem as well. Tried to clean install El Capitan, again & again, and same error message found.

Tried several USB stick, same output. Tired now, guess if apple could solve this. Sigh. Anyone, any advice? Much thanks.

Chooser[438:7016] TSplicedFont failed creating descriptor for:

Oct 3 05:56:45 MacBook-Pro Unknown[439]: (

Oct 3 05:56:45 MacBook-Pro Unknown[439]: {

Oct 3 05:56:45 MacBook-Pro Unknown[439]: UnicodeRange = "<__NSCFCharacterSet: 0x7fe26c5d3940>";

Oct 3 05:56:45 MacBook-Pro Unknown[439]: name = NotoSansBuhid;

Oct 3 05:56:45 MacBook-Pro Unknown[439]: },

Oct 3 05:56:45 MacBook-Pro Unknown[439]: {

Oct 3 05:56:45 MacBook-Pro Unknown[439]: UnicodeRange = "<__NSCFCharacterSet: 0x7fe26c5d39f0>";

Oct 3 05:56:45 MacBook-Pro Unknown[439]: name = NotoSansHanunoo;

Same problem here. Installing from a USB with a Macbook Pro 2011.

The log keeps repeating the same error over and over. Seems rather odd that Apple developers would set such a long timeout, but I'm going to let it work all night and see what happens since others have had success.

This isn't a very good start for an OS version that was supposed to be about fixing bugs.

It worked, in the morning El Capitan was installed and so far it's working great.

I had this same issue,

I tried installing to mac book pro for each English and Korean language but failed.

How can I perform roll back to the previously installed version of OSX?

xclass wrote:

I had this same issue,

I tried installing to mac book pro for each English and Korean language but failed.

How can I perform roll back to the previously installed version of OSX?

If you deleted your disk you have to download the previous OSX version from the Mac App Store in a different computer. Then create the USB, install as usual, and restore from time machine if you use that.

Same problem here, tried many USB sticks 8GB/16GB to no avail. Installation process takes ages and error log(cmd+L) shows the same errors

TSplicedFont failed creating descriptor for: ...

I am trying to get El Campo onto iMaC Mid 2010

El Capitan installation constantly failing, ended up installin Yosemite.

I am a 25 year Mac User. The only fix that worked for me was installing the El Capitan to an external hard drive and then using Carbon Copy Cloner to copy that external drive back to my Macs internal drive. It is much easier than you would think. I posted the same thing earlier but nobody has commented so I thought I would try again. It works perfectly.

I have attempted to install El Capitan more times than I can remember all without success. I made a USB installer and got further with it, also tried to install to an external drive that I had successfully installed El Capitan Beta on. Per some of the earlier posts, when it got to the last second and seemed to hang, I walked away and let it go. It did continue further, but after it came back to the Install OS X screen several times, the drive was trashed and un-repairable. I reformatted the external partition. So after 3 days of frustration including a support chat with Apple I give up. El Capitan has issues with my 2010 Mac Mini and I agree they haven't flushed all the bugs out. Far too many people with El Cap install issues across a variety of machines. Yosemite runs fine. When the next update comes out I'll decide whether I'll try to update the OS. What happened to "it just works"? IMHO I think it passed away with Steve Jobs. Thanks to all for the great posts and ideas.

Hello,

I had the same problem. I solved it by creating an USB Boot Stick with OSX Yosemite with Disk Maker X, installed Yosemite and then updated to El Capitan and at least played back the last Time Mashine Backup...

Not a comftable way, getting everything back in place took me more than 6h but all other attemps failed...

Hi all,

I found a solution.

My scenario: I am replacing a 5200RPM native OS drive with a shiny new 500gb Solid State Drive. I don't have an OSX install disc, or image on USB. When I tried running the installer, it wouldn't move forward. Looking at the logs, there was constant chirping about

MacBook-Pro Unknown[439]: {

MacBook-Pro Unknown[439]: UnicodeRange = "<__NSCFCharacterSet: 0x7fe26c5d3940>";

MacBook-Pro Unknown[439]: name = NotoSansBuhid;

MacBook-Pro Unknown[439]: },

MacBook-Pro Unknown[439]: {

MacBook-Pro Unknown[439]: UnicodeRange = "<__NSCFCharacterSet: 0x7fe26c5d39f0>";

MacBook-Pro Unknown[439]: name = NotoSansHanunoo;

For those that don't know, Apple is badass and includes recovery options into it's BIOS to install a fresh OSX without the need of a USB drive, install disc or anything physical. All you need is internet.

1. Boot down mac computer.

2. Replace the drive.

3. boot up and immediately hold down cmd+r (Recovery)

4. It asks for wifi credentials or ethernet connection.

5. Then it brings you to the recovery page. You have 4 options.
* Restore from Time Machine backup
* Reinstall OS X

* Get Help Online
* Disk Utility

6. Select Disk Utility.

7. Identify the new drive. "Erase" (format) the drive to be Mac OSX Journaled, GUID partition.

8. Quit out of disk utility.

9. Go back to the menu of 4 options. Select Re-install OSX.

*10. It'll eventually ask for Apple ID credentials.

11. Type them in, and it'll begin installing El Capitan OSX.

12. I still note those errors in the logs, but they seem unrelated to the actual install process. I think it's just crying in the background for unknown reasons..

*Please note, at Step 10, is where I got stuck before and began my google search. I looked at the installer logs, and noticed the same exact message you all were seeing about TSplicedFont failed. When I was at step 10, I was using my mother's Apple ID credentials to go forward, and I thought the messages in the logs were related to missing files and such... But I think it's just noise in the logs that don't affect the actual installation.

The reason why I personally got stuck was the credential my mom had for her Apple ID. The password she was using was "old security" type password and was considered insecure. Since my mom didn't change it to be properly secure, Apple accepted the password, but never moved forward because it's insecure and needs changing. So every time I went to use my mother's Apple ID with correct password, it would give me a 'unknown error' but wouldn't say the password was wrong... because it wasn't wrong, just insecure and old. If I typed in a blatantly wrong password for her Apple ID, it would fail immediately with incorrect credentials. After some spinning of wheels, I tried a different Apple ID (my own) and instantly it started downloading the files and began installing the OSX El Capitan.

Out of curiosity, I went to https://appleid.apple.com/ and entered my mother's credentials with the old password. It let me login, but it instantly asked me to change the password as having all lowercase wasn't secure anymore and must be changed.

So my suggestions is not to linger on to this log message, as it's probably just noise in the logs. What you should really make sure of, if you're using an Apple ID to install the OSX, is to make sure the password has been updated, and that you can login using those credentials at https://appleid.apple.com/

IF USB OR DISC IS FAILING. Try the method i described above using CMD+R on boot.

Hope this helps.

Henry

I am currently having these same issues trying to install El Capitan on my iMac (2009ish):

Here is what I have done so far:

1. Downloaded El Capitan (several times over) from the App store, installed on 16GB USB stick using TERMINAL method (also tried Diskmaker, same result).

2. Installing on a totally wiped, 320GB hard drive, reformatted - checked for errors - there is nothing on this drive and it should be working fine!

3. Reset the PRAM (command-option-p-r), and SMC ((left side) Shift-Control-Option keys and the power button at the same time)

4. Unplugged the computer and left it overnight

5. Reset the date using terminal, tried both -ntupdate using the internet, and also disconnecting the network and doing a manual date/time entry. The date is in January 2016.

Each time it tries installing, I get the corruption error, and the log shows activity, and PLENTY of it.

The install log has been running for over 18 hours, and currently is on process #192,000+ and counting!

The errors all begin with, "Language Chooser [439:7042] TSplicedFont failed creating descriptor for:" and then a UnicodeRange after that.

Every once in while, it flashes up a LOG MESSAGE QUOTA EXCEEDED - SOME MESSAGES FROM THIS PROCESS HAVE BEEN DISCARDED error - it happens too

Any ideas on what may be going wrong and how to fix it?

I NEED to get an operating system on this computer, I know its old - but its still worth something!

Thanks for your help all!

Hi Dellison,

Try my method that I described in my comment: Re: Install Issue: TSplicedFont failed creating descriptor...

Use CMD+R to install the OSX El Capitan

I repeat, TSPLICE messages in the logs are just noise. They are a not a stopper for this installation!

Hi carrascoproducer,

I have tried your methods, CMD+R, and it still isn't working.

Just to clarify, if I remove my USB key - and connect the network cable, and then press CMD+R upon startup (I've tried before the power button, just after the sound, etc) all I get is the white question mark and the grey folder blinking. It does not proceed past this point.

If I have the USB key in, then I get to the utilities screen, but then it wants to install from the usb drive, not from the network. As soon as I remove the USB key, the screen goes blank grey, and I have NOTHING.

Also, my iMac was pre-Lion, in which (I think) apple built-in the recovery into the mac. I think my mac originally had Leopard 10.5 on it. It's a 2008/09 era iMac. Yeah, its old but according to Apple, it should run El Capitan (iMac 2007 and newer).

I have a disc copy of Snow Leopard, I am wondering if I should give this a shot, and then upgrade to Mavericks once it is installed. I was HOPING for a clean install of Mavericks, but at this point I will settle for a working Mac again!

Thanks for your help Carrascoproducer. Your advice is sound, it may just be the age of my hardware.

Your symptom is unreleated to this thread

Try this: Re: question mark folder when i startup?