bbinkerd Posted January 26, 2019 Author Share Posted January 26, 2019 I originally tried all of this on my primary account. It's an Admin account because I always like my computers to greet me with "Behold, the Great Lord and Dog" (yeah - that Microsoft fiasco left it slightly dyslexic). The main account can't select a file to use as nxm - no browse or selection capability. On the Admin account, when I go into the Microsoft file extension manager, the .nxm extension is shown to be handled by Vortex. I may just beg Wife to let me get another computer while I do a complete rebuild on this one. Link to comment Share on other sites More sharing options...
Depp3000 Posted January 31, 2019 Share Posted January 31, 2019 Hi bbinkerdI had a similar issue today. Were you able to fix it in the last few days? Link to comment Share on other sites More sharing options...
BigBizkit Posted February 1, 2019 Share Posted February 1, 2019 If you are absolutely sure Vortex is set to handle nxm links (like in the screenshots HadToRegister provided) it might be down to you using an admin account (which is not recommended in the first place, also please don't run Vortex as admin). Disassociating NMM should not even be necessary. The last application set to handle nxm links will take over (in your case that should be Vortex). Link to comment Share on other sites More sharing options...
bbinkerd Posted February 15, 2019 Author Share Posted February 15, 2019 This issue should be laid to rest. I now have proof positive that this whole fiasco is the result of Microsoft mangling the living crap out of my PC with one of their updates. I was just forced to reformat my c: drive and reinstall Windows. Since doing that, Vortex has behaved in a very precise and predictable manner. I really like it more than NMM (or other programs) for mod management. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.