News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Patch Lady – 31 days of paranoia – day 10

    Posted on October 10th, 2018 at 22:52 Susan Bradley Comment on the AskWoody Lounge

    Patch Lady here – I wasn’t going to do a post on Patching with a paranoid theme in mind until later in the month but several articles and the fact that this week is the 15 year anniversary of when we moved to a second Tuesday of the month routine prompted me to write this now.

    Today two more tech journalists have joined myself, Woody and others in tilting at the windmill, better known as Microsoft.

    Ed Bott and Mary Jo Foley added to the choir of voices asking Microsoft to slow down and focus on quality, not quantity.  I remember a time years ago that patches came out at any time, any hour and I had to review if I was at risk of attack and consider installing updates during lunchtime and rebooting our office server to ensure that I was protected.  Now we are at a point in time that no prudent person alive would install updates on the day they come out.  Even worst, most prudent folks are waiting at least a week or longer.  That’s making me very paranoid that we are going to have a very bad security issue arise because we aren’t patching.

    Make no mistake I strongly still believe that there are good people that work inside of Microsoft that care about consumers, that care about patch quality, that care about feature release quality.  But if I let my paranoia take over, and look at the focus on Azure, and know that once everything is packaged in a format that will run in a browser, then the desktop becomes irrelevant.

    In patching there is a point in time where the risk of installing the patch and the resulting side effects is less than the risk of the attack that the patch is protecting you from.  It’s that point in the middle where the scale tips away from patch pain to risk of attack that is the perfect point of installing updates.  Microsoft tries to be the system administrator for all home users and any small (or even medium) business that is looking to Microsoft update for their updates.  Right now I’m paranoid enough to say publicly that they are failing badly.

    I don’t even have to wrap my head with aluminum foil to know that the worse thing that can happen to a computer user is to reboot their computer after an update and have it not boot.  Yet that’s what happened to some in January of this year.  I don’t have to add to my paranoia of lack of backups to be concerned when users lose data during a process that should them bring excitement to their computing experience.  Once upon a time I knew people that camped out overnight at Best Buy to get the latest version of Windows.  Now we have people losing data when they get a feature release.  The fact that the amount of people impacted was not a material amount was just luck.  The second of the two data loss bugs (the one they fixed in KB4464330) had the potential to hit a lot of Enterprises if they hadn’t found that bug.

    My biggest paranoia about patching today is that all of this paranoia about patching is no longer irrational paranoia over immaterial corner cases that the vast majority of people would never hit.  My biggest paranoia is that more and more people will stop updating because of the reality that we are seeing.

    I’m also paranoid that folks in the insider program will overstate the severity of their bugs to the point that adding a severity rating to every bug will make no difference and once again we will have bugs that hurt lost in the firehose of feedback and upvoting.

    Microsoft needs to take a severe action like moving feature release cadence to once a year to showcase that they too want to stop the paranoia over patching and make us feel comfortable again.

    I remember when we had horrible patch quality.  I remember when we had patches released without a solid release schedule.  I remember when patches were pulled back, had to be redone.  And I feel paranoid that we are back to where we started 15 years ago.

  • Can’t get the Win7 Monthly Rollup to install? Error 0x8000FFF again? There’s a reason — and you aren’t gonna like it

    Posted on October 10th, 2018 at 10:25 woody Comment on the AskWoody Lounge

    If you thought that Microsoft solved the 0x8000FFF problem last week, you thought wrong. @abbodi86, @PKCano and @geekdom have uncovered the “exclusive” culprit.

    Computerworld Woody on Windows.

  • Hoffman: Bing results are racist, antisemitic, pedophiliaic, conspiratorial

    Posted on October 10th, 2018 at 08:11 woody Comment on the AskWoody Lounge

    I didn’t believe it until I tried some of the searches myself. Google comes up clean, but Bing barfs big-time.

    Chris Hoffman at How-To Geek: Bing Is Suggesting the Worst Things You Can Imagine

    Microsoft has a responsibility to clean up Bing. A major search engine (and especially one that is increasingly becoming a harder-to-turn-off default built into Windows 10) shouldn’t be suggesting its users search for racist garbage and images of underage children.

    Wonder if Satya has seen this? Bing’s come a long way since he was in charge.

  • The three Win10 version 1809 builds, what they mean, and what they break

    Posted on October 10th, 2018 at 06:57 woody Comment on the AskWoody Lounge

    If you were brave/foolhardy enough to install Win10 1809, there’s some relief in yesterday’s Cumulative Update.

    There are three builds of Win10 1809 now, each with their own… let’s call them foibles…

    0.01% of seekers got their Documents folder zapped? Pshaw. I’ve heard that folks fed the 1809 upgrade through WSUS also saw their Documents and Photos folders cleaned out. Can you corroborate?

    Computerworld Woody on Windows.

  • I just downloaded a copy of the Win10 ISO installation file. How can I be sure it’s for version 1803?

    Posted on October 10th, 2018 at 04:40 woody Comment on the AskWoody Lounge

    A very timely question just appeared in my inbox.

    I did do one thing today, that had got “timed-out” earlier this month…  downloaded the Win10-1803 ISO.  Or at least, I think it was the 1803 version, which is what I wanted to ask you about.

    The MediaTool download stated it was for 1803 – can I rely on that being 1803?  Is it possible it slipped me a copy of 1809 while pretending it was 1803?

    I’ve just filed it away for future reference, as an insurance policy (not that I think my machines are deemed to be “supported” for anything past 1511?).

    A whole lot of people are going to be asking that question over the next few days. Fortunately, the answer’s easy – if you know the dism trick.

    Check out my full explanation in the Computerworld article Grab a free copy of Win10 version 1803 and save it for a rainy day.

    If you already have an ISO file and want to know for sure if it’s 1803, start at Step 10.