Skip to main content
T
tgeq175e
Participant
June 8, 2023
Answered

Re: where can i get an MSI installer of Adobe Creative Cloud for Desktop

  • June 8, 2023
  • 2 replies
  • 12840 views

I realize this is an old thread, but I wanted to follow up on this post with a further question. Is there a way to create just 1 msi file that would install the Adobe Creative Cloud app? 

 

Here's the issue I am running into: when I create the package that I want, it is a zip file, that once extracted has numerous directories and subdirectories that apparently the msi file depends on; however, I am looking to deploy this via enterprise-level deployment software and I can only upload an .msi file -- there is no way to include several other folders, etc. along with it. How would I accomplish this--this has got to be common as the prior 2 insitituions/companies I have worked for had deployed creative cloud to 100's of workstations, accounts, etc. 

      Correct answer Anshul_Nautiyal

      Hi, 

      I can't seem to get the MSI or .EXE to work.

      When attmepting to install the .EXE manually I get this error and it won't work via Intune for the Win32 App.

      02/06/25 12:52:03:480 | [INFO] | | ASU | MSIInvoker | MSIInvoker | | | 25076 | Setup exiting with return code (1)
      02/06/25 12:57:58:174 | [INFO] | | ASU | MSIInvoker | MSIInvoker | | | 15820 | Build Version - 2.2.0.6
      02/06/25 12:57:58:174 | [INFO] | | ASU | MSIInvoker | MSIInvoker | | | 15820 | Logging Level verbosity Set to 4
      02/06/25 12:57:58:174 | [ERROR] | | ASU | MSIInvoker | MSIInvoker | | | 15820 | Failed to get Build directory path or Windows installer MSI path.

       

      When attempting manually through the MSI an error is being thrown up due to the MSI not being signed and having the Adobe certificate, do you happen to have an MSI with the Adobe Certificate signed? Or a way I can attach the certificate from the .EXE to the MSI?


      Hi @JF_Tote,

      Thank you for reaching out. The error messages provided indicate multiple issues during the installation of both the EXE and MSI versions of the Adobe package. A return code of 1 typically signifies a general installation failure, which could result from missing dependencies, permission restrictions, or an incorrect installation path. I recommend running the EXE as an administrator to rule out permission-related issues.

      The error "Failed to Get Build Directory Path or Windows Installer MSI Path" suggests that the installer cannot locate the necessary installation files or paths. This could be due to insufficient permissions preventing access or extraction. Please ensure the installer has the appropriate permissions and that all required files are intact.

      Additionally, remnants of older Adobe versions can sometimes interfere with new installations. I recommend uninstalling any previous Adobe versions and using the Adobe CC Cleaner Tool to remove leftover files and registry entries before attempting the installation again.

       

      For deployment, you may also consider using single-app packages, which can be found here: Pre-Generated Packages Guide.

      Let me know if you need further assistance.

      Regards,
      ^AN

      2 replies

      J
      JF_Tote
      Participant
      February 3, 2025

      Hi, 

      We are attempting to install the MSI now and are getting the following error when attempting to install manaully:

      When attempting via Intune it comes back with Fatal error, I believe it will be due to this.

      Anyone know how to resolve?

      A
      Community Manager
      Anshul_NautiyalCommunity Manager
      Community Manager
      February 3, 2025

      Hi @JF_Tote,

      Thank you for reaching out. It looks like you have an active Teams subscription associated with the Adobe ID you used to post your query. You’re encountering the fatal error while trying to install the MSI through Intune, and receiving the following prompt during a manual installation. Here are some steps to help resolve the installation issue:

      Verify Package Integrity
      Ensure the MSI file isn’t corrupted. Try re-downloading or re-extracting it to ensure all files are intact.
      Run as Administrator
      When installing manually, right-click the MSI file and select “Run as administrator” to avoid permission issues.
      Enable MSI Logging
      Run the installer with logging enabled to capture detailed error codes. Reviewing the log can pinpoint which step is failing. Use the following command to enable logging:
      Check for Previous Installations
      Sometimes, remnants of an older Adobe version can interfere. Uninstall any previous Adobe versions and clean up leftover files/registry entries if necessary. The Adobe CC Cleaner Tool can help with this. 
      Bypass SmartScreen Warning (testing)
      If Microsoft Defender SmartScreen is blocking the installation because it doesn't recognize the publisher of the MSI package:
      Right-click the MSI file > Properties > Unblock > Apply > OK. Then try installing again.
      Alternatively, you can temporarily disable SmartScreen:
      Go to Settings > Windows Security > App & Browser Control > Reputation-based Protection > Turn off Check apps and files. Run the installer, then re-enable SmartScreen after installation.
      Deployment through Intune:
      For deployment through Intune, you can check out the following document: Deploy packages using Microsoft Intune.
      Additionally, you can try using single-app packages for installation: Package templates.
      I hope this helps! If you have any further questions or need additional assistance, feel free to ask.

       

      Regards,
      ^AN

      J
      JF_Tote
      Participant
      February 6, 2025

      Hi, 

      I can't seem to get the MSI or .EXE to work.

      When attmepting to install the .EXE manually I get this error and it won't work via Intune for the Win32 App.

      02/06/25 12:52:03:480 | [INFO] | | ASU | MSIInvoker | MSIInvoker | | | 25076 | Setup exiting with return code (1)
      02/06/25 12:57:58:174 | [INFO] | | ASU | MSIInvoker | MSIInvoker | | | 15820 | Build Version - 2.2.0.6
      02/06/25 12:57:58:174 | [INFO] | | ASU | MSIInvoker | MSIInvoker | | | 15820 | Logging Level verbosity Set to 4
      02/06/25 12:57:58:174 | [ERROR] | | ASU | MSIInvoker | MSIInvoker | | | 15820 | Failed to get Build directory path or Windows installer MSI path.

       

      When attempting manually through the MSI an error is being thrown up due to the MSI not being signed and having the Adobe certificate, do you happen to have an MSI with the Adobe Certificate signed? Or a way I can attach the certificate from the .EXE to the MSI?

      M
      MR31052825yqbh
      Participant
      September 22, 2023

      Hello, I am in the same situation. The Online package creator creates a big zip file, in which are both the MSI and many other files.

      kglad
      Community Expert
      kgladCommunity Expert
      Community Expert
      September 25, 2023

      i've not done this so i'm not aware of the issues but, on the off-chance you haven't read this, start here

      - https://helpx.adobe.com/enterprise/using/deploy-packages.html

       

      if you've already gone through that and not found help, open the support tab on your admin console > start chat or start case or request expert session. https://helpx.adobe.com/enterprise/using/support-and-expert-services.html

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices