Hello, forum. I'm about ready to pull my hair out. I cannot figure out what is happening or why.
So, Steam and Mod Organizer had an update roughly around the same time. I was playing Skyrim earlier, and it was fine. I updated both and went back later to run SKSE through Mod Organizer and received the error:
"Steam application error P:0000065432"
I did everything I could think of doing, including restarting Steam, my computer, deleting ClientRegistry.blob from the Steam program file, and launching and not launching MO in Adminstirative Mode.
Another solution I tried was revalidating my files in Steam. After I did that, I went to clean the four ESMs besides Skyrim.esm in TES5Edit before trying SKSE again.
Imagine my surprise when Mod Organizer is no longer recognizing Dawnguard.esm as even existing anymore. Nothing I do will make MO even see that Dawnguard is sitting in the Skyrim data folder. I even tried uninstalling and reinstalling Dawnguard IN the Steam client, to no avail. MO isn't recognizing Dawnguard.esm anymore.
So now not only will SKSE not run through MO, MO isn't even recogninzing Dawnguard, which is causing a LOT of mods to lose their master file. This is beyond frustrating and I cannot figure out if it's Steam or MO causing this issue. I would appreciate any help I can get in solving this on my own, or until I find out it's an issue with MO and Steam and I'll need to reinstall NMM.
EDIT: I feel like an idiot. Apparently my firewall was sandboxing Steam, MO AND Skyrim, and not telling me.
Lesson learned, kids: Don't trust Comodo's Game Mode.
Question
TheGlassesGirl
Hello, forum. I'm about ready to pull my hair out. I cannot figure out what is happening or why.
So, Steam and Mod Organizer had an update roughly around the same time. I was playing Skyrim earlier, and it was fine. I updated both and went back later to run SKSE through Mod Organizer and received the error:
"Steam application error P:0000065432"
I did everything I could think of doing, including restarting Steam, my computer, deleting ClientRegistry.blob from the Steam program file, and launching and not launching MO in Adminstirative Mode.
Another solution I tried was revalidating my files in Steam. After I did that, I went to clean the four ESMs besides Skyrim.esm in TES5Edit before trying SKSE again.
Imagine my surprise when Mod Organizer is no longer recognizing Dawnguard.esm as even existing anymore. Nothing I do will make MO even see that Dawnguard is sitting in the Skyrim data folder. I even tried uninstalling and reinstalling Dawnguard IN the Steam client, to no avail. MO isn't recognizing Dawnguard.esm anymore.
So now not only will SKSE not run through MO, MO isn't even recogninzing Dawnguard, which is causing a LOT of mods to lose their master file. This is beyond frustrating and I cannot figure out if it's Steam or MO causing this issue. I would appreciate any help I can get in solving this on my own, or until I find out it's an issue with MO and Steam and I'll need to reinstall NMM.
EDIT: I feel like an idiot. Apparently my firewall was sandboxing Steam, MO AND Skyrim, and not telling me.
Lesson learned, kids: Don't trust Comodo's Game Mode.
Edited by TheGlassesGirl4 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