I attempted to install BOINC on new host (Win10, x64) but it fails to connect to core client.

Default routes are changed.
(c:\bin\BOINC for app and c:\BOINCdata for projects)
So, what could be done besides to download not recommended but working one instead (and what is the working one today?)?

---

What CPU? Late generation Intel core range, low power version? We know about that one - SSL (secure sockets layer - https) crashes.

Use https://boinc.berkeley.edu/dl/boinc_7.16.5_windows_x86_64.exe or https://boinc.berkeley.edu/dl/boinc_7.16.5_windows_x86_64_vbox.exe instead.

What CPU? Late generation Intel core range, low power version? We know about that one - SSL (secure sockets layer - https) crashes.

Use https://boinc.berkeley.edu/dl/boinc_7.16.5_windows_x86_64.exe or https://boinc.berkeley.edu/dl/boinc_7.16.5_windows_x86_64_vbox.exe instead.

Yes, it's Apollo Lake N3450

Unfortunately, 7.16.5 x64 doesn't work either.
Behavior is little different.
Now it's perpetually in "connecting to localhost" state (w/o failure to connect but w/o real connect too).

UPDATE: cancelling project add window allowed to connect. And now project add filled with projects names. Good so far...

UPDATE2: Thanks, Richard, you are real friend! Now my last computational device connected to SETI too :)

---

I'm beginning to wonder if it has anything to do with enabling VT in bios?

If that doesn't do it, you can install the 32 bit version. It runs most projects just fine.

There have been countless posts on this forum with users having this issue and no concrete answer as to why some 64 bit windows will run it, and others don't.