Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
I don't think anyone knows why.
Briefly, its install folder handling predates both Steam and Windows.
It doesn't play nice with them, and vice versa.
Hence Windows might introduce new conflicts beyond SE:V's 2006 scope:
- if your Steam root is your C:/
- if you use Windows OneDrive, or any other path-munging service
- if app uses a since-deprecated API to open folder (c.f. Stardock)
- other

The Windows Update tip makes some sense.If a (newer) Windows service quietly munges some filepaths to give SE:V the illusion
that it owns its own folder, but an Update disables that service, that can break paths until.
SE:V might be the oldest app you run on your PC this year. (Go launch SE:IV
That kills saves from prior to the change.