Lots of little patches, but nothing that puts a dent in this month’s big bugs

Then there’s the “upgrade privacy warning” patch that looks like more advertising, the bizarre “Surface – HIDClass 4/26/2018 12:00:00 AM – 3.3.206.0” driver for non-Surface machines, Spectre v2 microcode fixes for Win10 1803… and no Monthly Rollup Previews.

Weird month.

Computerworld Woody on Windows.

Single-purpose patch for CVE-2018-8174, the VBScript 0day, available from 0patch

This isn’t an endorsement.

If you read my summary of this month’s patches, you’ll recall that there’s one potentially important patch:

Microsoft released an explanation for the one “critical” Windows patch this month that is being actively exploited — a zero-day. Called CVE-2018-8174, the security hole involves the way Internet Explorer (mis)handles VBScript programs.

That’s the one big security hole staring at us so far this month. I still haven’t heard of any exploits other than the ones identified by Kaspersky and Qihoo 360 (remember – they involved PDF files in Yiddish/Hebrew sent to Chinese organizations), but it’s still a potential problem.

And then Microsoft screwed up the Windows 7 patches this month, breaking networks on some Win7 systems.

Given the current state of affairs, you can either fix the VBScript 0day and possibly break your network card in the process, or you can avoid the update entirely until Microsoft finally fixes it. Whenever that may be.

I was surprised to discover that 0patch, a well regarded patching platform from ACROS Security, now has a free patch available that plugs the 0day hole by simply, well, plugging the 0day hole. What a novel idea. Microsoft should do that… he says, tongue planted firmly in cheek.

I’m NOT recommending that you run out and install the 0patch patch. It always gives me the willies when I see a non-Microsoft product offered to fix a Microsoft bug. But in this case, if you read the description, the analyst there who wrote the patch (Mitja Kolsek) knows what he’s doing.

So rather than recommend that patch, I’m putting out a feeler to see if any of you have installed this patch — or if you have experience with other 0patch patches.

Whaddya think?

How and where to find ISOs for old versions of Windows 10

You’ll find lots of torrents and pirate download sites, but I still strongly recommend against using them (yes, even if you check the hashes).

Instead, read this article by Ed Tittel and Kari Paajolahti. They look at downloading through the UUP Dump MiniServer and HeiDoc.net (an old friend). They both offer links into Microsoft’s own copies of the old ISOs.

That’s the way to go.

Win10 version 1803 shoots PowerShell dropdown list

I’m still amazed at how many bugs are floating around.

If you’re in the Windows Insider program, I recommend that you look at Thomas G’s feedback and vote it up:

When using commands, PowerShell no longer shows a list of suggestions of commands (dropdown list).

It just shows a . below the command as if it’s unable to open the list.

Patch Lady – KB4103718 /KB4103712 known issues

As noted in https://support.microsoft.com/en-us/help/4103718/windows-7-update-kb4103718 and in https://support.microsoft.com/en-us/help/4103712

A question about KB 4103728 – what is it?

Interesting observation from MG:

Microsoft posted a link on Reddit that doesn’t make much sense. In particular, @einarmsft posted this:

Hi folks! May’s Cumulative Updates are going out today, here are links to the release notes:

1803 – https://support.microsoft.com/kb/4103721

1709 – https://support.microsoft.com/kb/4103727

1703 – https://support.microsoft.com/kb/4103731

1607 – https://support.microsoft.com/kb/4103723

1511 – https://support.microsoft.com/kb/4103728

RTM – https://support.microsoft.com/kb/4103716

As always, please let us know what you’re seeing!

What’s with the 1511 link? Microsoft ended support for Win10 1511 in April. I wonder if they actually build the KB, or if they posted a link by mistake. As far as I know, the only older versions of LTSC are for 1507 and 1607.

Any guesses?

Windows 10 version 1803 isn’t compatible with Toshiba solid state drives, either

Last week we learned that Microsoft didn’t bother to test Win10 version 1803 on some of its Surface Pro (2017) laptops — if they had, they would’ve discovered that 1803 crashes the system entirely. Every Surface Pro (2017) with an Intel solid state drive crashes. Every. Single. One.

Now we’ve received official confirmation that Win10 1803 doesn’t work with Toshiba SSDs, either. Microsoft says they “may experience degraded battery life” but I’m seeing reports that they turn hot as a fiddle in Devil Went Down to Georgia. (That’s my favorite version.)

Computerworld Woody on Windows.

Thx to Wazhai.

There goes another excuse for not backing up

Just got a message from Noel Carboni.

I just ordered another new backup drive from Amazon (via your home page link), a MyBook 8 TB drive.

The price was decent I think – $169.99. For EIGHT TB. I’ve seen Seagate 8 TB drives for less, but I prefer the Western Digital brand myself.

I would post this on your site in a post encouraging people to do backups – but I don’t know how to format the link to make sure you get your commission.

Problem solved. 🙂

Seriously, this is an amazing price for a very capable piece of hardware. If you aren’t doing backups, you just lost another excuse.