Leopard Install fails with 2 minutes remaining

I have searched this forum and elsewhere on internet for similar issue. I hope someone here can help me. I am experienced Mac user but this is first time I have had problem I cannot solve by myself!
PowerMac G5 Dual 2.7 with 4.5GB RAM
I was running Tiger on the machine since purchase, no problems. I installed (Upgrade) Leopard (Family Pack)on the machine when it first came out,
no problems. Upgraded to 10.5.2 no problems. (Also installed Leopard on PowerBook G4, no problems.)
But earlier this week just surfing the web I get the gray overlay with "You must restart your computer" in 5 languages. Since then the machine gets the gray "Restart" overlay upon reboot.
I ran Apple Hardware Test (Extended) from the DVDs that came with the PowerMac. It took 2 hours but everything passed.
From this point I did the installs with only the keyboard and mouse plugged into the USB on the back of computer. No other connections except monitor.
I purchased new hard drive Erase w/ zeros and was able to reinstall Tiger successfully from the same original DVDs. Was able to upgrade that Tiger to 10.4.11. No problems. Multiple reboots, no gray overlay.
Now I try to upgrade to Leopard, and it got to "2 minutes remaining", and I get the gray overlay. So I try an Erase / install of Leopard to the new drive again, same gray overlay at 2 minutes remaining.
- Took the PRAM battery to Radio Shack and it measured around 3.4 volts (it is a 3.6 volt battery). I purchased a new battery anyway
and replaced it, tried Leopard install again, same gray overlay at 2 minutes remaining.
- Last, I took out 2GB of the non-Apple RAM, try install again, same gray overlay at 2 minutes remaining.
At this point I don't know what else to try. Maybe take out remaining 2GB of non-Apple RAM? That will leave .5GB RAM
Thank you for your help
Jenny Zhao

Thank you for the responses. I removed the other non-Apple RAM and attempted Leopard Install onto empty HD. The install process was much slower, and got the gray "Restart" overlay with 52 minutes remaining.
- never tried an "Archive and Install". Either Upgrade, Erase & Install, or Install.
- Hard drive. I get the gray "restart" overlay with two different HD, the one that had been running Leopard since 10/26/2007. And on the new HD purchased to try to resolve the issue. BTW I could connect to the original HD in Firewire Target mode no problem to pull files off. So i thought maybe problem w/ original HD with booting. But since I have same issue (gray overlay either running or installing Leopard) trying clean install on a brand new HD, I do not think HD.
- Heat: that is good observation. But then I was able to reinstall original Tiger no problem. So perhaps something with cooling has become enough to affect Leopard operation but not Tiger? I do not see any indication of leaking fluid (this is liquid cooled Power Mac G5, not Intel). How to troubleshoot heat issue?
- defective DVD: maybe. But worked OK first time Leopard installed on both Powermac and Powerbook.
I think maybe: some hardware besides RAM/Logic board/PRAM has failed or "become less than optimal" that Leopard is more sensitive to compared to Tiger. But how to diagnose?
AppleCare expires May 19 on this machine, perhaps I can contact Apple?
Jenny Zhao

Similar Messages

Leopard install fails with panic: "Unable to find driver for this platform"

I have an early 2006 20" iMac with OSX 10.4.11 installed. Running perfectly with latest Firmware, permissions repaired, just perfect. I now want to upgrade to OSX 10.5, so I insert the Leopard Install DVD, reboot, and then to my horror a kernel panic, screen goes black with message panic(CPU 0 ...): "Unable to find driver for this platform", with the usual boxed message about holding the start button.
Grateful for any help.

I finally managed to install Leopard by using a 2nd iMac to read the install DVD, and using firewire and Target Mode as described in http://reviews.cnet.com/8301-13727_7-10327225-263.html?tag=mfiredir . This seems to imply that the kernel panic is due to some hardware fault with my iMac's optical drive.

Snow Leopard Install Failed

Tried installing Snow Leopard on MacBook Pro (Intel Core i5). Drive has been repartitioned, however install fails with message "Install Failed - Mac OS X could not be installed on your computer - The Installer could not copy the necessary support files".
Tried several times but same message each time. Can't even seem to eject disc to check it (although brand new so shouldn't be any problems). Help appreciated...

Restart, holding down the mouse key. That should eject the disc. You might have a faulty install disc. Call Apple.

Install failed with exit code 11?

Hi,
I am trying to deploy a language pack and set the override language to English-US which I have created 2 programs for in my package. When the first program runs I am getting an error in the execmgr.log that "Install failed with exit code 11" Any
ideas what this means? When I run this command manually on the machine it works fine:
"C:\WINDOWS\System32\Dism.exe" /online /add-package /packagepath:"en-us\lp.cab"
I checked the dism.log as well but I don't see any errors. Both logs are below, any help or suggestions would be greatly appreciated TIA
<![LOG[Command line = "C:\WINDOWS\System32\Dism.exe" /online /add-package /packagepath:"en-us\lp.cab", Working Directory = C:\WINDOWS\ccmcache\4j\]LOG]!><time="08:00:28.447+300" date="01-27-2015" component="execmgr"
context="" type="1" thread="4976" file="scriptexecution.cpp:352">
<![LOG[Running "C:\WINDOWS\System32\Dism.exe" /online /add-package /packagepath:"en-us\lp.cab" with 32bitLauncher]LOG]!><time="08:00:28.447+300" date="01-27-2015" component="execmgr" context=""
type="1" thread="4976" file="scriptexecution.cpp:370">
<![LOG[Created Process for the passed command line]LOG]!><time="08:00:28.509+300" date="01-27-2015" component="execmgr" context="" type="1" thread="4976" file="scriptexecution.cpp:513">
<![LOG[Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
AdvertisementId = "LIA20115";
ClientID = "GUID:428D91E4-84BD-4740-97D9-9177C39FA3F0";
CommandLine = "\"C:\\WINDOWS\\System32\\Dism.exe\" /online /add-package /packagepath:\"en-us\\lp.cab\"";
DateTime = "20150127130028.509000+000";
MachineName = "";
PackageName = "";
ProcessID = 2012;
ProgramName = "Install";
SiteCode = "";
ThreadID = 4976;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\WINDOWS\\ccmcache\\4j\\";
]LOG]!><time="08:00:28.509+300" date="01-27-2015" component="execmgr" context="" type="1" thread="4976" file="event.cpp:715">
<![LOG[Raised Program Started Event for Ad:LIA20115, Package:LIA002A0, Program: Install]LOG]!><time="08:00:28.509+300" date="01-27-2015" component="execmgr" context="" type="1" thread="4976"
file="executioncontext.cpp:459">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="LIA002A0",ProgramID="Install", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="08:00:28.509+300"
date="01-27-2015" component="execmgr" context="" type="1" thread="4976" file="event.cpp:405">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="LIA002A0",ProgramID="Install", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="08:00:28.509+300"
date="01-27-2015" component="execmgr" context="" type="1" thread="4976" file="event.cpp:405">
<![LOG[MTC task with id {B7EEE891-740D-4762-8D2B-BA2D7E351F1D}, changed state from 4 to 5]LOG]!><time="08:00:28.525+300" date="01-27-2015" component="execmgr" context="" type="1" thread="5904"
file="execreqmgr.cpp:6288">
<![LOG[Program exit code 11]LOG]!><time="08:00:28.650+300" date="01-27-2015" component="execmgr" context="" type="1" thread="2488" file="scriptexecution.cpp:676">
<![LOG[Looking for MIF file to get program status]LOG]!><time="08:00:28.650+300" date="01-27-2015" component="execmgr" context="" type="1" thread="2488" file="executionstatus.cpp:282">
<![LOG[Script for Package:LIA002A0, Program: Install failed with exit code 11]LOG]!><time="08:00:28.650+300" date="01-27-2015" component="execmgr" context="" type="3" thread="2488" file="executionstatus.cpp:252">
<![LOG[Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramErrorEvent
AdvertisementId = "LIA20115";
ClientID = "GUID:428D91E4-84BD-4740-97D9-9177C39FA3F0";
DateTime = "20150127130028.650000+000";
ExitCode = "11";
MachineName = "";
PackageName = "LIA002A0";
ProcessID = 2012;
ProgramName = "Install";
SiteCode = "";
ThreadID = 2488;
UserContext = "NT AUTHORITY\\SYSTEM";
]LOG]!><time="08:00:28.650+300" date="01-27-2015" component="execmgr" context="" type="1" thread="2488" file="event.cpp:715">
<![LOG[Raised Program Error Event for Ad:LIA20115, Package:LIA002A0, Program: Install]LOG]!><time="08:00:28.650+300" date="01-27-2015" component="execmgr" context="" type="1" thread="2488"
file="executioncontext.cpp:572">
<![LOG[Execution is complete for program Install. The exit code is 11, the execution status is FailureNonRetry]LOG]!><time="08:00:28.665+300" date="01-27-2015" component="execmgr" context="" type="1"
thread="1956" file="execreqmgr.cpp:4165">
<![LOG[Requesting MTC to delete task with id: {B7EEE891-740D-4762-8D2B-BA2D7E351F1D}]LOG]!><time="08:00:28.681+300" date="01-27-2015" component="execmgr" context="" type="1" thread="1956"
file="executionrequest.cpp:9041">
<![LOG[MTC task with id: {B7EEE891-740D-4762-8D2B-BA2D7E351F1D} deleted successfully.]LOG]!><time="08:00:28.681+300" date="01-27-2015" component="execmgr" context="" type="1" thread="1956"
file="executionrequest.cpp:9070">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="LIA002A0",ProgramID="InstallEN", actionType 10l, value Result:FALSE, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="08:00:28.697+300"
date="01-27-2015" component="execmgr" context="" type="1" thread="1956" file="event.cpp:405">
<![LOG[Deleting request for program Install. Failing parent program InstallEN]LOG]!><time="08:00:28.697+300" date="01-27-2015" component="execmgr" context="" type="1" thread="1956" file="execreqmgr.cpp:8147">
<![LOG[Requesting MTC to delete task with id: ]LOG]!><time="08:00:28.697+300" date="01-27-2015" component="execmgr" context="" type="1" thread="1956" file="executionrequest.cpp:9041">
<![LOG[This execution request does not have a corresponding task in MTC.]LOG]!><time="08:00:28.697+300" date="01-27-2015" component="execmgr" context="" type="1" thread="1956" file="executionrequest.cpp:9059">
<![LOG[Requesting MTC to delete task with id: {B7EEE891-740D-4762-8D2B-BA2D7E351F1D}]LOG]!><time="08:00:28.697+300" date="01-27-2015" component="execmgr" context="" type="1" thread="1956"
file="executionrequest.cpp:9041">
<![LOG[This execution request does not have a corresponding task in MTC.]LOG]!><time="08:00:28.697+300" date="01-27-2015" component="execmgr" context="" type="1" thread="1956" file="executionrequest.cpp:9059">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="LIA002A0",ProgramID="Install", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="08:00:28.697+300"
date="01-27-2015" component="execmgr" context="" type="1" thread="1956" file="event.cpp:405">
015-01-27 08:00:28, Info                  DISM   DISM.EXE:
2015-01-27 08:00:28, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2015-01-27 08:00:28, Info                  DISM   DISM.EXE:
2015-01-27 08:00:28, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.3.9600, Running architecture=x86, Number of processors=4
2015-01-27 08:00:28, Info                  DISM   DISM.EXE: Dism.exe version: 6.3.9600.16384
2015-01-27 08:00:28, Info                  DISM   DISM.EXE: Executing command line: "C:\WINDOWS\System32\Dism.exe" /online /add-package /packagepath:"en-us\lp.cab"
2015-01-27 08:00:28, Info                  DISM   DISM Provider Store: PID=5984 TID=4336 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2015-01-27 08:00:28, Info                  DISM   DISM Provider Store: PID=5984 TID=4336 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2015-01-27 08:00:28, Info                  DISM   DISM Provider Store: PID=5984 TID=4336 Loading Provider from location C:\WINDOWS\System32\Dism\FolderProvider.dll
- CDISMProviderStore::Internal_GetProvider
2015-01-27 08:00:28, Info                  DISM   DISM Provider Store: PID=5984 TID=4336 Connecting to the provider located at C:\WINDOWS\System32\Dism\FolderProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2015-01-27 08:00:28, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2015-01-27 08:00:28, Info                  DISM   DISM.EXE:
2015-01-27 08:00:28, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2015-01-27 08:00:28, Info                  DISM   DISM.EXE:

Thanks, it seems as though it is not doing anything now. I just see that the policy has arrived in the log below but it is not installing it? The dism.log hasn't changed at all so it seems that it isn't even executing the command now? Am I missing something
else? I even tried re-advertising it though client center.
Command is now:
C:\WINDOWS\sysnative\Dism.exe /online /add-package /packagepath:"en-us\lp.cab"
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="LIA002A0",ProgramID="InstallEN", actionType 45l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="08:52:28.943+300"
date="01-27-2015" component="execmgr" context="" type="1" thread="5036" file="event.cpp:405">
<![LOG[Policy arrived for child program Install]LOG]!><time="09:12:48.440+300" date="01-27-2015" component="execmgr" context="" type="1" thread="3528" file="execreqmgr.cpp:6867">
<![LOG[Policy arrived for parent package LIA002A0 program InstallEN]LOG]!><time="09:12:48.487+300" date="01-27-2015" component="execmgr" context="" type="1" thread="3528" file="execreqmgr.cpp:6893">
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="LIA002A0",ProgramID="InstallEN", actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="09:12:48.487+300"
date="01-27-2015" component="execmgr" context="" type="1" thread="3528" file="event.cpp:405">
<![LOG[Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramOfferReceivedEvent
AdvertisementId = "LIA20116";
ClientID = "GUID:428D91E4-84BD-4740-97D9-9177C39FA3F0";
DateTime = "20150127141248.502000+000";
MachineName = "";
ProcessID = 2012;
SiteCode = "";
ThreadID = 3528;
]LOG]!><time="09:12:48.502+300" date="01-27-2015" component="execmgr" context="" type="1" thread="3528" file="event.cpp:715">
<![LOG[The user has logged off.]LOG]!><time="09:36:59.174+300" date="01-27-2015" component="execmgr" context="" type="1" thread="4320" file="execreqmgr.cpp:5138">

Flash Player Install failed with error code: 30

Hi, I want to report a problem with the Adobe Flash Player 13.0.0.182 (Mac OS X, English) installer on OS X 10.9.2. Mavericks. I'm posting this so the engineers will know what to fix in the next update version.
I have a 2013 iMac so according to Adobe blog posts it shouldn't be affected by the invalid cpu instruction issue.
Symptom is the first installer downloads the 2nd, starts to launch it, then quits it with "Error: Unable to proceed with the installation" and a green (success?) checkmark. The GUI provides no other assistance except to "FINISH", which leads to the generic "Adobe Flash Player could not be installed." page.
The system log says: Adobe Flash Player Install Manager[22567]: Install failed with error code: 30.
The FlashPlayerInstallManager.log says:
2014-04-13 16:12:01 -0500 [I] IM: ---------- log start ----------
2014-04-13 16:12:01 -0500 [I] IM: All install checks pass
2014-04-13 16:12:01 -0500 [W] IM: Unexpected umask value for process: 0
2014-04-13 16:12:06 -0500 [I] IM: User does not have any processes that need to be closed.
2014-04-13 16:12:06 -0500 [I] IM: [install started]
2014-04-13 16:12:06 -0500 [E] RA: Unable to launch FPInstallHelper. Error = 'launch path not accessible'
2014-04-13 16:12:06 -0500 [E] RA:
Attributes for '/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/FPInstallHelper':
    NSFileCreationDate = "2014-03-27 04:20:43 +0000";
    NSFileExtensionHidden = 0;
    NSFileGroupOwnerAccountID = 0;
    NSFileGroupOwnerAccountName = wheel;
    NSFileHFSCreatorCode = 0;
    NSFileHFSTypeCode = 0;
    NSFileModificationDate = "2014-03-27 04:20:43 +0000";
    NSFileOwnerAccountID = 0;
    NSFileOwnerAccountName = root;
    NSFilePosixPermissions = 2541;
    NSFileReferenceCount = 1;
    NSFileSize = 13348;
    NSFileSystemFileNumber = 4892044;
    NSFileSystemNumber = 16777224;
    NSFileType = NSFileTypeRegular;
2014-04-13 16:12:06 -0500 [E] RA:
Attributes for '/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T':
    NSFileCreationDate = "2014-04-07 13:43:21 +0000";
    NSFileExtensionHidden = 0;
    NSFileGroupOwnerAccountID = 0;
    NSFileGroupOwnerAccountName = wheel;
    NSFileModificationDate = "2014-04-13 21:12:06 +0000";
    NSFileOwnerAccountID = 0;
    NSFileOwnerAccountName = root;
    NSFilePosixPermissions = 449;
    NSFileReferenceCount = 12;
    NSFileSize = 408;
    NSFileSystemFileNumber = 4552991;
    NSFileSystemNumber = 16777224;
    NSFileType = NSFileTypeDirectory;
2014-04-13 16:12:06 -0500 [E] IM: [install failed: 30]
2014-04-13 16:12:06 -0500 [E] IM: Install failed with error code: 30.
2014-04-13 16:12:06 -0500 [I] IM: ---------- log end ----------

I have a 2013 iMac so according to Adobe blog posts it shouldn't be affected by the invalid cpu instruction issue.
Regardless... I still recommend "falling back" to 12 until they get this release right for everyone. I've read plenty of posts in the Apple forums from new iMac, Mini and MacBook users who've had nothing but trouble. Even the "gurus" there are linking to Chris Campbell's post here:
ATTENTION MAC CUSTOMERS - Flash Player 13 "Plugin Failure" Workaround
Using the offline installer completely eliminates the errors seen with the stub installer.

DTM install fails with error 1935 on Windows 7

Trying to install DTM 600_b047 on a Windows 7 64-bit system. Install fails with
Error 1935 and HRESULT= 80073712. Have tried to run via Run As Administrator. It seems to get most of the way through before failing. (Without Run As Admin, it fails much earlier complaining about a cab file not found.)
Any ideas?

Hey adairlw,
Welcome to the BlackBerry Support Community Forums.
What security software is currently installed on the computer?
Also can I get you to re-name the install shield folder which is located under C:\Program files\common files. Once you re-name the folder, then try to install the software.
I look forward to your reply.
-ViciousFerret
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Like! for those who have helped you.
Click Accept as Solution for posts that have solved your issue(s)!

ACR 8.4 CC RC install fails with AAM message 'patch not applicable'

ACR 8.4 CC RC install fails with AAM message 'patch not applicable' - Running Photoshop CC on OSX 10.7.5
Anyone seen this or have any ideas for a fix?
I also have my legacy CS6 installed on the same Mac - tried installing ACR 8.4 CS6 RC and that fails with the same dialogue box from AAM
The DNG converter installs no issue.
Thx
Chris.

Do you have some other software, like Photoshop Elements 12 on your system that would generally also be compatible with ACR 8.4 final but isn’t compatible with the RC because the RC’s only for PS users?
I installed the RC the same day it was released on my computer that has PS-CS6 & PS-CC with Windows 7 and it worked ok, so the update generally works, but something isn’t on your systems.
Are you up-to-date with your PS-CC version, which seems to be 14.2.1:
http://blogs.adobe.com/crawlspace/2014/02/photoshop-cc-14-1-1-update-now-available.html
And is CS6 updated to 13.0.6?
http://www.adobe.com/support/downloads/product.jsp?product=39 <http://www.adobe.com/support/downloads/product.jsp?product=39&platform=Macintosh> &platform=Macintosh

Install Xcode from Appstore. Shows "Installing. 3 minutes remaining."

Hi,
Trying to install Xcode (for iOS 7) from Appstore.
Latest Mac OS X also is installed. Only Xcode shows "Installing. 3 minutes remaining."
From then on, nothing happens.
Any help please?

I'd quit the Mac App Store then look in /Applications to see if there is a file called Xcode. If so drag it to the trash then reboot and try loading it again.
Post back if you still have the problem.
regards

Cumulative Update 3 client update install failed with code 1642

We have SCCM 2012 R2 and recently updated to CU3
Existing client is version 5.00.7958.1000
Pushing update package created during CU3 update failing on some computers
I am trying to update some of laptops using CU3 x86 update and getting following errors
Script for Package:ABC00126, Program: Cumulative update 3 - x86 client update install failed with exit code 1642
I have reviewed many forms but couldn't find relevant.
Update works on about 70% on machines with same image but failed on rest with same 1642 error
Same issues occurs applying client on during TSequence on some of machines.
It is very inconsistent,
Any help would be greatly apprciated
Thanks
RJ
RJ09

I verified package does copied over in ccmcache folder.
Also try to run update package using pstools, got error same as Torsten mentioned.
Here are logs from client.
Checking content location C:\Windows\ccmcache\gt for use
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Successfully selected content location C:\Windows\ccmcache\gt
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Executing program as a script execmgr
13/01/2015 6:56:04 PM 2588 (0x0A1C)
Found executable file msiexec.exe with complete path C:\Windows\system32\msiexec.exe
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Successfully prepared command line "C:\Windows\system32\msiexec.exe" /p configmgr2012ac-r2-kb2994331-i386.msp /L*v C:\Windows\TEMP\configmgr2012ac-r2-kb2994331-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Command line = "C:\Windows\system32\msiexec.exe" /p configmgr2012ac-r2-kb2994331-i386.msp /L*v C:\Windows\TEMP\configmgr2012ac-r2-kb2994331-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous, Working Directory = C:\Windows\ccmcache\gt\
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Created Process for the passed command line
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
AdvertisementId = "ABC212D1";
ClientID = "GUID:f298da2e-dfd1-428e-8b3c-b03602f95719";
CommandLine = "\"C:\\Windows\\system32\\msiexec.exe\" /p configmgr2012ac-r2-kb2994331-i386.msp /L*v C:\\Windows\\TEMP\\configmgr2012ac-r2-kb2994331-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous";
DateTime = "20150114005604.541000+000";
MachineName = "DH-07";
PackageName = "ABC00126";
ProcessID = 3496;
ProgramName = "Cumulative update 3 - x86 client update install";
SiteCode = "abc";
ThreadID = 2588;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\Windows\\ccmcache\\gt\\";
execmgr
13/01/2015 6:56:04 PM 2588 (0x0A1C)
Raised Program Started Event for Ad:ABC212D1, Package:ABC00126, Program: Cumulative update 3 - x86 client update install
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="ABC00126",ProgramID="Cumulative update 3 - x86 client update install", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="ABC00126",ProgramID="Cumulative update 3 - x86 client update install", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
MTC task with id {8EB498C5-71D5-4933-BA80-6EEB8E189F98}, changed state from 4 to 5
execmgr 13/01/2015 6:56:04 PM
2588 (0x0A1C)
Program exit code 1642 execmgr
13/01/2015 6:56:04 PM 2784 (0x0AE0)
Could some please review and advise..
Thanks
RJ09

Flash Player Install Manager[681:16322] Install failed with error code: 30

OS 10.10, MBP 2011 i7, latest updates. I ran the installer by opening up the app package and invoking the install via terminal. at the 75% mark ( download finishes ) the installer fails. in the terminal I got this maybe helpful error message. any idea on getting flash to install ? its worse because I've run the uninstaller so parts of various websites don't work now
S

ok, its a permissions error because the installer isn't at the right run level, even asking for my admin password. if I do
sudo Install Adobe Flash Player.app
[enter password]
Installer now runs. it generates a bunch of error messages in the terminal
Install Adobe Flash Player[744:19476] Error loading /Library/QuickTime/DivX Decoder.component/Contents/MacOS/DivX Decoder: dlopen(/Library/QuickTime/DivX Decoder.component/Contents/MacOS/DivX Decoder, 262): Library not loaded: /Library/Frameworks/DivX Toolkit.framework/Versions/A/DivX Toolkit
Referenced from: /Library/QuickTime/DivX Decoder.component/Contents/MacOS/DivX Decoder
Reason: image not found
——— does this about 10 times ending like this -------
2014-10-28 22:03:10.831 Install Adobe Flash Player[744:19476] Error loading /Library/QuickTime/DivX Decoder.component/Contents/MacOS/DivX Decoder: dlopen(/Library/QuickTime/DivX Decoder.component/Contents/MacOS/DivX Decoder, 262): Library not loaded: /Library/Frameworks/DivX Toolkit.framework/Versions/A/DivX Toolkit
Referenced from: /Library/QuickTime/DivX Decoder.component/Contents/MacOS/DivX Decoder
Reason: image not found
2014-10-28 22:03:47.190 Adobe Flash Player Install Manager[764:19989] Install failed with error code: 17.
the install actually finishes though and flash is working… YAH ! but only a semi uber geek would ever figure this out or think to try it. please fix the installer as its got a problem under 10.10

Installing Mountain Lion from Snow Leopard, Install failed and HD write-locked

I recently downloaded the mountain lion installer from the App Store and I ran the installer. Stupid person as I am, I did not have any backups for my file and I naively assumed that an apple OS installer would be without flaws. Boy, was I wrong. I need every bytes of my data (or close to every bytes) but the installer failed.
Mid installation, the installer stopped and said that the installation failed and that I need to repair my disk. So I restarted the computer and I ran disk utilities (my start up disk was the OS installer and the installer allows me to run several programs, including terminal, disk utilities, and by the way, when I held option while starting up to see which start up disks I have, I only had the OS installer as the start up disk. Also, the installer allows me to run a program called "Startup Disk" when I click on the apple logo on the top left corner, but it doesn't allow me to startup my computer using Macintosh HD) and noticed that when I highlighted Macintosh HD, my "Repair Disk" button was grayed out. So first things first, I ran the "Verify Disk" button but after a minute or so, Disk Utilities said that verification failed and that Macintosh HD needs to be repaired. But the "repair disk" button is grayed out! So I went to the Mountain Lion installer again and ran it. Of course, it failed again so I restarted the computer.
So I tried to first back up all files in Macintosh HD to an external hard drive using Disk Utilities, and I used features such as "New Image" and "Restore" but they both ended up in "Input/Output error". I tried many methods with Disk Utilities but they resulted in errors.
After some research, I noticed that some people's computers worked after they reset their PRAM. So that's what I did. I held command+option+P+R when computer started up and I reset the PRAM. When the start up disk (which is the OS installer, not the normal operating system) loaded, I was greeted with choose languages option and then I was back in the Mountain Lion installer state. I again ran the installer again, hoping something would be different, but then it was different. But not in a good way. When I was told to choose where I would like to install Mountain Lion, I noticed that Macintosh HD was grayed out. Last time, I was at least able to run the installer but this time, Macintosh HD was grayed out. The installer said that my Macintosh HD was locked. After some research, I learned that apparently, the Mountain Lion installer write-locks Macintosh HD mid installation.
So now I am stuck and I am thinking of two things (plus some questions)
1. I am wondering if there is a way to unlock Macintosh HD. But even if I can unlock Macintosh HD, there is no guarantee that the installer will successfully install Mountain Lion, am I right?
a. so how can I un-write-lock Macintosh HD?
2. More realistically, I am thinking of borrowing someone else's macintosh computer and use it as the backup center. I have a firewire cable and a terrabyte external hard drive. So what I'm thinking is that I'll hook my computer in target mode to my friend's computer and I will also plug in my external hard drive to my friend's computer and then I can download and run Carbon Copy Cloner from my friend's computer to copy all data from my Macintosh HD to my external hard drive. And then I will erase my Macintosh HD, freshly install Mountain Lion onto it and then copy all data back from my external hard drive. But I am not sure about few things.
a. it looks like my Macintosh HD is write-locked. Can I still use Carbon Copy Cloner to copy all data from Macintosh HD (in target mode) to my external hard drive?
b. will my computer allow me to erase (or format) Macintosh HD?
c. will my erased/formatted Macintosh HD able to install + be installed Mountain Lion OS?
If you are here, then you have read my long long problem. Thank you very much and I would really really really appreciate your answers and opinions. Thanks

I'm not sure where you read that about the disk being "write-locked." That doesn't make much sense, given that the major task an installer like this must achieve is writing a whole bunch of files to the hard drive. I think your source was mistaken.
As to what happened, it sounds like your hard drive was badly corrupt to start with, or possibly was on the edge of failing and is now in the process of dying entirely. If you don't have backups of your data, that does not bode well for you, unfortunately. If you can manage to use target mode to copy your data, do that.
Once you're sure you've got all your data, you need to start up from your Snow Leopard install disk and repair the hard drive. (Since it sounds like the Mountain Lion installer didn't work, I wouldn't trust the recovery partition that Mountain Lion installs.) Or, even better, just erase the hard drive entirely and reinstall Snow Leopard. Then, once you're back up and running, with all your data back on the system and with Snow Leopard updated to the most recent version, try installing Mountain Lion again. If any of that fails again, the problem is likely to be a dying hard drive, and you'll need to replace it.

Lion OSX install: "about one minute remaining" for 2 hours!... is it hung up?

I am loading Lion OSX over Snow Leopard (after doing Snow Leopard updates) and Lion the install is hung up with "about one minute remaining". It has been like this for over two hours. Should I do a hard shutdown and retry install or just let it go on overnight hoping that it will have finished by tomorrow morning? This is a new harddrive with Leopard then Snow Leopard and now Lion. Mid 2007 iMac. 3gig RAM.
Thanks.

tgrey wrote:
I ended up letting it spin its wheels over night and then did a hard shut down in the morning. After 5 minutes I started it up again and Lion installed smoothly.
Go to Applications > Utilities > DiscUtility and repair permissions for your HardDrive just to make sure nothing has been jostled around during the install. Never hurts to do this.
Good Luck
Pete

Family Pack Leopard install fails G4 Dual 1.2Ghz

All, I purchased the Leopard family pack and have successfully installed it on an Intel Macbook Pro and a G5 2.3Ghz DP machine - flawless, no problems during installation or after.
However, any attempt to install on a G4 Dual 1.2Ghz + 2Gb of RAM + just bought a Seagate 500Gb Barracuda internal drive (well within the designated technical requirements), I've tried the following.
1. Booting the G4 off the Leopard install DVD, I get the following error: Failed Install message = "The Installer could not validate the contents of the Essentials Package...".
I can never get beyond this point. After receiving this error, the internal disk isn't even recognized on the bus - I have to pull the disk out, put it in an external case to reformat it. I've even tried a low level format and also had Seagate replace the disk thinking it was defective.
2. I then thought it may be an issue with putting the Seagate disk in cable select mode versus master / slave configuration. The Seagate is the only hard drive in the machine. I have tried both cable select and master/slave configuration - both freeze after install, etc. without fail.
3. Tried installing Leopard on the G4 by connecting it to the G5 in target disk mode. It installed, but routinely just freezes (NEVER had this issue with Tiger on this machine).
I do see lots of people posting issues with the "The Installer could not validate the contents of the Essentials Package..." error.
For the record, after successful Leopard install using technique #1 and #3 - I am also unable to run the Migration assistant - it fails every time with a kernel panic. I'm not having any trouble with the Leopard install media on any of the other 2 machines, nor did I have issues running the migration assistant.
Any ideas are appreciated. thx,

themdg - you said you put back your 2-512 original RAM cards and tried to install Leopard and the install failed. But my original, factory-installed RAM was third-party RAM which prevented me from installing Leopard, giving the “essentials” error. Only when I purchased RAM from Apple, and used only that RAM to install, could I get it to work correctly.
Check your original RAM. If it is not the Apple brand, it may not work because of that, even if it was the factory-installed RAM.
After I installed Leopard with only the Apple RAM, I added back the third-party RAM and I’ve been running Leopard flawlessly since.
It seems the installation software, which meticulously checks the installer disk for flaws, should also check the RAM to see if the installation will be successful (i.e., check to see if it is going to produce the “essentials” error) and also check to see if you have enough valid RAM to install, before it begins installation, and to let the user know there will be a problem unless the RAM is changed to valid cards.
I “assumed” I had enough valid RAM when I first tried to install Leopard because I had a G5, but it had only 256 MB of non-Apple brand RAM (minimum of 512 is required). A direct check of that by the installer and letting me know it was a problem would have saved me a lot of trouble checking lots of other potential problems, like a bad installer disk, a third-party drive, etc., before I figured out it was insufficient and incompatible RAM for the installation.
I read the minimal requirements for installation of Leopard and probably someone will say I should have checked all those before I tried the installation, but I didn’t, as I’m sure many others have not, because we “assume” Apple had tested it and would prevent us from making any mistake like this.
Previously Apple made their software and hardware to “just work” by providing error messages before we made an error and we have come to rely on that. But they overlooked this problem on this update. It’s the first time I’ve had a problem with an update from Apple.
I’m still a loyal Apple user, but I’ll check requirements a little closer with future updates.

Mac OS X 10.5 Leopard Install Failed

Trying to upgrade a Power Mac Dual G5 from Mac OS X Tiger to Leopard 10.5. When I try to install the Leopard Disc, I keep getting an "Install Failed" message. This is what is said:
Install Failed
Mac OS X could not be installed on your computer
The source media you are installing from is damaged. Try installing from a different copy of the source media or contact the manufacturer for a replacement.
Click restart to restart your computer and try installing again.
Now, I've used this disc once before for an upgrade on a laptop and worked fine, just started to fail when used on the G5. The disc is not scratched, nor looks damaged. Not sure why it's saying damaged? Any insightful knowledge would be appreciated.
Thanks!

The install disks I have are the ones he got with his Mac Mini. Are there different install disks for iMacs? On the disks themselves, it says "for Mac computers."
Do I have to buy an OS which is specifically for iMac?
The discs that came with his computer have only the necessary software pieces needed to run his computer--it lacks the drivers that would be needed run your iMac. (In addition, installing the same copy of the OS on two computers would be a violation of the license, even if it worked.)
You need to buy a retail version of Leopard or Snow Leopard. Since your iMac has an intel processor, you can buy the cheaper Snow Leopard ($29) from the "Store" tab at the top of this page or anywhere that sells Mac software.

LEOPARD INSTALL FAILED - 2ND COPY OF LEOPARD!

I tried putting Leopard on - the disc was scanned and it then went on to install. About 1/3 way through, screen came up with "INSTALL FAILED... MAC OS X could not be installed on your computer. The source media you are installing from is damaged. Try installing from a different copy of the source media or contact the manufacturer for a replacement."
I went back to the Apple store in Regent Street, got a new copy, re-installed the computer with the original recovery discs, and then re-installed the Leopard disc. All was going well until again I got through the 1/3 part of install and the same thing happened as quoted above.
I can't believe the SECOND new copy I got can also be faulty... any other ideas? My machine is completely newly installed, and still no joy.
Does anyone know what else can be done?

OK great news. I finally got it to install on my G5.
See my previous post for the trial and errors.
Here is what I finally did:
1. Unplugged all external drives.
2. Removed all memory except what shipped with my G5. (don't skip this step because other's have said they found bad memory and that solved their problem too.)
3. Boot from the Leopard installer.
4. Ran disk utility before trying to install.
5. Repaired disk permisions from insaller disk.
6. Cant' recall if I rebooted again or not... sorry.
7. Installed Leopard flawlessly. (this was the first time it made it past about 75% before saying "Installation Failed" ... "this DVD disk is damaged etc."
8. I am back up and running.
Thanks for everyone's help.

Leopard Install fails with 2 minutes remaining

Similar Messages

Maybe you are looking for