home
Morrowind
Terms of Service | Privacy Policy
Copyright © 2024 Robin Scott. All rights reserved.

NMM v0.15.0 issues

  • Comment
More articles
Last night we released the Nexus Mod Manager version 0.15.0 for general download to fix the issues that Bethesda and Valve presented all the mod managers out there with the changes to the way load orders are handled. Sadly Bethesda didn't give us nearly enough time to ensure we could solve the issues they've presented us (and I'm sure they'd argue they don't have to), so I know that wrinklyninja (of BOSS) has worked at least 100+ hours in the last week alone on getting the BOSS API to a usable state for kaburke (NMM) and Lojack (Wrye) to equally spend a lot of time updating the respective mod managers.

Unfortunately version 0.15.0 of NMM has a program breaking bug in it at the moment that is going to need to be hotfixed as soon as possible. Lots and lots of people have reported this issue so I think it's safe to assume that almost everyone has the same problem! There is a fix for this right now, however, if you are willing to do a little folder copy and pasting. Alternatively you can wait for a hotfix, that will hopefully come today, or roll-back to version 0.14.2.

The fix is very simple. Navigate to where you have NMM installed (the default location is C:Program FilesNexus Mod Manager), copy the "data" folder from inside the Nexus Mod Manager directory, go back one folder (to C:Program Files) and paste the data folder inside the Program Files directory. NMM should now start, load, and work. If it doesn't then I'm afraid you have a different problem, and one that has likely been in NMM since before this version.

When a hotfix gets released for version 0.15.0 you'll be safe to remove the copied data folder from your Program Files directory.

Many apologies for the program breaking bug, but everyone involved has been scrambling and putting in ludicrous hours (especially wrinklyninja, who deserves your thanks) to get this problem sorted for you as quickly as humanly possible.

69 comments

Comments locked

A moderator has closed this comment topic for the time being
  1. Dark0ne
    Dark0ne
    • Site Owner
    • 2,903 kudos
    Going to lock this thread as it is now obsolete in light of the recent news.
  2. skyrimnub
    skyrimnub
    • member
    • 0 kudos
    v0.15.7 - still crashes

    I have not attempted any recovery actions from v0.14.2, so my info is still in that state.
  3. stefbuik
    stefbuik
    • premium
    • 0 kudos
    Still broken..

    I dunno what Bethesda and valve did, but I got an update, and immediately it was "end of story" for modmanager.
    It also suddenly decided that the password for skyrimnexus wasn't valid..great! thanks a lot valve&bethesda. "When no bugs present, we will create some, for users might get shocked otherwise" -Bethesda's company motto...

    Shame, because MM was sheer genius, especially the "download with manager"- button.. sniff it's gonna be dearly missed...
  4. itsdodge
    itsdodge
    • premium
    • 0 kudos
    NMM Guys - thanks for the heads up.

    You have a great Mod well worth the pain (you don't know what you've got till its gone!) I rely on NMM (it's like I was a blind man who discovered he could see with glasses!)

    Thought It was something like that - although do manage myself to mess things up regularly,

    I want you guys to know that I try and endorse your mod every couple of days - but the button doesn't like me!
  5. renbear
    renbear
    • supporter
    • 2 kudos
    wrinklyninja, Awesome! Thank you VERY much for the reply. I was worried y'all didn't know about it. Good luck dealing with the new load order issues!
  6. billygoat654
    billygoat654
    • premium
    • 6 kudos
    please take your time i think we can all live without skyrim for a little while i went nearly 21 years before i played it after all
  7. wrinklyninja
    wrinklyninja
    • premium
    • 338 kudos

    Dark0ne and the NMM authors: There's more than one major crash bug in 0.15! Windows XP users crash with an error dialog which states, The procedure entry point RegGetValueW could not be located in the dynamic link library ADVAPI32.dll.

    This function does not exist in 32-bit Windows XP (sp3). It DOES exist in 64-bit XP, and 32/64 bit Vista and later. See the following MSDN links for developers having the same issue:

    http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/c7558c45-f027-42a2-9791-7432615a3859/

    http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/97e55815-d73c-48c3-9a60-1ca617218bd2/

    NMM will not run on 32-bit Windows XP as long as you use that function.

    It was an issue with the BOSS API that has since been fixed in the SVN.
  8. renbear
    renbear
    • supporter
    • 2 kudos
    Dark0ne and the NMM authors: There's more than one major crash bug in 0.15! Windows XP users crash with an error dialog which states, "The procedure entry point RegGetValueW could not be located in the dynamic link library ADVAPI32.dll."

    This function does not exist in 32-bit Windows XP (sp3). It DOES exist in 64-bit XP, and 32/64 bit Vista and later. See the following MSDN links for developers having the same issue:

    http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/c7558c45-f027-42a2-9791-7432615a3859/

    http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/97e55815-d73c-48c3-9a60-1ca617218bd2/

    NMM will not run on 32-bit Windows XP as long as you use that function.
  9. GoDawgsGo
    GoDawgsGo
    • premium
    • 0 kudos
    thank you to gopher for his video, after attempting all the "fixes" just reverting was easy enough.
  10. SirTopas
    SirTopas
    • premium
    • 23 kudos
    Reverted to 0.14.2 and it's working fine. I'm more than happy with NMM, so please don't feel you need to rush around at mach 2 with your hair on fire getting this resolved. Thanks for the great site(s) and the great tool.