Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
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.