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

Blog Archives

  • Microsoft issues new cumulative updates for Windows 10 1803 and 1809

    Posted on May 21st, 2019 at 15:02 PKCano Comment on the AskWoody Lounge

    On Tuesday, May 21, Microsoft released Cumulative updates for Windows 10 v1803 and v1809.

    v 1803 KB 4499183 Build 17134.799
    v 1809 KB 4497934 Build 17763.529

    Starting with update [KB4499183 and KB4497934], we are introducing functionality that allows you to decide when to install a feature update. You control when you get a feature update while simultaneously keeping your devices up to date. Feature updates that are available for eligible devices will appear in a separate module on the Windows Update page (Settings > Update & Security > Windows Update). If you would like to get an available update right away, select Download and install now. To find out more about this feature, please go to this blog.

    When Windows 10 devices are at, or within several months of reaching, end of service, Windows Update will begin to automatically initiate a feature update. This keeps those devices supported and receiving the monthly updates that are critical to device security and ecosystem health.

    The changes to v1803 and v1809 will be available in the June Patch Tuesday updates.
    These Cumulative Updates are Previews. You don’t need to install them.

  • KB 4487017 Feb Cumulative update for Win10 v1803 causing BSODs

    Posted on March 19th, 2019 at 14:57 PKCano Comment on the AskWoody Lounge

    @weedacres reports that the Feb 2019 Cumulative Update KB KB4487017 for Win10 v1803  is causing BSODs.

    One of my customers called yesterday reporting BSOD’s on their two HP AIO’s. This KB is the 2019-02 Cumulative update for 1803. This apparently started on or about 3/8 when the update was installed.

    I found that they’re getting 001a BSOD’s and after some research saw that many others are having the same problem. I saw several failures while working on both PC’s and finally uninstalled the update last evening. I hid it with wushowhide and so far all seems well.

    My question is how long with wushowhide keep it hidden? Am I going to have to hand tend this thing until the March updates install?

    Is anyone else seeing this problem?

    This is a correction to an earlier report. It was not KB 4023057 causing the problems.

  • Microsoft yanks buggy second monthly cumulative update for Win10 version 1803, KB 4467682

    Posted on December 6th, 2018 at 13:33 woody Comment on the AskWoody Lounge

    Remember the buggy Win10 version 1803 patch that bluescreens Surface Book 2 machines?

    Microsoft urged Surface Book 2 owners to boot around the bluescreen and uninstall the patch. Which is just what you want to tell your boss about her brand new, expensive Surface Book 2, right?

    Looks like MS has retracted completely and pulled the patch. The KB article now says:

    After installing this optional update some users have reported getting a blue or black screen with error code, “System thread exception not handled.” As a precaution, we have removed this optional update from Windows Update and Microsoft Update Catalog to protect customers. Fixes and improvements will be available in the December 2018 security update release and will include a resolution for this issue.

    One can only hope that Microsoft will test this patch, for a change, before it appears.

    And that “optional” stuff. That’s just a fig leaf. The second monthly cumulative updates are “optional” in the sense that you have to click on Check for Updates. Which isn’t exactly optional, to my way of thinking.

    Thx Günter Born, who promises to have a blog post tomorrow that describes a second bug in the same cumulative update.

  • Last month’s second Tuesday cumulative update for Win10 1803 is bricking Surface Book 2

    Posted on December 4th, 2018 at 09:44 woody Comment on the AskWoody Lounge

    See what I mean about testing cumulative updates before they’re rolled out?

    KB 4467682, last month’s second cumulative update for Win10 1803 (the “non-security only” patch from Nov. 27) is bricking many Surface Book 2 machines. I’ve been rallying for Microsoft to start testing its “C or D week” cumulative updates before they’re released. Here’s an excellent example of why that’s crucial.

    Richard Speed at The Reg reports:

    Blue Screens of Death (BSOD) first began occurring shortly after the update, KB4467682, was dropped on 27 November.

    The BSOD headache manifests itself by throwing a SYSTEM THREAD EXCEPTION NOT HANDLED error and rebooting the computer. Some users reported seeing the error repeatedly, while others are luckier, losing their work only three times a day or so.

    Liam Tung at ZDNet reports that:

    People on Microsoft’s answers forum and on Reddit are complaining about Blue Screen of Death, or BSOD, issues that began occurring after installing cumulative update, KB4467682, released last Tuesday for Windows 10 version 1803.

    Permit me to repeat, for emphasis. Microsoft should be testing these patches before they’re pushed. I’m not talking about employee-tested dogfood. I’m talking about real, live testing regimens, out in the real world.

    The only way that’s going to happen is if Microsoft has a real testing method set up. Leave the ninja cats and cute narwals to the marketing folks. I’m talking about targeted tests, for people with skin in the game.

    The Windows Insider Release Preview Ring is made to test cumulative updates before they’re installed. But that only works for one version of Win10.

    As of this moment, the Release Preview Ring is only for Win10 1809. There should be similar test rings for all supported versions of Win10 — at the very least, 1709, 1803 and 1809. And then, gosh, Microsoft should actually use them.

    I really don’t understand what’s so hard here.

    Thx @MikeFromMarkham

  • You may have received the upgrade to Win10 1803 last night

    Posted on November 7th, 2018 at 09:30 woody Comment on the AskWoody Lounge

    Just a quick note. Those of you running Win10 version 1703 or 1709 who have “feature update deferral” set to 120 days should see 1803 in your Windows Update chute this morning.

    Win10 1803 hit “Semi-Annual Channel” (formerly known as “Current Branch for Business”) on July 10. Add 120 days to that and you get Nov. 7.

    Thx, @zero2dash.

  • On beyond Win10 version 1703 – Is 1803 ready yet? Really?

    Posted on November 4th, 2018 at 06:03 woody Comment on the AskWoody Lounge

    I’m sitting in the horns of a dilemma, and figured I’d toss this one out for discussion.

    Lots of folks are still on Win10 version 1703. I’m one of them — on my main machines, anyway. With Microsoft claiming that it won’t issue any more security patches for 1703, I’m pretty much forced to move on. (Yes, I know I can stick with 1703, but the volume of patches we’ve seen for Win10 argues volubly in favor of moving on.)

    Thus the dilemma (trilemma?). Assuming I stick with Win10, do I jump to 1709, 1803 or wait a bit and go with 1809?

    I’ll rule out 1809 just out of hand. Microsoft’s obviously working hard at making it a worthy version of Windows. But it ain’t good enough for Microsoft yet, and if it isn’t up to Microsoft’s standards, it sure as shootin’ isn’t up to mine.

    I’ve heard recent reports that the long-lingering problems with 1803 have been fixed, by and large. But in the once-burned-twice-shy tradition, I’m highly skeptical.

    Version 1709 has been stable for a while — and Microsoft has plugged a lot of holes in it, with a huge bunch arriving just a few weeks ago. But if I  move to 1709, I’ll have to move again in six months. If I jump to 1803, it’ll be patched until a year from now.

    And if there’s one thing I hate to do, it’s upgrade Windows versions on a production machine.

    What do you think?

    If I were buying a new machine I’d go with a Chromebook, frankly, but that’s a different story entirely.

  • 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.

  • Hey, Win10 peeps: Now’s a good time to download and save a fresh, clean copy of Win10 version 1803

    Posted on September 26th, 2018 at 13:29 woody Comment on the AskWoody Lounge

    It’s a fairly straightforward process, as long as you have access to a Windows 10 machine.

    Step-by-step details in Computerworld Woody on Windows.

    Thx for the nudge, @PKCano!