Jump to content

NMM & Windows 10 Technical Preview


elmetnuter

Recommended Posts

Maybe because of that revision number, NMM is looking for revision number 4.5.2 and tries to access it, then it throws a access-denied because 4.5.2 does not exist.

 

Probably gonna have to wait for next win 10 build to fix that.

 

Windows Defender for great justice.

 

EDIT:

 

Seems Windows Tech Preview Build 9860 is actually running .NET Framework 4.5.53343. its 4.5.5, not 4.5.2.

Release version: 381023.

 

The release version for .Net Framework 4.5.1

Release version: 378758

 

So either there is a major change to come in the next .NET Framework that will break NMM, which would require NMM devs to get to work, or the Tech Preview is broke or the version is so new and fresh, its a Z or 4.5.5* (in dev), which would require the Windows team to get a finger and fix eet.

Edited by MrJohn
Link to comment
Share on other sites

  • 2 weeks later...

this was really pissin me off for the last week+. tried installing all the standalones for .Net, tried enabling everything .Net oriented in Windows features, tried multiple install\reinstalls of NMM versions. eventually installed MO to do NMM's job but Skyrim would not remember the installed mods, had to run MO 1st and launch from there every time.

 

kept suspecting it was the 10TP causing this issue after reinstalling vanilla Skyrim and a default NMM and still no go. nice to have wasted 5-6 hours going back and forth. Nexus should have tested and reported the incompatibility by now. thank you someone tried the XP\Legacy version and was helpful enough to post this simple solution. works great now.

Link to comment
Share on other sites

  • 3 weeks later...

Checked some more. Windows 10 Tech Preview Build 9879 actually has an earlier build of .NET Framework 4.6 Preview. Version 4.6 is now out for 8.1 (I don't know if this is compatible with NMM version 0.52.3).

The build number for .NET Framework 4.5.2 is: 379893.

Framework 4.6: 381029

Windows 10 Tech Preview: 381024.

 

This can be checked by running Regedit and checking the key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

 

Here is a Microsoft Answeres link, they've provided no answer but it may seem they know about this.

Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...