I'm in a bit of a bind because I've handed over my PC to a technician, and I need to know what will happen to all my files, especially the ones on my desktop, when they install Windows on a new SSD. I've been having issues with my PC after a Windows 11 update, and now I'm worried. The technician mentioned that my old C: drive will remain untouched, but I'm really anxious about my Downloads, Desktop, and Documents. If they install the OS on this new SSD, will all those files from my current C: drive stay intact? Or am I at risk of losing everything? I know I should have backed things up properly, but it's urgent now, and I'm hoping someone can clarify this for me!
3 Answers
Doing a clean install means it wipes everything if you're using the same drive. But since you're using a new SSD, your old C: drive—and everything on it—will stay just as it is. If you want to access your Downloads and Desktop later, they should still be there. Just remember to avoid the option that says "remove everything" if you ever reset your PC in the future. Keep your fingers crossed that the tech sticks to his word about not touching the C: drive!
If you're installing Windows on a brand new SSD, your files on the old C: drive should remain safe and untouched. The important thing is that you're installing the OS on a different drive, so nothing will be deleted. Just be careful if you ever consider installing on the same drive—that's when you risk losing everything! It's a good idea to always keep backups, though, just in case.
If you're really worried, you may want to consider cloning your old SSD to the new one before the install. This way, nothing gets lost in the process, and you have a full copy of everything just in case. Hard drive cloning software can help you with that, and it often comes with new drives. But as it stands, you really should be okay just going for the fresh install on the new SSD!

Exactly! Just follow your technician's advice, and you should be good to go. Always a good idea to have a backup plan for future installs, though!