You don't need to diskpart during the install, the diskpart tool is triggered as part of the GUI when you can see all the partitions and delete / remove them as required.
I've not had a bloatware laptop in the last 5 years whose recovery partition doesn't show up. That partition tool is literally diskpart in gui format.All normal partitions yes, not necessarily recovery partitions put on there by OEMs.
UGH, I have a win10pro installation that is around 3 years old, and I'm regretting not squashing it and restarting the universe. Always takes over a day.
There are two things regarding this endeavor that I hate:
1. Figuring out where all the game storage is. Everything, even with Steam, seems to be craftily hidden in obtuse areas, or at least this was the case 3 years ago. I crock together a script to handle this, but the number of games I've given my kids is legion, and heaven help the stability of our universe if things go missing (lol).
2. Dealing with people insisting to me that Windows doesn't really slow down and it must be my fault. LOL. That weird stance has been going on forEVER. As a software engineer for 4 decades, I've seen windows from the very beginning and even pre 3.11WFW slowed down to a crawl over time. Contrast that with Linux, which never ever slows down, but comes with it's own set of legendary nightmares.
I'm looking for a gaming backup application that can help. Basically, bridge the gap between Epic/Steam/bla/bla/and bla/ delivery engines.
Any ideas?
What are you doing to your OS that needs this 6 monthly cycle of absolute faff (even with disk images considered)?
As mentioned before, I am running the same Windows install since Vista, just in-place upgraded with each new version and kept on top of monthly maintenance and file/registry cleanups of orphan data. Machine is as smooth as a fresh install still and as can be for a SATA SSD (20s cold boot to desktop etc).
What are you doing to your OS that needs this 6 monthly cycle of absolute faff (even with disk images considered)?
As mentioned before, I am running the same Windows install since Vista, just in-place upgraded with each new version and kept on top of monthly maintenance and file/registry cleanups of orphan data. Machine is as smooth as a fresh install still and as can be for a SATA SSD (20s cold boot to desktop etc).
There's no way a Windows install slows down noticeably these days with normal usage. Small drop offs on a stopwatch or specific benchmarks perhaps, but not to the degree you're describing.
As I've said before, get some disk imaging software, get EVERYTHING the way you want it, then every ~6 months you wipe and re-do from the image. No slowdown. Everything as you want it. If you miss a bit of software you re-do from the image, install said software, and re-make the image. Takes away so much pain!
As mentioned before, I am running the same Windows install since Vista, just in-place upgraded with each new version and kept on top of monthly maintenance and file/registry cleanups of orphan data. Machine is as smooth as a fresh install still and as can be for a SATA SSD (20s cold boot to desktop etc).
I'm one of those who used to reinstall Windows 95/98/ME (yes I used it) and XP every few months, but in all honesty from Windows 7 onward I haven't seen any point. From a real world perspective I can't tell any difference between a week old Windows 10 and one which is a year old, so long as it's a semi decent PC.I've been hearing that same "these days" statement for decades. The problem is, "these days" never arrives.
What programs do you use for cleaning up the files and reg. etc.?
I used to use ccleaner but then read bad reports of them bloating the app, doing some dodgy stuff or something....
You almost certainly know this already, but keep in mind that certain "upgrade in place"s are actually full re-installs in disguise.
Back when NT 5 was rebranded to Windows 2000 (~1998) and included versions for home use, there was no way for any part of the prior software to be saved properly. It was an entirely new code base, and even the registry structure was completely different. So if you upgraded in place from anything prior to and including WinME (GodhelpyouwiththatPOS) to anything Windows 2000 or later, you had a full reinstall, not an in-place upgrade.
That's interesting. I thought you were supposed to reinstall Windows when changing the MOBO/CPU.My previous Windows install lasted from the release of Windows 10 until the end of December last year. During thet time it saw two motherboards, three CPUS, and two GPUs (one AMD, one NVidia). I only reinstalled when what was later diagnosed as a bad RAM slot started causing BSODS and corrupted everything. Windows is pretty resiliant to hardware changes these days.
Definitely not needed for CPU alone. Motherboard used to merit a reinstall but these days windows detects the new hardware and automatically restarts a few times to install the new drivers.That's interesting. I thought you were supposed to reinstall Windows when changing the MOBO/CPU.