Microsoft releases Windows 10 build 17134.753, 16299.1127 - here's what's new

Patch Tuesday was over two weeks ago, and that means that it's time for more cumulative updates. Today, Microsoft released updates for every version of Windows 10 with the exception of the newest one, version 1809.

As usual, these updates contain a long list of fixes, longer than the actual Patch Tuesday updates. They're optional, and you won't receive them on your PC unless you manually check for updates and install them manually. If you don't take them, these fixes will be included in the next Patch Tuesday updates, which are mandatory.

If you're on the Windows 10 April 2018 Update, or version 1803, you're going to get KB4493437, which brings the build number to 17134.753. You can manually download it here, and it contains the following fixes:

  • Addresses an issue that causes Internet Explorer to block a sub-resource download when its loaded over the HTTP protocol on a page hosted over the HTTPS protocol.

  • Addresses an issue that may prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.

  • Allows the built-in Administrator account to run Microsoft Office setup after downloading the installer in Microsoft Edge.

  • Addresses an issue that may cause the loss of Favorites or the Reading List in Microsoft Edge after updating the operating system.

  • Addresses an issue that disables the new App Container feature for Microsoft Office.

  • Addresses an issue that prevents certain apps from launching when you set folder redirection for the Roaming AppData folder to a network path.

  • Addresses an issue that causes the removal of the Microsoft Office desktop app to stop responding and blocks the installation of a newer version of the app.

  • Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.

  • Addresses an issue that causes ShellExperienceHost.exe to stop working when the start date for the Japanese Era is not on the first day of the month. For more information, see KB4469068.

  • Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.

  • Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.

  • Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.

  • Updates fonts to support the new Japanese Era. For more information, see KB4469068.

  • Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.

  • Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.

  • Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.

  • Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.

  • Addresses an issue that causes the error, “0x3B_c0000005_win32kfull!vSetPointer" when the kernel mode driver, win32kfull.sys, accesses an invalid memory location.

  • Addresses an issue that may cause the UI to stop responding for several seconds when scrolling in windows that have many child windows.

  • Addresses an issue that may cause a touch screen to stop working after restart.

  • Allows existing devices that are managed by Configuration Manager to be enrolled in Microsoft Intune using Co-management without any user interaction. It does not require an active user to be logged in, and there are no Multi Factor Authentication (MFA) prompts. This update also allows the Co-managed mobile device management (MDM) enrollment to use the device credential it received when the device is enabled to join Hybrid Azure Active Directory (AADJ).

  • Addresses an issue that prevents BitLocker from encrypting a removeable drive when there is no connectivity to store the recovery key in Active Directory or Azure Active Directory.

  • Addresses a gradual memory leak in LSASS.exe on systems that have cached logon enabled. This issue mainly affects servers that process many interactive logon requests, such as web servers.

  • Addresses an issue that may allow a user to continue logging on to an account using a smart card after disabling the account.

  • Addresses an issue that prevents access to enterprise resources when using Kerberos with Windows Hello for Business (WHfB) credentials. This causes users to receive multiple prompts to provide their credentials.

  • Addresses an issue that slows server performance or causes the server to stop responding because of numerous Windows firewall rules. To enable the changes, add a new registry key “DeleteUserAppContainersOnLogoff” (DWORD) on “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy” using Regedit, and set it to 1.

  • Addresses an issue with Always-On VPN exclusion routes that only work for link-local exclusions.

  • Addresses boot failure issues that occur when you restart certain hyperconverged infrastructure (HCI) virtual machines.

  • Addresses an issue that causes a roaming profile user to lose customized Start menu settings after upgrading the operating system (OS). After installing this update, administrators must enable the UseProfilePathMinorExtensionVersion registry setting described in KB4493782 for roaming user profiles (RUP). This key allows you to create a new RUP for an upgraded OS and prevents the loss of a custom Start menu. The RUP must be stored locally, and you must restart the device to enable the feature.

  • Addresses an issue that causes connection requests to the Remote Desktop Session Host (RDSH) servers in the deployment to fail. This issue occurs because of a deadlock in the Connection Broker.

  • Improves results when provisioning printers in educational environments that include multifunction printers.

  • Addresses an issue that prevents access to Server Message Block (SMB) shares on or from SMB-enabled physical or virtual network interface cards (NIC) that are configured with a virtual private network (VPN) interface.

  • Addresses an issue that prevents Print Workflow Applications from launching for Point and Print.

  • Addresses an issue that may prevent Universal Windows Platform (UWP) apps from receiving keyboard input when its user interface thread becomes too busy. This issue occurs when the UWP app has an embedded WebView control.

This update also includes two known issues to be aware of:

Symptom Workaround
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.

To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:

Option 1:
Open an Administrator Command prompt and type the following:

Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No

Option 2:
Use the Windows Deployment Services UI.

  1. Open Windows Deployment Services from Windows Administrative Tools.
  2. Expand Servers and right-click a WDS server.
  3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.

Option 3:
Set the following registry value to 0:

“HKLM\System\CurrentControlSet\Services\WDSServer\ Providers\WDSTFTP\EnableVariableWindowExtension”.

Restart the WDSServer service after disabling the Variable Window Extension.

Microsoft is working on a resolution and will provide an update in an upcoming release.

Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.

Do one of the following:

  • Perform the operation from a process that has administrator privilege.
  • Perform the operation from a node that doesn’t have CSV ownership.
Microsoft is working on a resolution and will provide an update in an upcoming release.


Those on the Windows 10 Fall Creators Update, or version 1709, will get KB4493440, bringing the build number to 16299.1127. This version, along with earlier versions, is unsupported for Windows 10 Home and Pro, so you'll only get this update if you're on Education or Enterprise. You can manually download it here, and it contains the following fixes:

  • Addresses an issue that causes Internet Explorer to block a sub-resource download when its loaded over the HTTP protocol on a page hosted over the HTTPS protocol.

  • Addresses an issue that may prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.

  • Allows the built-in Administrator account to run Microsoft Office setup after downloading the installer in Microsoft Edge.

  • Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.

  • Addresses an issue that causes ShellExperienceHost.exe to stop working when the start date for the Japanese Era is not on the first day of the month. For more information, see KB4469068.

  • Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.

  • Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.

  • Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.

  • Updates fonts to support the new Japanese Era. For more information, see KB4469068.

  • Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.

  • Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.

  • Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.

  • Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.

  • Enables a touch keyboard to support new Japanese Era characters. For more information, see KB4469068.

  • Addresses an issue that causes the error, “0x3B_c0000005_win32kfull!vSetPointer" when the kernel mode driver, win32kfull.sys, accesses an invalid memory location.

  • Addresses an issue that causes a device to stop working when logging on or off if the device is running antivirus, endpoint detection and response software.

  • Addresses an issue that may cause a touch screen to stop working after restart.

  • Addresses a gradual memory leak in LSASS.exe on systems that have cached logon enabled. This issue mainly affects servers that process many interactive logon requests, such as web servers.

  • Addresses an issue that may allow a user to continue logging on to an account using a smart card after disabling the account.

  • Addresses an issue that prevents access to enterprise resources when using Kerberos with Windows Hello for Business (WHfB) credentials. This causes users to receive multiple prompts to provide their credentials.

  • Addresses an issue in which Windows Management Instrumentation (WMI) policy provider (PolicySOM) consumes all available dynamic User Datagram Protocol (UDP) ports. This causes the affected machines to become unresponsive.

  • Addresses an issue that causes a roaming profile user to lose customized Start menu settings after upgrading the operating system (OS). After installing this update, administrators must enable the UseProfilePathMinorExtensionVersion registry setting described in KB4493782 for roaming user profiles (RUP). This key allows you to create a new RUP for an upgraded OS and prevents the loss of a custom Start menu. The RUP must be stored locally, and you must restart the device to enable the feature.

  • Improves results when provisioning printers in educational environments that include multifunction printers.

This update only has one known issue:

Symptom Workaround
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.

Do one of the following:

  • Perform the operation from a process that has administrator privilege.
  • Perform the operation from a node that doesn’t have CSV ownership.
Microsoft is working on a resolution and will provide an update in an upcoming release.


Users on the Windows 10 Creators Update, or version 1703, will get KB4493436, bringing the build number to 15063.1784. You can manually download it here, and it contains the following fixes:

  • Addresses an issue that causes Internet Explorer to block a sub-resource download when its loaded over the HTTP protocol on a page hosted over the HTTPS protocol.

  • Addresses an issue that may prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.

  • Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.

  • Addresses an issue that causes ShellExperienceHost.exe to stop working when the start date for the Japanese Era is not on the first day of the month. For more information, see KB4469068.

  • Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.

  • Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.

  • Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.

  • Updates fonts to support the new Japanese Era. For more information, see KB4469068.

  • Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.

  • Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.

  • Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.

  • Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.

  • Addresses an issue that causes the error “0x3B_c0000005_win32kfull!vSetPointer" when the kernel mode driver, win32kfull.sys, accesses an invalid memory location.

  • Addresses an issue that may cause a touch screen to stop working after restart.

  • Addresses a gradual memory leak in LSASS.exe on systems that have cached logon enabled. This issue mainly affects servers that process many interactive logon requests, such as web servers.

  • Addresses an issue that may allow a user to continue logging on to an account using a smart card after disabling the account.

  • Addresses an issue that prevents access to enterprise resources when using Kerberos with Windows Hello for Business (WHfB) credentials. This causes users to receive multiple prompts to provide their credentials.

  • Addresses an issue that occasionally causes a PostScript printer to use the wrong font.

  • Addresses an issue in which Windows Management Instrumentation (WMI) policy provider (PolicySOM) consumes all available dynamic User Datagram Protocol (UDP) ports. This causes the affected machines to become unresponsive.

  • Addresses an issue that causes a roaming profile user to lose customized Start menu settings after upgrading the operating system (OS). After installing this update, administrators must enable the UseProfilePathMinorExtensionVersion registry setting described in KB4493782 for roaming user profiles (RUP). This key allows you to create a new RUP for an upgraded OS and prevents the loss of a custom Start menu. The RUP must be stored locally, and you must restart the device to enable the feature.

This build has the same known issue as the one for version 1709.

Next up is KB4493473, which brings the build number to 14393.2941 for users of Windows 10 version 1607 or Windows Server 2016. You can manually download it here, and it contains the following fixes:

  • Addresses an issue that causes Internet Explorer to block a sub-resource download when its loaded over the HTTP protocol on a page hosted over the HTTPS protocol.

  • Addresses an issue that may prevent Custom URI Schemes for Application Protocol handlers from starting the corresponding application for local intranet and trusted sites on Internet Explorer.

  • Addresses an issue that prevents the CALDATETIME structure from handling more than four Japanese Eras. For more information, see KB4469068.

  • Addresses an issue that causes ShellExperienceHost.exe to stop working when the start date for the Japanese Era is not on the first day of the month. For more information, see KB4469068.

  • Updates the NLS registry to support the new Japanese Era. For more information, see KB4469068.

  • Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format. For more information, see KB4469068.

  • Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era. For more information, see KB4469068.

  • Updates fonts to support the new Japanese Era. For more information, see KB4469068.

  • Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character. For more information, see KB4469068.

  • Addresses an issue that causes the Clock and Calendar flyout control to display the day of the week incorrectly mapped to a date in the month of the new Japanese Era. For more information, see KB4469068.

  • Adds alternative fonts for the new Japanese Era fonts. For more information, see KB4469068.

  • Enables Text-To-Speech (TTS) functionality to support new Japanese Era characters. For more information, see KB4469068.

  • Addresses an issue in Gdi32full.dll that causes an application to stop responding.

  • Addresses a gradual memory leak in LSASS.exe on systems that have cached logon enabled. This issue mainly affects servers that process many interactive logon requests, such as web servers.

  • Addresses an issue that causes Lightweight Directory Access Protocol (LDAP) client applications to stop responding for at least 30 seconds when many LDAP queries are requested through multiple connections. This occurs because of a race condition in wldap32.dll. You must install this update on the LDAP client that calls wldap32.dll.

  • Addresses an issue that may prevent Cluster Aware Update from restarting nodes when a cluster's credentials are reset. Cluster Aware Update must restart nodes after installing an update. The error is the following:

  • ”Failed to restart "NODENAME": (ClusterUpdateException) Failed to restart "NODENAME": (Win32Exception) The user name or password is incorrect.”

  • Addresses an issue that may cause Microsoft Cluster Shared Volumes File Systems (CSVFS) to stop working under certain conditions.

  • Addresses an issue with setting up a Storage Replica in a Scale-Out File Server with a Storage Spaces Direct cluster. Using Test-SRTopology to query multiple volumes when the Primary DNS suffix is different than the domain name may cause the query to fail with a null reference exception in GetPartitionInStorageNodeByAccessPath.

  • Addresses an issue that may cause error 0x7E to occur when adding a node to an Exchange Database Availability Group server.

  • Addresses an issue that causes slow screen refresh rates when an application creates and destroys many child windows.

  • Addresses an issue that causes connection requests to the Remote Desktop Session Host (RDSH) servers in the deployment to fail. This issue occurs because of a deadlock in the Connection Broker.

  • Addresses an issue that occasionally causes a PostScript printer to use the wrong font.

  • Addresses an issue that fails to enumerate devices that have 64-bit base address registers and are assigned to virtual machines. This issue also prevents Windows from detecting these devices. This issue occurs on hosts that have the Hyper-V role enabled.

This one has four known issues:

Symptom

Workaround

For hosts managed by System Center Virtual Machine Manager (SCVMM), SCVMM cannot enumerate and manage logical switches deployed on the host after installing the update.

Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.
  1. Run mofcomp on the following mof files on the affected host:
    1. Scvmmswitchportsettings.mof
    2. VMMDHCPSvr.mof
  2. Follow the best practices while patching to avoid a stop error in vfpext.sys in an SDN v2 environment (NC managed hosts).
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.

Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters.

Microsoft is working on a resolution and will provide an update in an upcoming release.

After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.

To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:

Option 1:
Open an Administrator Command prompt and type the following:

Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No

Option 2:
Use the Windows Deployment Services UI.

  1. Open Windows Deployment Services from Windows Administrative Tools.
  2. Expand Servers and right-click a WDS server.
  3. Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.

Option 3:
Set the following registry value to 0:

“HKLM\System\CurrentControlSet\Services\WDSServer\ Providers\WDSTFTP\EnableVariableWindowExtension”.

Restart the WDSServer service after disabling the Variable Window Extension.

Microsoft is working on a resolution and will provide an update in an upcoming release.

Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.

Do one of the following:

  • Perform the operation from a process that has administrator privilege.
  • Perform the operation from a node that doesn’t have CSV ownership.
Microsoft is working on a resolution and will provide an update in an upcoming release.


Finally, KB4498375 is for the original version of Windows 10, now known as 1507. It brings the build number to 10240.18187, you can manually download it here, and it contains the following fixes:

  • Addresses an issue that prevents an input method editor (IME) from supporting the new Japanese Era character.

  • Updates the NLS registry to support the new Japanese Era.

  • Addresses an issue that causes the DateTimePicker to display the date incorrectly in the Japanese date format.

  • Addresses an issue that causes the Date and Time Settings control to cache old Eras and prevents the control from refreshing when the time enters the new Japanese Era.

  • Updates fonts to support the new Japanese Era.

This update only includes one known issue, and it's the same one as the update for versions 1703 and 1709.

Report a problem with article
1548949498_du6c-k9v4aamv91
Next Article

Nintendo kicks off registration for Mario Kart Tour's closed beta testing

1501541244_titanfall_2
Previous Article

Respawn delays "future Titanfall games" to focus on Apex Legends development

15 Comments - Add comment

Advertisement