Jump to content
  • 0

Failed to write settings (errorcode 161)


MaximilianPs

Question

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.

Link to comment
Share on other sites

10 answers to this question

Recommended Posts

  • 0

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

 

There is also another pop-up message

 

SQ1MErU.png

 

Substantially it say that:

Impossibile to copy file. Unexpected error. 

Insufficient system resources to complete the requested service

Edited by MaximilianPs
Link to comment
Share on other sites

  • 0

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.

Link to comment
Share on other sites

  • 0

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 by MaximilianPs
Link to comment
Share on other sites

  • 0

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

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.