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

Daily Archives: November 14, 2019

  • Born: Microsoft incorrectly signed the MSRT update that’s been bouncing around. It’s fixed now.

    Posted on November 14th, 2019 at 13:01 woody Comment on the AskWoody Lounge

    News on that infuriating MSRT update bug. If you recall, the version of KB 890830 that arrived on Patch Tuesday was all over the map. As I said in Computerworld:

    There are hundreds of reports online of people who found that the MSRT installer threw an 800B0109 and wouldn’t install; or installed but then reinstalled on reboot; showed up multiple times in the Installed Updates list; didn’t show up in the Installed Updates list in spite of running; and several variations on those themes.

    I also said that the bad patch was fixed on Tuesday night – but, at least for some people, it wasn’t.

    Now comes word from Günter Born about the root cause of the problem:

    Microsoft made a mistake signing the update package in question… KB 890830 is no longer available via Windows Update… Microsoft has updated the package (in the Update Catalog) for Windows 7 and Server 2008/r2 and replaced the faulty certificate.

    He reports that the newly updated (but not yet pushed) version installs correctly. (Actually, I should say “runs correctly,” because the MSRT programs just run, they don’t install anything.)

    UPDATE: @Speccy has observed that the problem isn’t with the certificate, but with our old friend the SHA-2 signing problem with Win7 patches. Looks like he’s right. Read more here.

  • Win10 Update Assistant to move to 1909 next week

    Posted on November 14th, 2019 at 12:49 woody Comment on the AskWoody Lounge

    If you’re planning on using the Win10 Update Assistant to get onto version 1903, better move fast. KB 3159635, which describes the Update Assistant, was updated an hour ago to say:

    Installation of Windows 10, version 1909 with the Windows 10 Update Assistant will be available the week of November 18th, 2019.

    That gives you less than a week to download and squirrel away an official, clean, free copy of Win10 version 1903. I have step-by-step instructions in Computerworld.

    Thx, VulturEMaN

  • Python programmers: Watch out for Win10 version 1903

    Posted on November 14th, 2019 at 07:07 woody Comment on the AskWoody Lounge

    We had a report a few hours ago from MartinPurvis that performing an in-place upgrade from Win10 version 1803 to version 1903 clobbered Python:

    Turns out that a user path variable is added to the top of the environment variable list which gives priority to a 0kb python.exe inside the Windows Apps AppData instead of using the user defined python directory before the in-place upgrade.

    Looking around the web, I see that’s a common complaint. Poster Ac3_DeXt3R on SuperUser says:

    On typing “python” from search, opens the Python 2.7 prompt but when I type from command prompt window, it triggers the Microsoft Store.

    Poster ecool on the Microsoft Answers forum said, back in May:

    Windows 10 is using the System Environment variables over my User Environment. So just ordering the Python location to the top of the System Environment Path variable worked to remove the annoyance of trying to run python and it opening to the Windows Store.

    Back on the SuperUser site, Ramhound says:

    This was intended behavior. Microsoft added this behavior with 1903 because they recognized developers struggle getting Python installed. I read about this change but I don’t recall where I read it.

    I can’t find the original description Ramhound describes. Can anybody out there point me to it?