Acrobat pro want launch after Win 11 24H2 update

[Peter22440460bx94]

My Acrobat Pro won't launch after I installed the Win11 24H2 update.
Acrobat distiller works as does LR & PS.
When acrobat is started no window opens but it can be seen in the task manager.
I have uninstalled via Creative Cloud but now I can't re-install as it gets stuck at 30%.

Anyone else having this problem after updating to Win11 24H2 (full official release, not the pre-release version)

[Peter22440460bx94]

No.

If you use this plug in for work purposes I.e. reading standards, I would suggest you contact the publishers/ distributors of the document with DRM and complain. All the solutions weaken the security of your companies IT infrastructure.

[WUBI]

This seems to have worked for me too. Adobe and Microsoft need to sort this out with an update though - it's so frustrating.

[ricks_dermatology_0175]

Going to Preferences-> Security(enhanced)-> unchecking "Enable Protected Mode at Startup." worked for me as well.

Adobe makes billions a year but can't make software tha opens up when you launch it.  Beautiful.

[Peter22440460bx94]

But that puts you at risk.

Remove Fileopen keeps you secure.

[Haseeb_Ahmad0998]

If Acrobat Pro isn’t launching after updating to Windows 11 24H2, try these steps:

1. End Background Processes: In Task Manager, end any Acrobat-related processes and restart your PC.
2. Creative Cloud Cleaner Tool: Use Adobe’s Cleaner Tool to completely remove Acrobat Pro and its dependencies. Download it here.
3. Run as Administrator: When reinstalling Acrobat via Creative Cloud, right-click the installer and select "Run as Administrator" to prevent installation issues.
4. Check for Compatibility: Ensure Windows 11 24H2 is fully updated and that Acrobat is compatible.
5. Contact Adobe Support: If the problem persists, reach out to Adobe for assistance.

For more tips and tools, visit ytcroxyproxy.com!

[kengosse]

I used the free version of Acrobat Reader but haven't been able to open it since updating last week to Windows 11 24H2 (other apps have been affected, too). I've read in various web discussions that Adobe and Microsoft are working on it. I tried all combinations of running as an administrator and compatibility for Windows 8, but none worked. Guidance on various websites suggest using Preferences to uncheck "Run in AppContainer," but that requires you open Reader first. I couldn't.
I found several sites that suggest a Registry change. I don't recommend anyone fiddle with the Registry, but I've done it, with guidance and caution, for years. In particular, https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/sandboxprotections.html#sandbox-protection.... They suggests changing the Protected Mode from On (1) to Off (0). I found numerous values in the Adobe section of the Registry for "Protected," but finally found "bProtectdMode" in

\HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\DC\Privileged\
I changed it from 1 to 0. I've been able to use Reader again. It runs with or without Admin mode and Compatibility. I have a note to myself to watch for a permanent fix and install the update.

Thanks to everyone who provided help to find a solution.

[ChrisPbass]

1/3/24 - still doesn't work.  
I'm trying to help someone with their computer.
I've never heard of fileopen

They have intuit proseries and sharevault which both utilize PDFs so I'm wondering if that's the problem.
For now, we are using Cut*PD4 pro.  not trying to steal biz or anything, just saying what we're doing.

[ChrisPbass]

That would be 1/2/25 

[julius_1721]

Hi Souvik,

thanks for the compatibility tip. While it is a workaround that lets me at least read the pdfs I paid a lot of money for, it's far from a solution. Has several drawbacks, IT security, "take the tour" every time I open Adobe Reader, just like many others noted.

What's hard to understand is why after almost four months, Adobe still has no real fix.

Can you provide a reliable estimate at what date we can expect a fix?

Thanks

Julius

[Peter22440460bx94]

This isn't really an Adobe or Microsoft problem but a Fileopen problem. Remove the plug in Fileopen and all will work.

I found the only work around that keeps all the security to my system is to remove the DRM from the documents. This maybe unlawful in some regions.

[julius_1721]

Trouble is, if I remove the FileOpen plugin, then I cannot read the CIE standards any more, which are protected with FileOpen. And I _do_ need these standards in my daily work. As a member of CIE, I'm simply not going to do something illegal here. CIE has paid for the FileOpen service, and the service is bad. I'm 100% percent sure that if someone on this planet has enough leverage to make the FileOpen people fix it, then it's Adobe. Moreover, Souvik from Adobe wrote more than once that "we are working on a fix".

[Peter22440460bx94]

It is not necessarily unlawful to remove drm, it all depends on intent, reasons, wording of the copyright etc.

If you are a member of CIE it is upto you to push back at the restrictive practices that CIE have used, and the third party supplier they have chosen to enforce these.

Imo DRM only affects those using the standards legally. Ppl using them illegally will continue to circumvent DRM.

The single user, single print is a restrictive practice and hinders industry. Amazon use a single license DRM system where any licensed user can access the document bit only 1 at a time.

I have complained to BSI that, as a cyber security leader, why they would want me to remove security features that Adobe have spent time in developing.

Who polices the Police!

[julius_1721]

I told CIE, of course. They are looking into it, but they are slow, like all standardization bodies, and my voice may not have sufficient weight. And while I am a freelancer and nerdy enough to know how to remove DRM if I'd want to, I'm not going to waste my time on finding and studying lengthy copyright documents, which at best will be ambgiuous anyway. Many others who need FileOpen protected documents will not be savvy enough to remove DRM, or will be restricted to do so through their employers' corporate policies.

The ball is squarely in the joint court of Adobe, Microsoft and FileOpen.

[julius_1721]

And yes, of course, @Peter22440460bx94 , I fully agree with you on this: The practice is restrictive and hinders industry. I have bought other pdf files, for example the LaTeX Companion III from Pearson/InformIt, which has my name on every page, in a hard to remove way. I think that should be sufficient and much less annoying. But it would put FileOpen out of business, of course. If someone would be savvy enough to work around the "hard to remove" part, that person could just as easily remove the FileOpen DRM.

[Tyson32690690akfj]

It's actually likely that CEI is breaking their own terms of service by making you compromise your own security and being unable to deliver the product that was originally sold. We use ASME and CSA standards on the daily and I did some research into their terms of service and essentially if your document provider mandates the use of insecure configurations to access its files, this could be considered unreasonable and a breach of implied usability and safety standards based on thier own terms of service. I would reccomend writing a letter to CIE that formally states this breach of contract.

Just my two cents at least. 

[julius_1721]

And now, as of today, Acrobat Reader stopped working even though compat mode to win 8 is set. As if Adobe wanted to punish me.

[SASITHARAN]

This Not working I need the Acrobat pro want launch for signing of Offical Documents, PLEASE HELP

[Tyson32690690akfj]

Best bet is to re-write it in MS word, print it off and sign it with a pen lol.

[Tyson32690690akfj]

In all seriousness, try opening Acrobat DC on it's own without trying to open a file. then go: Menu > Preferences > Security (Enhanced) > Make sure "Run in AppContainer" is UNCHECKED. Be aware that this gives root access for any software embedded into a pdf to run directly on your device and can be a serious breach of security. Makes sure you Re-Enable "Run in AppContainer" once you are done.

[OttoNormal]

Hi all, 

same issue here .. nothing seems to work for me.
im using current adobe acrobat build (24.005.20392) Win 10 22h2 paird with FileOpen B998 (latest build asswell).
FileOpen.api is visable within the plugins folder. FileOpen Service is running. Run in AppContainer and Proteced Mode at Startup ist unchecked as well. I have a fresh install of my os and adobe as well.
any help would be nice. 

[julius_1721]

Adobe is awfully quiet recently in this discussion. A person named Souvik gave some promising comments weeks or months ago, but no more. It seems to me that Adobe just doesn't care. I'd be delighted to be be proved wrong!

[S. S]

Hi @julius_1721,

I am still up on the thread, however, I haven't heard anything concrete from the FileOpen team.

A ticket is open on their end, and the last comment we heard from them was, that they have found the fix and will add it to the next iteration of the plugin.

I will keep the thread updated on the progress.

-Souvik

[julius_1721]

Souvik,

thanks for your response, but it doesn't make the situation much better.
I currently __can__ __not__ open documents I paid a lot of money for, and which I need for my work.
Are you seriously trying to tell me that Adobe doesn't have enough leverage over FileOpen to make them act in a timely manner? When is that next iteration they "promised"? In 2032? (Sorry for getting sarcastic...)

[Tyson32690690akfj]

The issue is that FileOpen is 3rd party service that is not manditory to use with Adobe acrobat. The content creators or owners are electing to use the FileOpen software to protect their documents. The push needs to come from the companies that are paying bills that keep lights on at FileOpen.

[julius_1721]

@Tyson32690690akfj, @S. S , I don't buy this blame game. To quote from the "Adobe Reader Integration License Agreement", which FileOpen must have signed:

"If Adobe, in its sole discretion, determines that the Licensee Plug-in fails to conform the Application, Licensee will, at Adobe's written direction, (i) modify the Licensee Plug-in as requested by Adobe within thirty (30) days of written notice, or (ii) cease distribution of the Licensee Plug-in within fifteen (15) days of written notice. Licensee, will promptly cooperate with Adobe to facilitate periodic review of the Licensee Plug-in and will promptly correct any non-conformity as requested by Adobe".

Souvik: All it would have taken for Adobe would have been to produce this written notice months ago. Adobe has plenty leverage, but doesn't use it. I think it's pretty obvious that Adobe just doesn't care.