Jump to content


Photo

Google Chrome Can't Download from Skyrim Nexus using MO


Best Answer DoubleYou , 10 November 2014 - 08:24 AM

You do not need NMM for MO to download mods.

 

Proper debugging of downloading with manager issues should follow the troubleshooting instructions on the wiki:

 

Problem: When I click the Download with Manager button on the Nexus, nothing happens.
Possible solutions: There are many reasons why this may happen. Please try these possible fixes:

  • Click the globe Globe_MO.png button.
  • Go to the Nexus tab in Settings and click the Associate with "Download with manager" links button.
  • Go to your ModOrganizer directory and run the nxmhandler application. If the program is pointing to Mod Organizer, click the Register Active button, click yes at the prompt, and close. If the program is not pointing to Mod Organizer, right-click in the window and select Add, select the game you are handling, browse to the appropriate ModOrganizer.exe application, click OK, click the Register Active button, click yes at the prompt, and close.
  • If you are using Google Chrome:
    1. Locate the "Local State" file (enter %LocalAppData%\Google\Chrome\User Data\ in the Windows Explorer address bar).
    2. Open the file in a text editor such as Notepad while Google Chrome is closed.
    3. Search for "nxm" (Click Ctrl+F and enter nxm).
    4. Delete the line that says "nxm": false (if true, still delete the line).
    5. Save the file.
    6. Next time you click the Download with Manager button, Chrome should pop-up a dialog asking to launch the application registered for nxm links. Click Launch.
  • If you are using Firefox, open Firefox, and inside Options, go to the Applications tab. Search for nxm and point it toward the nxmhandler application located inside the ModOrganizer directory if the option exists.
Go to the full post


  • Please log in to reply
60 replies to this topic

#61 noobgoldberg

noobgoldberg

    Prisoner

  • Members
  • 1 posts

Posted 13 October 2017 - 09:59 PM

 

The problem had started just the other day after my "IObit Advanced system care" program recommended that I update Chrome just before my problems started.

I had the same problem and a google search led me to this thread.  Although the old "Local State" method no longer works, in that same "User Data" directory I opened up the "Profile 1" subdirectory (I have multiple Chrome profiles so perhaps you only have one, or it's called Profile 2, or even just "Profile") and opened the "Preferences" file in Notepad++. 

 

Then I searched for "nxm" and it was embedded in the JSON array, like so: 

"news":false,"nntp":true,"nxm":false,"shell":true,"snews":false,"vbscript":true

I deleted (including the comma!):

 "nxm":false,

...saved the file, started Chrome, and when I clicked on the big green button in Nexus it properly asked me if I wanted to use the MO2 handler again. Everything is now back to the way it should be. 

 

It looks like the file location has simply moved from "User Data\Local State" to "User Data\Profile 1\Preferences" (or whichever profile number you are currently using). 

 

EDIT: Easiest way to identify the profile you're currently using is to check the "Preferences" file modification date, which should be today's date (because you just closed Chrome before you edited the file). 


Edited by noobgoldberg, 13 October 2017 - 10:02 PM.

  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users