GSDFan

This is explained in the WIKI under Third Party Programs. I hope this helps.

Destroying the world since 2012.

Running the game from outside MO uses the configuration files from My Games\falloutnv folder. When run from MO the files in the current profile are used. Since you can run the game external to MO, create a new profile so MO can copy those files to a new profile. Do not enable any mods. Go into the MO logs directory and delete any log there. Run the game from the new profile and if the same problem happens, post the contents of the newly created log files in a spoiler or to some other place so we can take a look at them.

You can disable the mods up to the point it worked, your UI mods, and see if it works. If it works start enabling mods in small blocks of say four and run the game. If it misbehaves then it is a matter of figuring out which one of the mods in the latest block is giving you the problem.

As a general rule of thumb please only post in one place, thanks. Edit; I sent a message to someone to lock one or the other.

Doesn't Chrome have lots processes running in the task manager just so it can be fast to start? I don't have it installed so I can't check this, but I seem to remember that.

GrantSP beat me to the bug report. I can also verify this, but I have noticed that this also happens with the “Overwrite Steam App ID†check box and edit field. The other two check boxes hold their states. I added this to the bug report.

That is because that file is the modified file and Steam will throw that error because it is not the original. Someone else used this argument and it worked for them, "-laaexe \FalloutnvMO.exe" Notice that the dot is gone and don't use the quotation marks.

Double click the mod and select the "Nexus Info" tab, Mod id is on the top left. You can change the mod is and Version there.

We have to resort to third party apps: Start10, the first Windows 10 Start menu alternative! Is a paid app. Start Menu X is a free with a paid option for more features. Classic Shell is a free alternative which is donation supported. Iobit Start menu 8 supports windows 10 and looks to be free. There are others also. I use Start10 and it allows you to choose between Windows 7, Modern style and Win 10 style and provides options to enhance your Windows experience.

@scorpgul Hi, in looking over your skyrimprefs.ini I see the following, iSize W=3840 and iSize H=2160. In your profile your display is as follows, BenQ XL2420T 120Hz 24inch 1920x1080 TN+. Have you tried to set your ini to 1920 x 1080?

And then there is this: Microsoft can disable your pirated games and illegal hardware | Alphr

Yes that will produce the message posted in the picture above and a similar log to the one posted above. Although we can't see past what is shown and there may be another install, that picture shows FNIS2, FNIS3 and patch unchecked. It is sorted by install date and not priority. The FNIS mods appear to be installed at priority 22 and 23.

FYI this is just for reference from a complete run of FNIS under Win 10 with MO 1.3.8. There should be more after the following lines: DEBUG (15:58:13.0264): hooks removed ----------- LOG END ----------- The next few lines from my successful run of FNIS show that it is working. See the spoiler: [spoiler=FNIS Working lines]DEBUG (05:22:33.0928): first access to FNIS Behavior V5_5 -- ALWAYS necessary-11811-5-5 DEBUG (05:22:33.0928): createfile w: D:\Steam\SteamApps\common\Skyrim\data\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exe -> D:\Steam\SteamApps\common\Skyrim\ModOrganizer\mods\FNIS Behavior V5_5 -- ALWAYS necessary-11811-5-5\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exe (80000000 - 3) = 0000069C (0) DEBUG (05:22:33.0928): createfile w: D:\Steam\SteamApps\common\Skyrim\data\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exe -> D:\Steam\SteamApps\common\Skyrim\ModOrganizer\mods\FNIS Behavior V5_5 -- ALWAYS necessary-11811-5-5\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exe (80000000 - 3) = 000006A0 (0) ................ More of the same here, just too much to post here. This is the end of the successful run: DEBUG (05:22:52.0121): add mod file D:\Steam\SteamApps\common\Skyrim\ModOrganizer\overwrite\\tools\GenerateFNIS_for_Users\FNISmodList.txt (tools\GenerateFNIS_for_Users\FNISmodList.txt) DEBUG (05:22:52.0124): findfirstfileex D:\Steam\SteamApps\common\Skyrim\data\tools\GenerateFNIS_for_Users\temporary_logs\*: . (10) DEBUG (05:22:52.0125): findfirstfileex D:\Steam\SteamApps\common\Skyrim\data\tools\GenerateFNIS_for_Users\temporary_logs\*: . (10) DEBUG (05:22:52.0127): findfirstfileex D:\Steam\SteamApps\common\Skyrim\data\meshes\actors\character\characters female\*: . (10) DEBUG (05:22:52.0128): findfirstfileex D:\Steam\SteamApps\common\Skyrim\data\meshes\actors\character\characters female\*: . (10) DEBUG (05:22:52.0129): findfirstfileex D:\Steam\SteamApps\common\Skyrim\data\meshes\actors\character\characters\*: . (10) DEBUG (05:22:52.0129): findfirstfileex D:\Steam\SteamApps\common\Skyrim\data\meshes\actors\character\characters\*: . (10) DEBUG (05:22:52.0130): findfirstfileex D:\Steam\SteamApps\common\Skyrim\data\meshes\actors\character\behaviors\*: . (10) DEBUG (05:22:52.0131): findfirstfileex D:\Steam\SteamApps\common\Skyrim\data\meshes\actors\character\behaviors\*: . (10) DEBUG (05:23:08.0308): remove mod file D:\Steam\SteamApps\common\Skyrim\data\tools\GenerateFNIS_for_Users\MyPatches.txt INFO (05:23:08.0308): deleting D:\Steam\SteamApps\common\Skyrim\data\tools\GenerateFNIS_for_Users\MyPatches.txt -> D:\Steam\SteamApps\common\Skyrim\ModOrganizer\mods\FNIS Output\tools\GenerateFNIS_for_Users\MyPatches.txt DEBUG (05:23:08.0309): add mod file D:\Steam\SteamApps\common\Skyrim\ModOrganizer\overwrite\\tools\GenerateFNIS_for_Users\MyPatches.txt (tools\GenerateFNIS_for_Users\MyPatches.txt) DEBUG (05:23:08.0317): hooks removed ----------- LOG END ----------- If we are going to use this as a troubleshooting aid we need to know what a successful log looks like. My guess is MO created the Log End after FNIS abruptly ended and MO can't determine the difference so we need to look at why the generator stopped. When you created the executable did you go to the data tab, click on the tools folder and right click GenerateFNISforUsers.exe and add as an executable or did you add it manually?

With the modified launcher you have to start the game from Steam. You should get a window with the option to run Fallout launcher, FOSE, Mod Organizer and exit the modified launcher. You can't run it from MO.

OK good to know. With the non-Steam version how do you launch the game then? From MO with obse_loader.exe shortcut or clicking the exe in the directory? I ask because I am trying to figure out if there is a circular hook going on if launched from MO. MO launching obse_loader.exe then obse_loader.exe launching stuff down the line then MO again via script extender setting. That may explain the double launcher problem.

I just found how to do this. Click in the search box and click on the notepad icon. Click on the settings option and turn Cortana off. A new option will appear to turn off online and web suggestions. When you do this the search box changes to "Search Windows" and when you click in the search box the gear icon appears on the left instead of the notebook icon.

I bet that it is something that will never be turned off completely as Bing is tightly woven into the OS. On my Win 10 if you click in the search bos and click the notebook icon I get access to a lot of quick switch settings. there is also a link to more advanced settings also.

All I did was right click the task bar to open the menu, went to Cortana and selected hidden. That big search box is no gone.

If that was your first run of MO than that is a random order. You should drag and drop them as outlined in the guide.

You say you have the non steam , retail, version of Oblivion. do the following, I don"t have this version so I can't test it: 1. Copy obse_1_2_416.dll, obse_editor_1_2.dll, obse_loader.exe and the Data folder to your Oblivion directory. This is usually in your Program Files folder, and should contain files called "Oblivion.exe" and "OblivionLauncher.exe". 2. MO Should be set to run as Mod Organizer as the load mechanism. 3. Run oblivion by running obse_loader.exe from the Oblivion directory as a shortcut in MO run section.

The proper way to use MO, Oblivion and OBSE is to set the “Launch Mechanism†in the workarounds tab to Script extender and Launch the game from Steam. This means that you mod in MO and run the game from Steam. You also need to enable the Steam community in game option in Steams Oblivion settings. If you try to run the game from the MO configured “OBSE†shortcut you will get the “You are trying to use a Steam version of Oblivion. Steam users should launch the game through Steam, not by running obse_loader.exe. If OBSE fails to load, go to Steam > Settings > In Game and check the box marked "Enable Steam community in game". Please see the instructions in obse_readme.txt for more information.†message and the loader will exit. If you run the shortcut “Oblivion launcher†the launcher will open as usual. If play is pressed it will close and open again and when play is pressed the game will start. If the MO configured shortcut “Oblivion†is run the configuration utility will open up and you can run the game from here. In all of the above situations you should not be running the game from here. Steam needs to be the mechanism to do this. My theory on this, whether right or wrong, is that Steam launches the game, then the "in game community" which in turn allows obse_1_2_416.dll and obse_steam_loader.dll to do their work. The file obse_loader.exe is not needed for the Steam version of the game. It is for the retail version of the game only and should be deleted. Running the game from Steam will allow the launcher to run first. At this point MO has not been loaded and if you view the Data files only the vanilla game directory will be seen. The launcher is reading the Oblivion.ini in the "My Games" folder and DLCList.txt and Plugins.txt from C:\Users\username\AppData\Local\Oblivion folder. Any changes made here will be written to those files and not the ones in the active MO profile. Pressing the play button will allow the game to start, which in turn launches the 'in game community" and then allow the OBSE_XXXX.dlls to load, which will load MO as a script extender from the games vanilla directory. MO should now be active and the VFS and all of the MO mods should be loaded.

Try running the game from steam once to set up the Windows registry so other programs can find the game.

I create a mod out of the overwrite folder after I install this and activate it and it does not reappear in the overwrite folder.

12a restart MO to make sure it writes its files to the games Data OBSE Plugins folder.