Issue: Google Maps addresses not populating during delivery orders or visual map not populating.
Solution: Force TLS 1.2 settings in the Windows Registry
Due to a known Microsoft update issue, TLS 1.2 security settings has been disabled in the following Windows Operating Systems:
- Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1
How to force TLS 1.2:
Update the Registry
- Enter Run in the Windows Search bar.
- Enter regedit, then select OK.
- If prompted to allow this program to make changes, select Yes.
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319.
- Take the following steps if the SchUseStrongCrypto key is not present.
- Right-click anywhere on the right and select New then DWORD (32-bit) Value from the context menu.
- Enter SchUseStrongCrypto in place of New Value #1.
- Double-click the new SchUseStrongCrypto key and enter 1 in the Value data field.
- Now go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319 and repeat step 5.
About the issue:
Microsoft has issued an out-of-band (OOB) non-security update to address an issue caused by the October 2022 Windows security updates that triggers SSL/TLS handshake failures on client and server platforms.
On affected devices, users will see SEC_E_ILLEGAL_MESSAGE errors in applications when connections to servers experience issues.
"We address an issue that might affect some types of Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. These connections might have handshake failures," Microsoft explains.
References:
https://softwarekeep.com/blog/how-to-troubleshoot-tls-handshake-issues-updated