I've got an ASP.NET MVC 5 project using EF 6 that this error just popped up in. I've been researching this for days, but I can't determine WHY this error has just now appeared.

I am only getting this locally, so it is something related to my local software. I'm REALLY confident that this is a bug introduced in .NET Framework 4.7.2. It appeared after the April 2018 windows update ran on my local machine.

The application is connecting to Azure SQL Database and it runs perfectly fine on Windows Server 2016.

I have tested this from a fresh install of Windows, with just the bare minimum software required to get the project to run - I still get the error.

I've found posts all over for this issue, mostly related to slightly different errors, however. I've also been able to resolve the issue by modifying my queries, but that's not the solution I'm looking for.

Has anyone else experienced this issue? How would I definitively determine if .NET Framework 4.7.2 is the culprit? And if so, what can I do about it?

Please let me know if you need any additional information. Thanks in advance!

PS - I've got a workstation with an identical setup, only difference being that I haven't run the April 2018 update on it. I don't have this error when using this workstation. This is the primary reason I believe the bug(?) to be related to the latest Windows Update.