bug Failed to write settings (errorcode 161)

[MaximilianPs]

Every time that I quit Skyrim, MO2 (2.0.8.3b) stop to works and I get this error:

 

"An Error occured trying to update MO settings to G:/Steam/...../ModOrganizer/ModOrganizer.ini: Invalid Path (errorcode 161)"

 

Quit MO2, and restart the application solve the problem until the next time when I run SkyrimSE and I quit it.

[GrantSP]

Can you please post the full pathname. Errorcode 161, and the message itself, refer to an invalid pathname.

You might also try and check to see that the path you are expecting to see actually is correct.

[MaximilianPs]

Full path is G:\Steam\steamapps\common\Skyrim Special Edition Tools\ModOrganizer\

 

There is also another pop-up message

 

 

Substantially it say that:

Impossibile to copy file. Unexpected error. 

Insufficient system resources to complete the requested service

Edited September 15, 2017 by MaximilianPs

[GrantSP]

Have you ever been able to run MO2 from that address?

I'd suggest moving it out of the Steam path and into a folder of its own, e.g. G:\Tools\MO2\ or even G:\MO2\

 

Also if you are currently on Win10 you may have the issue the Creator update introduced and therefore you will have to wait for the Windows update that fixes it. There is one in the pipelines at the moment.

[MaximilianPs]

Ok I'll move it on a different drive too. and in a Root folder.

In the meantime I've got a different error too (lol)

Fail-fast exception.

A fail fast exception handlers will not be evoked and the process will be terminated immediately.

 

[GrantSP]

hmm... I think there may be underlying issues here with your system. Never seen a 'fast-exit exception' error with regard to MO/MO2 before so I can't give you any specifics on why that occurred.

 

Has MO2 ever worked on your machine?

[MaximilianPs]

Yep, and still working fine, but I can run Skyrim just one time, once I quit the game MO2 start issuing, and I need to quit it.
I'll do another test, by moving it on a different drive. Maybe it's the SSD, or maybe I should try to install MO2 from scratch.

Edited September 16, 2017 by MaximilianPs

[Greg]

I think what you are describing might be a known issue with Mod Organizer 2. It seems Mod Organizer 2 is in a bad state after exiting the game so the workaround is to restart Mod Organizer 2 after exiting the game. I seem to remember LePresidente posted some information about this and asked if any C++ developers could help fix this issue.

 

Mod Organizer 2 crash due to running out of Memory after closing Fallout 4

0x800705aa exceptions

0xC0000005 exception after writing to file via usvfs_x64 with xEdit

[MaximilianPs]

Mod Organizer 2 crash due to running out of Memory after closing ... Skyrim Special Edition   
Exactly !

[easyrider1988]

Same issue here but only if I run the game via skse64 loader (SKSE64 2.0.0 / 2.0.1).

[MaximilianPs]

Confirm, that the issue is SKSE64!