GrantSP

This comment from the game engine needs to be investigated. It simply can't be dismissed as not important as the game engine is making this call, not MO or SKSE. The way it looks to me is you have a mod, or remnants of a mod, active in the Data folder of Skyrim, thus outside of MO's management. Add to that the strange INI settings and I would say you need to do a thorough cleanout of your game and start fresh. The time you take searching for an errant mod or setting may be better spent doing a fresh install. Since you said at the outset you have come to MO from NMM it is entirely possible that something has been left behind where it shouldn't be.

I should also ask, do you mind providing a list of the mods that you find problematic with the BAIN installation in MO and we can see if something further can be done to improve that feature?

Fair enough. Ok, firstly ensure your 'bash.ini' has the correct setting for that folder to be used for installing mods. Make sure the comment mark (;) is removed from the beginning of the line. sOblivionMods=C:\<path_to_location>\Oblivion ModsNext whenever WB's 'Installer' tab is accessed for the first time a dialogue will show asking if you want to enable installers, if you have already said yes you will need to use the context menu on that tab by 'right-click' -- "Enabled" and then wait for WB to run through all the locations it expects mods to be found. Those mods should now be displayed in the tab.

There will be no reason that 1.3.9 will make any difference to those mods/plugins. Make sure you haven't changed anything when you updated your MO to 1.3.9. Have you ensured you have the SKSE scripts installed correctly?

I'm not really sure what it is you are trying to do. Why is there a need to use the WB installers option if you use MO to manage your mods?

It's not the fact I want to use my camera & microphone, it's more the fact I just want the CHOICE to say IF I can use them. Having them not work isn't my issue, it's having the choice taken from me. Anyway, now I have the problem the wife found the update on her laptop and has now installed Win 10, but she didn't do any of the privacy changes that I did! Now I have to go through and make changes to her system to restore my sanity before I'm bombarded with questions as to why X, Y & Z is happening to her computer. Ahh the joys!

Whats wrong with my face?

If the mod in the 'Left-hand' pane is showing that flag and text it is because it contains nothing. Most likely you made an error when creating your bashed patch. At the very least you should see the file "Bashed Patch, 0.esp" and there also should be a folder called 'Docs' and a MO created file called "meta.ini". The mod can be examined by either 'Right-click' -- 'Information' > 'Filetree' or by double-click -- 'Filetree'. If it is empty then simply delete the mod and create a new patch with Wrye Bash and then create it from the contents of the 'Overwrite' folder.

Welcome to STEP. You might have better luck if you post this in a more appropriate topic. This is a very specific topic about user's views on the STEP guided install, if you post this in the DynDoLOD thread you have better chances of an answer.

The log is in this archive for what reason?

Further to the checking for pirated games, Microsoft will also continue to send back to base details about your system even if specific options like Cortana or OneDrive are disabled. More on my laptop refusing to start in lockscreen mode, even when I have set all the power options to 'Sleep' when the lid closes, when I'm away for a set time, etc. it refuses to do so and I am presented with the desktop on start. Possibly related, but an issue as yet, my camera and microphone can't seem to work for Win 10. All of this may therefore just be an issue with Toshiba needing to provide patches for their machine.

Have one from me also.

A really stupid setting in Win10 is if you have your account set to use your online Microsoft account the system doesn't wake from sleep to the lockscreen but goes straight to the desktop, thus having your entire system exposed and online. Only when you have your account using a local password does it wake to the lockscreen. An added bad setting is if using the Microsoft account your system can be started and accessed even when the laptop lid is closed, and should be sleeping. I awoke early last night and walked past my laptop to find the wireless and HDD lights active and the system apparently accessing files online. On investigation MS was downloading some updates ready for me to confirm/deny installation of. This is a major breakdown in security and something which prompted me to go back to using a local password.

Ok I won't ask... what was your mistake? Regardless of where the Microsoft installer is placing the SDK, all you need to do is replace that path in the commandline. simply replace the highlighted text with: "C:\program files (x86)\Microsoft Kits\8.1a\bin\NETFX 4.5.1 Tools\corflags.exe" /32bit+ "c:\Program Files (x86)\steam\steam apps\common\skyrim\papyrus compiler\papyruscompiler.exe" "C:\program files\Microsoft Kits\8.1a\bin\NETFX 4.5.1 Tools\corflags.exe" /32bit+ "c:\Program Files (x86)\steam\steam apps\common\skyrim\papyrus compiler\papyruscompiler.exe" All that needs to called is the "corflags.exe", it makes no difference where the commandline is pointing as long as that file is found there.

To both of you, the necessity to install the Papyrus compiler fix is only needed if you intend on making changes to the scripts used in a mod, for the average user you will not need to worry about that. The only proviso is if you have been specifically instructed to make cjanges to any scripts by this guide, I have not installed this guide, I don't even use the STEP Skyrim guide, so I'm not sure.

That 'unhandled exception' error has been noted by a few users lately and it is currently under examination by @fore. There is no apparent correlation between the user's systems as they don't all share the same OS or mod setup. I can't replicate it and I see no reason why that error would be generated based on the code in FNIS and MO that is being called. That isn't to say there isn't a correlation (bug), just that I can't find one.

The descriptions on the 'Downloads' page now reflect the fact that 1.2.18 is only needed for XP users and that it isn't the 'latest' version.

When you double-click on the PocoBuenoV5.fomod in the 'Downloads' tab do you get the small dialogue entitled: 'Quick Install'? If yes do you then press 'Manual' and are then presented with the 'Install Mods' dialogue? This is the dialogue that will say if the mod has: "No game data on top level." If not could you post your log from the 'logs' folder?

There's no problem with that. You are running 64bit Windows so the default application path is 'Program Files'. It's only when you install a 32bit application that it will be placed in the 'Program Files (x86).

JayzTwoCents is another good one I'm subscribed to.

According to that log FNIS is called and runs and the mods active in the "August" profile are there for use.

Saw that video earlier. I like LinusTechTips, I think I have the same sort of humour.

I'm not sure why this whole discussion got onto .NET frameworks, FNIS is a VB exe and the only .NET code in MO is to do with the fomod installer, there should be no issue with running FNIS in MO because of .NET. (Edit: To answer my own stupid question. .NET Framework is Microsoft's CLR, ie. 'Common Language Runtime' framework and as such it is needed to allow programmes created with a number of different languages, VB, C#, C++, etc. to use the same set of extra runtime code, thus removing the need to install separate packages for differing codebases.) So FNIS, a VB programme and MO's FOMOD installer both need to have the correct .NET version installed even though the main executable, MO, is a C++ programme. Please clear your MO 'logs' folder and then try again to run FNIS. Post the contents of that folder along with your modorganizer.ini. We need to know what is being called and how before we proceed. If this was an issue with .NET and FNIS via MO, 100's of users would have posted similar reports before.

This is not an issue with the program. All the executables will use the same set of mods that the current profile has been set for. If you have recently updated either your Steam client or verified your game cache try running the game from outside the MO environment first, just in case the registry needs a refresh. Without any diagnostic material (logs, inis, etc.) it will be hard to see what is not correct with your setup.