With the selection tool selected and the comments pane open, you should be able to click and type anywhere in your PDF, and the relevant text edit tool will be applied (strikethrough, replace, insert). This is a great timesaver. On my Mac, though, this works until I press one of the 'problem' keys – such as e, y, i, d, h, j – at which point no mark-up appears and my keyboard is disabled (including the arrow keys) until I close Acrobat and reopen it.
Does anyone else have this problem or know how to fix this bug? It doesn't seem to make a difference whether or not 'single-key accelerators' are enabled, and I don't think I have these keys assigned as hot keys in any other programs.

Acrobat is not updating the AATL trust list automatically or even asking when a document that is signed is opened.

There is a checkbox under Preferences > General > Trust Manager > The Automatic Adobe Approved Trust List (AATL) updates. Load trusted certificates from an Adobe AATL Server is checked. This is the default when you install acrobat. It however does not update the list. If you uncheck the box, close Acrobat, then open Acrobat check and reclose and open, it works.

Most users won't know to go here and all documents end up looking like they are not valid.

I would like to submit this bug.

I have seen many posts instructing users to add the certificate manually to the trusted certificates which is a bad idea. Updating the AATL solves this issue for all certificates that are signed using AATL partners.

I'm working everyday with thousands of PDF files for our repository www.ceeol.com. To maintain my overview in WINDOWS-Explorer, quite often I have to change the file names of the PDF-filess. For example, if I've downloaded 100 PDF-documents from a web page, which are a series of numbered documents, then I want to include the numbering in the file name. To do this, I have to open the files, read the number in the document, close the file again and then rename it accordingly.
PROBLEM:
Renaming is not possible because ADOBE-Acrobat does not release the file, even if I close file AND EVEN the programas such.
Renaming the file the PDF-file is possible only after I've switched to Windows Task Manager where I need to stop manually with "End Task" the processes
* Adobe Collaboration Synchronizer 21.7 and / or
* Adobe AcroCEF
This is very time consuming and annoying. It would be a great advantage if PDF files were actually released after editing and closing them in Acrobat and would not remain not blocked by Windows as if they were still open in ACROBAT

The batch OCR feature is simply not fit for purpose and needs completely replacing.

1. When performing a batch OCR the application is entirely locked into the process and is unable to do any other tasks. Acrobat installs itself as the default PDF viewer, so you cannot even view a PDF by default when the OCR process is running. There needs to be a way to run these batch processes as true background tasks that do not interfere with other Acrobat functions, or the ability to open multiple instances of Acrobat.

2. The batch process will often crash without warning or error message, I simply come back later and find Acrobat is closed and only a few of my files were converted.

3. On the Mac (latest OS) when a batch is running it does NOT behave nicely with the rest of the system. It sets the cursor pointer to the 'busy wristwatch' SYSTEM WIDE, not just for when the actual Acrobat app is in focus. It also likes to bring the Acrobat window to the front a LOT, which means you have to drag Acrobat off screen to stop it interfering with other things.

The automation for OCR is clearly a hack that's been put on top of an architecture that was never designed to be automated.

When will we get a modern application that justifies the monthly fees we pay for this?

User has a Citrix virtual desktop with a USB HP printer connected to a Thin Client, and redirected into the Citrix desktop using the Citrix Universal Printer.
Prior to this version, opening a PDF and printing to that redirected printer presented no problem. On this most recent version it does with a quick "The document could not be printed" error and then it spits out a blank page.
Ideally I'd like to get my hands on 20.005.20058 to verify this, but I cannot find the full download now. I have however installed an older version 15.*** and this prints just fine. This to me is pointing to a potential bug in this most recent version, since the user was able to print just fine before on the previous version, updated to the latest on his machine 6 days ago.
How can we go about troubleshooting this further as this appears to be a bug. How can I get my hands on a recent previous version of Adobe to verify that it's this specific version?

Several major bugs have been documented by users in the Adobe Community Forums since Acrobat and PDF Maker were updated on September 14, 2021.

They are:

1: Alt-Text from MS Word is not converting into the PDF. Instead, it is dropped and gibberish code is inserted. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017 This violates the PDF/UA-1 standard which requires that every graphic have alt-text that verbally describes the graphic.

THIS IS A HUGE BUG. You essentially have made Acrobat unusable for those who are required by their country's laws to make fully accessible PDFs.

2: Every cell border on every table cell is being tagged as:
<P>PathPathPathPath. This violates PDF/UA-1 because unnecessary visual formatting is not being tagged at Artifacts.
See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

3: The underline on Hyperlinks should be tagged as artifacts. Right not, it appears as one or more "PathPathPath" which is announced by different assistive technologies. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

4: Borders and background shadings on Text Boxes are being tagged as a combination of <Figure>s and PathPathPath. This too is a violation of PDF/UA-1. https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

5: Paragraph borders and shadings: same deal as #4 above.Per the PDF/UA-1 standard, they are visually decorative and should be artifacted. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017

NOTE: To be correctly tagged per PDF/UA-1, the borders/shading content should:
— Not appear anywhere in the Tag tree, either as <Figure> or as "Path" in a yellow content container box.
— Not appear in the Order panel.
— Should appear as Artifact in the Content panel.

6: Dragging and dropping elements in both the Tag and Order panels is now broken.

The text cursor doesn't show anymore, and the little black line doesn't show anymore and instead appears several inches away from where it really is. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017 and also https://community.adobe.com/t5/acrobat-discussions/acrobat-pro-reading-order-box-and-tag-dragging-no-longer-visible/m-p/12395226#M329877

And finally...
7: Once this update is installed, users can't revert back to a previous version of PDF Maker because Adobe doesn't allow that in Acrobat like it does with other Creative Suite applications.

So once the update is completed, it makes PDF Maker completely unusable for tagged accessible PDFs.

This affects millions of your government customers world wide, as well as millions of government contractors and millions of academic customers...all of whom are required by their country's laws to make accessible PDFs.

2 sets of sample Word and Matching PDF files are submitted as demonstrations of the problems in the exported PDFs via PDF Maker.

In an interactive PDF created from InDesign, interactive buttons do not load the destination page correctly when the PDF is viewed using the newest version of Acrobat or Acrobat Reader on a Mac.

Steps to reproduce the issue:
1)Create a 2 page document in InDesign
2)Fill the second page with placeholder text
3)Create a bookmark for the second page
4)Create a button on the first page
5)Set the button event to On Click
6)Set the button action to Go To Destination
7)Set the destination to the bookmark you created in step 3
8)Export an interactive PDF
9)Open the PDF and click the button.

Environment:
Mac 10.15 (OS version appears to be irrelevant), Intel Mac, Acrobat 2021.007.20091 (this bug appears to be new to this release)

Expected result:
Clicking the button loads the destination page.

Observed result:
Clicking the button only displays a portion of the destination page in the shape of the button.

Other details:
• This problem did not exist until recently, possibly the 20091 release
• This problem can be resolved by using an On Release action instead of an On Click action.
• This problem does not occur in Acrobat for Windows
• This problem does not occur when viewing with a web browser
• This problem occurs slightly different on an M1 Mac: The desination page does load, but there is a noticeable lag where only a portion of the destination page loads.