Why Windows 10 Sucks or Everything Wrong with Microsoft Windows
Some of the author&#x27;s points are right, however in my opinion a lot of them are wrong, and seem to be coming from the perspective of &quot;it&#x27;s not linux so it sucks&quot;<p>&gt;The user as a system administrator (thus viruses&#x2F; malware - most users don&#x27;t and won&#x27;t understand UAC warnings).<p>How is this different from sudo?<p>&gt;No good packaging mechanism (MSI is way too fragile).<p>In all of my years using windows I&#x27;ve had msi fail only a handful of times.<p>&gt;No system-wide update mechanism (which includes third party software - to be fair there are third party applications which offer this functionality, but then such applications don&#x27;t support core Windows updates).<p>Microsoft update will update some third party software, like flash. There is so much software on windows that a centralized update system isn&#x27;t really tractable.<p>&gt;In certain cases it&#x27;s extremely difficult to find or update drivers for your hardware devices (anyone who&#x27;s tried to install a fresh Windows onto their laptop will testify).<p>Problem with the oem, not with windows. It&#x27;s up to the hw manufacturer to publish drivers in easy to find places.<p>&gt;Windows is extremely difficult to debug (e.g. try finding out why your system is slow to boot).<p>While not as easy as debugging with source Microsoft provides debug symbols for all major kernel components. This makes getting a kernel stack trace and examining structures very easy.<p>&gt;Windows boot problems are too often fatal and unsolvable unless you reinstall from scratch.<p>Only if you don&#x27;t know the correct utilities to use. Most boot issues can be fixed with a combination of bcdboot, bcdedit, and repairing the dism image. On the rare occasion that those don&#x27;t work you can go even deeper with a kernel debugger.<p>&gt;The Windows OS installer doesn&#x27;t give a damn about other OSes installed on your PC and it always overwrites the MBR. In case of already existing Windows installations, it sets the newly installed Windows as the default OS - no questions asked. In case of UEFI, booting of other non-Windows OSes is unsupported and Windows actively prevents this.<p>This was true back when MBR was used. It is now extremely difficult to use MBR with windows, and almost all other OSs support UEFI by this point. Saying booting of other non-Windows OSs is just wrong. This person&#x27;s source is a technet post, which you can consider the microsoft equivelant to stack overflow. The accepted answer is from a community moderator. In my experience if it&#x27;s not a Microsoft employee replying, then there&#x27;s a 90% chance that the answer is wrong. Windows does not wipe out any other UEFI boot application binaries or the boot nvar entires. It just adds its own binaries, adds a nvar boot entry, then set&#x27;s that entry as the default. Hitting your boot menu key when you boot will allow you to select any of the other entries, and your firmware setup utility will allow you to change the order in which they boot.<p>&gt;Windows anti-virus products oftentimes make your PC less safe - so if you want perfect security and privacy, stop using Windows and migrate to Linux right away. OEM updaters make your PC wide open for attacks.<p>For most power users, it&#x27;s true. AV products do increase your attack surface for only a small benefit. However, in a corporate enviornment with less tech savy users, they are extemely needed. People will just click whatever links and download and run anything.<p>&gt;Microsoft has recently decided that you will no longer be able to download certain Windows updates manually. You&#x27;ll only be able to get them via Windows Update.<p>That is 100% not what they&#x27;re saying. They&#x27;re just saying they used to publish the update files to two places, and now they&#x27;re going to reduce redundancy and only publish them to one, the update catalog. You can visit the update catalog in a browser and still download all of the updates.<p>&gt;&quot;sfc &#x2F;scannow&quot; is offered as a solution to most Windows Update Service and Microsoft Installer Service errors, yet in absolute most cases it&#x27;s totally ineffective.<p>This is commonly offered as a solution on community forums, but I rarely see it offered as a solution on official Microsoft documentation.<p>&gt;Windows does not automatically clean temporary files ever, however it must do that for every reboot&#x2F;power cycle - partially solved in Windows 10 1809.<p>This seems like personal preference to me. I&#x27;d rather keep %TEMP% around and only clean it out with cleanmgr when needed. Several browsers store their cache in %TEMP% and I&#x27;d rather not have that wiped out across reboots.<p>&gt;Windows keeps a large number of databases of the applications which the user runs: Windows Activity History, bam.sys, Prefetcher, Program Compatibility Assistant and others.<p>The only one you should be upset about is Windows Activity History. BAM is used to help determine when the machine is idle and background maintenance tasks can be performed without impacting the user. The prefetcher is used to speed up the initial start of applications. The compatibility assistant is used to help increase backwards compatibility with older software.<p>&gt;Safe Mode has become impossible to access unless you&#x27;ve booted into ... the running OS, which totally defeats its purpose. Also Safe Mode is hidden behind almost a dozen of steps vs. a single F8 key press on boot in every Windows version from 95 to 7.<p>True that they&#x27;ve made it much harder to access by default which I think is the wrong move. If you reset the computer while windows is in the middle of booting several times you&#x27;ll be brought to a recovery menu which will let you boot into safe mode.