Short answer: yes.
Longer answer: I believe so. I’m not doing anything different than I have with previous installs. I execute the batch file by double-click, I’m not in a console window already. I am logged in as the Windows administrator, and confirm administrator permissions when prompted by the install procedure.
I have not launched an admin console window and executed the batch file from that window, nor have I forced the batch to run “as administrator”. I do not expect that this would address my issue, but it’s possible.
As it stands right now I’ve opted to install 2017 and work with that until it is no longer supported. I’ve not had the same problem with the 2017 installation procedure (which bolsters my impression this isn’t a permissions issue). If others have experienced the same problem I would welcome their comment after attempting the install with explicit administrative access.