Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • Mystery patch KB 4023057 reappears — a “reliability improvement” to some 1507, 1511, 1607, 1703, 1709 and 1803 machines

    Posted on November 19th, 2018 at 11:58 woody Comment on the AskWoody Lounge

    Here we go again.

    KB 4023057 has been updated, with a lengthy KB article and very little substance that I can discern.

    This update includes files and resources that address issues that affect the update processes in Windows 10 that may prevent important Windows updates from being installed. These improvements help make sure that updates are installed seamlessly on your device, and they help improve the reliability and security of devices that are running Windows 10.

    We saw it on Sept. 9 and earlier on January 8.

    @ch100 has offered the only explanation that makes sense to me:

    KB4023057 was and still is one of the most weird and unexplained updates in the recent times. This update has never been offered to WSUS, but only to Windows Update. This would indicate that it meant for unmanaged end-users and unmanaged small business users…

    This patch may be harmless, but why it was released and where it actually applies, it is still a mystery.

    It’s most likely associated with the 1809 rollout, although why it didn’t appear in early October when 1809 first raised its ugly head leaves me baffled. Anybody out there have a better intel?

  • Forcing the issue with Win10 v1809

    Posted on November 18th, 2018 at 17:03 PKCano Comment on the AskWoody Lounge

    Always a Guinea Pig – Forcing the issue with Win10 v1809.

    I am running Win10 Pro in VMs, so this was a test situation, not my daily driver. The host system is MacMini, MacOS Mojave using Parallels Desktop 14, Ivy Bridge i7 with HD Graphics 4000 and running TrendMicro – the last two are counts against me from the beginning because 1809 has problems with both the graphics and the AV. But this system is also running an up-to-date Insider Preview, so I thought I’d give it a try.

    I was running v1709. In the Settings, I set SAC (Targeted), delay Feature = 0, delay Quality = 0, no pause. Try what I may, I could not get WU to offer anything but v1803, so I let it upgrade to v1803 in hopes I’d see v1809 on the other side.

    No joy. I finally downloaded the v1809 ISO and burned it to a double layer DVD (the x64 is HUGE). I could have copied the ISO to the VM and mounted it there, but I did not want the extra 5GB in the VM. I accessed the DVD from within the VM and ran setup. After accepting the EULA, I chose to keep my data and programs (an in-place upgrade) and let it install.

    The ISO installed Win10 v1809 Build 17763.107 with no problems. i immediately ran Windows Update and was offered KB4467708 which brought the Build to 17763.134 – according to WU up-to-date. Thanks to Parallels Tools driver emulation, the HD 4000 was not a problem. And the VM is running BitDefender Free, so no conflict there either.

    Although I have not had time to look at it in depth, here are some of the superficial observations:
    + I did not lose any data – because in the test machine there was no data to lose and I had not relocated the User folders to another location other than C:
    + Under Default Programs, all my third-party defaults came through (at least they are on the list) – Thunderbird, Firefox, VLC, Windows Picture Viewer, etc.
    * System Restore was turned off (again)
    * Under Network, sharing had been turned back on – I had it turned off in the VM for testing. I have not checked to see if the VM is visible on the network.
    + I went back through all the Settings App. Anything new is turned on by default, and some of the ole settings were also changed.
    * Task Scheduler – I had to disable the tasks under Application Experience and CEIP (again) as they were turned back on. Some of the other Tasks that I have been disabling I no longer have permission to change the setting.
    * I have blocked Cortana/Bing in Group Policy, along with other things like web search. I have not had time yet to go back over those settings.
    + I did not get Apps like Candy Crush. I did open a few of the UWP Apps just to see if they worked. Geezz, they’re ugly! Dumbed down, flat, ugly! No wonder I use Classic Start and third-party programs.

  • Patch Lady – now we’re talkin’ 1809 transparency

    Posted on November 16th, 2018 at 22:13 Susan Bradley Comment on the AskWoody Lounge


    Updating the master patch list tonight and look at the new known issues:

    Apple has identified an incompatibility with iCloud for Windows (version where users may experience issues updating synching Shared Albums after updating to Windows 10, version 1809.

    After updating to Window 10 version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.

    And the issue with mapped drives now showcases it will be fixed by the end of November:

    Next Steps: Microsoft is working on a resolution and estimates a solution will be available by end of November 2018.

  • The folks running Win10 1809 seem to know what they’re doing

    Posted on November 16th, 2018 at 10:33 woody Comment on the AskWoody Lounge

    I know it’s a controversial observation, especially around here, but I’m starting to hope that the current regime (whomever they may be) are using the tools they have to roll out Win10 1809 in a much more sane way.

    My most recent cause for hope: The “C week” or “D week” non-security cumulative update for Win10 version 1809, KB 4469342, is going out to the Insider Release Preview ring, for testing before broad deployment.

    That’s exactly what the Release Preview ring was made for. And it’s never been used correctly. Until today.

    Details in Computerworld Woody on Windows.

  • Windows 10 version 1809 advances to build 17763.165 – with no documentation, of course

    Posted on November 16th, 2018 at 08:29 woody Comment on the AskWoody Lounge

    I’m reading between the tea leaves here, but it appears as if KB 4469342 was released to the Insider Release Preview ring, then to the Win10 1809 masses at large, early this morning. It’s not showing up on my machines just yet, but there are reports popping up all over.

    If you install KB 4469342, you end up with build 17763.165.

    The official update page doesn’t list it, of course.

    Thx @hoyty

    UPDATE: The cumulative update was only distributed to the Insider Preview Ring — which is precisely what the Insider Preview Ring was built for. See https://www.askwoody.com/2018/the-folks-running-win10-1809-seem-to-know-what-theyre-doing/

  • Malicious Software Removal Tool update, KB 890830, throwing weird WinXP (!) EULA prompts

    Posted on November 15th, 2018 at 05:11 woody Comment on the AskWoody Lounge

    If I’d seen it once, I’d just disregard it as another bizarre Microsoft bug. But we have three reports now, like this one from @Morat:

    I’m running Windows 7 Pro 32-bit. MSRT Nov 2018 KB890830 popup notice says, “Prerelease Version of Service Pack 2 for Microsoft Windows XP Professional, Home, Media Center, or Tablet PC Edition END-USER LICENSE AGREEMENT FOR PRERELEASE CODE”. What the heck… prerelease code for Windows XP?

    There’s confirmation from @bsfinkel and from an anonymous poster.

    Looks like there’s a bug in KB 890830 for 32-bit Win7 — Prerelease code for XP? Pshaw.

    Thx, @Microfix

  • Patch Lady – 1809 and mapped drives

    Posted on November 14th, 2018 at 14:34 Susan Bradley Comment on the AskWoody Lounge

    For those of you in a domain, who have Windows 10 pro versions, please make sure that you  have put in place feature update deferrals to ensure you don’t receive 1809 until you … and Microsoft … are ready for it.


    I cannot believe.. well I guess in this era of Microsoft I can believe… that Microsoft would release an update that would impact their customer base like this.  Yes, it’s documented, yes there are “workarounds” but there is possibilities that line of business applications will not be happy with these solutions given.

    In Microsoft’s zeal to code for their future, they are putting bugs in their existing customers.  UNC paths and browser only may be the wave of the future, but to many small and medium businesses with older workforces (like mine) a mapped drive is the typical way that many firms still have their network set up.

    Furthermore this bug is not listed as a known issue on the Windows 10 update history page (only the file association bug is) so I’m going to have to keep track of KB4471218 to see if this gets resolved in the future.

    Bottom line ensure you have feature update deferrals in place.  And note that you can set a deferral for longer than the platform is supported on the Pro version.  For example Windows 10 pro only gets an 18 month window of support for security updates until you have to upgrade to the next feature release.  So you could put in place a 365 day deferral and then end up where your version (Windows 10 1703 for example) fell out of support last month.  Microsoft does not code the feature deferral process with Pro in mind, they have Enterprise and Education skus in their vision when they code the deferral process.

    So be aware if you do choose a deferral period of 365 days, and you have Pro version, you WILL be deferring yourself into an unsupported condition and will need to either change the deferral to 0, or manually install the next feature release to get yourself to where you will receive security updates again.

    And at the risk of sounding like a broken record, if you are a Home version, ensure you upgrade to Pro so you can defer feature upgrades.

    Today’s post is a Two Pinocchio rated post.  Not simple and certainly NOT transparent.

  • Patch Tuesday problems include even more reported bugs with Win10 version 1809

    Posted on November 14th, 2018 at 08:10 woody Comment on the AskWoody Lounge

    Server and WSUS have their share of problems, too, and the new SSUs may need feeding.

    Details in Computerworld. Woody on Windows