Just download and test, only then report so-called errors, which are not errors.īut I can't leave it as it is read in the above line.

In the above course of tweets it is explicitly mentioned that the file name of the. I explicitly tested it with a download and unzipped it. Once it is simply crap if the name of the MSI installer does not correspond to what an administrator should expect. Then a deployment in an enterprise environment becomes a game of roulette. I haven't tested now if the setup.exe reloads more msi packages from the web during execution. The tweets mention names like AcrobatDC.msi and AcrobatRdrDC.msi, which is different from the files in the screenshot above.īut there's more to the story if you take a deeper look. The discussion goes even further in this thread – there Karl had also raised the issue on October 13, 2021.Īndrew Jimenez writes there that the installer does bring Adobe Reader DC to the system. Would the blog reader be right somewhere with the above comment. But there are some subtleties to consider in enterprise environments.

Besides the issue mentioned earlier that an. Msi install file should reflect what is then installed, there is another issue.Īndrew Jimenez noted that while the installer does indeed install Adobe Acrobat Reader DC 64-bit, the product name in the registry does not reflect this. However, he said that when you launch the product and go to the 'About' page, it reports that it is Adobe Acrobat Reader DC (i.e., not the 64-bit version). #TEST ADOBE ACROBAT VERSION FOR ANDROID#.

How to test adobe acrobat 9 key