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



Microsoft arbitrarily cripples legacy games that are functional, based on fake security concerns.
I myself had two incidents in which it bricked my hard drives with a specific update. Not a security update, but a special type of "preview" update. The first time this happened, I thought it was just my drive dying but the second time I knew it was Windows.
I learned pretty quickly that if I was going to create a dual-boot system, to install Windows first, then Linux. If I do it there other way around, the Windows installer would often break something, while the Linux installer was much more considerate for my Windows installs.
Today, I run Linux exclusively with intent to run Windows in a VM, and only when absolutely necessary. So far, it just hasn't been necessary.