The problem is that the old program also uses upload not more.
Microsoft issued a warning to administrators to avoid running a supported version of .NET Runtime on Windows because it could jeopardize security and destabilize the system.
.
Currently, a new version of .NET is installed only if the program needs to be used. One may have multiple versions of .NET at the same time, but if there is an old one, it may allow malware to attack or cause the system to fail to meet corporate security standards.
.
Microsoft now indicates that the supported version is .NET 8 or above. Previous versions are considered expired, and even if a new version of .NET is installed or removed, care must be done because older .NET-built programs may not work. If the developer does not update to support the new version first, the program will not automatically switch to the new runtime.
.
Updates have to be made on the developer side. Whether it's editing the code, adjusting the framework, or compiling a new version of the app to support runtime, administrators have to check which version of .NET each app is using.
.
Microsoft recommends checking through the listdlls.exe -d coreclr.dll -accepteula -v command in the Command Prompt permissions, then synchronizing with app developers who still use the old version to complete the update, and after the update is complete, re-checking to ensure that no old runtime is pending. The final step is to uninstall the expired version of .NET to close a potential vulnerability.
.
However, Microsoft no longer recommends expired .NET because there are no patches, no security updates, and no technical support, and it is also vulnerable to vulnerability detection by security software. Upgrading is the safest option to prevent potential problems.
.
Source: Neowin



















































































