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

Monthly Archives: May 2020

  • Arrived

    Posted on May 31st, 2020 at 12:39 woody Comment on the AskWoody Lounge

  • Open questions about the Win10 version 2004 upgrade

    Posted on May 31st, 2020 at 07:35 woody Comment on the AskWoody Lounge

    Susan has spotted the new Feature Update notification at the bottom of the Windows Update pane on her main machine:

    I still haven’t seen it on any of my machines.

    Can anyone tell me, definitively, which combination of circumstances lead to the appearance of that notice? Looks like having Feature Update deferrals set to non-zero may be part of the equation, but I don’t see the whole picture yet.

    What concerns me the most are the very infrequent mentions of 2004 being installed without a click on the “Download and install” link.

    I’m willing to bet that the people who get upgraded to version 2004 somehow, accidentally perhaps, clicked on that link.

    Do you have any observations to the contrary?

    Of course, I DON’T recommend that you install 2004. Let’s see what the pioneers discover….

  • Falcon 9

    Posted on May 30th, 2020 at 14:44 woody Comment on the AskWoody Lounge

    Tomorrow, the ISS.

  • Patch Lady – I’m not worthy for 2004

    Posted on May 29th, 2020 at 23:02 Susan Bradley Comment on the AskWoody Lounge

    Lenovo ThinkPad laptop.  Thought I’d check to see if 2004 is being offered up.   I’m not worthy.


  • Where we stand with the May 2020 patches

    Posted on May 29th, 2020 at 12:06 woody Comment on the AskWoody Lounge

    What a month!

    From an undocumented drive-by “Intel” microcode patch to an unannounced zero-day (which didn’t turn out to be very pressing), to five documented but ho-hum zero-days, more audio problems, a conflict with HP’s software that threw a BSoD, and an Office 365 Click-to-Run bug that took a day to patch, it’s never a dull moment.

    Details in Computerworld Woody on Windows.

  • Win10 version 2004 is here but… surprise!

    Posted on May 27th, 2020 at 13:49 woody Comment on the AskWoody Lounge

    Win10 version 2004 has been officially released.

    Microsoft’s been testing it since December. We’ve been getting official notices about 2004’s status for months. The last official notice, on May 12, didn’t list any known bugs. Today’s notice, though, comes packed with all sorts of known, officially acknowledged, problems:

    • Difficulty connecting to more than one Bluetooth device
      Windows 10 devices with certain Realtek drivers might be unable to connect to more than one Bluetooth device.
    • Errors or issues during or after updating devices with Conexant ISST audio drivers
      Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004.
    • Errors or issues during or after updating devices with certain Conexant audio drivers
      Devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen.
    • Issues using ImeMode property to control IME mode for individual text entry fields
      Some IMEs for certain langauges might have issues using the ImeMode property with certain apps.
    • Variable refresh rate not working as expected on devices with Intel iGPU
      Enabling VRR on affected devices will not enable the VRR for most games, especially games using Direct X 9.
    • Stop error when plugging or unplugging a Thunderbolt dock
      Devices using Thunderbolt docks may receive a stop error when plugging in or unplugging the dock
    • Errors or unexpected restarts for some devices using Always On, Always Connected
      Devices with more than one Always On, Always Connected capable network adapter might have issues.
    • No mouse input with apps and games using GameInput Redistributable
      Affected apps and games using both GameInput Redistributable and Windows 10, version 2004 might lose mouse input.
    • Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present
      Devices with apps or drivers using certain versions of aksfridge.sys or aksdf.sys might have issues updating or starting
    • Issue with older drivers for Nvidia display adapters (GPU)
      You might have issues if you are using an Nvidia display adapter (GPU) and drivers with a version below 358.00.

    The announcement also says:

    Windows 10, version 2004 is available for users with devices running Windows 10, versions 1903 and 1909 who manually seek to “Check for updates” via Windows Update.

    The wording of that is a bit strange… but it looks like this version works like the last two versions: If you go into Windows Update in Win10 1903 or 1909, click Check for Updates, and Microsoft determines that your machine is ready for 2004, you get the notification that the 2004 update it available. I think. (My production machines aren’t showing anything at this point.)

    You have to click on Download and install before it’s installed on your machine. That’s what I published in Computerworld earlier this week: How to block the Windows 10 May 2020 update, version 2004, from installing. It’s also what Microsoft promises in its just-published guide How to get the Windows 10 May 2020 Update.

    As best I can tell, clicking on Check for Updates in Win10 1903 or 1909 does NOT immediately upgrade you to 2004.

    What are you seeing?

  • Patch Lady – here comes 2004

    Posted on May 27th, 2020 at 12:41 Susan Bradley Comment on the AskWoody Lounge

    It’s official 2004 is out.  I’m hearing that the media creation tool doesn’t quite work yet.  Again, I always see this as a sign I should have moved to the one right before this, not that I should jump on this release — especially for production machines.

    Holler if you see issues in your testing.

  • Patch Lady – making sure you control your Microsoft account

    Posted on May 27th, 2020 at 11:34 Susan Bradley Comment on the AskWoody Lounge

    So I was helping a co-worker the other day with his home PC.  It prompted him to set up Windows Hello.  Well we didn’t want to set up Windows hello.  Turns out that was triggered by a pending reboot but in the process of turning off windows hello we realized that his Microsoft account at some point in time has been hacked.  We went to reset the password for his old Microsoft account that was still on the box (he logs in with a local account not Microsoft) and was told that we’d need to get a security code from a secondary email account that …. uh… it’s not ours.

    I cannot stress enough these days that should you use an email address for a log in to anything these days that you ensure you turn on two factor authentication.

    I’m now having to wait 24 hours to try again to recover access to this Microsoft account.  Wish me luck.