Windows 10: Issues with Updates KB4523786 and KB4522355

[German]On October 24, 2019, Microsoft released the optional update KB4522355 to fix the start menu and many other issues caused by previous update – and causes additional issues. In addition, an AutoPilot update KB4523786 has been planned to be rolled out for certain machines in the corporate environment, but that has gone wrong.


Advertising

Chaotic AutoPilot Update KB4523786

Windows AutoPilot  is a collection of technologies for setting up and pre-configuring new devices that can only be used in corporate environments. Effective October 24, 2019, Microsoft released KB4523786 (Cumulative Update for Autopilot in Windows 10 Version 1903, October 22, 2019). The update is optional, so it was only offered after an update search. The update is intended to bring some improvements and fixes for Windows 10 devices configured with Windows Autopilot.

Microsoft explicitly writes in the support article that this update will not be rolled out for Windows 10 Home. Even Windows 10 Pro will not receive the update if the device has not been prepared and registered for AutoPilot. That’s the theory I described last night in the blog post Windows 10 V1903: AutoPilot-Update KB4523786. Shortly after the article was published, users protested in my blog, because they were offered and installed this update on Windows 10 Home.

John wrote:
On my Windows 10 Home I also received the autopilot update (KB4523786). Strange!

Peter wrote:

The same goes for me.
I have Windows 10 Home 64 Bit Version 1903 (Built 18362.449 after updates).
The following updates were successfully installed:
KB4522741 Cumulative Update for .Net Framework 3.5 and 4.8
KB4523786 Windows Autopilot Update
and the optional:
KB4522355 Cumulative Update for Windows 10 Version 1903

Apparently Microsoft ‘opened the floodgates’ too wide for this update and distributed it with the watering can to all Windows 10 systems with version 1903, no matter which SKU was available. Theoretically, this should not be a problem, as the AutoPilot update remains unused on such machines. But it’s stupid when unused code floats around on the system – at some point there will be collisions. So you should uninstall the update via Control Panel -> Programs and Features -> Installed Updates.

Meanwhile Microsoft has blocked the AutoPilot update KB4523786 on 10/25/2019 again for distribution via Windows Update (see). Woody Leonhard revealed some more details in this ComputerWorld article. For example, a user in this post points out that the update is intended for lower-level TPM chips. This is also mentioned in the Microsoft support article. So the update is supposed to correct some problems like hangers by the TPM chip. Possibly the update distribution has been fixed to this TPM chip. Be that as it may, the Microsoft support articles claim something different than what the users see. But now the update should no longer be offered.

Addendum: Microsoft software engineer PaulSey has posted at Microsoft Answers this explanation, why the update was also spread to Windows 10 Home:


Advertising

A Windows Autopilot update, which was targeted as part of the out of box experience for new devices, was incorrectly offered to customers running Windows Home edition during regular scheduled Windows update scan. Once we became aware of the issue, we stopped distribution of the update. No action is required on your part.

So it was a mistake of Microsoft, but you don’t have to do anything else.

Update KB4522355 for Windows 10 Version 1903

Optional cumulative update KB4522355 was distributed on October 24, 2019 for Windows 10 version 1903 and to insiders with version 1909. It is intended to fix a number of bugs in the relevant Windows 10 versions (see Windows 10 V190x: Update KB4522355 released).

Bleeping Computer writes here, that the issues with some Intel and Broadcom Wi-Fi adapters has been fixed. But the upgrade block to Windows 10 V1903 has not yet been lifted, and some users report that their WLAN adapters are still not working.

It might also be helpful to have a fix to eliminate the high CPU load on Remote Desktop Connections (RDP). It also promises to fix the start menu problems caused by previous updates (see Windows 10: Fixes for October 2019 (start menu) issues). However, there are user objections.

  • In this German comment user JensDoe reported, that this update bricks his desktop search again.
  • In this German cKomment a 2nd user reported, that the update didn’t fix the bricked desktop search on his system.
  • User Darren reported here, that his broken start menu is still unfixed.

Somehow this update probably leaves some users open to ‘wishes’. Have you noticed any other problems?

Similar articles:
Windows 10 V190x: Update KB4522355 released
Windows 10 V1903: AutoPilot-Update KB4523786.
Windows 10 V190x: Update KB4522355 released
Windows 10 V1903: Update KB4517389 breaks Edge Browser [Fix]
Windows 10: Fixes for October 2019 (start menu) issues


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

8 Responses to Windows 10: Issues with Updates KB4523786 and KB4522355

  1. EP says:

    ask JensDoe if he’s using privacy tools like O&OShutup10 or Destroy Windows Spying (DWS) on his 1903 computer

  2. David says:

    I can’t even install KB4522355, i have tried 4 times and different times of day and all I get is Attempt failed, will try again later and error code 0x80073701, I have no idea what that means, it did install other updates fine, one for net framework & autopilot, also has installed windows defender updates fine, just not sure what the issue is with Kb4522355

    • guenni says:

      Error code 0x80073701 stands for ERROR_SXS_ASSEMBLY_MISSING and indicates a missing assembly. Such errors commonly ‘don’t fix themselves in the rules’. I had picked this up in the blog posts:

      Windows 10 V1903: Install errors with Update KB4512508
      Windows 10 V1903: Update install error 0x80073701 confirmed

      Currently I just found four to five cases, where users are affected by this install error. From this view I guess, it’s a damaged user client with a corrupt .NET Framework install (maybe caused by 3rd party antivirus software). The common trouble shooting (check for corrupted files, see Check and repair Windows system files and component store, use build-in Windows 10 update trouble shooter, reset Windows Update store etc.) won’t help/fix this issue.

      In some case it helps booting in safe mode, disable antivirus software, install the latest servicing stack update (SSU) and try to install the failed update again. If that doesn’t help, you can try to analyze the CBS.log file in C:WindowsLogsCBS. Maybe the missing files may be identified – and in this case, the broken previous update or .NET component may be uninstalled. In some cases language files are the cause for this issue. I’ve discussed some hints within my German blog post Windows Server 2016: Feature-Installation Fehler 0x80073701 and this German post shows, how to fix the issue by cleaning the registry from entries to missing assemblies.

      In other cases, maybe an inplace-upgrade will repair the botched references or the assembly store (see here).

  3. AE Carlson says:

    I have 4 Windows 10 machines that do not show my SAMBA server in Network anymore after this recent batch of updates. (October ’19). I can map folders on my server to drive letters, but I need the server to show up in Network. My backup software does not see the mapped drive letters, plus I have more than a couple of (critical) programs that need runtime folders or support folders set in order to work. These runtime folders are on the server so I can access them from multiple machines. (not anymore I guess). When I browse to set these programs up the drive letters are absent and the server is not listed in Network. I have tried every suggestion that I have seen on the net, but no luck. Spent the whole day, so finally did a system restore, still no luck, will see if a restore point earlier in time exists and try again. This was the update that removed Home Group, which I never used, but apparently there is no WORKGROUP anymore either, which might be the problem.

  4. Advertising

  5. N_stu says:

    KB4523786 has bricked two of my home machines with intel Motherboards! None of the windows support tools and fix options are working!

  6. six_tymes says:

    Have you used privacy tools like O&OShutup10 or Destroy Windows Spying (DWS) on your pc’s prior to this update ?

  7. EP says:

    I’m seeing a few recent reports that the KB4524570 update released on 11/12/2019 has really fixed the Start Menu and Search functions in 1903/1909.

    • guenni says:

      I got a few comments from German blog reader, asking for news about start menu issues, because it hasn’t been fixed. Mixed experiences.

Leave a Reply

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