I experienced something similar today. For me, it related to my company's internet making use of a security tool called Netskope that intercepts https traffic (yep, companies are sniffing our private traffic too now ;)).
I've experienced similar network issues with other tools at work (like python pip installer), and our IT dept advised that we need to install a Netskope root certificate into any tool we use that doesn't make use of the operating system's security store (and they use their own).
So, to get a feel for how this issue impacted me in relation to this "eclipse-inst-jre-win64.exe" installer file, I learnt that I could run the installer with an extra argument, to specify my own jvm:
eclipse-inst-jre-win64.exe -vm "C:\Program Files\Java\jre1.8.0_251\"
This got me the following error:

...and that was the clue I needed to realise that this Eclipse installer .exe had JDK 11 built into it.
So, given that, I felt that I should try download my own JDK 11 and add this 'netskope.pem' root certificate into that, so I'll share my steps in doing so:
I grabbed jdk-11 from here:
I extracted the “openjdk-11+28_windows-x64_bin.zip” file onto my local drive
- E.g. to “C:\Users\GurceI\Downloads\jdk-11\”
Added ‘nscacert.pem’ to jdk-11’s keystore from the command-line, with:
cd c:\Users\GurceI\Downloads\jdk-11\
bin\keytool.exe -import -keystore lib\security\cacerts -file c:\ProgramData\netskope\stagent\download\nscacert.pem
(default keystore password = “changeit”)
I then ran the eclipse-installer with an extra argument to point it to my jdk-11 (rather than its internal one):
eclipse-inst-jre-win64.exe -vm "C:\Users\GurceI\Downloads\jdk-11\"
...and then, finally, the installer worked, no more network issues :)
