GrantSP

The error usually occurs when MO was initiated via a download of a mod from Nexus, and not via a desktop shortcut, for whatever reason the switch removes that error. You can safely remove the switch if you ensure MO is started via a shortcut before using LOOT, but there is no gain from removing the switch.

Moved to the General Support Forum.

If @EssArrBee wants to add it to the list, that's fine. Anyone should be able to add it to the wiki guide. Since it is a very simple mod to add that has absolutely no conflicts with anything at all, except of course JIP CCC, installing it by anyone will be easy. So long as MO shows it providing those textures, everything is fine.

Thanks. I can't see anything significant. BTW, remember to use spoiler tags for those long texts.

If you still have the old ini I would like to see it to compare with a current one. Clearly there must be a setting from an older version that is causing that.

The JIP CCC ThinUI mod is a piece of cake to install, nothing special about it. Just place somewhere after the JIP CCC mod, it only replaces a handful of the UI element textures in the JIP CCC bsa.

Very weird! I would also advise installing any tools like LOOT into folders outside the 'Program Files (x86)' folder. Anywhere else would be good just to avoid potential issues with Windows UAC.

There's an UI modification for JIP's Companion Control that looks quite nice.

The papyrus log shows a number of script errors relating to some mods Amazing Follower Tweaks, CASM, Arissa, and a number of Jaxonz tools. These will need to checked to ensure you have them in the correct order both in the left and righ panes of MO. This is where NMM and MO differ greatly. MO will allow you to install mods in any order but you need to manage any conflicts by arranging them correctly so the game is provided with the correct assets, in this case scripts. However, as papyrus logs only log errors related to scripts, they are a poor diagnostic tool for general CTDs and other problems. Looking at your load order it looks like a number of supplementary plugins are loaded before their main plugin and that will be a problem. I don't actually have Amazing Follower Tweaks to check if they do need to be after the main plugin or not.

Your assumptions are correct, all your tools read the plugin list supplied from MO so the question we need to track down is: Which list is being parsed by your tools? If you don't already have one, make a new profile in MO and enable a handful of plugins and then run one of the tools, such as LOOT. If it recognises those plugins, change back to the STEP one and check that. My reasoning is this. Either the actual content of the plugins list wasn't saved or was set to read-only and your tools couldn't read it or the working directory of those tools was somehow changed to see the default list in your My Documents folder. If you could provide the ModOrganizer.ini for us we can see if any setting is off.

Don't know the cause of the error messages, and from the reported issues it looks like they are very strange ones to pinpoint, all I can suggest is to try a clean install of MO again. Delete everything in your MO install folder except: 'mods','downloads' & 'profiles' folders and the ModOrganizer.ini & nxmhandlers.ini. If you have one also the categories.dat. Grab the latest archive of MO and extract the contents of that into the now cleaned out folder.

Thanks for your input. Yes, of course all relevant information is vital with any support question. After all this discussion though, I think it is clear that this isn't so much a software error, rather a missing installation requirement for "some" users. That isn't to say the blame resides with the user or the developer, just a statement of fact. ALL Windows systems have the basic .NET system as part of the OS now and it only needs to be enabled for some users, or the 3.5 version needs to swapped out for version 4.0+. You may recall I mentioned an issue I had with Microsoft's own installers refusing to see their own installed software. I re-examined those programs and it was indeed this sort of issue. The software was there but not enabled for that installer to see, though the functionality was there. That was frustrating to fix.

hmm... another .NET 3.5 question!

With the 'Sort' tool (a stripped down version of LOOT) in the 1.3.x versions, there is no report window after sorting your plugins. If you need the report afterward you can install and run the full LOOT from inside MO.

The only reason I can think of why the Control Panel didn't 'fix' it for you was you didn't restart your system afterward. I checked a couple of times with the hand made registry edits and the Control Panel tool and the entries are the same. The only difference being using the Control Panel tool, Windows enforces a restart on you before assigning those entries. The end result though is all you really need and if everything is fine now, all's good.

The errors are due to the mod(s) not finding the required meshes and/or textures for those weapons. Recheck the guide and your load order to ensure the correct mod(s) are placed in the correct order.

That Alternative Repairing mod looks intriguing.

Don't worry too much about your English skills, plenty of people here will be more than willing to make any edits to it for you if you wish.

hmm... it would seem MS is focusing it's nefarious tasks on you poor souls in the US. My GWX folder hasn't been touched since the Win10 systray alert first showed up. Still, I do appreciate the heads up to disable it. It was also pleasing to read @Arthmoor go off the deep end on MS. I always had him pegged as a calm level headed fellow that can't be ruffled, apparently MS is really good at that.

The reason why @Tannin has marked this as "will not fix" is because he is working on a completely new 'hooking' system that should eliminate all these types of issues. I haven't run into this lately largely because I haven't run WB for months. It probably is there but since it doesn't affect the actual patch, there is no issue for me.

Sorry, I'm good at confusing things. You are both right! Sort of. The Control Panel fix for .NET 3.5 is much easier to use and it does exactly the same thing as your, and my, registry edits. But the bigger question in my mind now is: Why is MO making a check for 3.5 if 4.0 is used in the compilation?

That's fine, I just checked Microsoft's documentation and .NET 3.5 is included in ALL versions of Windows and it only needs to be enabled via the Control Panel, as outlined above. So I've learned two things in this discussion: there is a version of .NET suited for MO in ALL Windows installs and there is a little tool that enables itJust to clarify more the way MO checks for the needed .NET version, according to Microsoft the actual registry key is the one @SkyrimCliff pointed out.

To be technically correct the fix provided by @DoubleYou is used to redirect registry entries when the computer it is on is using a 64bit OS. The actual entry is simply redirected to the other registry branch as posted by @SkyrimCliff. Both work because the OS will end up in the same place when the search for that key is made.

hmm... how do you make weather mod comparisons that detail everything? Could be a battle over which one.

No need to bump it, give us a chance to get through everything. I believe you may be seeing what is described in this topic thread. Also the bashed patch gets placed in the data folder when you install WB, nothing to be worried about with that.