Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
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.