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

  • Here’s what I don’t know about the upgrade to Win10 version 1909

    Posted on November 8th, 2019 at 10:49 woody Comment on the AskWoody Lounge

    Next Tuesday, the whole ball game changes — Microsoft’s releasing Win10 version 1909 and the latest official version of Win10 will change, from 1903 to 1909.

    I’ve been looking at the “version upgrade that looks like a cumulative update” concept and I’m still stuck on some important details. At least, they’re important to me.

    Those of you already running Win10 1903 will get a polite invitation to Download and install the Feature update to Windows 10, version 1909. So we’re promised, and that’s what I’ve seen in the beta builds. Cool.

    Here’s what I don’t know. If you have a definitive answer to any of these questions — or even an educated guess — I’d sure like to hear about it.

    Q1: Will the “Download and install now” offer on 1903 machines be subject to the same quality update deferral settings that control cumulative updates?

    • In other words, in Win10 1903 Pro, if I Pause updates or Defer quality updates, will the “Download and install now” offer wait until the Pause or Defer has expired?
    • In Win10 1903 Home, if I Pause updates, will “Download and install now” appear right away, or only after the Pause expires?

    (I’m assuming that the Pro feature update deferral setting has no effect. Right?)

    Q2: Will the “Download and install now” offer on 1809 Pro machines be subject to the  feature and quality update deferral settings?

    • Here’s where things get sticky. It looks like Win10 1809 Pro users will also see the “Download and install now” message in the screenshot — presumably enabling you to move from 1809 to 1909 without going through 1903. That’s great. But will the “Download and install now” offer wait until the Quality update deferral has expired? Or will it show up right away?
    • Will the Branch Readiness level or the feature update deferral setting have any effect on when and/or if the “Download and install now” offer appears?

    Q3: Will Win10 1809 Home machines ever see the “Download and install now” offer? If so, will the offer appear even if I have my internet connection set to metered? Is there an entry in the wushowhide list that’ll block the “Download and install now” offer?

    And the key question…

    Q4: After Tuesday, will it be possible to move from Win10 1809 Home to Win10 1903 Home?

    It isn’t at all clear to me that there’ll be a straightforward way to go from 1809 Home to 1903 Home after 1909 is released, unless you have a copy of 1903 squirreled away. Getting a clean, official copy of 1903 right now is easy. I have full step-by-step instructions in Computerworld. But after Tuesday, it’s going to get significantly more difficult.

    Q5: All of the same questions, but for Win10 version 1803.

    Remember that 1803 hits end-of-support on Tuesday, but in the normal course of events you should be good for security patches until December’s Patch Tuesday. So how does the “Download and install now” offer fit into the 1803 scheme of things?

    By the way, if you want to make sure you don’t get 1909 until you’re good ‘n ready, the nostrums in my November 1 article in Computerworld should take you over the hump.

    UPDATE: Just to be absolutely clear… MS has NOT committed to shipping 1909 next Tuesday. It just seems to be a general consensus of opinion.

  • Looks like Win10 version 1903 will get a fix for the Windows Update “disappearing deferral dialog” bug

    Posted on November 7th, 2019 at 06:53 woody Comment on the AskWoody Lounge

    I’ve seen it now on two systems, with my very own eyes.

    One of Win10 1903 Pro’s most obnoxious bugs will probably get fixed next week.

    If you’re concerned about updating Win10 version 1903, you probably know that there’s a bug in the Windows Update advanced options setting, where changing either the feature update or quality update deferral setting caused that entire piece of the dialog to disappear. The settings were still there, and they still had an effect on when your machine was updated. But you couldn’t see the settings, short of digging into Group Policy or the Registry.

    Looks like the bug’s been fixed in the “optional, non-security” second October cumulative update for Win10 1903 — which means it’s likely to appear on Patch Tuesday next week.

    Best I can tell, Microsoft has never acknowledged the bug, and they certainly haven’t announced that it’s been fixed.

    I’m starting to warm up to Win10 1903.

    Details on Computerworld. Woody on Windows

    Thx @Bree on Tenforums, @Tex265, @b, @PKCano, @abbodi86

  • Win10 version 1903 is likely the most-common version of Win10

    Posted on October 31st, 2019 at 06:48 woody Comment on the AskWoody Lounge

    You know how I hate spewing AdDuplex numbers — they’re based on usage of a tiny sample of Microsoft Store apps, most of which you’ve never seen — but according to Ad Duplex, Win10 version 1903 is now running on more than half of all Win10 machines. Their graph:

    I have it on very good authority that there’s a special location in Dante’s Seventh Ring (is that like a Release Preview Ring?) for writers who use “M19U” instead of “Win10 1903,” but nevermind.

    You can draw any conclusions you like, but in broad strokes it looks like the Win10 world is rapidly converging on version 1903.

    I’ll have more on that in the next few days.

  • Microsoft confirms printing bug in second September cumulative update for Win10 1903

    Posted on October 1st, 2019 at 11:21 woody Comment on the AskWoody Lounge

    The Windows Release Information Status page was updated last night to say:

    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing. Some apps may close or error when the print spooler fails and you may receive a remote procedure call error (RPC error) from some printing utility or printing apps.

    Affected platforms:

    • Client: Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1; Windows 7 SP1
    • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

    Workaround: Retrying to print may allow you to print successfully. If retrying does not allow you to print, you may also need to restart your device. If your device is using a v4 print driver and a v3 driver is available, you can also try installing the v3 driver as a workaround.

    Next steps: We are working on a resolution and will provide an update in an upcoming release.

    The announcement’s a little strange in a couple of respects.

    • The report says the bug appears in 1903, 1809, 1803, 1709, 1703, Win7 and 8.1. But I don’t see anything anywhere else about the bug in versions of Windows other than 1903. Can anybody out there confirm?
    • The “Originating update” column says it appeared in the Sept. 23 cumulative update KB 4522016 – which is the second monthly cumulative update for Win10 1903. Yet the KB article itself doesn’t mention the problem, nor does KB 4517211, the third September cumulative update for 1903, which presumably contains the same bug.

    I also note that the update doesn’t single out HP printers — although the majority of complaints I’ve seen are with HP printers.

  • Hedge your bets: Download an official, clean copy of Win10 version 1903 (build 18362.356) and save it for a rainy day

    Posted on September 26th, 2019 at 08:58 woody Comment on the AskWoody Lounge

    You can get a copy of Win10 1903 whether you’re running Windows or not. Might prove nice to have on a rainy day.

    Full step-by-step instructions in Computerworld. Woody on Windows

  • Microsoft acknowledges, and fixes, the audio bug in this month’s Win10 1903 patch

    Posted on September 14th, 2019 at 11:13 woody Comment on the AskWoody Lounge

    I’ve been grousing about the audio bug all week, but Friday afternoon we got official confirmation:

    Audio in games is quiet or different than expected

    Microsoft has received reports that audio in certain games is quieter or different than expected. At the request of some of our audio partners, we implemented a compatibility change that enabled certain games to query support and render multi-channel audio. Due to customer feedback, we are reverting this change as some games and some devices are not rendering multi-channel audio as expected. This may result in games sounding different than customers are used to and may have missing channels.
    Affected platforms:
    • Client: Windows 10, version 1903

    It appears as if the problem’s solved with that weird ghost patch, KB 4516421, that I originally thought might be a hoax. I was saying it was a cumulative update, but as @abbodi86 notes, it’s a tiny patch.

    As @EP says:

    KB4516421 for 1903 is available only thru WU/MU (windows update/microsoft update) and WSUS, not thru MUC (ms update catalog) as noted in that Knowledge Base article

    I did a recent WU scan on a friend’s pc running v1903 and that update was not offered – guess it’s only available to machines running usb audio devices

    Somebody please tell me that 1903 is ready for prime time.

    I wonder how the installer knows if you have a conflicting USB mic that hasn’t been plugged in…

  • Will Win10 1903 and 1909 co-exist?

    Posted on September 12th, 2019 at 09:54 woody Comment on the AskWoody Lounge

    I’m still scratching my head over this one. Please tell me if you’ve heard anything, official or otherwise.

    Sometime in the next few weeks, Microsoft’s going to release Win10 version 1909. We know it’s going to appear as a cumulative update to Win10 1903 — just like a Service Pack, which is great.

    Here’s the question: Will Win10 customers be able to continue to use and update Win10 1903 without making the leap t0 1909?

    We have concurrent patches in beta testing with builds 18362.xxx and 18363.xxx separately available. The former apply to 1903; the latter to 1909.

    Will the stubborn ones in the crowd (e.g., me) be able to stick with 1903 for a while, to see what, uh, surprises await us in 1909? If you’ve seen anything official, please post a link!

  • Microsoft confirms: Visio online stops working with Win10 1903

    Posted on September 8th, 2019 at 06:10 woody Comment on the AskWoody Lounge

    Here’s one I missed…

    Sergiu Gatlan at BleepingComputer points to an official Office online document that says:

    Visio stops working when using the keyboard

    You may have experienced the Visio app becoming slow or stalling when using the keyboard. This issue occurs on Windows version 1903. If you don’t know which version of Windows you have, see Which version of Windows OS am I running?

    This is a known issue and we are actively working on a fix.

    There’s a workaround — turn off Show text suggestions as I type — but no details about the 1903 build number.

    The Microsoft 365 Service Status page lists the bug, saying:

    Current status: We’ve completed development of the fix and we’ll begin performing exhaustive internal validation before deploying to the affected environments. We expect this validation phase to take an extended period of time while we ensure the effectiveness of our fix. Once the validation is complete, we will deploy it in the next Windows update.

    Scope of impact: This issue may affect any of your Microsoft Visio users that are on Windows Build 1903 and have the “Show text suggestions as I type” feature enabled.

    Start time: Tuesday, May 21, 2019, at 12:00 AM UTC

    Root cause: A code issue within Microsoft Windows is causing the Microsoft Visio service to experience stalls or delays.

    Next update by: Thursday, September 26, 2019, at 7:00 AM UTC

    MS has known about this since May 21. I’m really late to the party….