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
You can move games between Windows installs and systems without any issues.
Copy the entire Steamapps folder, that way you will grab both the games and the appmanifests.
Beyond that, everything else can come over intact, including your games and anything else like pics and music.
Fair enough.
It is true that a previous Windows install may not allow the change of the motherboard and CPU without requiring it to be reformatted. so its always best to backup anything you want to keep either on a secondary drive or a USB stick. You will know if this is the case if when you try to enter Windows all you get is a blue screen.
If you have a secondary drive for games and storage you could just have the games installed to that drive instead of moving them back to the OS drive or SSD if thats the case. Many games are perfectly fine on an HDD and only a select number of games are best on an SSD.
Also keep in mind that if you do have to reinstall Windows chances are you'll lose many of your game saves, Steam Cloud isnt 100% in restoring your saves. So unless you have already started, using Game Save Manager would be a good idea just in case.
As there wasnt a lot of information to go on, i merely stated a few different situations.
No Steam games are not prone to corruption. No data is "prone to curruption" when copied, if stuff is corrupting when you copy it you likely have deffective hardware in your machine.
You are aware that on a default Windows install the system partition holds ALL your personal data and programs right? You should wipe the entire drive to make sure the Windows installer doesn't mess up the partitioning of the drive, and there is not reason to save the bootloader etc.. anyway when reinstalling Windows.
"A well timed VIGF"? A what?
All this stuff you are recomending doesn't make any sense. And even if OP followed your "advice" he would still end up wiping his entire drive and has to move his games over to a external drive anyway.
Most game files are of course compressed or encoded, making them more prone to "whole-file corruption" than regular text files. Nonetheless, your point is taken, no file is on its own more likely to become corrupted than another, however when a program such as Steam is managing the files the chance of corruption increases simply due to the added complexity of the process and the added actions being performed on the data.
I've moved many Steam game folders between different computers, and every single time I've had to VIGF (Verify Integrity of Game Files) a couple of games (but not all) afterwards. Possibly this is due to some Steam process changing or updating the files while they are being copied, as I tend to be somewhat reckless with which programs I leave running while copying/moving.
Yes, I am aware that Windows defaults to a silly partition table when installing. However, I'd challenge you to find a techie recommending that you put all your files in the System partition. I will not be held accountable for Microsoft's poorly chosen default settings. On the other hand, through the thousands of Windows installs I performed for students while working at a high school, I've never once experienced the Windows installer bungling up the partiton table (no, we were of course not using the Windows default single-partition setup). I'd like to see a reference for that, as I've only ever seen it when installing very obscure operating systems like ReactOS. There are also conceivable reasons for wanting to save the bootloader, such as having a dual-boot configuration or custom bootloader installed (I ran Windows XP on GRUB after struggling with getting the Windows bootloader to load from an early PCI-e SSD).
The only hardware defect in this computer is that the lights on the RAM stick in slot DIMM_A2 sometimes desync from the other lights when the computer is locked (or more accurately, when user mode drivers such as the ones used by iCUE/AURA cannot run, or if said drivers are forcefully killed). There are certainly no drive defects, and I can provide SMART data to back this up.
I rarely have to do a file iintegrity check when moving them between Windows installs and PCs.
The very fact that WIndows doesn't let you manually partition the drive and mount the file system is the issue. The only OS I have had issues with it messing up the partition table is Solus, need to format the drive after installing Solus before I can repartition it. I also have my system partition and the home partition seperated on my Arch and OpenSUSE installs, I would prefer to be able to do something similar with Windows as well.
But I don't keep any important data on the PC period. I don't have any really important data at all, my PC can explode and the cloud can catch fire, I can live without this stuff.
I don't see how a problem that is admittedly specific to Solus is applicable to a question about Windows.