GrantSP

There is no ModID for that mod because it is sourced from a Mega account, not Nexus, and therefore does not have a ModID. Just ignore that and install.

Okay, a couple of points. If you have an AV package running try adding MO to its exclusions settings, or at worse disable it before running MO. The usvfs log is probably empty because your system is hindering MO from 'hooking' the process and/or writing that log file. Anytime MO is run, regardless of whether another tool is called, that log should be created and updated during the entire time MO is open. Secondly you have a lot of messages about missing Russian language files. Based on your username I'm assuming you're not using a Russian version of Skyrim, that being the case I would like to know how you installed MO and from where you got the program. If the language is not what you expected to see, open the 'Settings' -- 'General' and choose "American English" from the dropdown list.

To both of you, could you please post your MO logs and ini. There is nothing inherently different with running WB in MO2 compared to MO. I have it running just fine in my MO2 install and there are no issues I can see. STEP does not endorse hacky workarounds like that proposed here. The user should not have to make copies of every plugin in the game's "data" folder to get WB to work.

Thanks. I usually make that mistake until I get into February.

<!--========== Radiation Meter =======================--> <rect name="RadWrap"> <locus> &true; </locus> <x> <copy> 50 </copy> <add src="io()" trait="_HUDRad_X" /> <add src="screen()" trait="width" /> </x> <y> <copy> -37 </copy> <!-- DarN CHECK --> <add src="io()" trait="_HUDRad_Y" /> </y> <visible> <copy src="io()" trait="_HUDShowRadiation" /> <and> <not src="io()" trait="_xRad" /> </and> </visible> Notepad++ is a very good tool to have installed on any system. It's free and is much better to use on any text file, especially on large files.

You can do that, inside "spoiler" tags, or use an online site like PasteBin to host them and post the links.

What happens if you delete the patched game exe and run the unpatched exe from MO? If you can run the game from that then the patching process is broken, try running the patcher as ADMIN as detailed on the patcher's Nexus page. If you also go to a black screen with the unpatched exe then the current profile in MO is not loading all the required assets.

Updated the guide to use the new 4Gb patch instead of the older 'loader' style.

I've updated the guide to include the newer patch and removed all references to the older one.

MO2 stores the ini and logs in %appdata%.

Use Windows explorer and open: C:\Users\Admin\AppData\Local\ModOrganizer\SkyrimSE\logs\ and delete everything in that folder. Reload MO and start an instance of SSEEdit and then post those logs here please. The lines above that are of concern is: Using plugin list: C:\Users\Admin\AppData\Local\Skyrim Special Edition\Plugins.txt Warning: Could not find plugin list The first line is what SSEEdit is looking for and MO should be parsing the plugins.txt from you currently active profile into that memory location. For some reason it isn't. Hopefully the logs will tell me why. Is there any reason why you are running your system from the Admin account? It shouldn't be of concern as that should mean all executables will have the same privileges, but I don't view this as a good idea. Using a general user account with elevated privileges when needed is much more secure.

In general you shouldn't extract your BSAs, as @Arthmoor instructs, unless the guide you are following specifically instructs otherwise. @Neovalen's Skyrim Revisited is one such guide.

MO FAQ, 1st question.

If you ran the patcher then the executable that you call needs to be the newly patched exe. DO NOT try and run the NVSE loader or the previously used patch. FNV4GB.exe, and any files in the 'exes' folder should be removed from your system as they are no longer needed. This means you should also ensure your executables list in MO is pointing to just the game, nothing else.

Glad to hear you got around that error. As I've noted in this thread AV software is notorious with interfering with MO and its 'hooking' function. Instead of disabling your AV, you may be able to add MO to the exemptions list.

Since you're using MO2 I doubt very much you will have extracted the contents of the BSA. MO2 has no function to do this as MO did and I know of no reason why you would manually do this. Additionally Skyshards looks for only the base game file as masters so there is no problem with that installation. Post your MO ini and the contents of the log folder here so I can examine what is happening.

The button labelled: "Manual".

LMGTFY

I see nothing wrong in your settings so I can't see why that mod will install without prompt. Do you see other mods install with the manual dialogue? If so perhaps your computer parsed an additional mouseclick without your prompting. To reiterate that mod should, by default, open as a manual install in MO. Putting that aside you can make the necessary changes as outlined in the guide by using MO's 'Filetree' tab or by using Windows explorer. All that you need to ensure is the plugin in the subfolder is used, not that in the main folder.

Are you sure the file you have is the file you downloaded. The checksums for that file are: MD5: 1F6E8A5312D6A377EE9E67772349C036 SHA1: B4778A0287D680D5DB663AB86BB67A42AEAA77B7 CRC32: C359D247 Since the 'Content-addon' file contains no fomod script to install it, it should not automatically do anything. Whatever the situation could you post your MO.ini so we can see what settings you have enabled?

STEP makes use of ModOrganizer which utilises its own BSA management system. Simply check those archives in MO's 'Archives' tab and rest assured they will be used.

MO makes use of simple text files to keep track of all the game plugins, mods, etc. Nothing is stored in the registry. MO2 uses the Windows storage setting %appdata% which will be something like this: C:\Users\GrantSP\AppData\Local\ModOrganizer\in your system. Obviously not with my username in the path. Deleting this folder will remove MO2 from your system, at least as far as the settings are concerned, the actual executable is where ever you installed it. The mods, downloads and profiles are also in that location, unless you changed that in the MO settings.

Not according to your posted INI it wasn't.

Not sure where you are reading the instructions but this has been included in the STEP guide for sometime.

That's good, that means your previously cleaned ones are still active. Carry on from where you left off.