- 0
Failed to start helper
-
Similar Content
-
- 4 answers
- 876 views
-
CTD from having dyndolod.esp enabled in new save and old 1 2
By pentapox,
- SKYRIMSE
- DynDOLOD 3
- (and 1 more)
- 18 answers
- 1,661 views
-
- 13 answers
- 3,618 views
-
-
Recently Browsing 0 members
- No registered users viewing this page.
Question
aboutthe1910s
I've used MO2 with the classic version of Skyrim for a while, so I was already familiar with it. It was working fine. But I finally decided to switch over to SSE, and I uninstalled and deleted nearly everything on the SSD I keep Skyrim on. The problem came when I downloaded MO2 again and tried to set it up to work with Nexus links. I had them working fine before. But now every time I try to associate them, whether I do it through MO2 itself or by trying to run nxmhandler.exe, nxmhandler.exe mysteriously *disappears* from the folder and if I'm trying inside MO2 I get a message that says "Sorry, failed to start the helper application." When I try to run helper.exe to see what's going on with it, all it says is "Invalid number of perameters -1." I scoured the internet before making this post trying to figure it out for myself. I made sure I was running as administrator--I even set nxmhandler.exe and helper.exe to run in administrative mode too, just in case. It made no difference. I redownloaded and repaired the VC redist files suggested on the MO2 Nexus page (even though MO2 was working fine this morning, so I was pretty sure it wasn't that.), and that didn't help. I have the entire drive set as an exception in my antivirus software. I had some MO files in my App Data folder that I deleted. I even reformatted my SSD because I thought it might be a weird Windows 10 administration/privilege issue, and that might solve it. I mean, yeah, I know perfectly well how to just download manually and install, but it's nice to be able to right click a mod and go to the Nexus page for it after it's installed, and that doesn't work with manual installation. Also, I'm not sure what else the helper.exe does, but I feel like there might be other issues at some point if I can't get it working. Help, please?
And now I'm getting a message saying that I don't even have administrative permission to put the nxmhandler.exe file in the drive at all. Everything else copies over just fine, it's just that one fine that Windows is being ridiculous about. I checked the properties for the folder, and sure enough Windows thinks it's Read Only and no matter how many times I unset it, it keeps stubbornly saying that it is when I close and reopen the properties. I tried disabling Read Only through commands, and even that didn't help--when I checked the properties it still thinks the folder is Read Only. And I ran a diagnostic tool on the drive, and it says it's fine, so I don't think the drive is just broken. So I'm guessing this is a Windows10-is-awful-and-I-hate-it issue, not actually an MO2 issue.
Edited by aboutthe1910s4 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now