Jump to content
  • 0
bweep

Can't Launch Creation Kit Through MO2

Question

I've been troubleshooting this for two days now and I still cannot find the cause. Creation kit used to work fine, but at some point at the end of this week while I was installing mods for SSE, it decided it no longer wanted to cooperate. Whenever I try to run CK through MO2, it simply locks up for a bit before unlocking without any sort of error. During troubleshooting, I realized MO2 has the same issue with SSE and the SSE launcher. I

 

Things I've tried:

  • Reinstalling Skyrim SE twice, making sure the whole folder was wiped before reinstalling the second time. I've verified the integrity of the game files twice between these two times.
  • Reinstalling CK at least thrice, and even the bethnet launcher once (I made sure CK was installed in the SSE directory)
  • Reinstalling MO2 twice
  • Renaming MO2's SSE mod folder so the list would be not only entirely disabled but entirely empty. (SKSE is the only thing installed, and it's installed manually.). I'm willing to wipe the folder in its entirety if anyone thinks that might warrant a different result.
  • Restarting the computer
  • Making firewall and AV exceptions for MO2 and CK
  • Temporarily disabling firewall and AV entirely

Other details:

  • I am aware that installing in program files causes issues. I have steam installed in the D: drive in a self-made folder, but it is still titled D:\Program Files (x86). Could this possibly be insufficient?
  • Creation kit was not installed as a mod (not that I'd know how to install CK in particular as a mod) so it's not available in the left pane
  • SkyrimSELauncher.exe appears to be working at first but simply closes out with no follow-up or error when I hit play.
  • SKSE and xEdit run just fine. In-game SKSE w/o mods seems to run just fine.
  • Mod Organizer is not installed onto the steam or skyrim folders. It is in D:\Modding\MO2
  • The only thing I could think of that hasn't been affected by my troubleshooting was that there was a Windows 10 update between when CK last worked and now
  • SSE launches fine through Steam. CK runs just fine through the bethnet launcher and directly from the folder
  • SSE version 1.5.80, SKSE version 2.0.16, MO2 version, CK version 1.5.73 (but I've also used 1.5.3)
  • I don't see anything in the properties of the .dll files of MO2 indicating they're blocked, but I don't see anything indicating they aren't either.

I might be missing something, but I'll give an update if I recall any extra details. 

Share this post


Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 0

Installing Steam and Skyrim in D:\Program Files (x86) should be fine provided you created the folder yourself. I've done pretty much the same thing on my system except I named it D:\Program Files. To be honest, I'm not see anything here that stands out as a possible issue other then the nagging Windows 10 update. I do remember some of the folks here ran into issues with Wrye Bash that required forcing an update to Windows 10 build 1809 or later, but I think this is an issue with Wrye Bash that's most likely unrelated to Creation Kit. (see https://forum.step-project.com/topic/14158-cant-use-wrye-bash-from-mo2/?hl=force+update&do=findComment&comment=236549)

 

The only thing I can think of is to enable debug logging and to go through the log file to see if anything there stands out. To do this, delete everything in the Mod Organizer\Logs folder to start clean. Run Mod Organizer. Click Configure Settings and Workaround (the screwdriver/wrench icon a the top left), go into the Diagnostics tab and change Log Level to Debug. Click OK to close the dialog. Now run Creation Kit and wait for it to exit. Close Mod Organizer and upload mo_interface.log and usvfs-*.log to somewhere like PasteBin or a cloud drive and include a link to it here.

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Mopotter
      1. I've been using MO 2 for years for 3 of my games, Skyrim, Skyrim SE and FA4.  No problems and yesterday  I know I did something wrong because the top line of items is missing and Skyrim SE is the only game I can access.  But I don't know what I did or how to fix it.  I've  uninstalled and reinstalled with no change.   Hoping someone has done this and can explain how to fix it.  

    • By Ayohaych
      Hey all.
      Sorry if this has been asked but I couldn't find anything.
      I got a Steam Deck recently and was in the process of setting Skyrim SE up with mods.
      Right now it actually works, however I can't seem to figure out how to launch Skyrim SE Launcher? I need to change settings so it runs better.
      When I open Skyrim from Steam, or use bottles to run Skyrim SE Launcher, it launches MO2. From there I have to select SKSE and hit run and it launches.
      If I click the drop down and select Skyrim Special Edition Launcher, it says an instance of mod organizer is already running.
      Any ideas on how I can get around this to launch the launcher so I can change my settings?
      It seems there is _SkrimLauncher.exe file that must of been automatically created by MO2, however when I run that with Bottles, and make changes, it doesn't seem to have the changes when I run SKSE.
      Thanks for any help!
    • By koopastroopas
      I have always used Wrye with MO but now on a fresh install of everything(Skyrim SE) when I try to rebuild the Bashed Patch I get an error saying "file not found, it may have been moved, edited or deleted. I have no idea what that means since it doesn't even tell me what file is supposedly missing. Any ideas as to whats going on here?
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.