{"id":13546,"date":"2018-10-10T02:30:10","date_gmt":"2018-10-10T10:30:10","guid":{"rendered":"https:\/\/www.palada.net\/index.php\/2018\/10\/10\/news-7313\/"},"modified":"2018-10-10T02:30:10","modified_gmt":"2018-10-10T10:30:10","slug":"news-7313","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2018\/10\/10\/news-7313\/","title":{"rendered":"What the heck is it with Windows updates?"},"content":{"rendered":"

<\/p>\n

Credit to Author: Steven J. Vaughan-Nichols| Date: Wed, 10 Oct 2018 03:00:00 -0700<\/strong><\/p>\n

To help make life better for you, my loyal readers, I suffer by running Windows 7 and 10 on two harmless \u2014 never hurt anyone in their lives \u2014 PCs. Well, I did. But, in the last week I ran into not one, but two, showstopper update bugs.<\/p>\n

First, on Windows 10, I was one of those \u201clucky\u201d people who had files vaporize when I \u201cupdated\u201d to Windows 10 October 2018 Update (version 1809). Because I only use Windows for trivial tasks, I didn\u2019t lose anything valuable when the patch decided to erase everything in the My Documents folder.<\/p>\n

Somehow, I think most Windows users use Windows for more important work than I do. I hope you have current backups. At least Computerworld<\/em>\u2019s Woody Leonhard has some good news: You can get those deleted files back<\/a>.<\/p>\n

The story, Microsoft now admits, is that the 1809 release erases, for some people, all files in the Documents, Pictures, Music, and Videos folders.<\/a> The folders are still there, but nothing\u2019s left in them. It\u2019s sort of the neutron bomb<\/a> of Windows updates.<\/p>\n

How could this happen? Seriously, how can you have a release that does this to users? Where was the quality assurance team? Where were all those Windows 10 Insider Preview users? Oh, wait. The brave beta users had seen this problem! ZDNet\u2019s Ed Bott reported last week that he\u2019d found a report from three months ago from a tester who said that \u201cmy Documents folder had been overwritten with a new Documents folder<\/a>, complete with custom icon. All contents were gone.\u201d<\/p>\n

Once more, and with feeling: WTH, Microsoft!<\/p>\n

You can\u2019t call this a fluke. It\u2019s not as if Windows 10 is some Teflon-coated operating system that has never done anything wrong with its updates. Remember the April 2018 Update (version 1803)?<\/a> That\u2019s the one that had conniption fits with SSD drivers and Avast antivirus software. I remember, and not fondly.<\/p>\n

How hard is this really, Microsoft? You literally have millions of Preview users. At least one of them spotted this newest bug months before release. There may not be many people running into this problem, but anything bad enough to destroy users\u2019 files should be a red-letter, fix-it-now bug. It has proved bad enough that Microsoft has stopped the 1809 upgrade in its tracks until the problem gets resolved.<\/p>\n

Which, as I write this on Oct. 7, hasn\u2019t happened; the problem remains unfixed.<\/p>\n

Meanwhile, over on my Windows 7 box, I ran into that good old mystery \u201cerror 0x8000FFFF<\/a>\u201c notice. Lots of things can cause this error. The effect is always the same. You can\u2019t update Windows.<\/p>\n

I don\u2019t know about you, but I don\u2019t like running Windows PCs without the latest security updates. I\u2019m funny that way.<\/p>\n

In this latest go-round, I couldn\u2019t install Microsoft\u2019s two most recent monthly security rollup updates or the September security-only update. This one had me puzzled.<\/p>\n

It turns out \u2014 bear with me, because this gets messy \u2014 I hadn\u2019t installed a critical (but not security-related) servicing stack update (SSU), KB 3177467<\/a>, that Microsoft had released in October 2016. Unless I have a particular reason to do it, I don\u2019t install all critical Windows fixes. This will teach me. It turns out that the Windows 7 Service Pack 1 (SP1) patch was not marked as being related to security, though it was.<\/p>\n

I wasn\u2019t the only one with this problem. Enterprises were hit, too. Microsoft staffer John Wilcox said that \u201cmany organizations missed the update<\/a> and decided to install only the default monthly security fixes instead of the full servicing stack update.\u201d<\/p>\n

Wilcox, taking a different tack than the company has done with the Windows 10 mess, also explained how Microsoft missed this problem. \u201cWe test our monthly patches on fully patched, up-to-date systems, which is why this issue was not seen in our testing, or by any of our preview partners.\u201d I appreciate the candor.<\/p>\n

Going forward, this blunder won\u2019t happen again. Well, at least not exactly like this. First, Microsoft is reissuing the September update and tagging it as a security update to unblock any remaining customers from installing the August 2018 or later monthly security-only updates.<\/p>\n

Next, Microsoft is updating all release notes so they instruct you to install the latest SSU for your platform before installing the latest cumulative update. You do read the release notes, don\u2019t you? I don\u2019t care what operating system or program you\u2019re running, reading release notes will save you a lot of grief.<\/p>\n

Finally, if you don\u2019t read the notes, all future new SSUs will be marked as \u201csecurity,\u201d not just \u201ccritical.\u201d This way, if you still are installing only security fixes, you won\u2019t be caught out again.<\/p>\n

It\u2019s worth noting that even today I prefer Windows 7 to 10, and I find it more than a little ironic that the Windows 7 problem has a better fix than the still-unresolved Windows 10 episode. Which leads to another question for Microsoft: Are you sure you want to kill off Windows 7<\/a>? Just asking!<\/p>\n

http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: Steven J. Vaughan-Nichols| Date: Wed, 10 Oct 2018 03:00:00 -0700<\/strong><\/p>\n

\n
\n

To help make life better for you, my loyal readers, I suffer by running Windows 7 and 10 on two harmless \u2014 never hurt anyone in their lives \u2014 PCs. Well, I did. But, in the last week I ran into not one, but two, showstopper update bugs.<\/p>\n

First, on Windows 10, I was one of those \u201clucky\u201d people who had files vaporize when I \u201cupdated\u201d to Windows 10 October 2018 Update (version 1809). Because I only use Windows for trivial tasks, I didn\u2019t lose anything valuable when the patch decided to erase everything in the My Documents folder.<\/p>\n