I apologize if this has been discussed before, I did a fairly extensive search, and found nothing.
As the title says, after installing TTW, all the MO2 folders (from the root on down) are set to read-only, meaning I get this error message every time I attempt to launch the game :
failed to set archive key in ......../fallout.ini (errorcode 0)
I can circumvent this by opening explorer and removing the 'Read Only' attribute form the folder and all its sub-directories, and keeping the folder open while running the game. The problem is, when I close MO2 (and the folder), the read-only attribute is reset, meaning I have to do this every single time I want to launch the game.
Maybe this is a 'first world problem', but it is annoying and I was wondering if anyone has experienced this.
This also means that saves are not saved, unless I uncheck the 'use profile specific game saves' and save directly to the my documents folder, which is not horrible I guess, but it is not expected behavior.
I have used (and presently use) MO2 to manage all my other Bethesda Games (FO4, Skyrim SE, oblivion, and prior to the installation of TTW, FNV and FO3). I have never had this happen with any previous games or installs, which is why I am inquiring about this here, and not on the MO2 forums.
My MO2 installations are as such, if it matters:
G:/
<root directory>
_Mod Organizer 2 - SKYRIM SE
_Mod Organizer 2 - FALLOUT 4
_Mod Organizer 2 - TTW
SteamLibrary (where all above games are installed)
I also have MO2 set to run as administrator.
Has anyone else experienced this odd behavior?
The forum has been set to read-only mode. For community discussion and questions, head over to our Discord: https://discord.taleoftwowastelands.com
MO2 makes everything 'Read Only'
- comatosedragon
- Posts: 22
- Joined: Thu Jan 03, 2019 1:58 pm
Re: MO2 makes everything 'Read Only'
<<<Moderator, Please Feel Free to Lock or Delete This Thread>>>
I feel like such a tool. I had not restarted my PC for several days, and upon restarting, there was a pending windows Update, which apparently fixed this problem (...Somehow. Windows is a strange beast sometimes...)
To be clear, the folders are no longer set as read-only, and I no longer receive the error message.
Please forgive my ignorance, and forgive me for bloating up the forum with a useless thread.
I feel like such a tool. I had not restarted my PC for several days, and upon restarting, there was a pending windows Update, which apparently fixed this problem (...Somehow. Windows is a strange beast sometimes...)
To be clear, the folders are no longer set as read-only, and I no longer receive the error message.
Please forgive my ignorance, and forgive me for bloating up the forum with a useless thread.
- RoyBatty
- Gary
- Posts: 7742
- Joined: Sun Apr 27, 2014 10:26 am
- Location: Vault 108
Re: MO2 makes everything 'Read Only'
Also the NV launcher sets Fallout.ini read only for whatever unknown reason, I think MO2 doesn't like that very much.
