Vielen dank, Herr Karl Heinz Kremer. I discovered the true nature of the error¹, but I also discovered that Adobe is not consistent regarding the significance and resolution of error 1935. Please note the radically divergent messages regarding the error content between my question (which I got from a screen capture) and that posted by Adobe. The messages bear only a single thing in common: The NAME/NOMENCLATURE of the error. They are, in fact, NOT the same errors. Adobe installation troubleshooting also failed to direct me to the page you so kindly referenced.
¹Now, I could slap myself silly. The moment I forced a reboot, it ocurred to me that it might be a Java-related issue or something like that. An unmentioned error messge seemed to hint at a scripting problem. I was right. You see (here's the slap myself silly part), I'd forgotten a Windows 7 64-bit batch update operation had not been completed. Changes had been written to the OS that had not been finalized by the mandated restart, and among those changes were some that prevented a successful installation of Adobe's Acrobat Reader. Furthermore, I conjecture that those changes were browser-specific, the Read PDF Files In Explorer plugin. Suggestion of proof for theory: The installation of Acrobat didn't actually FAIL until the "Close" button of the error message was responded to; The last time I reproduced the error, I did not hit the aforementioned button. Instead, I opened the newly-installed application…successfully, without any error. Then I did the reboot, after which the OS was reconfigured vis-a-vis updates. The next installation attempt was 100% without error. This also led me to believe that installation method was not germane to issue.
NOTE RE Adobe answer: It's not precisely true; that answer is relevant only to 32-bit operating windows platforms…at least that's what the "win32" and "x86" indicates. That's not what MY message says, and I have x64 6-core processor architecture running a 64-bit platform.