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

Windows compatibility with builds from 3rd party

New Here ,
Oct 21, 2019 Oct 21, 2019

I am trying to get adobe suite through my school and they have to download packages ('build') in sets through an administrator account and then transfer it to my laptop. The package is set up for Windows but downloaded through a mac. The issue is that, when installing, the green bar gets to about 90% before restarting, getting to the same place and then going back to 0 and closing the installer without finishing. I have used an Adobe cleaner and tried restarting my laptop and having the installer be the first programme to run.

487
Translate
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 ,
Oct 21, 2019 Oct 21, 2019

You need to talk to your schools IT department and or the section that set this type of thing up.

Personally I have never heard of something like this, Especially the part about the package being for Windows but downloaded on a Mac.

The Win installed will be a .exe file and on a Mac it is a .dmg. Never the twain will meet.

 

Translate
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 ,
Oct 22, 2019 Oct 22, 2019

First, thank you for your reply. Second, the Creative Cloud Installer is .exe but the self-service installer is .msi. When I run the Creative Cloud Installer, it runs an error message that says "Installation Failed. Please refer to PDApp.log for more information (which runs an insanely long log that I don't understand).

 

In the Log, however, I have been able to find that the programme 'failed to launch the bootstrapper process. Stopping the Installation process'. Also, I think this might be because it is trying to launch the bootstrapper from a location that does not exist. The launch location is, according to the log,  .../Adobe-Self Service- Windows- English/Build/ASU2/Set-up.dat but there is no ASU2 folder in the Build folder. Any idea how I can change this issue? Should I rename the ASU_4.9 folder to ASU2 so it is recognised?

 

Edit: I tried this and, unsurprisingly, it did not work. Here is a link to a google doc of the log: https://drive.google.com/file/d/14Z-S2xNDwXCKlAXHR6qhi801j3-OK8e7/view?usp=sharing

Translate
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
Mentor ,
Oct 22, 2019 Oct 22, 2019
LATEST

Good morning, SSheath.
I think may be stuck that I downloaded the package through Mac.
As the package may be damaged, as the Just Shoot Me says, it is necessary to check with the school that received the package with the log.

Translate
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