Rick White

Hit the same issue and can confirm my PFBlockerNG network ad-blocker blocking this domain caused this issue. Removing the domain from the block list solved it.

I hit this issue and found my network ad-blocker (PFBlockerNG) was intercepting/blocking access to fpt.live.com, causing this issue:

[4781:4786:0323/101601.307308:ERROR:ssl_client_socket_impl.cc(883)] handshake failed; returned -1, SSL error code 1, net_error -202
[4641:4641:0323/101601.438895:ERROR:bad_message.cc(29)] Terminating renderer for bad IPC message, reason 213
terminate called after throwing an instance of 'std::bad_function_call'
  what():  bad_function_call
terminate called after throwing an instance of 'std::bad_function_call'
  what():  bad_function_call
terminate called after throwing an instance of 'std::bad_function_call'
  what():  bad_function_call
terminate called after throwing an instance of 'std::bad_function_call'
  what():  bad_function_call
Created browser window for reuse: 0x140001a
[4641:4762:0323/101952.574432:ERROR:cert_verify_proc_builtin.cc(1063)] CertVerifyProcBuiltin for fpt.live.com failed:
----- Certificate i=0 (CN=pfsense-pfBNG-DNSBL-673c8f488a8eb,O=pfBlockerNG DNSBL Self-Signed Certificate) -----
ERROR: No matching issuer found

Removing that domain from the block list resolved the issue, and the Microsoft login page would render properly.