Not sure if it’s the latest, but behavior definitely changed, couldn’t upgrade our instance because the service wouldn’t start, when I tried to run it in console, the error it spat out was a SSL verfication error, which is a breaking change listed in 4.0.0:
(A temporary workaround would be to set “TrustServerCertificate=True” in the connection string, you can apparently also set Encrypt=False, but I did not test that), for reference here’s how that looks like in the connection string:
Server=<dbserver>;Database=<dbname>;Integrated Security=true;TrustServerCertificate=True;
Of course the real permanent solution is to install a trusted certificate on your SQL server 