• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

The Bootstrapper Process return code is (5).Stopping the installation process.

New Here ,
Jul 08, 2016 Jul 08, 2016

Copy link to clipboard

Copied

I can't figure out what this error code means.

I've included the entire PDApp.log below but first a little information about my situation:

I'm trying to install this on a Windows 7 computer from the only account, which is an Administrator account; I'm selecting to run the setup as administrator, and UAC functions normally, allowing me to give it permission to run, and then it hangs on the bootstrapper (obviously). The FAQ doesn't include my error code in the common error codes, nor can I find info about a "5" anywhere else online.

07/08/16 03:45:05:048 | [INFO] |  | ASU | MSIInvoker | MSIInvoker |  |  | 5568 | Setup exiting with return code (6)

07/08/16 03:45:11:125 | [INFO] |  | ASU | MSIInvoker | MSIInvoker |  |  | 1052 | Build Version - 1.9.5.141

07/08/16 03:45:11:125 | [INFO] |  | ASU | MSIInvoker | MSIInvoker |  |  | 1052 | Logging Level verbosity Set  to 4

07/08/16 03:45:11:125 | [ERROR] |  | ASU | MSIInvoker | AAMEEUtilities |  |  | 1052 | Failed to get directory handle(C:\Users\caitlin\Downloads\CCCore\Build\Setup\*)(3)

07/08/16 03:45:12:059 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 2908 | Build Version - 1.9.5.141

07/08/16 03:45:12:059 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 2908 | Logging Level verbosity Set  to 4

07/08/16 03:45:12:059 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 2908 | Executing immediate custom action for install mode.

07/08/16 03:45:12:060 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 2908 | The CustomActionData string is : mode=install;sourceDir=C:\Users\caitlin\Downloads\CCCore\Build\;installDir=;origDB=C:\Users\caitlin\Downloads\CCCore\Build\CCCore.msi;installLang=

07/08/16 03:45:12:060 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 2908 | Successfully executed the immediate custom action for install mode .

07/08/16 03:45:15:666 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Build Version - 1.9.5.141

07/08/16 03:45:15:666 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Logging Level verbosity Set  to 4

07/08/16 03:45:15:666 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Executing the deferred custom action.

07/08/16 03:45:15:669 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Obtained the following as CustomActionData

07/08/16 03:45:15:669 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | (mode=install;sourceDir=C:\Users\caitlin\Downloads\CCCore\Build\;installDir=;origDB=C:\Users\caitlin\Downloads\CCCore\Build\CCCore.msi;installLang=)

07/08/16 03:45:15:669 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | (mode=install;sourceDir=C:\Users\caitlin\Downloads\CCCore\Build\;installDir=;origDB=C:\Users\caitlin\Downloads\CCCore\Build\CCCore.msi;installLang=)

07/08/16 03:45:15:669 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Original database path is : C:\Users\caitlin\Downloads\CCCore\Build\CCCore.msi

07/08/16 03:45:15:682 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | OptionXML saved at location :: C:\Users\caitlin\AppData\Local\Temp\{3E7DC3F5-476B-4698-8A1B-40905DA8DCC1}\\{053E0105-17A4-460E-BB5E-F9FA4E9ABC3D}

07/08/16 03:45:15:855 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Build Version - 1.9.5.141

07/08/16 03:45:15:856 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Logging Level verbosity Set  to 4

07/08/16 03:45:15:856 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | CustomAction Parameters obtained...

07/08/16 03:45:15:856 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 |  optXMLPath :: C:\Users\caitlin\AppData\Local\Temp\{3E7DC3F5-476B-4698-8A1B-40905DA8DCC1}\\{053E0105-17A4-460E-BB5E-F9FA4E9ABC3D}

07/08/16 03:45:15:856 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 |  setupBasePath :: C:\Users\caitlin\Downloads\CCCore\Build\

07/08/16 03:45:15:856 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 |  installDirPath ::

07/08/16 03:45:15:856 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 |  installLang ::

07/08/16 03:45:15:856 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Initializing Custom Action Data from parameters

07/08/16 03:45:15:856 | [INFO] |  | ASU | DeploymentManager | Utilities |  |  | 5864 | Folder does not exist

07/08/16 03:45:15:856 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Provisioning Tool path is (C:\Users\caitlin\AppData\Local\Temp\{3E7DC3F5-476B-4698-8A1B-40905DA8DCC1}\\{6964ECCF-6442-4091-B7A8-0FA2644C2B6E}).

07/08/16 03:45:15:857 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Starting to run the custom action for install mode

07/08/16 03:45:15:857 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | STEP 1: Starting to parse Option XML.

07/08/16 03:45:15:862 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Match OS lang option selected

07/08/16 03:45:15:862 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Added OS Language (en_US) to the install language fallback.

07/08/16 03:45:15:862 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Install language fallback contains following languages :

07/08/16 03:45:15:862 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 |     (en_US)

07/08/16 03:45:15:862 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 |     (en_US)

07/08/16 03:45:15:862 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Self-Update BootStrapper Relative Path doesn't exist.

07/08/16 03:45:15:863 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | No of updates found (0).

07/08/16 03:45:15:863 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | No of HD products found (0).

07/08/16 03:45:15:863 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Custom deployment path doesnt exist in options XML

07/08/16 03:45:15:981 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Number of Medias found = 0

07/08/16 03:45:15:981 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Deployment Manager is running in Update Mode.

07/08/16 03:45:15:981 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | STEP 2: Checking if updates are applicable to the machine.

07/08/16 03:45:15:981 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Number of updates to apply is (0).

07/08/16 03:45:15:981 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | STEP 3: Starting apply updates to AAM.

07/08/16 03:45:15:981 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Bootstrapper launch location is :: C:\Users\caitlin\Downloads\CCCore\Build\ASU\Set-up.dat

07/08/16 03:45:19:187 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Build Version - 1.9.5.141

07/08/16 03:45:19:187 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Logging Level verbosity Set  to 4

07/08/16 03:45:19:187 | [FATAL] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | The Bootstrapper Process return code is (5).Stopping the installation process.

07/08/16 03:45:19:188 | [INFO] |  | ASU | DeploymentManager | Utilities |  |  | 5864 | Folder does not exist

07/08/16 03:45:19:188 | [ERROR] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | Failed to get/verify the UpdaterCore inventory base path (C:\Program Files (x86)\Common Files\Adobe\AAMUpdaterInventory\1.0\)

07/08/16 03:45:19:188 | [WARN] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | sendAnalytics : Unable to find deviceId.

07/08/16 03:45:19:188 | [INFO] |  | ASU | DeploymentManager |  |  |  | 5864 | Event Guid generated is: '5fee399b-5416-445b-bccb-4e2ad95f1618'

07/08/16 03:45:19:199 | [INFO] |  | ASU | DeploymentManager |  |  | HTTPConnector | 5864 | GetIEProxyInfo - No default proxy present on the user machine

07/08/16 03:45:19:396 | [INFO] |  | ASU | DeploymentManager |  |  | HTTPConnector | 4300 | HTTP Request Status code 200.

07/08/16 03:45:19:396 | [INFO] |  | ASU | DeploymentManager |  |  | HTTPConnector | 5864 | The http request returned HTTP_Status:0 HttpCommunicator error:0

07/08/16 03:45:19:396 | [INFO] |  | ASU | DeploymentManager |  |  |  | 5864 | Waiting for the async thread to get the task completed

07/08/16 03:45:19:398 | [INFO] |  | ASU | DeploymentManager |  |  |  | 3312 | Async thread is completed. Now exiting from function.

07/08/16 03:45:19:399 | [INFO] |  | ASU | DeploymentManager | DeploymentManager |  |  | 5864 | The install workflow is terminating.

07/08/16 03:45:19:922 | [INFO] |  | ASU | MSIInvoker | AAMEEUtilities |  |  | 1052 | Process creation completed.

07/08/16 03:45:19:922 | [INFO] |  | ASU | MSIInvoker | MSIInvoker |  |  | 1052 |  The return Code from Create Process (1603).

Views

9.5K

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
Adobe Employee ,
Jul 08, 2016 Jul 08, 2016

Copy link to clipboard

Copied

Votes

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
Community Beginner ,
Jul 10, 2017 Jul 10, 2017

Copy link to clipboard

Copied

I had this same error when I would use the CC Cleaner tool to Uninstall the Creative Cloud Desktop package that was created using the CCPackager tool.

After uninstalling the CC Desktop package, it would fail to reinstall with exit code 1603.  I checked the PDApp.log and it showed a FATAL error "The bootstrapper Process return code (50). Stopping the Installation."

My solution to allow the reinstall of the CCDesktop package was in the wrapper script (vbscript) to install the package I had to do the following:
TASKKILL.exe /F /IM explorer.exe /T  (kills any explorer.exe processes)
Install the Creative Cloud Desktop package

oWSH.Run "explorer.exe"  (creates an explorer.exe process)

I believe the reason explorer.exe needs to be killed first is because the CC Desktop includes the "Creative Cloud Files" symbolic link under Favorites in the Windows Explorer window.  I noticed that the first time I installed the package interactively, the MSI itself does kill the explorer process and recreates it, so I'm not sure why on a reinstall it isn't able to do it as well.

I suggest if you are deploying this silently via SCCM you only install it when no user is logged on.

When you use the CCPackager tool to create a package for the CC Desktop simply uninstalling the MSI using msiexec will not actually remove the CC Desktop.

This appears to be by design by Adobe as they don't want this component to be uninstalled from the PC when you remove these CC packages.

The only silent uninstaller I can find for the CC Desktop was using the CC Cleaner tool. 

Votes

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 ,
Dec 11, 2017 Dec 11, 2017

Copy link to clipboard

Copied

This sorted my error 50 out too - nice one Davet - so yes, going to go with the "no user logged on" method rather than a task kill, I'll see how it goes out to 15-20 machines and if it's still an issue may have to update to the harsher task kill method (wouldn't be surprised if our desk got a ton of calls on roll out day though as peoples "systems break")

Definitely a harsh learning process managing Adobe suite upgrades. I don't know why they can't generate more user friendly logs - can they not bundle error codes with more details i.e. what the code is/which specific element (e.g. in this example, explorer.exe) rather than us having to do harsh investigations.

Votes

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
Explorer ,
Jun 17, 2018 Jun 17, 2018

Copy link to clipboard

Copied

Hi davet85363853,

Sorry for the latish ask, but in this area nothing is too late if we can breath and are in able to ask.

I have tried your suggestion via vbs to wrap the instalation of Animate CC 2017 but the result was the same - no luck!

Here is the last log lines of PDApp.log:

06/18/18 08:38:02:483 | [ERROR] |  | ASU | MSIInvoker | AAMEEUtilities |  |  | 6900 | Failed to get directory handle(D:\temp\install\Adobe Animate CC 2017.1\Build\Setup\*)(3)

06/18/18 08:38:03:481 | [INFO] |  | ASU | MSIInvoker | AAMEEUtilities |  |  | 6900 | Process creation completed.

06/18/18 08:38:03:481 | [INFO] |  | ASU | MSIInvoker | MSIInvoker |  |  | 6900 |  The return Code from Create Process (1633).

Second, i also used Adobe CC Cleaner tool to clean out previous Creative Cloud Desktop package instalation.

Third, this is the VBS wrapper code:

set objShell = CreateObject( "WScript.Shell" )

set objRes1 = objShell.Exec( "TASKKILL.exe /F /IM explorer.exe /T" )

'A setup.exe is in the same folder as vbs script

set objRes2 = objShell.Exec( "setup.exe" )

' Wait for the child process to finish

Do While objRes2.Status = 0

     WScript.Sleep 100

Loop

`Start explorer

set objRes3 = objShell.Exec( "explorer.exe" )

I test is as Run as Administrator. The OS is Windows 7 pro SP1 32 bit.

If you could find any other solution it would be great for meq and may be for others.

Thanks in advance

Votes

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 25, 2021 Aug 25, 2021

Copy link to clipboard

Copied

Sorry I'm replying to such an old thread... but it's the first one that pops up with the boostrapper (5) return error code...

 

I had this issue today. The method that fixed it for me was to close out of MS apps (excluding MS Teams), then re-run the installer.

Votes

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 25, 2021 Aug 25, 2021

Copy link to clipboard

Copied

LATEST

Glad you replied! This did it for me too.

Votes

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