Getting frequent "No Response" on Acrobat PRO (latest verson) when using SDK (C#)

I have a C# app that reads the word count for a page and then reads that number of words, concatenating each into a large string that I can examine.

This worked fine on my win11 development system that had Acrobat Pro 2015 and an 8th gen Intel CPU.

I then moved the sources, using GitHub, to a test system that has Acrobat Pro, latest version, and a 12th Gen CPU.  This matches the deployment system better than my dev system. 

I started seeing timeouts of about 30 seconds but no errors are shown in the win11 event viewer.  Sometimes the app stops after 4 pages occasionally it gets to 30 pages.  Rarely it reads all 70 pages.  It is unusable.   When this happens “Acrobat 32” is left in memory and I have to use the tasks manager to kill it else my app cannot start.

I changed the app so that Acrobat displays the document as soon as it is opened instead of after reading the words.  This made a huge improvement, but I see the following that concerns me:

 Occasionally there is still a pause.  The cursor starts circling (busy) and if I attempt to move the document, I get a message the document has “No Response”.  After a few seconds there is progress and I may see another pause at, for example, page 40.  After a few seconds it resumes reading and finishes and all words of all pages have been processed correctly.  Nothing was lost or skipped over.

Question 1

I do not know what the problem it. Could Acrobat or the SDK be phoning home?  Ie: a network timeout while the app is running?

I am accessing that test system remotely using splashtop.  There is very little screen update which make me think the problem is not the remote access.

Question 2

Since the 2015 Pro seems to have no problem, can I take the .exe and the DLLs that are built and deploy those on the target?  Or do I need to build the DLLs using the latest Pro?

Thank you for looking!