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)

[julius_1721]

P.S.: https://adobe.documents.adobe.com/public/esignWidget?wid=2AAABLblqZhBUIBdPKhHnYBG6VrIVGxBdO73_xEZ7O6...

[sbingham]

With apologies for all this inconvenience, FileOpen is preparing to release a new Client that addresses the issue with AppContainer in Win11 24H2. There is a Beta version of this Client in the installer at https://plugin.fileopen.com/test

This installer won't work with 32-bit versions of Reader, but we expect to have a version that does later today.

We'd recommend uninstalling the previous Client and returning the system to prior configuration, i.e. getting out of Win8 compatiblity mode and/or re-enabling AppContainer.

Please send any feedback to support@fileopen.com

[julius_1721]

@sbinghamthank you for your message, but we heard for almost four months now that FileOpen is working on a fix. All we still hear is that FileOpen is working on a fix. For many people, a beta version is something they cannot and will not install. I paid CIE for standards, and CIE paid FileOpen for the DRM service to protect them. "Beta version" is just a nice word for asking people like me to do your testing. But you don't pay me for testing. I paid you, even if indirectly. So I'm not going to do your testing.

When can we expect the release? Next week? Next month? Next year? Can you at least give us a reliable timeline? Thanks.

[sbingham]

Julius,

I acknowledge the frustration around how long it took to resolve this issue and agree that we should not expect end-users to debug our code. We will be distributing this new build to our licensees for testing tomorrow. If no significant issues are reported we will move it to release next week. 

We'll announce the release on our FileOpen blog  and I'll post an update here.

Again, we apologize for the inconvenience caused by this issue. 

[Peter22440460bx94]

Thanks for the update but due to the length of time taken and the security risk offered by the work round it appears to be more prudent to remove DRM in a sandbox. This allows industry to remain complaint to standards and also maintain security of an IT infrastructure 

It still amazes me that standard agencies failed in their duty of care whilst judging everyone else's adherence to cyber security protocols and standards.

DRM only annoys the law abiding and doesn't protect IP to a criminal

[daveNS]

Tyson32690690akfj Thanks for the workaround. disableing the app sandbox fixes the issue.

Crazy nobody from adobe could figure out there own app. Then again crazy MS can't build reliable updates and MS wonders why everyone who does real work still uses windows 10 or earlier OS.

[accounts_7774]

thanks, uninstalling fileopen today helped, we've been having issues for weeks. finally!!

[julius_1721]

It's two weeks now since @sbingham said "If no significant issues are reported we will move it to release next week." Since you didn't release a fixed version, I conclude that there are significant issues still. AFTER MORE THAN FOUR MONTHS. 

[sbingham]

The replacement FileOpen Client, Build1010, is now tested and available from https://plugin.fileopen.com/test 

We'll be moving this version to the main site tomorrow.

Testing did take a bit longer than expected, due to a few issues around user authentication, Offline Permission, and printing. 

Also, because the FileOpen ecosystem is distributed (many publishers have developed their own server logic, or licensed from one of our partners) we allocated time to get feedback to ensure backward compatibility.

[ChrisPbass]

I have used the W8 compatibility trick to get the program running.  I don't use fileopen intentionally.
I do use smartvault.  Adobe works on 1 computer and not on another, the difference is only SmartVault, afaik

[sbingham]

With the B1010 version of the FileOpen Client there is no longer any need to configure Acrobat/Reader to run in Win8 Compatibility Mode and/or to disable AppContainer. The default configuration of Acrobat/Reader is supported.

We are not aware of any issues related to SmartVault. Does that system include an Acrobat/Reader plug-in?

[ChrisPbass]

SmartVault doesn't have an Adobe plugin but it does handle PDFs.  It's a pretty big component of SV.

Thanks for the update.  I'll check it tonight

[julius_1721]

Are we now supposed to think B1010 is an "achievement"? It is not. It is a belated fix of an embarrassing bug. FileOpen, Adobe and Microsoft have demonstrated over the last four months that they don't care about the problems of the end users, as long as the intermediate party that applies DRM continues to pay. I completely understand the need to protect pdf documents. After all, I'm a scientific book author, and I serve on the advisory board of a large scientific publisher. But this whole FileOpen thing is going in the wrong direction. A better way is to apply a margin note + nearly invisible watermark stating the time and name of the licensee, in a pdf version that disallows editing. For bad actors, it's equally easy to remove FileOpen encryption as removing the margin note. For honest end users, the FileOpen approach is just a pain -- amply demonstrated over the last four months, and having lots of additional issues. It is quite telling that much of the trouble is with standards. Standard organizations are monopolists, by their very nature -- they like to use FileOpen, and we have to cope with it, as long as we need the original standard. Publishing houses have to compete for the attention of the readers -- they tend to not use FileOpen, because of the pain FileOpen inflicts on their customers.

[luca_6136]

Today, 20/02/25, with the last adobe version and the FileOpen B1010, continue to Not Working Properly.

What i can try? uninstalled acrobat & fileopen already. I can try remove the user account from pc and retry from zero. any suggest?

[julius_1721]

Depending on which documents you need FileOpen for (probably some type of standard), you can contact the central bureau of that agency, tell them about this problem that keeps persisting since over four months now, ask them to send you the standards you bought but cannot access in a watermarked and annotated but not FileOpen encrypted version. Worked for me, with CIE standards. And you can ask them to think of a better way than FileOpen to protect their documents -- see my post above.

[sbingham]

Hi Luca,

Sorry for the inconvenience. We're investing some issues reported with Win10, which we think may be related to a 32-bit OS or 32-bit Acrobat running on 64-bit OS.  Could you please check us whether the Win10 OS is 32- or 64-bit and whether Acrobat 32- or 64-bit?

The first you can find from Settings>Ssytem>About>Device Specifications>System type

The second from Acrobat>Menu>Help>About Acrobat (Pro/Std)

Thanks.

[luca_6136]

Win11 24H2 x64 10.0.26100 build 26100

Adobe acrobat pro 2024.005.20414 x64

fileopen client B1010

[luca_6136]

i try to use the non-CC version

Adobe acrobat pro 2024.005.20421 x64

still not working

[luca_6136]

tldr: i need to change pc to my coworker,  the old one is win11/adobe acrobat pro 24.005.20399/fileopen 0993 and works fine.

new pc (specs in previous message)keep saying "document already open on other machine".

i try to check if files are really open, log out from adobe account on the old pc, turn off the pc, ...

why on the new one dont work? same adobe account, same domain account...

[sbingham]

That message ("document already open on other machine") tells us that the FileOpen Client is installed and able to communicate with the publisher's server. However, that server is rejecting the request because the machine appears to be different from the one previously registered. If the two are in fact the same machine then there could be an issue with the FileOpen Client. If they are actually different machines then this is the expected behavior.

In either case the next step is to contact the publisher and request that the "new" machine be authorized. 

This isn't something FileOpen can address directly: we license software to publishers but have no direct control over which machines get authorized. 

If indeed there is only one machine then we'd like to investigate, and would ask that you send a message to support@fileopen.com.

[Tyson32690690akfj]

Can confirm that this new version seems to working well.

Thanks @sbingham 

[Zorik5E35]

Can confirm version 1010 working here as well.

Thank you

[jacks_3922]

Im having the same issue after the Win11 24H2 update. Acrobat Pro shows up in Task Manager but doesnt launch. Have you tried running the Creative Cloud Cleaner tool to fully remove Acrobat before reinstalling That might help fix the installation issue.

[sbingham]

This behavior may be caused by having an older FileOpen Client, which won't initialize under Win11 24H2 without some re-configuration.

The simplest approach is to uninstall the FIleOpen Client and install the current (B1010) version from https://plugin.fileopen.com/

If you prefer to keep using the old Client there are workaround instructions here: https://www.fileopen.com/issue-with-adobe-acrobat/reader-under-windows-11-24h2

[Frank_VanDerLiden8858]

The amount of incompetency it takes to have an issue ongoing for well over six months is astonishing!!! None of these workarounds work either I guess now it's a something else that needs to be done. Incompetency must be a key core value there at Adobe! Y'all are completely useless now as a matter of fact, instead of fixing this, I'm just gonna go out and purchase a license for an alternative. May I ask who your biggest competitor is because that's where I'd like to start first! Since you can't seem to keep your software running, I'll go see if your biggest competitor can do it and I'll quit paying you and I'll go pay them!! Maybe then you can pull your head out of your rear!