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)

[JLovell]

Same issue, i uninstalled Acrobat, reinstalled it... it then launched once but now does not work.

[sergio_0092]

Same here, the installer dont open

[JLovell]

If you set to run it in windows 8 compatibility mode I can get it to run.

[JLovell]

Ok, so after having another look thismorning, it's the preference 'Security (Enchanced)/Enable Protected Mode at startup' causing the issue for me... so, enable Windows 8 compatibility mode, then go and disable 'Enable Protected Mode at startup' the close and remove compatibility mode. I aslo needed to untick 'Enable Enhanced security' for signatures to work.

[TehBishop42]

Couldn't get Acrobat Reader 64-bit version to work; with/without compatability or container. However, I deleted 64-bit and installed (unmarked) (32-bit presumed) version from download site and it appear to be working. I did notice there's a 32-bit upgrade service running in the task list so I wonder if that's conflicting w/ the 64-bit version? Shots in dark. Good Luck.

[Peter22440460bx94]

I've solved my issue, it was Open file, a DRM service preventing acrobat from running. I've removed that and everything works as it should.

No idea how I'm going to open the DRM enabled files.

[JLovell]

Do you mean 'OpenFile'? I also have that installed for opening purchased BSI Standards.

[JLovell]

Sorry, i meant 'FileOpen'.

[Peter22440460bx94]

Yes.

I have it for the very same overly restrictive reason. Thanks BSI

[alanr71024047]

I can confirm this is a problem.  FileOpen does not like the new 24h2 update here either.

[tomw96711251]

Had the same issue. Disabling protected mode worked, but FileOpen seems to be the root cause of the problem. Not sure if this is also affecting those having issues installing Acrobat?

[adobeforumuser72]

Same Issue with FileOpen Plugin 998, Acrobat Reader running in the background but will not open. After FileOpen is uninstalled all works fine.

[Tyson32690690akfj]

I reached out to the File Open team and their president actually responded quite promptly, below is his response,

"Sorry for the inconvenience. We are aware of this issue. Here’s what we know so far:

We’ve gotten reports, and have confirmed, that there is an issue with Acrobat and the FileOpen Client under the new Windows 11 24H2 release. This has been available only as a preview, but is now starting to roll out in the UK and will be released in the US in coming weeks. Hopefully there will be a solution before it gets too widespread.

The issue appears to be related to an Acrobat security feature called “AppContainer” which is blocking interprocess communication between the plug-in and the Broker process. We think that Microsoft changed something that affected Adobe’s implementation. We are currently waiting for Adobe Engineering to give us an explanation. Our hope is that they can fix it via their own Updater, but we will create a new build of the FileOpen Client if necessary.

The issue manifests as Acrobat/Reader not starting up after the 24H2 update.  

There are two workarounds that we know of:

• Set Acrobat/Reader to run in Win8 Compatibility mode.
• Do this by right clicking the launch icon for Acrobat/Reader and selecting Properties>Compatibility>Compatibility mode>Run this program in compatibility mode for: Windows 8

• Configure Acrobat/Reader to run without AppContainer:
• Force-close FileOpenBroker64.exe from the task bar and re-start Acrobat/Reader. Dismiss the message from the FileOpen Client.
• Open Acrobat/Reader and from Menu>Preferences>Security (Enahnced)>Sandbox Protections and uncheck the box “Run in AppContainer.”
• Re-launch C:\Program Files\FileOpen\Services\FileOpenBroker64.exe
• Re-load Acrobat/Reader.

Both of these disable the AppContainer functionality. The first is a lot simpler to implement, and can probably be done for all users via administrative tools."

[julius_1721]

Thank you @Tyson32690690akfj  ! On my freshly installed Windows 11 PC, I installed Acrobat Reader, worked. Installed FileOpen (to access protected CIE standards I bought) and Acro Reader would not start (the acrobat.exe process ran, but no GUI window appeared). Locating Acrobat.exe in C:\Program Files\Adobe\Acrobat DC\Acrobat, right clicking, setting compatibility to Windows8 as you explained, solved the problem for me. Acro Reader runs, and the protected files open without problem.

[S. S]

Hi @Peter22440460bx94 @julius_1721 @Tyson32690690akfj @adobeforumuser72 @tomw96711251,

Sorry for your experience, and thanks for sharing this.

We are aware of the issue and are working with Microsoft on this. 

Microsoft Defender is scanning Acrobat Plugins, which is delaying the launch of the application. This should be fixed as soon as we are able to get to the fix with Microsoft on this.

We request your kind understanding and patience.

Thanks,

Souvik

[Boris_BL]

Grazie @Tyson32690690akfj 

Ho seguito la seconda soluzione e Acrobat ha ricominciato a funzionare.

[Karen_Daws]

Thank you @Tyson32690690akfj, worked perfectly!  

[Piney84]

Thanks so much, bye bye fileopen. I only needed it one time for an assignment anyway.

[Patrice352368558rj3]

Yes, the problem was solved after uninstalling FileOpen

[Jason_McClure5918]

Thanks everyone, same issue (WIN11 24H2). Uninstalled FileOpen and it is working again. Will work out how to open protected documents later.

[S. S]

@Jason_McClure5918 @Patrice352368558rj3,

Thanks for the confirmation. 

We are still in talks with the FileOpen team, and the fix should be available soon.

-Souvik

[Exciting_ease5FC2]

Hi,

Did you resolve this problem?

[S. S]

@Exciting_ease5FC2,

Thanks for writing in!

We are still figuring out a fix with the FileOpen. This should be fixed with the upcoming release.

-Souvik

[Peter22440460bx94]

Out of interest, how many only have FileOpen to access standards ie from BSI?

I've been arguing with BSI for over a year that their DRM is overally restrictive and if an employee leaves the business loses access to that document. I expected an Amazon approach where the document could be shared with access transferred so only one copy could be viewed at a time.

Not business friendly