![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Fully concur with toaderz observations. Windows 10 computers are marketed and sold as consumer products. They should not require endless tweaking and testing. Users should be able to use them.
I've observed a pattern when I encounter a glitch. For every glitch there a few dozen Web pages, many branded with the Windows name or logo. Each site typically offers multiple different solutions, which appear to work only for the person submitting the solution, and perhaps one of two other fortunates. Most of them are frankly Greek to me, demanding a familiarity and understanding of the inner workings of Windows that only those who work at that level of detail on a day to day basis have. Their technical expertise is orders of magnitude greater than mine.
I take great comfort in observing that in terms of being able to reach a consensus on a solution that actually works for more than a day or three, they don't have much better luck than I do.
The bottom line is that 20 GBytes is a ridiculous size for an "operating system" by most accepted definitions of the term. And it shows in the performance of basic tasks, like disc management.