Windows 10 Build 19044.1499 now available in Release Preview

Windows 10 Build 19044.1499 now available in Release Preview

No, we are not forgetting Windows 10. Microsoft’s old operating system has been behind it for 7 years and engineers continue to refine and improve it. We know that many of you are still using it and these are the news of this Build19044.1499 which will presumably be the February cumulative update.

What’s new in Windows 10 Build 19044.1499

  • Fixed an issue in Microsoft UI Automation that could cause Microsoft Outlook to stop working.
  • Updated daylight saving time to start in February 2022 instead of March 2022 in Jordan.
  • Fixed an issue that prevents the Windows Subsystem for Linux 2 (WSL2) localhost relay from starting when fast startup is enabled.
  • Added parameters passed to wmic.exe in telemetry to capture additional usage data to address application compatibility issues.
  • Fixed a problem in CLSID_InternetExplorer.
    Added a reminder to Internet Explorer 11 that notifies users of your upcoming withdrawal.
  • Fixed an issue that can sometimes cause Japanese Microsoft Office applications to stop working when using the new Japanese input method editor (IME).
  • Fixed an issue that caused apps to crash when typing text with the Chinese IME.
  • Fixed an issue that could cause Windows to crash when using the Pen Haptics API.
  • Updated phone number for Windows activation for locations that have an incorrect phone number.
  • Fixed an issue that causes a device to be incorrectly reported as not compliant with Conditional Access due to antivirus or firewall settings.
  • Fixed an issue that causes printing to stop or incorrect output to print when printing via USB in Windows 10, version 2004 or later.
  • Fixed an issue that affects the Remote Desktop display in some cases when using Advanced Video Coding (AVC) software encoding.
  • We fixed an issue that prevents certain surround sound audio from playing in Microsoft Edge.
  • Removed a crash on vpnike.dll and rasmans.dll.
  • Fixed an issue affecting the Fast Identity Online 2.0 (FIDO2) credential provider that prevented the PIN entry box from displaying.
  • They have fixed an issue that causes Windows to stop working and generate the error “IRQL_NOT_LESS_OR_EQUAL”.
  • Fixed an issue that could cause the Get-TPM PowerShell command to fail when trying to report the Trusted Platform Module (TPM). The command fails with error “0x80090011 Microsoft.Tpm.Commands.TpmWmiException,Microsoft.Tpm.Commands.GetTpmCommand”.
  • Fixed an issue that causes the Alt Gr key to stop working if a remote desktop client is running or if the RemoteApp has been disconnected.
  • Including a new feature that provides direct access to select your Microsoft Edge profiles from News & Interests. You can also go to Microsoft Edge directly from News & Interests in the same corresponding profile.
  • Added a new feature called Sync Your Settings for users migrating to Windows 11. We’ll use Sync Your Settings to automatically back up a list of your apps to your Microsoft account. We will then be able to quickly restore those apps to a Windows 11 device. This new feature will be rolling out in the coming weeks.
  • Fixed an issue that caused working Bluetooth devices to stop working when trying to connect to a non-working Bluetooth device.
  • Fixed an issue that caused lsass.exe to stop working and the device to reboot. This problem occurs when the Windows NT Directory Services (NTDS) counters are queried after the NTDS service has stopped.
  • Fixed an issue that caused the “Disallow compression on all NTFS volumes” Group Policy Object (GPO) not to be applied in some cases.
    We have fixed an issue that prevents Robocopy from retrying the file copy process.
  • Fixed an issue that could occur when Active Directory Federation Services (AD FS) verbose audit logging is turned on and an invalid parameter is logged. As a result, event 207 is logged, indicating that a write failure to the audit log has occurred.
  • A memory leak that occurs when WinVerifyTrust() is called has been worked on. This problem occurs if verification fails for the first signature of a file that has multiple signatures.
Read:  WhatsApp UWP app improves performance with light theme