Jump to content

Question

Posted

I'm not sure if I ran into a unique case or not, but I thought I'd post my workaround here just in case someone else stumbles across this.

 

My PC came with .NET Framework 4.5, but MO was still throwing this error. I tried another workaround posted here regarding changing registry values, but that didn't do the trick. Here's what I had to do:

 

  • Control Panel ---> Programs ---> Turn Windows features on or off
  • Enable .NET Framework 3.5

That's it.

3 answers to this question

Recommended Posts

  • 0
Posted

MO updated recently and probably changed its method of checking for it, which is why the registry change wouldn't work.

Gotcha. Is it specifically checking for v3.5? It seems so given the fix I applied.

  • 0
Posted

It's checking for 3.5 according to what I've only recently learned. It is because of the NMM code requiring dotNet. I still don't know if that is the actual version it uses, as I was under the impression that it required version 4+, in which case the warning would be looking for the wrong version. I'd have to research to find out if it actually requires that version or not.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.