Unfortunately, Windows 10 is unstable again after an update. And unlike last year, when the main issue occurred with one of the two major updates of the year (Windows 10 20H1), this time the issue is associated with one minor update, the ones that are generally applied automatically and which, although with exceptions, are generally not a problem.
If you have recently updated Windows 10 with the KB4598299 and KB4598301 updates, you may have encountered a problem in your system. And, in case you haven't, there is a possibility that it will happen in the future.
Users have started reporting crashes in multiple apps and in some cases even systems going into a loop of blue screens they can't get out of.
The updates mentioned, and therefore the problem, are limited to Windows 10 20H2, 20H1 (2004) and 1909, that is to say the three most recent updates and therefore the most widespread at present .
The updates with which this issue has been presented are intended to make improvements in the .NET Framework 3.5 and 4.8, primarily fixing issues, but also adding an improvement in the way some things work. .NET Framework updates are automatically installed when you check Windows Update for updates.
While most of the issues were reported using Windows 10, the bug also affects Visual Studio, Windows Presentation Foundation (WPF), and other products. Several support forums have posted messages mentioning issues potentially related to this update. And the one worth considering is that of Vasilios Magriplis in the developer community using Microsoft tools.
It says that shortly after installing Windows 10 update KB4598299, it started having issues with Visual Studio, issues that ended with the app crashing. And I say this post is especially interesting because in the responses we can find confirmation from Microsoft that they have identified the problem, which is associated with the update, and that they have already found the solution, which is awaiting publication.
In the meantime, until it's available, the only solution is to uninstall conflicting Windows 10 updates. Otherwise, everything indicates that the solution will be released next week.