GrantSP

When you start Skyrim from MO does the menu still look corrupted with the missing fonts issue? It should. I can't think of any reason why/how SKSE could cause that problem. I would create a new profile and install only a bare minimum of mods to check the problem. Firstly delete the original ini files in your My Documents folder and run the Skyrim launcher to create new ones. Then create a new profile in MO which will use these new inis as a base. Any edits that may have corrupted something shouldn't exist in these versions. Start the game from MO, both with and without skse, and see what the result is.

Try adding: -forcesteamloaderto the Arguments field.

MO makes checks for files that are 'ghosted' but AFAIK it has no functionality to add that as an extension to files, that is as you said, a Wrye Bash thing. I would examine whether WB is setting that first and disable it from within WB.

Post the path to SKSE as defined in the 'Executables' list in MO here. It should be pointing to skse_loader.exe in the same folder as your Skyrim game files, ie.TESV.exe. Could you clarify something? When you say the SKSE shortcut, you mean the one that doesn't use MO to load your game but the one created by the installer?

Are you sure what you are seeing isn't the result of a misplaced, or incorrectly installed, mod in the left-hand pane? If some texture issues exist it could be because the mod's assets are being overwritten by another mod.

As good as Boris' programs are, his website design is atrocious so I have no doubt you are not alone in finding things difficult.

As of LOOT 6.1 XP is also dropped. From what I hear, Microsoft may in fact be giving every current Windows user a free upgrade to Windows 10 when it is released. That may or may not be a good thing. At any rate if you are still using XP, it is time to move on.

Check the [Fonts] section of your ini to ensure all is set correctly. Sometimes if you miss setting the DarnUI fonts correctly the game can't get the main menu set up.

I know fore has already addressed this for a number of users and stated it is something to do with the .Net installation, but exactly what isn't clear. I doubt it is specific to MO, but I could be wrong, only way to check for sure is to try to use the tool outside of the MO environment. The error message does lead me to believe there is something wrong with your .Net environment but anything more than that, I can't tell.

Are you sure you haven't changed a setting in either the MCM menu or by using an outside tool that changes settings, like NV Configurator?

Just drag/drop each file into its specific mod so that they are found in MO's VFS each time it starts.

@toolio20 Can you just check a theory I am currently running with. In the shortcuts to MO on your desktop/startmenu, is the "Start in" field filled in with that path to your stylesheets? PS. I asked why you are deleting the ini because, as fixes go, that is definitely one of the worst. All your settings will be removed and nothing you set will be saved. If you had of simply stated at first the 'actual' problem and not the method you chose to get around it. Anyway, I fully understand the frustration you were no doubt experiencing at the time, no issue. I'm not having a shot at you, just a suggestion on how to get resolutions to problems in the future.

Well apart from following guides created by knowledgeable users like the STEP guides, you can examine the mod pages and see what users are reporting about it, any major concerns. The best advice I could give though is to know WHY you want these mods installed. Don't install something just because it is on the best mods list or it sounds like a good idea, know what you want to get from it. Then when another great mod comes along you can see where, if anything, there might be conflict. Modding your game is not an exact science. Trial and error are your friends. Also know the limitation of your system, what works for some may not work for you. I only have a gaming laptop and can't install a great many wonderful mods because it just can't handle it.

No idea why it says 0mb, presumably to cover all options for those cards, 1mb, 2mb, etc. I haven't used this tool so I can't say for sure.

If you are getting the SKSE folder being created in the overwrite folder then I would say you haven't installed it correctly in the first place. According to the best case method, the executables from the SKSE archive are installed into Skyrim's folder and the scripts are installed via MO's install method. Any SKSE plugin that creates an ini or log file needs to have those files drag/dropped into their respective folder so they are updated as needed. Nothing should be created new in the overwrite folder for SKSE after starting Skyrim.

@BarfingOgres Could verify a theory I'm running with at the moment? Check the shortcut on your desktop/startmenu for MO and tell me if the "Start in" field is filled in and what is its contents if it is.

Typically any card with xxxxM is found on a laptop/notebook and those listed as HD xxxxG are for desktops. The actual number may be slightly different but if you version falls within that series, use that one.

A point to keep in mind, the Papyrus log isn't a reliable indicator of mods that cause CTDs. That log only handles events that are calling the Papyrus scripting engine inside Skyrim, you could have any number of problematic mods that don't touch that and still get CTDs, or conversely, have a log full of apparent error messages generated by mods but your game functions just fine and you have no CTDs.

Fomod will have no bearing on how the MCM works ingame. It is as @Xaviien says an issue with SkyUI, or more specifically, the game engine labouring under a number of scripts and SkyUI's MCM scripts are playing 'catch up'.

Why are you deleting the MO ini? There should be no need to do this.

Going through the threads this morning, I made my way to a new posting in a thread about 'Being unable to download from Nexus' Every time I clicked to see what the latest post was about, a download starts for the file: download.htm. I quickly deleted these files and went here to report it. No other threads I have come across behave like this and I'm concerned someone may have left some malware or kiddy-script behind. Posting that URL in a new browser tab seems to take me to the thread so I am really not sure what is happening. Thanks.

This is a restriction imposed by Nexus and nothing to do with MO. Nexus uses a distributed network of servers, called CDN, to provide these files and each of them is provided a temporary access key whenever you click on the download in Nexus. These are designed to expire after a short time to stop file leeches from directly linking to them. Usually it lasts around an hour. Unfortunately for those with poor internet, or those that need to do other things while downloading, this means that link needs to be refreshes with a new key. This is only possible by downloading again from Nexus. There is a way around this if you are having poor download speeds. A program like FreeDownload Manager (FDM) can handle those downloads and if it is paused, and the key expires, you can start a new manual download in your browser, pause that download in your browser and examine the URL in your browser's download window. Copy it and paste it into FDM's download properties as a new 'mirror'. FDM will then add onto the existing download using the file from the new CDN and the download will continue from where you left off.

Be sure to click the 'Modify' button to save those settings. There have been a couple of users posting similar issues as yourself. For some reason some are having those settings look to the wrong location. One thing I noticed on my installations, though I had no issues with saving the settings, was the desktop shortcut had the "Start in" field pointing to an unnecessary folder and once I removed that, the settings pointed to the correct locations. So in your case, the shortcut field is pointing to the ModOrganizer folder and thus all the default executables are likewise looking there. One more thing. You might avoid any more potential issues if you install MO away from any folders controlled by Windows' UAC, such as the folder you currently have it in. Installing into a folder such as 'C:\Games\MO' will be free of Windows' restrictions.

@wario44 If you are seeing that file open as a manual install then there is something amiss with your MO installation. No matter which setting you have for your plugins, internal or external fomod installer, that file always shows in my MO 1.3.3 install with its fomod scripted install. Can I assume you updated to 1.3.3 over an existing 1.2.18? If that is true you may need to do a bit of cleaning. There could be some remants of the previous install conflicting, though @Tannin did make the new installer clean out that stuff first. At any rate, grab the latest MO full install archive, not the installer, and open it in your archive manager. Open an explorer window with the MO installation. Delete every folder and file that exists in the MO install AND in the MO archive. This is to ensure no leftovers from a previous install. The files/folders that you should be removing are: NCCplatformsdllspluginslootstylesheetstutorialstranslationslicensenxmhandler.exehelper.exehook.dllModOrganizer.exeuibase.dllmsvcr120.dllmsvcp120.dllpython27.zippython27.dll Everything else is either a setting you have made or the downloads, mods, profiles folders with your files in them. Copy all the contents of the MO Full install archive and the result will be a pristine 1.3.3 MO install with all your settings and mods intact. Try that mod installation again and if still doesn't work could you post all the relevant details into a bug report in the Bug Genie.

When I messaged him a few months back he indicated, or maybe I took it as that, he was the only one left. I could quite easily be in error on that. The point I was trying to get across though is, the latest release is only new functions, not changes to existing functions. (with only 2 minor fixes) Without getting into semantics over what constitutes a bugfix I was just highlighting the fact, installing 1.07.02 shouldn't be considered as an improvement to 1.07.01 or 'more bug free'. I meant no sleight on your recommendation to use it or yourself, just that 1.07.02 will be in the same state as 1.07.01 and shouldn't be viewed any differently. If the wording of my comment came across as anything more than that, I apologise.