Adobe Acrobat 24.003.20180 WIN11 - freezing problems

[karl_1382]

Hi,

as mentioned in 

Adobe Pro keeps crashing when opening some PDFs - Adobe Community - 14909692

I have the same issues here.
Opening PDF files directly from Outlook, saving them on local SSD or network shares causing the Acrobat to freeze when scrolling/try to print/try to save.

I ran the diagniostics, here ist the ID:

c46f70fa-6611-4e7c-9fc0-497c2e093deb

Please help solving the issues.

Thanks

[glen_7534]

We have ahs many customers report this issue starting last week. It is both Win 10 and WIn 11. Not all deviecs are effected.

[Michael24142568gyjd]

Disabling new acrobat reader works for us as well.

[ong_0993]

This happens for Adobe Reader as well. Started only recently. And yes, disabling new Adobe seems to solve the issue. The strangest thing is that not all users are affected. My office some of the staff (aka not all) are having issues. Some of the users said that they are using it and it feels normal and speedy. Perhaps it is some plugins in Adobe having the issue. Not very sure.

[glen_7534]

We now have MANY customers reporting this issue, on both Win 10 and Win 11 - all started a week or so back. On Acrobat Reader. Disabling 'new Acrobat' seems to have solevd it for everyone.

[zepelo]

Hi,

I haven’t read through the entire thread, but I’m experiencing the same issue with every PDF file I open on my system Acrobat freezes a few seconds. I came across my solution in one of the older threads—I’m not sure exactly where—and after disabling the Updater, my Acrobat Reader has been working smoothly.

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown\cServices]

"bUpdater"=dword:00000000

[Nin316611376og8]

I have been experiencing the same issue for months now. Despite multiple remote sessions with Acrobat support, the problem still persists. They keep attributing the issue to the AutoCAD PDF drawings I'm working on, which I find strange because I have been handling similar PDFs for years, and this issue only started occurring this year. I just finished another remote session today, and unfortunately, the issue remains unresolved. At least the last support agent mentioned that it is a bug and that their engineering team is working on a fix. I hope this gets resolved soon, as it has been affecting my work.