Greg

I'm not aware of any mods that can do this. I usually use Alternate Start to start outside Helgen Keep. This is more or less is like skipping the cart ride and the tutorial quest through the keep, although I realize this isn't exactly what you are looking for.

I wouldn't worry about it over much. This is the correct topic for your question and I locked your original post. DoubleYou is the BethINI creator and master and will respond to you question next time he's on.

I'm assuming this is for Skyrim Legendary Edition since you mention TESV.exe. First and foremost, ensure that Skyrim is not installed in a UAC protected folder like C:\Program Files or C:\Program Files (x86). It's rather unfortunate that this is the default path used by Steam but you should install Skyrim preferably in a folder you create so you don't run into odd permission and security issues. Basically all you need to do is download the appropriate version of SKSE and save the archive file somewhere. I recommend right clicking on the archive file in File Explorer and clicking Unblock and OK before extracting the files. Now just extract the files right into the Skyrim folder (this is the same folder containing SkyrimLauncher.exe and TESV.exe). This means you should have skse_loader.exe, skse_steam_loader.exe and skse_1_9_32.dll in the same folder as TESV.exe. While in the Skyrim folder, create a new folder named SKSE and in the SKSE folder create a new file named SKSE.ini. Ensure the file is really named skse.ini and not skse.ini.txt. Edit the file in a text editor like Notepad and paste this into it: [General] ClearInvalidRegistrations=1 [Display] iTintTextureResolution=2048 [Memory] DefaultHeapInitialAllocMB=768 ScrapHeapSizeMB=256 Save the file. Now run skse_loader.exe and you should be able to start and play a new game without any issues. Download Mod Organizer and be sure to unblock the file you downloaded before doing anything with it. If you are using the installer, double click the installer and install it somewhere outside the UAC controlled folders. You can use something like C:\Games or C:\Tools or a folder on any local hard drive or SSD. Do not install Mod Organizer in the Steam or Skyrim folders because the virtual file system will not work and do not install Mod Organizer to a network shared folder because Windows won't trust it. Run Mod Organizer and go through any settings that you need. I also recommend running TESV.exe once to verify that you can start and play a new game without any issues. Assuming the game is working fine from Mod Organizer, go back into Mod Organizer. Click the Configure executables button (the cog icon) and add a new entry as follows: Title: SKSE Binary: C:\Steam\SteamApps\common\Skyrim\skse_loader.exe Start in: C:\Steam\SteamApps\common\Skyrim Arguments: You may need to change the paths but this is basically all that's required. Click Add to add SKSE as a new executable and click Close to close the dialog. You should also be able to run SKSE from within Mod Organizer just fine without any issues.

i added the Mod Picker link but it won't be accessible until Mator approves it.

The Scripts and Sources folders are backwards. If you open the archive, you'll see it has Sources at the root and Scripts as a subfolder but it should be the other way around. This is fairly easy to fix by doing this using File Explorer. Open the Sources folder. Right click on the Scripts folder and click Cut.Back out to the Data folder. Right click in a blank area and click Paste. You should now see the Scripts folder as a subfolder of the Data folder.Click on the Sources folder and drag it onto the Scripts folder.Your folder structure should now be Data\Scripts containing the *.psc files and Data\Scripts\Sources containing the script source files.

You have Skyrim SE installed in C:\Program Files (x86) and this is known to cause issues. I suggest moving Skyrim SE to another folder that is not subject to the UAC restrictions.

I'm not sure which files you are moving to My Documents, but I wouldn't install Mod Organizer or any of the modding tools here. You can create a directory like C:\Games or C:\Tools and install the tools in this folder. You also just reminded me another issue you may run into. The virtual file system will not work if you run Mod Organizer as a regular user and Mod Organizer runs SKSE or Skyrim as an administrator. This is because Windows prohibits a user process from hooking an admin process. You shouldn't need to run any of the tools or the game as an admin anyway.

You do not need to be authenticated with Bethesda.net, but there are some relatively common issues that can cause mods not to load properly: Do not install the game into a UAC-controlled folder like C:\Program Files or C:\Program Files (x86). Files in these folders have an extra layer of protection that can throw off Mod Organizer's virtual file system. Do not install Mod Organizer into the Steam or Skyrim folder. This was somewhat common practice in a lot of guides years ago, but it's a really bad idea because Mod Organizer's virtual file system does not work correctly in this scenario. Antivirus software (or even Windows 10 itself) may be blocking Mod Organizer's hooking process that prevents the virtual file system from working. This is commonly caused by blocked files or overly aggressive antivirus software. The first step is to open the Mod Organizer folder with File Explorer, right click ModOrganizer.exe, and click Properties. If you see an Unblock button or checkbox, click it and click OK to apply the changes. Note that if ModOrganizer.exe is blocked, you may need to repeat this for every *.dll in the Mod Organizer folder and all subfolders. You'll have to do this one file at a time because Microsoft does not provide any mechanism to unblock multiple files. If the mods still aren't loading, you might temporarily disable any antivirus software and try again.

It sounds as if you have animations from a Skyrim LE mod installed so you might verify all your mods are from the Skyrim SE section on Nexus.

The only possibility I can think of offhand is to try to use Windows+Shift+Right Arrow or Windows+Shift+Left Arrow to try to force the dialog back onto the screen, but this requires the dialog to have active focus. You might ask the dev over on the Mod Organizer discord channel if there's a way to set the coordinates of the dialog in the INI file or registry to force it onto the screen the next time it's opened... assuming it actually opened.

I've never used Ordinator, but you might double check the load order for Thief Skills Rebalance for Ordinator.esp and Ordinator - Perks of Skyrim.esp. It may be fine the way it is. It just stood out as a possibility if Thief Skills Reblanace overrides records in Ordinator.

I don't have Skyrim SE setup with SKSE at the moment, so that setting may be only for Skyrim LE. My mom's in the hospital so it may be a fewweeks before I can get into the groove with Skyrim SE.

Have you tried increasing DefaultHeapInitialAllocMB in skse.ini? I think 768 is the minimum that should be used for this setting. If you already have it set to 768, you might try increasing it to 1024 to see if it helps. [Memory] DefaultHeapInitialAllocMB=768 ScrapHeapSizeMB=256

All of the saved game data is in the *.ess files. The *.skse files are created by SKSE and contain only the data SKSE needs to restore when you load a save. All this just to say that the *.skse files are pretty much useless without the *.ess files that go with them.

Which registry entries are you referring to here?

Skyrim Special Edition is available for free to everyone that has Skyrim Legendary Edition (or basically Skyrim with all of the downloadable content). The obvious advantage is that Skyrim Special Edition is 64-bit so it doesn't suffer from the same memory constraints as Skyrim Legendary Edition, but it has a few pitfalls as well. The most notable is that Bethesda updates Skyrim Special Edition occasionally for Creation Club and this invariably breaks SKSE and all mods that rely on SKSE until the mod authors release shiny new versions to support the latest version. Most folks seem to keep the updates disabled so they can keep playing and then manually update after all the all the mods have been updated. It's not necessarily the end of the world, but it is something you should be aware of so you don't get caught with a broken game unexpectedly. The general consensus is that most folks have already switched to Skyrim Special Edition and the next version of the STEP guide should be available for both Skyrim Legendary Edition and Skyrim Special Edition and this will likely be the last version of the guide that supports Skyrim Legendary Edition.

I think the installation should be relatively the same for all mod managers: Download SKSE obviouslyOpen the folder where you downloaded SKSERight click SKSE*.7z, click Properties, click Unblock and click OK. This is a safety precaution to prevent Windows 10 from causing issues later on.Extract skse*.dll, skse_loader.exe and skse_steam_loader.dll into the Skyrim folder. This is the folder with TESV.exe and SkyrimLauncher.exe.Run you mod manager and select to install a new modSelect skse*.7z in you download folder from Step 1 and install normally.The basic idea is to install the core components (the DLLs and EXEs) in the Skyrim folder and to install all of the scripts as a mod using your preferred mod manager. You can also install the scripts directly in the Skyrim/Data folder, but I prefer to install anything that goes in the Data folder as mod to keep the Skyrim folder structure as clean as possible.

The reason I offered the CBBE version of WSCO as an alternative solution is because I believe WSCO and CBBE/UNP are mutually exclusive. If you read the the installation notes in the WSCO description on Nexus, it explicitly states to uninstall CBBE or UNP if you are currently using them. This isn't necessarily the end of the world, though. The CBBE version of WSCO comes with the CBBE body meshes and WSCO custom body textures.

The other option is to install the UNP or CBBE version of WSCO in the Optional Files section. If you use a CBBE or UNP body, you may also need to replace some of the clothing and armors so they fit better.

If you use Mod Organizer 2 in portable mode, you can install as many copies as you want and all your mods are stored directly in Mod Organizer's mods folder. If you use Mod Organizer 2 in instance mode, you should have only and one copy of Mod Organizer 2 installed, but you can click the first button at the top left to switch between games. All of your mods are stored in %AppData/Local/ModOrganizer. I have no idea what happens if you try to install and run more than one copy of Mod Organizer 2 in instance mode. The Mod Organizer 2 devs prefer and recommend using instance mode, but I continue using portable mode because I think it's more flexible and allows me to easily backup/restore/duplicate just by copying the Mod Organizer folder.

This is an FOMod installer so run Mod Organizer, click Settings, click the Plugins tab, scroll down and click Fomod installer. Ensure enabled is true and and prefer is true.

This seems to indicate that nxmhandler.exe is running, but it can't find or load uibase.dll for some reason. As GSDFan indicates, the first step is to ensure you are not running Mod Organizer in a UAC controlled folder (like Program Files). If you are on Windows 10, you might also right click on nxmhandler.exe in File Explorer and click Properties. If you see an unblock checkbox, click it and click OK. Windows 10 can be a downright pain in the backside regarding security and misleading error messages. If you are using Firefox, go into Options, scroll down to the Files and Applications section (about mid-way down) and you should see a grid showing all the extensions Firefox can handle. Scroll through the list to find nxm. Click the box on the right (should be "Always ask") and verify the path to nxmhandler.exe is correct.

The usual culprits are covered in this thread and the most common one is naming the file skse.ini.txt instead of skse.ini. This one is really easy to do if you have file extensions hidden. You might also check D:\Users\Edahi\Documents\My Games\Skyrim\SKSE\skse_steam_loader.log since this one has some information on the heap settings read from the ini at the bottom of the log: dll = C:\Program Files (x86)\Steam\steamapps\common\Skyrim\skse_1_9_32.dll old winmain = 0069D1D0 runtime root = C:\Program Files (x86)\Steam\steamapps\common\Skyrim\ config path = C:\Program Files (x86)\Steam\steamapps\common\Skyrim\Data\SKSE\skse.ini overriding memory pool sizes default heap = 768MB (effective 512MB if not preloading animations) scrap heap = 256MB OnHook: thread = 21112 calling winmain What you've posted here seems to indicate skse.ini is in the correct folder and the contents of the file look correct to me as well.

The Mod Organizer devs are on discord and github, although I suggest browsing through the current Mod Organizer code. As far as I am aware, the FNIS code is not available.

If you are using Mod Organizer 2 (Installer), run the installer and tell it to install to a folder on your preferred drive (either D: or E:). If you are using Mod Organizer 2 (Archive), right click "Mod Organizer 2 (Archive)-6194-2-2-1-1564685345.7z", click Properties, click Unblock, and then extract the files to a folder on your preferred drive (D: or E:). Run Mod Organizer 2 and the initial dialog asks you to chose an instance. Select Portable and click OK then select the appropriate game you want to manage. If you do this, all of the mods you download and install are stored directly in the Mod Organizer folder you are currently using so it won't uses any space on the C: drive. The disadvantage with this approach is that portable mode can be used with only the game you initially selected. If you want to use Mod Organizer with another game (say Fallout 4), you'll need to install another copy of Mod Organizer and use that one in portable mode for Fallout 4. Just keep in mind that you can have as many copies of Mod Organizer 2 as you need.