Microsoft releases Windows 10 build 19043.1348 – here’s what’s new

Microsoft releases Windows 10 build 19043.1348 – here’s what’s new

As tends to happen on the second Tuesday of every month, Microsoft is releasing new updates for every supported version of Windows. That includes Windows 11, of course, but also a few versions of Windows 10. The only versions of Windows 10 that are still supported for consumer SKUs are 21H1, 20H2, and 2004, which are getting updated to build 19043.1348, 19042.1348, and 19041.1348, respectively.

The update itself is the same for all three versions, and it’s labeled KB5007186. You can download it manually here. This update is the same because these three versions of Windows 10 are essentially the same, albeit newer versions have some features enabled compared to older ones. As such, they get the exact same bits with each cumulative update.

Windows 10 build 19043.1348 and its equivalents don’t include a very descriptive list of fixes. The highlights section of the support page only mentions general security updates to Windows, and the full list of fixes includes a single item:

  • Addresses an issue of a 0 (zero) width Pen to render one pixel regardless of transformation.

However, this update does come with a few known issues, although some of them have been mitigated or have relatively easy workarounds. You can check the full list below.

Known issues in Windows 10 build 19043.1348

SymptomWorkaround
Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later.

Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps.

To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the using SSU:

  1. Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path>
  2. Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>
  3. You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU.

If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.

After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, “PSFX_E_MATCHING_BINARY_MISSING”.For more information and a workaround, see KB5005322.
After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, “Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials.” and “The login attempt failed” in red.This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to non-managed personal devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy linked below.

Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.

Group Policy installation files:

Important Verify that you are using the correct Group Policy for your version of Windows.

After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server:

  • 0x000006e4 (RPC_S_CANNOT_SUPPORT)
  • 0x0000007c (ERROR_INVALID_LEVEL)
  • 0x00000709 (ERROR_INVALID_PRINTER_NAME)

Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are more commonly found in enterprises and organizations.

For workarounds and the latest status for this issue, please see Windows release health:

We are presently investigating and will provide an update in an upcoming release.

While Windows 10 versions 21H1, 20H2, and 2004 are the only officially supported releases for consumer SKUs, Microsoft still supports some older versions of Windows 10 in specific channels. If you’re an enterprise or education user, you can find the updates for the different supported versions below.

Windows 10 versionBuild numberKB articleDownload linkSupported editions
190918363.1916KB5007189Update CatalogEnterprise and Education
180917763.2300KB5007206Update CatalogLTSC
160714363.4770KB5007192Update CatalogLTSB
150710240.19119KB5007207Update CatalogLTSB

Even with Windows 11 already out, Microsoft will continue to support Windows 10 through October 2025, so you have plenty of time before you need to upgrade. Specific versions will fall out of support over time, though, so you’ll need to at least be on the latest version of Windows 10.

About author

João Carrasqueira
João Carrasqueira

Writer at XDA Computing. I've been covering the world of technology since 2018, but I've loved the field for a lot longer. And I have a weird affinity for Nintendo videogames, which I'm always happy to talk about.