Anybody with the "Essentials.pkg" Error

[mrhelloandgoodbye]

i´ve started it normally no flags
and then this came up
what is that ?

 

[mrhelloandgoodbye]

i´ve got it to work !!!!!!!
everything is fine now
But i did the installation without the graphics card and when im putting the card in it doesn´t start up not correctly

i have the mis twin geforce gtx 750 1 gb graphics card

what have i to do to get my card working?

 

[Damian555]

I also have this error on one particular machine. I do a lot of Hackintosh installations and I have a USB stick with Clover and Yosemite ready to go.

This USB Stick works on almost all of my machines.

I got this error on a gigabyte ga-945gzm-s2 with GT640 gfx.

So what I did I connected the hard drive to another computer, installed from there, I did not get the error, reconnected it to the gigabyte, booted with clover, and it works flawlessly.

This seems to be a hardware related error.

Damian

 

[xXJuanXx]

(I'm replying to a comment because I couldn't find a reply to thread button)

What worked for me is removing anything that's not the installer in the USB. I had a few Mac apps and Multibeast on the USB as well as the installer, and that's why it didn't work for me.

 

[morph21]

So, just to add my 2 cents to this as I spent about 2 days and over 20 hours head walling ™ ...

TLDR: It was a bad memory stick, that simple.

HOWEVER, even with the bad memory stick in, Yosemite DID INSTALL in a regular HDD , but would fail every time on a SSD .

So, perhaps the installer has a bigger buffer for SSD, or whatever it is, it is not exactly the same process as the HDD.

After the installation I started having some weird errors, so a quick memtest86 download, then into a USB which makes it bootable already and of to test we go. Errors all over.

Interestingly enough, even the memtest86 failed to load, or was just taking a lot of time, when I had only the bad memory stick in. So, another trick here. Everything may look ok with two sticks, but as soon as you use more memory it goes bad.

Perhaps this would be a great Essentials.pkg fix tip, upon errors on that, hardware test immediately, as something could be very wrong.

GL everyone.

 

[manshmedia]

Followed this man's advice and my Yosemite install finally worked. Tried all the various boot flags, no dice. Even unplugged all my other SATA drives. This was the final straw and it worked!

I followed what this man followed. BUT i couldnt paste the second folder as my usb drive was 8 GB i used maxmem=8192 and GraphicsEnabler=No

One thing more i made a fresh copy of bootable USB just to be sure and copied Yosemite/content_MASreciept but it also gave an error . BUT still it worked for me. My system is i7 intel mother board with gtx card. Hope it helps.

 

[lemjello]

I was having the same problem after starting from scratch over a different problem. This thread gives me some good ideas on things to check after this 10.10.4 update finishes, so, thank you.

Weirdest thing, I got it to work by signing in to my wifi. I have a TP Link card and before installing, I signed in. I also found I always have to use -no-zp, but, the only thing that finally worked for me was signing in to wifi. Gotta be a fluke, right? Probably a weird RAM issue?

(EDIT) Just noticed in the BIOS that the RAM is running at 1333 instead of 1600. XMP was disabled. I'll try putting it back to Profile 1 after the update finishes....8min...etc

 

[Shad0wWalk3r]

what i did to solve this on my laptop was to use maxmem=4096 while i had installed 2x8gb ram sticks
and i didnt want to open the laptop and replace ram with the 4gb stock that helped me ,hope it will help others!

 

[jccds]

I had the same problem with two different usb pens. One of them was created months ago with 10.10 and another one with 10.10.5 created last week. I've installed with the first one at least two times with no problems in the past.

Reformatted and repartitioned my disk (Crucial SSD) and nothing.

At last tried the solution posted here, "-no-zp", which worked like a charm. Thanks

 

[frakman1]

made the USB installation with GUID partition instead MBR. this worked for me strange thing

I can confirm that this worked for me too.