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
  • Microsoft sneaks out largely undocumented hotfix for Windows 10, build 14393.577

    Posted on December 21st, 2016 at 08:09 woody Comment on the AskWoody Lounge

    This could be the way of the future for Win10 hotfixes.

    InfoWorld Woody on Windows

    Tip o’ the hat to @teroalhonen

    UPDATE: I’m now seeing reports that KB 3213522 is now being offered on WSUS servers. I still don’t see it on Windows Update, and it still isn’t listed on the Win10 update history page.

    If that helped, take a second to support AskWoody on Patreon

    Home Forums Microsoft sneaks out largely undocumented hotfix for Windows 10, build 14393.577

    This topic contains 27 replies, has 2 voices, and was last updated by

     abbodi86 2 years, 1 month ago.

    • Author
    • #16563 Reply

      Da Boss

      This could be the way of the future for Win10 hotfixes. InfoWorld Woody on Windows Tip o’ the hat to @teroalhonen UPDATE: I’m now seeing reports that
      [See the full post at: Microsoft sneaks out largely undocumented hotfix for Windows 10, build 14393.577]

    • #16564 Reply


      How it’s “undocumented” exactly? πŸ˜€
      KB article is clear enough πŸ™‚

    • #16565 Reply

      Da Boss

      My original headline was “largely undocumented” because it doesn’t appear in the Win10 update list, it isn’t distributed through normal channels – and unless you knew about it, you’d probably never find it.

      Still, as you say, the KB article is quite clear.

    • #16566 Reply


      There’s a typo “306632” in the article.

    • #16567 Reply

      Da Boss


    • #16568 Reply


      Maybe the best option at this stage is to wait and see where possible, because it is not so easy to wait for everyone with Windows 10.
      The previous 2 patches have had exactly the same issue supposedly fixed now and there is no guarantee that this third try will fix anything.
      The patch is in WSUS only for Windows 10 but there is no mention at this stage about Windows Server 2016 which is affected by the same problem too.

    • #16569 Reply


      Are these dynamic updates mentioned anywhere on this site?

      KB3207781 – Compatibility update for upgrading to Windows 10 Version 1607: December 13, 2016

      KB3203338 – Compatibility update for upgrading to Windows 10 Version 1607 and Windows Server 2016: November 8, 2016

      KB3199389 – Compatibility update for upgrading to Windows 10 Version 1607: October 27, 2016

      KB3192762 – Compatibility update for upgrading to Windows 10 Version 1607: September 29, 2016

      … and the list goes on back in time.
      The only relevant one is obviously the latest one, the first in this list.

    • #16570 Reply


      I see
      that’s actually true
      it’s not even listed in this article, which usually list the catalg-only updates

    • #16571 Reply

      Da Boss

      I don’t see them listed. Care to write something up about 3207781?

    • #16572 Reply


      They are manual updates (not CBS packages), only needed for installation media (“sources” folder in ISO)

    • #16573 Reply


      They are in the catalog if you search by Windows 10 1607.
      They are dynamic updates which are supposed to fix the installation at runtime by doing what Microsoft considers mandatory fixes.
      I don’t know if it makes any sense to install them separately, but I suppose it is possible because they are listed in the catalog.
      For other products like SQL Server or CRM Dynamics, the installer asks during the setup if the administrator wants to check Microsoft Update for the latest (setup) fixes.
      For Windows, there is no such prompt and I think they get installed in the background if required, possible depending on the scenario. I don’t see any of them listed as installed on clean installations, but they may get there in upgrade scenarios, possible depending on the level of patching before the upgrade.
      It looks a bit like the KB2952664/KB3150513, doesn’t it?

    • #16574 Reply


      If not badly affected by the issue which is supposed to be fixed and able to avoid automatic updating, I would stay with the monthly Security Updates for Windows 10 released on the main Patch Tuesday, second Tuesday each month.
      The other updates released are equivalent with the Optional Preview releases for Windows 7.
      If Windows 10 installations would not be so intrusive and taking such a long time with frequent issues, I would not have much objection even to the mid-cycle updates like this one.
      In this case, the current release would provide a fix only for those who have not yet installed the main Security CU for December 2016, KB3206632.

    • #16575 Reply

      Da Boss

      Fer sure.

    • #16576 Reply


      I think they get downloaded during the setup/upgrade in certain conditions and if Internet access is available. Or as you say, if you deploy based on an installation media other than the original ISO.

    • #16577 Reply


      This is an interesting issue if true.

      Note: I found the URL and the issue mentioned first on the email list.

    • #16578 Reply


      It’s not just this VBS mess Microsoft shipped with the last update. The last update also messed with the networking stack and after reboot, this junk called Windows 10 won’t even connect to the Internet or fire up Hyper-V VMs. If they can’t get it right even on stock DELL machines, [add your rant here]… Looks like they frell up the whole thing update by update. Then these nutjobs clock off for holiday…

    • #16579 Reply


      I have seen this networking issue related to Hyper-V when I used to be on the Insider track and was upgrading Windows 10 almost every week.
      The story learnt is that every time when there is a Feature Upgrade to be installed, it is much better to uninstall Hyper-V before upgrading and reinstall after upgrading.
      Because of those issues, I prefer to use VMWare Workstation instead.

    • #16580 Reply


      Based on @MSSucks post here, I am wondering if those with wireless connectivity issues had Hyper-V enabled at the time of the 1607 upgrade.
      This is something happening with every upgrade that I know and the behaviour is quite consistent with what I have observed previously.

    • #16581 Reply


      Well, Windows 10 AU (1607) was a clean install and there were no network stack issues until the recent ‘December’ update. Whatever, Microsoft still fails to deliver a stable Windows 10 version and more and more things are broken after each update. Since September (thanks to their ‘carefully tested’ Windows updates), the machines here (Dell, Samsung, …) won’t even boot into the desktop (local session manager hangs on start) after applying Windows updates, and it takes several ‘hard’ reboots to get the shiz back working. It’s remarkable that a multi-billion dollar company is able to mess up a stable product, but not to fix the junk they ship.

    • #16582 Reply


      I had an odd problem with KB3206632: it disabled the start menu, network access, volume control, and notifications on my task bar. Cortana, task view, pinned icons, language selector, and system tray expander all normally.
      I hoped that KB3213522 would solve this, but it did not. It causes the same problem. Have you heard anything like this?

    • #16583 Reply


      It comes on WSUS now, but not on Windows Update as far as I can tell.
      I think there is no reason to install if KB3206632 is installed successfully.

    • #16584 Reply


      Sorry, I thought that when you said the latest update it was about the upgrade to 1607, as I experienced what you described during those upgrades. So the December 2016 update may have as side effect breaking Hyper-V networking.
      As I said in my previous post, I stopped using Hyper-V exactly for those reasons, but I also know that Wi-Fi networking is generally not supported in Bridged mode and as I use Wi-Fi…
      Agree that Windows 10 has too many issues and I would add that Windows 2016 Server which was promoted as CBB recently in addition to CB and LTSB has other important unresolved issues as well.

    • #16585 Reply


      You might try a repair install with an in-place upgrade…

    • #16586 Reply


      Try to configure the settings under Setting applet – System – Display, notifications, apps, power/Notifications and actions.
      Do you use any third party application like CCleaner or Classic Shell or Windows 10 tuning applications?

    • #16587 Reply


      To be clear for the end-user, that would involve reinstalling the OS and should be used as a last resort solution.
      It is a bit too much for something that may happen again in the future and it is far better to learn how to fix it if at all possible.

    • #16588 Reply


      jmwoods – Thank you, but a reset is unnecessary. I use Programs and Features control panel to uninstall the update and restore functions.
      ch100 – More than just notifications fail and I see no Settings for those other lost functions. Of the third party applications you mention, I run CCleaner on demand to clean things up but I quit it when finished. I do not let it run continuously.

      Microsoft lists the 6 updates in the KB3213522 cumulative update. When I have a bit more time I will load each update to learn which of the 6 is the root cause.

    • #16589 Reply


      Server 2016 is LTSB only πŸ™‚

    • #16590 Reply


      I was wondering if CCleaner made some changes to registry keys sometime in the past which may affect that behaviour now.
      This was the purpose of asking for third-party applications.
      The behaviour which you see does not appear to be typical for any of the recent patches, as I didn’t see it mentioned here.
      Woody may have better information though.

    • #16591 Reply


      “I had an odd problem with KB3206632: it disabled the start menu, network access, volume control, and notifications on my task bar. Cortana, task view, pinned icons, language selector, and system tray expander all normally.
      I hoped that KB3213522 would solve this, but it did not. It causes the same problem.”

      Two different KB’s causing multiple issues…

      Unless there is a clean, recent disk image to restore from (including current user data), I would recommend a repair install with an in-place upgrade.

      To be even more clear, the downsides are…

      System Protection will be reset to the default of being turned off. It is recommended to turn on system protection after the repair install has finished to have restore points.
      You will lose any custom fonts.
      You will lose any customized system icons.
      You may need to re-establish your Wi-Fi connection.
      You will need to redo Windows updates subsequent to the build you have used for the repair install.
      Windows.old will be created.
      You will need to redo any language downloads including the display language if you changed that.

    • #16592 Reply


      Sorry, you are right.
      I was thinking about Windows 10 1607 πŸ™‚

    • #16593 Reply


      After doing the millionth time testing in relation to Windows 10 patching, I realised that what causes the known problem with 45%, 90% or another random number in the WU user interface is the so called Express package for each patch, which Microsoft believes to be the way to go to reduce the WU size and install only deltas.
      The Windows 10/2016 Update Agent is broken as it was mentioned on one of the Technet blogs, but it is not clear from the blog how exactly it is broken.
      It is claimed in few places that after installing KB3189866 manually, the issue is fixed. It is not and I cannot even find KB3189866 as it appears to be expired by Microsoft.

      The solution which works is all instances is to download the full package and install manually.
      The other solution for those with WSUS is to synchronise the full package and not to synchronise the Express packages or directly from Microsoft, which is the same with synchronising the Express packages.
      Windows update is normally providing the Express packages and will have the same problem until the WU Agent is fixed.

      Note: If the installation gets stuck to one of the random percentages mentioned above, the only reliable recovery method is to reset the SoftwareDistribuiton folder first and then install manually or from WSUS using the full package.

      How to reset SoftwareDistribution (WU cache)

      1. Stop Windows Update and BITS services
      2. Delete C:WindowsSoftwareDistribution folder with everything inside
      3. Start Windows Update and BITS services or even better restart the machine.

    • #16594 Reply


      In my particular case, it seems that it was a problem with my OS installation.Subsequent to this posting, I learned that my App Store app was broken in this same local user account and a day-an-a-half of futzing did not cure. I finally decided to accept jmwoods advice and reset. Reset failed. So I tried an in-place restore. Restore failed. I had to download the ISO and perform a clean install to get Windows 10 1607 back.

      On the clean install, KB3206632 installed normally.

      Thanks to all who responded. I appreciate it.

    • #16595 Reply


      @RichardP Thanks for feedback and glad that it is resolved, although you had to take the hammer approach to it. πŸ™‚

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Microsoft sneaks out largely undocumented hotfix for Windows 10, build 14393.577

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.

    Your information: