Windows 10 V1607: Mysterious Update KB4033637

[German]It seems that some users or Windows 10 Anniversary Update (Version 1607) are receiving Update KB4033637. The purpose of this update is unknown, there is no KB article yet. But I have my theory. [Addendum: MS has released a KB article, explaining the purpose of this update.]


Advertising

A reader pointed me to Update KB4033637

A couple of hours ago I blogged about Update KB4039396 (Windows 10 Anniversary Update, Update KB4039396), released on August 28, 2017. Then I received a comment (German) from a blog reader:

Gerade kam das Update KB 4033637 Windows 10 V1607 keine Ahnung was das wieder ist!

He received Update KB4039396, but there is no KB article about this update. That's not new, Microsoft says 'trust us …'

Searching the web, not enlightened

Searching the web, I found some mentions of this update in July and August.

  • July 14, 2017: The MS-Answers forum entry Failed to install – over 20 times! What is going on? is the first mention I found. An MVP colleague mentioned, that Update KB4033637 isn't distributed via Microsoft Update nor via Microsoft Update Catalog.
  • July 25, 2017: In MS-Answers forum somebody started the thread Windows 10 Update KB4033637, asking for the purpose of this update. A MS employee asked, why he asked this question, without giving further details.But it seems to mysterious, that the poster mentioned Windows 10 Version 1703 and says it updated the build to 15063.483. This build is available via Update KB4025342.
  • Within the thread linked above, some other users reporting issues like freezes, missing USB, missing WiFi (OS Build is 14393.1593), slow machines, crashes and so on.

Reading the combination of issues given above created some doubt on my side about the expertise of the posters. Maybe they had a typo within the KB number. But I found other hits within the internet:

  • July 27, 2017: The MS-Answers forum entry KB4033637 fails to update reported install issue. Another (French) user wrote, that KB4033637 for Windows 10 V1607 hangs at 45 % during download.
  • August 28, 2017: At Bleeping Computer we have a forum entry, also asking, what this update do and why there is no KB article.
  • August 29, 2017: A japanese article also mentions this update.  And some people at reddit.com discussing about that update.

I have absolutely no details, what this update is for – but wait, there is more, because the update is for real.


Advertising

Addendum: Searching within the fog

I booted a virtual machine with Windows 10 V1607 and after searching endless, the update was announced:

Update KB4033637 Windows 10 V1607

The update was successfully downloaded and then the installation went through. Then I received a restart notification.

Update KB4033637 Windows 10 V1607 Restart

After a restart, the VM was a bit slow (but that's maybe, what I awaited, after reading the comments mentioned above – a kind of placebo).

One user posted a screenshot within a forum, indicating an install date 01.01.1601 for this update. I guess, something is broken on his system. My test machine shows an install date 29.8.2017 in Installed updates history. This update isn't a Servicing Stack update, because KB4033637 can be uninstalled.

After login the machine suddenly showed me the following message (maybe it's coincidence):

Windows 10 privacy settings notification

Windows 10 Anniversary Update (V1607) asked me to check the privacy settings. And suddenly Update KB4033637 makes sense and explains, why people has seen this update in July 2017.

My guess: Update KB4033637 contains code to show users of Windows 10 Anniversary Update (V1607) the dialog above to check the privacy settings, making the system ready to upgrade to Creators Update. I've covered that within my German blog post Windows 10: Datenschutz-Infosplitter … in July 2017.

Digging deeper

But the update is listed in Windows 10 update history as a security update – so there is more in stack. I inspected Windows subfolder Softwaredistribution\ Download.

It's also possible to visit this page and download the package from July 2017 for an analysis.

The folder Downloads contains some empty sub-folders with x86_microsoft-windows-compat-appraiser or windows-a..rience-program-data with it's names. And I found sub-folders with XML files (BlockingMap.xml) containing IDs from apps or devices not compatible, I guess.

  • compat-appraiser has something to do with checking the compatibility before upgrade.
  • windows-a..rience-program seems to be related to Windows user experience program, and has to do with telemetry.

My impression is, that this updates distribute new metadata to improve compatibility check via Compatibility Appraiser. And maybe it updates data to gain telemetry entries. A short discussion may be found at MS Answers forum.

So it seems, this update prepares the system for an upgrade to Windows 10 (Fall) Creators Update (V1703 or V1709). [Addendum: At askwoody.com is a discussion, coming to similar conclusion as raised above – but the privacy settings notification seems to bee coincidence. Woody mentioned a tweet, that UAC was changed to notify a user when apps try to make change and also that win defender tried to reset chrome settings.] Unfortunately, as long as Microsoft refuse to document the details, there is room for conspiracy theories. Do you have other/further insights? Feel free to left a comment.

Addendum: KB-Article finally published

Ok, on August 30, 2017, Microsoft published details about Update KB4033637 (Updates to Windows 10, Version 1607 for update applicability: August 30, 2017). They wrote:

This update includes diagnostic and functional improvements for determining the applicability of updates in Windows 10 Version 1607. The files and resources in this update ensure that feature updates are installed seamlessly to improve the reliability and security of Windows 10.

Devices will automatically get the update downloaded and installed through Windows Update. So overall it proves most of my theories revealed above.

BTW: Just a case of obscurity has been documented at askwoody.com. User nt1996 published some explanation from Microsoft's premier support. He wrote:

I opened a case with MS Premier Support yesterday and got this response:

"The update contains bug fixes to the update system to help enable machines to get current, either to a current LCU or upgrade to Creators Update (1703). It doesn't force it, or change the experience/behavior, it enables more machines to successfully go through the process. It is an Update Stack Package with DTE and Appraiser for RS1.

But due to some issues, the update is not yet published to the catalog and there is no public facing KB article for now. I don't have any info on the issues other than they are being worked on and there will be public info published for the update and it will be published to the catalog."

Does anyone know what "an Update Stack Package with DTE and Appraiser for RS1" means (I am assuming RS1 is Redstone 1 aka Win10 Anniversary Update aka Win10 build 1607.

Funny thing (and I am still waiting an answer from MS on this): my machines got this KB4033637 but our WSUS did not sync it down from Microsoft!  So I don't know if there is a group policy setting that is somehow allowing my machines (and by extension the machines in our enterprise) to get patches directly from Microsoft.  That would not be cool.

It's unbelievable! There are some additional explanations from Mr Brian (thanks for your tips), revealing, what's changed with Update KB4033637. I would say, we are now reaching the days, where foreign blogs and websites contains earlier far more detailled (and accurate) information about patches, than Microsoft publishes. And this company says 'Trust us, we know which updates are good for you'.


Cookies helps to fund this blog: Cookie settings
Advertising


##1

This entry was posted in Update, Windows and tagged , , . Bookmark the permalink.

15 Responses to Windows 10 V1607: Mysterious Update KB4033637

  1. Pingback: Undocumented KB 4033637 pushed onto Win10 1607 machines @ AskWoody

  2. Noel Burgess says:

    This update reverted my machine from 14393.1613 to 14393.1593, the first time it's ever gone backwards. It also disabled my keyboard.

    What happened to KB4039396, that should have updated to build 1670?

  3. Pingback: Microsoft patch alert: Outstanding problems with recent updates – Nocturnal Zine

  4. Advertising

  5. Pingback: Microsoft patch alert: Outstanding problems with recent updates – Computer Security Articles

  6. Sara Muller says:

    Nice theories, but I do propose a different solution:

    Actually I started searching for info about KB4033637 because after the previous update I experienced many problems with my system (will not enter sleep mode, takes ages to shut down, does not start up) and after this update it worked fine again!
    So I was curious to see whether Microsoft would confess that they resolved these rather nasty issues. And look: no info available.

    • guenni says:

      The article has been updated, MS has documented KB4033637 – but nothing what would explains issues with this update ;-)

      • Sara Muller says:

        No, and one issue at least is still there: computer does not start up properly (black screen with blinking blip).
        I will pray that Microsoft does something…

        • Sara Muller says:

          Issue probably was due to the GE Experience (display, in particular for games which I do not use) which needed an for me unneeded upgrade…

  7. Pingback: Microsoft patch alert: Outstanding problems with recent updates | Antivirus and Security news

  8. Pingback: Microsoft patch alert: Outstanding problems with recent updates - The Gizmo Effect

  9. krzemien says:

    Update installed (I did not check Windows version prior / after it happened) and no visible change seen, everything works as it used to. No sign of 1703 either though…

  10. Pingback: Les bugs touchant les derniers correctifs de Microsoft inquiètent les utilisateurs | France Actu

  11. Ma-Al-Tr says:

    Having problems with my video camera, not working at all for Skype video calls after this update (working properly before update) Camera is just off, but only with Skype. Have followed all Microsoft, Windows 10 & HP support instructions to fix it, without success. Anyone else having same issue?

    • guenni says:

      I've seen several posts mentions this issue. Currently the solution is: Uninstalling this update and block it's reinstallation.

  12. ust says:

    yes guys. i solved it.

    fresh install windows, disable win update forever, including services and whatnot

Leave a Reply to guenni Cancel reply

Your email address will not be published. Required fields are marked *