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 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 and 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….

  • Things I didn’t know: “Check for updates” in Win10 1903 now warns about optional and feature updates

    Posted on September 5th, 2019 at 07:37 woody Comment on the AskWoody Lounge

    I must’ve been sleeping when this announcement hit the waves:

    Best I can tell, as is so often the case, Ed’s right. It looks like Microsoft has fixed one of the most abominable come-ons in Windows history. In every test I could come up with, clicking Check for Updates only in Win10 1903, triggers an “Optional updates available” notice and “Download and install now” link, instead of just carpet bombing the PC with anything in the update bucket.

    Are any of you seeing anything different? It hasn’t always been so.

    If that behavior’s true and consistent, I now have a second good reason (after Pause updates on Home) to upgrade to 1903.

    A related observation: It looks like we’ve definitively lost the user interface for “Choose when updates are installed” in Win10 1903 Pro if either feature or quality deferrals are non-zero. At first I thought that was a bug. Now I guess it’s a … feature?

    UPDATE: Ed just changed his long-standing ZDNet explainer about Windows updating. He’s included a section on this new “Download and install now” behavior for “optional” (= not Patch Tuesday) patches.

    As of version 1903, Windows 10 no longer installs feature updates automatically. Instead, as with the optional cumulative updates delivered in the “C” and “D” weeks, the update is listed as available in Windows Update, but you have to click Download And Install to kick off the installation. This change affects all editions, including Windows 10 Home.

    As best I can tell, that behavior changed very recently. It may have coincided with the change in the appearance/disappearance of the “Choose when updates are installed” part of the user interface in Win10 1903 Pro.

    There’s a whole lot of paddling going on beneath the surface. Fortunately, the changes (if they work the way Ed describes) are definitely in the right direction.

    Details in Computerworld Woody on Windows.

  • Another Win10 version 1903 redline bug: Disconnected RDP sessions peg dwm.exe at 100% utilization

    Posted on September 5th, 2019 at 07:07 woody Comment on the AskWoody Lounge

    Here’s an oldie but goodie just mentioned to me by Günter Born….

    In Win10 version 1903, if you use a computer to RDP into another computer, and then disconnect the RDP session on the second computer (without logging out), dwm.exe redlines one core on the originating machine.

    Apparently, disabling the WDDM driver using Group Policy fixes the problem.

    Microsoft knows about the problem — it’s documented on Answers forum and other posts here and here and here and here and here. There are lots of posts on the Feedback Hub, too.

    It’s not clear (at least to me) if this is an Intel driver problem, or a Win10 1903 problem. But it’s definitely widespread. And I’ve only seen it reported on Win10 1903.

  • Where we stand with the Cortana/Search redlining bug

    Posted on September 4th, 2019 at 06:05 woody Comment on the AskWoody Lounge

    We’re stuck between a rock and a very hard place.

    On the one hand, if you’re running Win10 1903 — you may have been pushed — you really need to get the first August cumulative update installed to guard against DejaBlue (which hasn’t been exploited yet).

    On the other hand, there are so many bugs in the first August cumulative update (VB/VBA/VBScript, Windows Sandbox, PXE, MIT Kerberos) that you really should get the second August cumulative update.

    On the third hand, if you install the second August cumulative update, your machine may start redlining.

    Tell me again how Win10 1903 is ready for prime time?

    Computerworld Woody on Windows.

  • Microsoft STILL hasn’t acknowledged the bugs in last Friday’s Win10 1903 cumulative update

    Posted on September 3rd, 2019 at 13:54 woody Comment on the AskWoody Lounge

    Last Friday, Microsoft released KB 4512941, the long-anticipated second August cumulative update for Win10 version 1903.

    Within a few hours, people were complaining on various online forums that installing the update immediately triggered excessive CPU use. I wrote about that on Friday night.

    Since then, explanations and workarounds have appeared all over the place. @EP came up with this list:

    one workaround to the problem posted on Softpedia news:

    Günter Born has had two — not one, but two — explainers with detailed analyses. Ends up that making certain registry changes can get the CPU utilization back to normal.

    Most damning, Mayank Parnmar at Windows Latest reported on Saturday:

    It’s important to note that Microsoft actually tested KB4512941 with Windows Insiders in the Release Preview Ring for more than a week before shipping the update to the general public.

    According to some posts on Feedback Hub, reports of high CPU usage were submitted multiple times by testers earlier this week, but the reports appear to have been ignored because they weren’t upvoted enough.

    So now it’s Tuesday, four days after the offal hit the fan… and Microsoft hasn’t said one thing about it.

    Even now, the KB article says:

    Known issues in this update

    Microsoft is not currently aware of any issues with this update.

    And the Release Information Status page says absolutely nothing.

    UPDATE: As I was writing this, MS posted on Twitter (thx, MJF)

  • Report that Win10 1903 cumulative update KB 4512508 clobbers Outlook 365 startup

    Posted on August 14th, 2019 at 14:39 woody Comment on the AskWoody Lounge

    A new report from the group:

    KB 4512508 causes Outlook 365 (Version 1902 Build 11328.20368 Click-to-Run – July version) to get stuck on loading profile. Uninstalling KB4512508 corrected the issue.

    I don’t see this listed as a known bug in either Win10 1903 or in Office.