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
  • LangaList: Should you force your machine onto Win10 1809 or wait for 1903?

    Posted on April 22nd, 2019 at 05:40 woody Comment on the AskWoody Lounge

    It’s a tough question. Fred Langa takes you through the pros and cons, and offers some solace during these trying times. If every version of Windows were good, it’d be a no-brainer. Demonstrably, that isn’t the case.

    Fred also has a peek into a bit of history with us still — the old 8.3 filename. It’s there, on your system, whether you know it or not.

    LangaList lives in this week’s AskWoody Plus Newsletter 16.15.0, out this morning to AskWoody Plus Members.

  • Reports of this month’s Win10 version 1809 cumulative update, KB 4493509, causing extreme slowdowns

    Posted on April 11th, 2019 at 08:28 woody Comment on the AskWoody Lounge

    We had an anonymous tip yesterday pointing to two posters on Tenforums who reported that they’re machines were turned into molasses after installing the Patch Tuesday updates for Win10 version 1809.

    Bogdan Popa has a roundup this morning of various additional complaints.

    No acknowledgment from Microsoft just yet – and I don’t see a pattern. Do you?

  • There’s a reason why your Win10 1803 machine hasn’t been pushed onto 1809

    Posted on April 9th, 2019 at 12:59 woody Comment on the AskWoody Lounge

    Microsoft gave up.

    The 1803-to-1809 push pace has gone from slow to glacial.

    Gregg Keizer has the details on Computerworld:

    According to AdDuplex, … Windows 10 1809 powered just 26% of surveyed Windows 10 systems as of March 26. The gain from February to March, only 5 percentage points, was about half the increase from January to February, illustrating the slowing of 1809’s adoption.

    I don’t trust AdDuplex’s numbers, of course, but the trend is unmistakable. Microsoft’s pulling back on 1809.

    I would submit that, with the redirection of the Windows Insider Release Preview Ring — used to be Win10 1809 cumulative update previews and now it’s Win10 1903 beta build — we’re seeing a full-on retreat. I fully expect that Win10 1909 will be nothing more than “Win10 1903 Service Pack 1/2” in fact, if not in name.

    Which is great. Perhaps Microsoft is pulling back from its insane twice-a-year Windows update pace.

  • Now’s a good time to download and save a copy of Win10 version 1809

    Posted on April 7th, 2019 at 12:13 woody Comment on the AskWoody Lounge

    Microsoft says that Win10 version 1903 will be in beta preview for a while, then pushed out to normal people in late May.

    That makes now a good time to store away a clean copy of Win10 1809. Even if you never use it, doesn’t hurt to hold onto it. Stick it on a little-used hard drive, or a USB stick. No need to do anything fancy – you may never want it – but for now the bits are free and clean.

    Here’s how:

    Step 1. Go to

    Step 2. Click Download Tool now. You get a prompt to run or save the file MediaCreationTool1809.exe.\

    Step 3. Click Run (or if it’s downloaded, double-click on MediaCreationTool1809.exe).

    Step 4. Click Accept.

    Step 5. Choose the radio button Create installation media (USB flash drive, DVD, or ISO file) for another PC then click Next.

    Step 6. Use the recommended options for your current PC or, if you must, changed the Language or bittedness. Click Next.

    Step 7. Click the ISO file radio button and click Next.

    Step 8. Choose a location for the downloaded files and click Save.

    Step 9. Wait. If you’re on a fiber optic line it’ll take a few minutes. If you’re on a lousy landline, it could take years. You can use your PC while you’re waiting. Watch grass grow. Count gigaflops. Go out and enjoy the weather and wonder at why you’re cooped up front of a PC on a day like this.

    Step 10. When Windows is done downloading and verifying the download, and it offers to Burn the ISO file to a DVD, just click Finish

    Step 11. Go look where you told the download to put the file. You should see a file called Windows.iso

    Step 12. IMMEDIATELY right-click on the file, choose Rename, and give it a reasonable name, such as

    Win10 1809 17763.1.iso

    If you want to verify the version number, double-click on the ISO file, right click on Setup.exe, choose Properties, and look on the Details tab.

    If you want to create installation media for Win10 1809 – a USB drive or DVD disc that you can use to boot and install Win10 1809 – follow the instructions here under the heading Using the tool to create installation media (USB flash drive, DVD, or ISO file) to install Windows 10 on a different PC. It basically takes you through the same steps, but has you veer off into the bushes in Step 7.

  • Microsoft unexpectedly declares Win10 1809 ready for business

    Posted on March 28th, 2019 at 13:13 woody Comment on the AskWoody Lounge

    This with a list of acknowledged bugs almost as long as my arm.

    Details in Computerworld Woody on Windows.

    Yeah, I think somebody read Susan’s Hey 1809, we need to talk.

  • More signs that MS is closer to releasing 1809

    Posted on March 19th, 2019 at 12:55 woody Comment on the AskWoody Lounge

    This page was changed today

    Any idea what’s up?

    Thx VulturEMaN

  • When will MS start pushing the update to Win10 1809 on machines set for the SAC “branch”?

    Posted on March 16th, 2019 at 07:38 woody Comment on the AskWoody Lounge

    It’s a simple question.

    I have my Win1803 machine set up with my recommended Windows Update advanced options:

    Microsoft says it’s getting rid of “Semi-Annual Channel.”

    So when does Windows start pushing 1809 onto my 1803 machine? I’ve been wondering about that for some time now — figured that MS would have to declare Win10 1809 “Semi-Annual Channel” at some point, if only to honor the settings in earlier versions of Win10.

    @PKCano had a fascinating observation:

    If they declare 1809 “ready for business” at the same time they release 1903:
    + The deferral period for 1809 begins, (for a maximum of 365 days) from that point.
    + If they release 1903, with the changes they have made to SAC doing away with SACT, the deferral period for 1903 begins, (for a maximum of 365 days) from that point.

    Now they have two versions of Win10 reaching the end of the deferral time simultaneously.

    Which I find to be a brilliant way to unwind the Gordian knot. Microsoft, basically, says “let ’em eat cake” and walks away.

    @b offered an interesting twist:

    Plus 60 days:

    For devices that have been configured with a branch readiness of SAC, for the upgrade to version 1903 only, we will add an additional 60 days to the configured deferral. This will simulate the delay previously experienced when Microsoft declared the SAC milestone. For example, if your device is currently configured to defer updates 30 days from the SAC release date, for the upgrade to version 1903 (and this time only), we would append a 60-day delay to that configured 30-day deferral–meaning that the device would be upgraded 90 days (60+30) after version 1903 is released. (Note that the additional 60 days will be handled on our service side, and will not be reflected in your device configuration.)
    Windows Update for Business and the retirement of SAC-T

    Microsoft has already said that it’ll jump over its now-declared-redundant “SAC” setting in 1809 by adding 60 days to the 1809 Windows Update “feature update” advanced setting. Perhaps, as @b says, they’ll do the same to 1803. [Permit me to clarify: I’m saying that Win10 1809 will be upgraded to 1903 according to the 60-days-plus-deferral-days rule. We know that. But I’m betting that Microsoft will use identically obfuscated logic to upgrade 1803 users straight to 1903 using the same rule.]

    What a thoroughly screwed up resolution to an incredibly convoluted series of patching re-re-re-definitions.

  • Will Win10 1809 ever be declared “suitable for business”?

    Posted on March 14th, 2019 at 14:35 woody Comment on the AskWoody Lounge

    It’s been a raging question for months. Win10 version 1809, released in October, has not been declared “Semi-Annual Channel” (the previous “Current Branch for Business”) worthy as yet, although it’s been out for … count ’em … five months.

    A month ago, Microsoft dismantled its whole update framework and threw away the names that we’ve known for so long — names, such as “Semi-Annual Channel (Targeted),” that are baked into the fabric of Windows Update in versions 1803 and 1809.

    @1EarEngineer just pointed me to a post from ‘Softie John Wilcox which, in response to a question about the updating mess, says:

    1809 has been released, there is no second, separate broad release.   For self managed customers, they control and decided when they have reached their deploy decision, and our guidance is they should have started the deployment process now with 1809, following our recommend framework.  This would be in the target phase, which we are in as well for WU.

    For devices we manage, that are connected to WU, we are in targeted phase, which means we are only publishing the update to targeted devices, not all devices.  This is our normal process, and as we get more data and confidence, we add more devise to the target list, until we reach our decision that its good for all, at which time we publish to everyone. That is when it becomes “broad”. That just signals that it is now broadly available ( same release ).

    Its not a time driven thing, but a data driven thing. 1803, it took 2 months, the historical norm was 3-4 months.  1809 will not be 2 months , but more to the norm.

    1809 is already on VLSC, we are now posting at the same time we start on WU, and will continue that going forward

    Which, to my mind anyway, reaches a new low in obfuscation. First of all, Win10 version 1809 is five months old. Second, if MS doesn’t declare it “Semi-Annual Channel” one of these days, all of those Windows Update advanced settings in Win10 version 1803 and 1809 are just so much mealy-mouth mush.

    Am I missing something here?