Discussion in 'other software & services' started by ronjor, Sep 30, 2014.
Never happened to me, but I don't double boot with any other OS.
Korben, it could resize your Win10 partition 500 MB smaller and create a RE partition in the 500 MB of Free Space. Or it might not do this at all if you have a MBR system with 4 primary partitions. It's no big deal. Your dual boot will not be affected.
Gentlemen, thank you!
Brian, I know you are the man when faced with these issues. You did help me to grasp Macrium ins n outs 4 years ago when I wasn't sure how to make the image.
Why am I not compelled to upgrade, then? I still have this itchy feeling something could go terribly wrong, just a hunch.
So you're saying I should be finding out right now the number of primary partitions?
korben, there is no need to worry. The chance of something going wrong is slim and even if something bad happens, just restore your Macrium backup image.
By the way, do you have a MBR or UEFI system? How many primary partitions are present on the system disk?
Windows 10 May 2020 Update is now rolling out to more users
June 10, 2020
ZDNet: Windows 10 2004 rollout: We're slowly throttling up availability, says Microsoft
Announcing Windows 10 Insider Preview Build 19645
June 10, 2020
What is the Windows 10 Windows Feature Experience Pack?
Once you get the May 2020 Windows 10 update, you also get this new pack, which Microsoft officials oddly won't discuss.
It looks like this and UEFI is mine.
I appreciate your time.
That looks fine. A Win10 upgrade might create an extra partition by resizing Win10 about 500 MB smaller. But no big deal. You won't notice the difference.
I am feeling reassured now, mate, for which I am grateful to you.
Build 10.240 is AOL soon right?
However, I have read so many bad words regarding the new versions that I still am in two minds about installing it. I mean I know my build is 5 years old and probably is much less secure than v 2004, but the only reason I am using it is games and that is 5x a week more or less. Is it worth the hassle?
Build 10240 is much faster and snappier than any build after it. That's like Windows 7 but with support for new Hardware. Way less crap, telemetry, and nuisances to deal with. I've tried every build and I can feel each build is just getting worse. Heck, even the latest Build 20H1 was supposed to be THE BUILD which will give us back the performance loss due to the Meltdown/Spectre patches, that's all BS. I feel no performance increase whatsoever.
The upgrade only takes 20 minutes on a fast computer. I've been pleased with each upgrade.
Folks, after the latest June 2020 update for Windows 10 20H1, when you guys use disk cleanup utility to clean up system files (this will include Windows update files), did you notice any change in OS disk usage before and after the cleanup is finished? There are folks saying that the disk cleanup utility still can not actually remove the Windows update files, but in my case, there is a ~2GB disk usage decrease after the disk cleanup, which appears to be a successful disk cleanup.
Could you guys please report the results on your computer?
Sometimes they get compressed to save space.Not sure how this is decided.I usually use Wise Disk Cleaner because disk cleanup is slow.
The same as always. Quite a few GB was removed by Disk Cleanup. On several computers I had more Free Space than before the upgrade.
After a fresh Win10 install you get 7 GB of Reserved Storage. 2004 has made it easy to remove this. Registry edit and Cumulative update aren't needed.
Hi Brian, the reserved storage upon a fresh install is new to me. Would you please share how to remove it?
After Update, Disk Cleanup offered me 2GB to remove, after running it, it actually cleaned around 1GB of data.
I don't use Disk Cleanup to remove previous versions of Windows anymore. I get better results using Storage Sense.
Reserved Storage is dangerous if you resize the partition into the Reserved Storage...
Say the Win10 partition is 21 GB with 9 GB of Free Space. You now enable Reserved Storage so you have 2 GB of Free Space. Windows sees 2 GB of Free Space but BIU, Linux, Gparted and Macrium Boot Disk still see 9 GB of Free Space and these apps will let you resize the partition into the Reserved Storage.
Let's say you resize the partition to 16 GB. The partitioning app shows 4 GB of Free Space. But when you try to boot Win10 you get a BSOD and that's it. Win10 can't be repaired. Resizing the partition to 21 GB doesn't help.
I got above 4GB of more space by removing old patch installation files in dir c:\Windows\Installer. But be very careful what you are removing, I removed ONLY files older than two years. MS doesn't recommend deleting any files there but I for one can say that with a certain degree of safety I am keeping 2 years old files without impacting my machine.
You can use PatchCleaner to cleanup Installer folder without worry. It will delete (or move to other location if you want so) only installers that are not registered any more. It usually saves me few GB of space on system partition.
Thank you guys/gals for sharing tips and tricks on how to optimize Windows 10 install - very much appreciate them all.
I always try to trim Windows as lean as possible after a fresh install and customize settings to my like, before I take an offline disk image. It appears this time I can gain at least a few more GB of disk space than using my previous routine, thanks to your tips.
Thanks for your test. This should be normal - my desktop is currently on Windows 10 LTSC 2019, and I noticed that the reported size of Windows update files could be different from the actual amount of space gained after cleanup. For Windows 10 2004 this discrepancy should be normal as well.
Just a couple of points regarding disk cleanup after updates.
There is a reason why Storage Sense (if you have it turned on) deletes unneeded files only after 30 days have passed. In some cases, certain things (apps/libraries) need to be compiled on users' machines after the upgrade is finished. This is especially true for .NET related updates, and they do come with cumulatives from time to time. The compilation does not begin immediately after the update but is instead triggered by a scheduled task.
Another thing to look out for is Windows Modules Installer process/service which sometimes runs after an update (it is triggered by the idle system state, and may not run for days if the system is busy). It does a similar thing as NET scheduled task, but for Windows components. By it's own description -
These are some of the reasons for updates not always being flagged immediately for deletion after the upgrade is finished and neither the old Disk Cleanup nor the Metro Storage can yet see them. Not until complation processes are complete, that is.
So even though what can and cannot be deleted is supposed to be managed by DiskCleanup/StorageSense, the process is not that straighforward and I'd still advise against a cleanup immediately post upgrade. Better to wait for a couple of days, especially after a feature upgrade.
Separate names with a comma.