I read this post 2 posts before and did not find an answer in this, as I described that I used the nxmhandler, which did not work. And I might remember something about 1 year ago, when I installed MO, that I had to change the registry entry manually, I just don't remember exactly.
And as I understand the feature of MO, of course it has to hijack this - then when it should do it. And your advise is not usable for me. Neither is NMM able to handle Skyrim-MO-files nor is MO able to handle Fallout 4 files. That's why I installed NMM, else I would have sticked and rather prefered MO. That's why I installed MO2, explicitly for FO4. But of course if something doesn't work for somebody, it's me. That also goes for MO1, which lags heavily, for me. NMM behaves normally in loading, installing and deinstalling files, and I like the category system of NMM way better. But of course it lacks the special features of MO. I would like to see an integration of the too. I would created one, had I that insight. I figured in the beginning of FO4 with only a few hundred mods it is not that a problem, until MO2 becomes stable.
When I installed MO it did not hijack Nexus links in first place. They where still handled by NMM, until this was changed manually. Now with a new installation of MO on a new computer this year I had to check a box in the settings to make MO handling Nexus links. I unchecked this now. Did not work. I read about the nxmhandler and used it. Did not work. Now this nmxhandler starts and immediately shuts down, not offering any choice. I suspect the nmxhandler evaluates, that MO does not hijack nmx-links. Still MO does.
As you say, that MO is hijacking NMM-links: several possibilites and trials of disabling this in MO did not work. So I think the error lies in MO, at least in the current version. I suspected this. In the last weeks I worked on reading up the STEP and installing Skyrim mods STEP by STEP. And from conversations between STEP members and Tannin, and that he masters all this alone. I have no hope that he has the time to care for my circumstances. I myself can care for this only because of less work to do at the moment, and I wasted already some days for researching this issues with the result that there are some issues. I might already have done better with a manual installation of mods in FO4. But on the other side I am still in the process of learning which mods are useful and in which order, that's where MO2 would have been useful.
Still I think the problem should be a registry entry, that does not get reset properly, and it might be a simple manual act that takes a few seconds. My hope that somebody knows this here was already low when I posted. Still I think a year ago I found the answer per google or as an explicite instruction somewhere, but not now.
So my question still stands unanswered. It might boil down to a specific registry entry that declares which program has to handle NMX links.
Edited by Truchses, 02 February 2016 - 06:53 PM.