I like Windows 10. But I don\u2019t like getting stuck in eternal reboot hell.For days now, one of my Windows 10 Anniversary Update PCs has been relentlessly rebooting and rebooting and \u2026 well, you get the idea. I\u2019m not alone. This Sisyphean cycle is plaguing many other people.Patches were welcome. After all, the Windows 10 Anniversary Update, a.k.a. Windows 10 SP1, came with a host of problems. There were unexplained freezes, Cortana was fouled up, webcams were broken and multiple third-party applications were turned into messes.And even mandatory, you-have-no-choice-and-don\u2019t-even-have-to-think patches seemed wise. Most people can\u2019t be trusted to pick a password that\u2019s not \u201cpassword,\u201d never mind patch their systems.But then came the first cumulative upgrade to Windows 10 SP1. Oh, it was a stinker! Not only did build 14393.82, not fix some of the earlier problems; it managed to blow up other things, such as PowerShell Desired State Configuration (DSC). If you\u2019re Joe User, you don\u2019t know what I\u2019m talking about. If you\u2019re Josephine Sysadmin, DSC\u00a0is probably what you use for jobs such as setting up all your users\u2019 systems. You know, the little stuff.When I championed automatic patching, I assumed two things. First, I imagined that it would target consumer PCs, leaving system administrators some control over updates. Nope. Ancient history. Now you get all the patches in a \u201ccumulative update.\u201d Don\u2019t want the patch that breaks your mission-critical widget? Too bad, too sad. Worse still for small businesses, Windows 10 shoves automatic updates down your throat. You can\u2019t stop the patches. Ever. Unless \u2014 I\u2019ll explain more about this in a minute \u2014 you forgo patches for a year.Second, I had really hoped that, since Microsoft was making patching mandatory, its patch quality assurance would go up. Ah, foolish me. Even now, I\u2019m watching my busted Windows 10 PC working on its fifth \u2014 or is it the sixth? \u2014 attempt to update itself.I really should have known better, given Microsoft\u2019s lousy record with its Windows updates. Anyone else remember the Jet Database patch, which bricked Windows 2000? The .Net SP that knocked out Quicken in 2008? Right before tax season? Or, my all-time favorite, the time Microsoft issued six \u2014 count \u2019em, six! \u2014 bad patches at once.So what can you do about this? Well, you can set your PC from the consumer-level \u201cCurrent Branch\u201d (CB) to the enterprise-oriented \u201cCurrent Branch for Business\u201d (CBB) upgrade track. With CBB, you can delay any \u201cupgrade\u201d from reaching your system for 12 months from when it was first released. Of course, if there\u2019s is a serious security patch in there, you\u2019re screwed. But at least hackers will have a working computer to mess around with. That\u2019s not what you want, although I would take it over what I have now: a useless PC displaying a screen message that says, \u201cWorking on updates 13%.\u201dAnd what is Microsoft doing about the unmitigated disaster that Windows 10 cumulative updates have been? Why, starting this month, it will require Windows 7 and 8.1 users to install all patches as well. To quote Susan Bradley, Windows patching expert, \u201cBottom line, everyone is holding their breath, hoping for the best, expecting the worst.\u201dAfter what I\u2019ve seen with Windows 10 patches, I know what to expect. Now are you ready to join me on a nice Chromebook or the Linux Mint 18 desktop?