How to run CR with TLS 1.0 disabled on SQL 2012 SP4 Server

In order to stay compliant with vulnerability scans TLS 1.0 was disabled on MS SQL 2012 SP4 database server. As a result of this change users are now being prompted to enter SQL user credentials when trying to run reports via application front end. We've read in forums that MS Patch KB3052404 would address this issue however this patch is rolled into SP4 per feedback that we've already received from Microsoft & problem with Crystal reports still remains. We wanted to check if anyone else has recently encountered similar problem & if there is an available fix?