Please see screenshot below. Don't ask me to buy a new HD, or turn off Hibernate. I MUSTN'T delete Adobe Acrobat, Illustrator, Photoshop; Microsoft Office; Nuance NaturallySpeaking; or Steam.
View attachment 5664
1) Redirect the following directories to another drive or secondary partition:
Desktop
Documents
Downloads
Pictutes
Music
Video
You should NEVER mix OS and Data in the same partition. Always keep them separate.
Use Macrium Reflect to create an image of the OS Partition. That way you have an image that contains all your installed Programs and Applications, so when (no IF's here. There will come a time when a Microsoft Windows Update will fk up something in Windows) Microsoft pushes out a bad Update, it only takes five minutes to reimage your OS Partition and you won't need to re-install Windows.
Same if you get a virus or Malware , etc.
No stress or worries about your system getting hosed because all you need to do is reimage the last good OS Partition.
PS. Here is some encouragement for you to follow my advise I posted prior. In Win10 I've been having major issues with the WinSxS and Inflight directories increasing in size daily almost exponentially for over a week. I had to jump thru some hoops to delete the 100MB Reserved partition between my C Partition and my D Partition in order to increase the size of the OS Partition before the free space got so low the system would not function......Let me digress for a bit to present some technical information that some or none of you may be aware of and may help in understanding the issues I was having and how I drilled down to the root cause and what I did to fix the 8 day long problem.
As a matter of reference, an NTFS partition can ONLY be expanded to the RIGHT, expanding to the left is not possible. So I deleted the small reserved partition between C & D, then expanded the C (OS) Drive partition to include the space where the reserved partition was. That then enabled me to expand the OS partition even more, "stealing" 20 GB's from the D (Data) Drive partition. I knew going in this would only be a temporary expansion as the OS partition continued its growth at breakneck speed. Thru the entire 8 days if this crap, in a spreadsheet I documented the sizes of the most important directories, including: Windows, WinSxS, Inflight, all three Programxxx directories, system 32, SysWow64, Servicing, Installer, and lastly the Users\%username% directory. After five days I was able to eliminate all three Programxxx directories, system32, SysWow64, and the Installer directory, thus leaving Windows, WinSxS, Inflight, and my user directory. Elimination of the former was a no brainier as they all had static sizes that didn't fluctuate.
During this entire duration of this issue, I consistently ran sfc/scannow, and several DISM command lines I had included in a cmd batch file. It became apparent that every time I ran this script, the Windows directory increased in size... albeit miniscule compared to the size increases of the WinSxS and Inflight directories. In my troubleshooting I began subtracting the size of Inflight from WinSxS. I discovered that the actual size of the WinSxS directory was actually static and it was the Inflight Directory that was the culpret. Keep in mind I disabled any and all updates and actually had the network cable disconnected.
After some research the general consensus was that it was not good practice to delete the WinSxS or any of its sub directories. At this point I didn't care. Besides I had a solid OS image from a few days prior to when this all began that would be my saving grace. I booted my system with the Reflect Emergency PE USB device and vegan deleting the contents of the Inflight directory, which was at this point 32GB's in size and growing. I knew that at some point of the deletions, it would come to a grinding halt due to Win Security that is damn near impossible to circumvent. I shut off the system and slept on it. In the morning I tried a DISM script that was suppossed to force a Component Cleanup but didn't do squat. So.... With knowledge gained from 30 years in upper level IT and years of dealing with oddball issues, I went into Task Manager and perused down the list until I came to a Servicing task. I knew that this Task was the one who is suppossed to keep the very problem I was having, from occurring. Turns out, even though in a Ready state, it had not ran for over two weeks. And after deeper investigation I concluded that for whatever reason, either MS Update KB5015730, Cumulative Update Preview for .Net Framework 3.5 and 4.8 for Win10 OR MS Update KB5015878, Cumulative Update for Win10 21H2, had hosed the Servicing Task, effectively preventing it to run as designed resulting in the exponential growth of the In Flight directory. At any rate I forced it to run by manually engaging the Task Start. It ran for a little over 40 mins at which time I rebooted and documented the directory sizes. Much to my sheer happiness, the sizes of the Windows, WinSxS, and Inflight folders had returned to the Pre-problem levels. Windows dropped from 51.6GB to 19.6GB. WinSxS dropped from 40.4GB to 8GB. And the main problem child, Inflight, dropped from 42.7GB down to 30.7MB!!!! Overall the used space on the OS Partition dropped from 71.5GB down to 37.8GB.The free space increased from 18.8GB up to 33.7GB. All sizes had returned to exactly what the average sizes have been for close to 18 months.
You may think and wonder why I wasted my time screwing around with an issue that could have been resolved in five minutes had I reimaged the OS Partition with a good, clean image created prior to the two MS Win10 Updates which I am throughly convinced were the bad Updates pushed out from MS. Simple answer is that, I have always taken on a seemingly hopeless path of discovery, through logical troubleshooting methods and knowledge gained over the decades. Since I retired from my IT career years ago, it has given me the time to literally jump into the Windows OS to learn anything and everything I can about how it functions and how there is always a path processes follow thru many different divergent rehlms of technology to arrive at the expected outcome. When that outcome encounters a bottleneck, or corruption, or even a complete showstopper, it becomes my focus to rectify the problem and make it all flow again.
.......Now, to pick up back where I diverged, after a couple of days of regular use, I felt there were lingering issues or fallout from all of it. I did reimage the OS, but being very aware that one or both of the two aforementioned MS Updates would once again attempt to Update my system. After some searching I discovered a MS utility that states it will stop all updates or only ones of your choosing. The name of this utility is, "showORhide_Updates_wushowhide.diagcab." It's Digital Signature is from Microsoft Corporation, with a Timestamp of June 24, 2021 8:15:06 AM.
I cannot state at this point if it actually works. It is a util that cannot be run until there are Updates in the process of downloading, otherwise it can't see what's not there. I was on the ready when I unpaused WU and saw that the two previous troublemaking Updates were in fact being downloaded. However, and for reason (s) I can't explain, all of the updates downloaded 100%, with one proceeding to install, with no recourse to stop it. So I quickly ran "sc config wuauserv start=disabled & SC stop wuauserv", effectively stopping and disabling the Windows Update service. This is where i am currently at. I stopped to take a break and ended up composing a tech diatribe.... Stay tuned in the next couple of days and I'll update you on what I find. Until then, A hui hou,
PhotoGeek