[SOLVED] Windows 11 Adobe Creative Cloud Installer Dependencies

F

F!NN

New Member
Messages
5
Reaction score
2
Hey, I am fairly new to NTLite and I've been working on a custom Windows 11 version for the past few days.
My goal is a clean and lightweight Windows 11 which still has all the features I need.
I used the GamerOS Preset made by Txmmy as basis and slowly added back the components needed for all the features and programs I use.
Thanks to NTLite this wasn't too complicated and I managed to get everything to work just fine.
Except one thing which is the adobe creative cloud installer. Every time I try to run it I get a installation error 717.
I did some testing and I am 99% sure its because of the custom image.
Is there any known component needed for the installer or a workaround to that problem?
I would be so grateful for any help I can get c:
 
I looked at the thread you send and it might become useful later. But my problem is that I can't even open the installer. As soon as I try to run the exe file I get an error. Pls correct me if I'm wrong but I dont think, that I will be able to fix the problem with windows media player.
I'll attach you a screenshot of the error:

View attachment 9034
 
I don't have edge legacy and I use creative cloud everyday, even though if it fixes the isue it might be something else
 
I was pretty busy the last few days but finally managed to do some testing.
After I added back the Internet Explorer - 32bit the adobe Installer works again.
I find it hard to believe that a company like adobe still uses IE.
Never would have thought that IE is the problem since it is ancient and also marked as green I expected it to be safe to remove.
garlin I have to admit that I didn't quite understood what you said. Is there a way to get it work without IE?
 
For countless years, MS encouraged Adobe and other software vendors to use Windows frameworks for better compatibility. This would include IE (HTML elements) and WMP (codecs). The problem is MS abandoned IE11 (rightfully) and Adobe's slow move to Plan B.

Plan B would be migrating to Edge (still a sin, but Edge will supported for a decade), or writing their own libraries.

Since Adobe hasn't hit the panic button, it's sadly up to us to figure out what backwards compatibility is required. If Interner Explorer - 32 bit was the missing key, I'm shocked that Adobe's code is that old. Would have expected it to use Edge (Legacy) instead.
 
Very Interesting but also sad and disappointing that the market leader is so lazy and outdated!
I would say the problem is solved and I want to thank you again for the help! c:
(Do I have to close or mark this thread now?)
 
garlin said:
For countless years, MS encouraged Adobe and other software vendors to use Windows frameworks for better compatibility. This would include IE (HTML elements) and WMP (codecs). The problem is MS abandoned IE11 (rightfully) and Adobe's slow move to Plan B.

Plan B would be migrating to Edge (still a sin, but Edge will supported for a decade), or writing their own libraries.

Since Adobe hasn't hit the panic button, it's sadly up to us to figure out what backwards compatibility is required. If Interner Explorer - 32 bit was the missing key, I'm shocked that Adobe's code is that old. Would have expected it to use Edge (Legacy) instead.
Click to expand...
Real problem is; devs are assuming (rightfully) all windows systems at core are the same. So they don't really care about changing the code about compatibility unless microsoft releases their plan about removing the component completely.
 
F!NN said:
I was pretty busy the last few days but finally managed to do some testing.
After I added back the Internet Explorer - 32bit the adobe Installer works again.
I find it hard to believe that a company like adobe still uses IE.
Never would have thought that IE is the problem since it is ancient and also marked as green I expected it to be safe to remove.
garlin I have to admit that I didn't quite understood what you said. Is there a way to get it work without IE?
Click to expand...
sir give me the link Internet Explorer - 32bit i have same problem
 
There is no link, it's a Windows component that you shouldn't remove so Adobe's installers are happy.
 
When you're making your custom ISO, keep "Internet Explorer - 32 bit" in Components. Don't remove it.

If you have a licensed copy of NTLite, you can try to reinstall IE - 32 bit using host refresh. Make a new image, but with IE - 32 bit. If you don't have the licensed copy, then you will have to start over with a new image and re-install Windows before Adobe works again.
 
garlin said:
When you're making your custom ISO, keep "Internet Explorer - 32 bit" in Components. Don't remove it.

If you have a licensed copy of NTLite, you can try to reinstall IE - 32 bit using host refresh. Make a new image, but with IE - 32 bit. If you don't have the licensed copy, then you will have to start over with a new image and re-install Windows before Adobe works again.
Click to expand...
btw, once I installed adobe with "Internet Explorer - 32 bit", is it possible to do a host-refresh and remove it then? Or will it break again xd
 
I believe the installer needs it. After that, I don't know if the Adobe products use it again to download update files.
 
garlin said:
I believe the installer needs it. After that, I don't know if the Adobe products use it again to download update files.
Click to expand...
good point, it very much likely uses the same tech to install/upgrade other stuff, so i better let it be there. thanks!
 
You must log in or register to reply here.
Back
Top