Error .net framework 4

Deleted022220

Well-known member
Joined
Dec 14, 2019
Posts
74
Cannot repair this version, I think registry keys missing or something. Also, C:\Windows\Microsoft.NET\Framework64 does not contain 4.0 folder.
I highly appreciate your help.
 

Attachments

  • Capture.PNG
    Capture.PNG
    7.7 KB · Views: 7

Attachments

Personally, I would not recommend using driver updating utilities as they can cause issues. Monitor your system for issues and post back if you encounter any in the next 24 hours.
 
There are only two places from which one should source drivers in other than the most exceptional of circumstances:

1. The drivers & software pages for your model at your computer OEM's support site.

2. The drivers from a given component OEM's support pages.

You may safely use the driver updater software from your computer's OEM, e.g., HP Support Assistant, Toshiba Service Station, or similar, or from the manufacturer of the specific components in your system. Intel seems to churn out driver updates at a shockingly fast rate these days, and I have resorted to the Intel Driver & Support assistant to keep the drivers for the Intel components in my system up to date.

Third party driver update utilities should, in my opinion, be avoided like the plague. I have seen them cause nothing but grief and tears many times over my years in the computing game.
 
As a final addition, there is no reason to seek out drivers before a Windows 10 install (whether repair or clean) these days, nor any need to rush out afterward, either.

Compared to when Windows 10 was introduced in 2015, when many third party entities appeared to be ignoring the barreling train that was Windows 10 and that had been well-known to be coming, most have now supplied Microsoft with the correct drivers for The Great Microsoft Driver Library in the Cloud to cover the vast majority of hardware produced over the last 15 years.

You'll know if a given device is not functioning correctly in short order, and then it makes sense to seek out a driver for it on the rare occasion when that occurs.

I haven't had to get a replacement driver on any of the systems I've worked on for at least two years or slightly longer now (or at least I haven't on account of anything related to Windows 10 not having a driver that works).

If you simply must have a driver monitoring utility, use the one that your computer's OEM supplies - and they all have them these days. You then know that the drivers in question have been thoroughly vetted for your precise hardware.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top