Home News Windows 10 Version 17134.3736 Update – A Plethora of Bug Fixes Have...

Windows 10 Version 17134.3736 Update – A Plethora of Bug Fixes Have Arrived

0
SHARE

Microsoft is always “cooking” new software updates and this is why Windows 10 has been so successful. Windows 10 is renowned for the premium user experience that it offers and it’s all thanks to the constant stream of updates that Microsoft releases. These updates introduce bug fixes that take care of known software issues which are causing problems to Windows 10 users and this is exactly what the latest Windows 10 Version 17134.376 update does.

Windows 10 Version 17134.3736 Update

The new Windows 10 update has been made available for download today and it introduces a bunch of bug fixes that Windows 10 users have been asking for a long time. Even though Microsoft took its time to deliver these bug fixes, it’s always better late than never. Nonetheless, Windows 10 users can manually download the update starting today.

A Plethora of Bug Fixes      

With that said, we are going the list some of the most important bug fixes that the new Windows 10 update introduces so that users know what they are going to receive:

  • Addresses an issue that sometimes prevents documents from appearing in the Microsoft Edge DevTools debugger;
  • Addresses additional issues with updated time zone information;
  • Addresses the redenomination of local currency that the Central Bank of Venezuela Implemented to enter the Bolivar Soberano into circulation;
  • Addresses an issue that causes the audio service to stop working or become unresponsive while using call control, controlling volume, and streaming music to Bluetooth audio devices;
  • Addresses an issue that causes the OS to stop working when a Bluetooth device is accidentally removed;
  • Addresses an issue in which application on systems with more than 4 GB of memory receive Access Denied error code “0x5” when calling CreateProcessWithLognW();
  • Addresses an issue in which the AccountName in the Event Log entry for the Microsoft-Windows-Kerberos-Key-Distribution-Center source and Event ID 7 sometimes appears corrupted;
  • Addresses an issue that might cause TCP connections opened for an application running on Windows Container to fail sporadically. This occurs when the container runs on a Network Address Translation (NAT) Network provided by Windows Network Address Translation (WinNAT). A SYN timeout occurs after reaching the maximum SYN Retransmit count;
  • Addresses an issue that causes the printing of PDF files from SharePoint Online to fail with the error, “Couldn’t open PDF”;
  • Addresses an issue that prevented the launch of Windows Defender Application Guard (WDAG) on Windows 10N (Europe) devices after servicing;
  • Addresses an issue that prevents the deletion of Immediate Tasks when their deletion timer occurs, such as when you configure Group Policy preferences for Immediate Task actions;
  • Addresses an issue that incorrectly implies that user policies have not been applied after configuring a user rights Group Policy setting. Reporting tools, such as RSOP.MSC or Gpresult.exe /h, do not show the user rights policies or display a red “X” instead;
  • Addresses an issue in which connection group folders are not properly merged;
  • Addresses an issue that prevents the clock and date flyout from appearing when the region format is Spanish (Spain) and the sorting method is Traditional;
  • Addresses an issue in which Scheduled Tasks configured to run on a specific day of the week don’t execute at the expected time;
  • Addresses an issue that may cause the system to stop working during the shutdown of some Windows Presentation Foundation (WPF) apps because of TaskCanceledException. Apps that are vulnerable to this issue perform work involving weak events or data binding after the Application.Run() function returns values;
  • Updates the .NET Framework’s support for the formatting of Japanese dates for the first year in the eras. When the format pattern is “y年”, the year format will use the symbol 元 and not use year number 1. Additionally, the .NET Framework will support dates that include 元.