Some computers in our environment will only autotag with cloud tagging disabled, others allow auto tagging with cloud tagging enabled

Hi ​@Thomas28297428epyk ,

Thanks for the detailed write-up. This is a tricky one, and you've already done a lot of the legwork. The full uninstall, Cleaner Tool, and reboot rule out a bad install, and testing the same file across machines rules out the document. That leaves us looking at what's different about the machines that stall versus the ones that work.

Here are a couple of things to try on an affected machine, since they're separate from what you've already covered:

• Sign out of Acrobat completely, close it, sign back in, then run the auto-tag again on the same file. This refreshes the account and service session without touching the install.
• When it sits at 20%, let it keep running and see whether it eventually shows an error or just stays there. If any error message appears, the exact wording helps us narrow down where it's stopping.

Since it works on some machines and not others, it's also worth having your team confirm the affected machines can reach our required domains, in case something like a proxy or security filter is treating them differently. Our full list is here: https://helpx.adobe.com/enterprise/kb/network-endpoints.html

A few questions to help us dig in further:

• Are the affected and working machines on the same OS version and build, or do they differ?
• Do the affected machines have any different security or endpoint software installed than the ones that work?
• Are they on the same network as the working machines, or do some of them route differently?

A short screen recording of the hang on one of the affected machines would help us too.

If it's still stuck after all that, please open a case through the Admin Console > Support so our team can pull the service-side logs and see exactly where the process stalls. Sharing the affected machine details and any error wording will help them get to it faster.

Thanks,
^AV