Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
That is a typical writing error which happens either due to
a) permission issue
b) storage issue
c) hardware issue
most people who have had the same issue did not realise that they needed 70-100 GB of free space on C: for their Windows to run properly, leading to not enough space for additional savegames. That being written you should always check whether the issue resolves by giving the game higher permissions - aka run as admin - and run a checkdisk/CrystalDisk info to exclude hardware issues.
I tried running as admin but still the error appears. I Removed all my mods and re-installed the game again , with the mods that i backed up (since my saves has mods in em) but still failed to load.
The moment mods are involved, support of any kind cannot help - as the mod changes how the game behaves and sometimes even how the savegames are loaded. In fact, savegames which are affected by mods are outside any guarantee for them to work.
The only thing you can do are
a) consult the mod author(s) about the known issue
b) set your game back to vanilla state and check with an unmodded savegame if the error reoccurs
In general the 222 is a writing error as in the game cannot do the saving properly, leading to a corrupted and unusable savegame, which is only happening under the mentioned above circumstances
but as soon as mod are involves you can never tell if mod x,y,z, any of them is trying to write something into the savegame, which collides with something else. Most often that happens if savegames add items or enemies to your game which never existed before and alike.
When running mods I always strongly recommend to follow the general tips
https://steamcommunity.com/app/1086940/discussions/0/4696782945526623592/
If you forgot how to remove the mods completely you can use this before reinstalling the game to put your game back to vanilla state - however: once a savegame is affected it cannot be saved anymore
https://steamcommunity.com/sharedfiles/filedetails/?id=3165940575
only the mod author might know what is causing the file writing collision inside the savegame