{"id":1103,"date":"2018-12-19T22:15:51","date_gmt":"2018-12-20T03:15:51","guid":{"rendered":"http:\/\/www.both.org\/?p=1103"},"modified":"2024-04-20T06:49:03","modified_gmt":"2024-04-20T10:49:03","slug":"why-i-hate-windoze","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=1103","title":{"rendered":"Why I Hate Windoze"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n 1 <\/span>\r\n<\/div><\/div>\n

Well – one reason anyway.<\/strong><\/p>\n\n\n\n

I use a virtual Machine (VM) with Windows 10 installed for research on a new book I am writing. I started that VM this afternoon to do some testing and took a few screen shots to include in that book. After I finished up with that, I was going to shut down the VM but then this – the Blue Screen of Updates.<\/p>\n\n\n\n

\"\"<\/a>
Windoze Blue Screen of Updates<\/figcaption><\/figure>\n\n\n\n

This has been going on for hours, now, despite the fact that this VM has assigned to it 8 CPUs (4 Cores) of the 32 CPUs (16 cores) and about 24GB of RAM of the 64GB that I have on the physical host. Here is what that looks like in htop.<\/p>\n\n\n\n

PID    USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command\n\n22254 dboth      20   0 26.3G 23.7G 23.5G S 13.1 37.9  4h32:53 \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 08219ab\n22422 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  1:41.72 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22304 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:00.16 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22302 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  1:52.65 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22301 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:00.10 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22300 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:00.02 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22299 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:00.00 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22298 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:33.08 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22297 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:00.73 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22296 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  1:54.59 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22295 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  1:43.01 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22294 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:00.32 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22293 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:00.39 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22292 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:00.00 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22291 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:00.00 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22290 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:01.40 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n22289 dboth      20   0 26.3G 23.7G 23.5G S  0.0 37.9  0:30.35 \u2502  \u2502  \u251c\u2500 \/usr\/lib\/virtualbox\/VirtualBoxVM --comment Win10 --startvm 0821\n<SNIP><\/code><\/pre>\n\n\n\n
These lines copied from htop<\/strong> show that the Win10 VM has been running for hours and taking over 26GB of RAM. This includes what I assigned plus the VirtualBox overhead. But that is huge in terms of both RAM and CPU time. Updates to a Linux system never, ever take that much system resource or real-world time.\u00a0<\/p>\n\n\n\n
Meanwhile, the virtual machine is of no use to me as I cannot do anything on it until the updates and multiple reboots are completed.  Not to mention the fact that I had no choice about when this happened. It just started and did not give me an opportunity to opt-out. <\/p>\n\n\n\n
On Linux I can work while the updates are being installed, and I don’t have to reboot until I am ready. Only one reboot is ever needed to install updates and I can choose when I want the updates to be installed and then, separately, when I want to reboot my Linux computer.<\/p>\n\n\n\n
To make this even more disturbing, after it finally rebooted for the umptieth time — or so I thought — I logged in and it had the audacity to display in the screen, “Hi. We have some updates to install,” or something to that effect. <\/p>\n\n\n\n
Some of my friends wonder why I don’t use Windows. This is one reason. <\/p>\n","protected":false},"excerpt":{"rendered":"
I was working with a VM this afternoon that has WInblowz 10 installed to do some testing for a book and took a few screen shots to include in that book. After I finished up with that, I was going to shut down the VM but then – the Blue Screen of Updates that lasted forever.<\/p>\n","protected":false},"author":2,"featured_media":2571,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[5,28],"tags":[],"class_list":["post-1103","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux","category-opinion"],"modified_by":"David Both","_links":{"self":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/1103","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1103"}],"version-history":[{"count":20,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/1103\/revisions"}],"predecessor-version":[{"id":5017,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/1103\/revisions\/5017"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/media\/2571"}],"wp:attachment":[{"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1103"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1103"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}