Jump to content

Mods Install Issue: "An Exception Occurred in the script."


Recommended Posts

I did a reinstall of the Nexus Mod Manager since its update and have been reinstalling some mods.

Mod Configuration Menu is a pretty darn important one but every time I try to activate it in the Mod Manager I get the message "An Exception Occurred in the Script."

Same happens when trying to install Primary Needs Hud.

 

I've tried enabling every permission possible, excluding the files from anti-virus scans, etc. Nothing seems to be working.

Any ideas? (Fix listed Below)



Edited by xxgotholicxx
Link to comment
Share on other sites

OKAY NEVER MIND EVERYONE!
I found the solution thanks to user ElysianMods.

All you gotta do is Run NMM as Administrator, go to Settings, and "Add Shell Extensions for Supported File Types". Then just restart NMM.

I apologize for making this topic but hey, maybe if someone is having this issue and hasn't seen ElysianMod's post on the MCM Posts section, they now will know how to fix it.
Also I apologize for writing all this down here in this comment... I'm really not well versed with how Forums work.

Edited by xxgotholicxx
Link to comment
Share on other sites

What mod manager are you using?

What error message are you getting? Have you looked at the Windows Eventlog to see if there is a system error at the same time?

 

To recap with updated info:

As of 08 May 2018, the Nexus has changed some site security to come into compliance with the new "European Union General Data Protection Regulation" (EU GDPR) rules. This breaks older versions of NMM and other tools using the older unsecured API. It is usually reported as being "blocked by the Windows firewall" or causing a "script" or "W3C XML Schema" error installing mods. You will need to update it from NMM on GitHub or this Nexus NMM download page. Check the version numbers between those sites and use the latest (v0.65.4 at this time). Please see this Nexus site news article for details.

A Working "unofficial" fix (confirmed) to login to Nexus with MO (v1) or older NMM versions without updating is available in this Reddit thread: Classic Login fix for MO1/NMM.
Note: this "fix" reverts to using the older, unsecure API at a fixed, no longer used IP address (instead of the address returned using DNS), and thus negates the EU GDPR standard. It could get shutdown without warning 25 May or after as that is the EU deadline for compliance and Nexus is hosted in the United Kingdom. Use at your own risk.

Some people are finding that even after updating NMM to v0.65.4 they still get a "script exception" message when installing some mods (such as UIO and MCM). This seems to be resolved by this suggestion from user ElysianMod:

  • Run NMM as an "Administrator privileges" account.
  • Go to NMM "Settings".
  • Enable "Add Shell Extensions for Supported File Types".
  • Then restart NMM.

(Supposedly this fix will be included in the next "unofficial" update to NMM on GitHub.)

Make sure NMM gives your user account the correct permissions.

  • <right-click> your shortcut or NMM.exe and go to "Properties".
  • look for the tab at the top labeled "Securities".
  • select the "user account" you are using (note: changing this may require you to use an account with "Administrator" privileges. In that case select the "user account" you normally use to play the game).
  • click the "edit" button located under the box listing the "user accounts".
  • make sure all options are selected, from "full control" to "special permissions"

So: did you update, or try the "workaround" instead?

 

[Edit: Updated with latest info.]

 

-Dubious-

Edited by dubiousintent
Link to comment
Share on other sites

  • 1 month later...

I had a similar issues and I noticed that the box that says "Add Shell Extensions for Supported File Types" was unchecked for me as well. However when I checked the box and pressed OK i was given the message "Couldn't add shell extentions. Check TraceLog for more info". I'm at a loss at this point. I've uninstalled and reinstalled the manager several times, ran the program as an administrator and tried changing the settings but no luck. Any one know a solution?

Link to comment
Share on other sites

Most likely reason is that you installed Steam and/or NMM to the default location ("C:\Program Files") folder tree. Files and folders there are treated differently than other locations and resist any changes as attempts by potential malware. Please see the "Installing Games on Windows Vista+" article in my signature and move it out of that location.

 

We've been giving this advice for many years now (since Vista was released and FNV was "new"). The situation only gets worse every year. As much of a PITA as moving game files is, it's never going to get any easier than now.

 

-Dubious-

Link to comment
Share on other sites

  • 2 weeks later...

Sorry Dubious, but it is not fixed my problem. I already using different directory even hard disk for Nexus Mod Manager, but still getting the "Couldn't add the Shell Extension" error, and that article not helping there. Thanks anyway. I have that problem since yesterday, I cannot add shell extensions after reinstall of NMM (because it was broken had to reinstall it)

Edited by Clira
Link to comment
Share on other sites

  • Recently Browsing   0 members

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