Locked

Flash Player Install failed with error code: 30

New Here ,
Apr 13, 2014 Apr 13, 2014

Copy link to clipboard

Copied

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   IM: ---------- log start ----------
2014-04-13 16:12:01 -0500   IM: All install checks pass
2014-04-13 16:12:01 -0500   IM: Unexpected umask value for process: 0
2014-04-13 16:12:06 -0500   IM: User does not have any processes that need to be closed.
2014-04-13 16:12:06 -0500   IM: [install started]
2014-04-13 16:12:06 -0500   RA: Unable to launch FPInstallHelper. Error = 'launch path not accessible'

2014-04-13 16:12:06 -0500   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   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   IM: [install failed: 30]
2014-04-13 16:12:06 -0500   IM: Install failed with error code: 30.
2014-04-13 16:12:06 -0500   IM: ----------  log end  ----------
 

Views

3.0K

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Apr 13, 2014 Apr 13, 2014

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 15, 2014 Aug 15, 2014

Copy link to clipboard

Copied

LATEST

The cause of this problem seems to be a bug in the installer that causes the installation process to fail if the installer is executed on an OS X user account that has only standard privileges rather than administrative privileges. You can work around the problem by executing the installer on a user account that has administrative privileges.

It would seem that Adobe have yet to master developing software for multi-user operating systems.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines