Download KB5005103 Offline Installer, Windows 10 v1909

Microsoft released the optional update KB5005103 with several improvements and fixes. Here are the direct links to download KB5005103 offline installer.

Out of the blue, Microsoft released a new optional update called KB5005103 for Windows 10 v1909 users. Compared to other optional updates released recently, the KB5005103 update is pretty small regarding what it does and fixes. Mainly, the KB5005103 update fixes the MP4 file format playback issues in the Windows 10 Movies & TV app. In addition to that, the update also fixes a OneDrive issue where the “Known folders only” option is frequently resetting.

Other fixes and improvements in the update include but or are not limited to fix for WinRM service, window minimize issues, issues with Windows Defender Exploit Protection, bugs in Microsoft Input Indicator, issues with robocopy command, and more. As always, you can find the full list of fixed issues and improvements down below.

Like with any optional update, you don’t have to install it mandatorily. In fact, Windows 10 won’t download the update unless you click the download and install link on the Windows Update page. That being said, the fixes and improvements in this update will eventually be included in the regular cumulative updates, which are installed automatically. If the Windows Update is causing problems or if you are unable to install the update for whatever reason, download KB5005103 offline installer using the links provided below.

Download KB5005103 offline installer

As always, the KB5005103 update is available as an offline installer via the Microsoft Update Catalog website.

Go to this webpage, find your Windows 10 version and click the “Download” button next. Another window or tab will open. Here, click the available link, and the offline installer is downloaded to your computer. After downloading, double-click on the installer and follow the wizard to install KB5005103. Remember that the update will only install if it is supported. Also, it might download additional updates or dependencies, if required.

KB5005103 changelog

  • Addresses an issue that prevents users from tracking Distributed Component Object Model (DCOM) activation failures.

  • Addresses a threading issue that might cause the Windows Remote Management (WinRM) service to stop working when it is under a high load.

  • Addresses an issue that causes the Windows Management Instrumentation (WMI) provider host process to stop working. This occurs because of an unhandled access violation that occurs when using the Desired State Configuration (DSC).

  • Addresses an issue that causes file migration between Distributed File System (DFS) paths that are stored on different volumes to fail. This issue occurs when you implement the migration using PowerShell scripts that use the Move-Item command.

  • Addresses an issue that prevents you from writing to a WMI repository after a low memory condition occurs.

  • Addresses an issue that might prevent you from minimizing an application that uses unthemed windows.

  • Addresses an issue that prevents the Windows Movies and TV app from playing .mp4 media files that contain Pixel Aspect Ration (PAR) information.

  • Addresses an issue that causes Authentication Mechanism Assurance (AMA) to stop working. This issue occurs when you migrate to Windows Server 2016 (or newer versions of Windows) and when using AMA in conjunction with certificates from Windows Hello for Business.

  • Addresses an issue that prevents Secure Launch from working on some devices.

  • Addresses an issue that prevents Code Integrity rules from working correctly when specifying Package Family Name rules in a Code Integrity policy. This issue occurs because of the incorrect handling of case-sensitive names.

  • Addresses an issue that prevents the ShellHWDetection service from starting on a Privileged Access Workstation (PAW) device and prevents you from managing BitLocker drive encryption.

  • Addresses an issue in Windows Defender Exploit Protection that prevents some Microsoft Office applications from working on machines that have certain processors.

  • Addresses an issue that causes the Input Method Editor (IME) toolbar to appear even when the Remote App is closed.

  • Addresses an issue with a critical exception that the Open File dialog fails to handle. As a result, a Microsoft Foundation Class (MFC) application unexpectedly closes.

  • Addresses an issue that might occur when you configure the policy, “Delete user profiles older than a specified number of days on system restart”. If a user has been signed in for longer than the time specified in the policy, the device might unexpectedly delete profiles at startup.

  • Addresses an issue with the Microsoft OneDrive sync setting “Always keep on this device”. The setting is unexpectedly reset to “Known folders only” after you install a Windows update.

  • Addresses an issue that might create duplicate built-in local accounts, such as administrator or guest account, during an in-place upgrade. This issue occurs if you previously renamed those accounts. As a result, the Local Users and Groups MMC snap-in (lusrmgr.msc) appears blank with no accounts after the upgrade. This update removes the duplicate accounts from the local Security Account Manager (SAM) database on the affected machines. If the system detected and removed duplicate accounts, it logs a Directory-Services-SAM event, with ID 16986, in the System event log.

  • Increases the default number of entries in the local security authority (LSA) Lookup Cache to improve lookup performance in high lookup volume scenarios.

  • Addresses stop error 0x1E in srv2!Smb2CheckAndInvalidateCCFFile.

  • Addresses an issue that might cause a system to stop working after a deduplication filter detects damage in a reparse point. This issue occurs because of deduplication driver changes introduced in a previous update.

  • Addresses an issue with using the robocopy command with the backup option (/B) to fix data loss. This issue occurs when the source location contains tiered Azure File Sync files or tiered Cloud Files.

  • Stops running queries against OneSettings APIs from the obsolete Storage Health feature.

That’s it.

Leave a Comment

Scroll to Top