KB4541335 for Windows 10 1903 and 1909 released
Microsoft released the optional non-security update KB4541335Â for the company's operating systems Windows 10 version 1903 and version 1909 on March 24, 2020.
The company announced earlier that it will pause the production and distribution of preview updates for all supported versions of Windows from May 2020 on.
Note: Preview updates should be considered beta updates. These are usually included in the following Patch Tuesday update and should not be installed unless they address critical issues that are experienced on devices. In any case, it is recommended that you create a backup of the system before you install any update.
KB4541335 for Windows 10 version 1903 and 1909
Windows 10 version 1903
The following issues are fixed in the preview update:
- Fixed a document repository printing issue.
- Fixed the cause of a misleading reset message for Win32 apps converted to UWP.
- Fixed a Microsoft Foundation Class toolbar drawing issue in multi-monitor environments.
- Addressed an issue that ignored the first key stroke in a DataGridView cell.
- Fixed a performance issue that occurred when DRM content is played or paused in the background.
- Fixed a PrintWindow API issue that caused screenshots of windows to fail.
- Fixed a File Explorer issue that caused it to close unexpectedly when using roaming profiles between different Windows 10 versions.
- Fixed a search issue that failed to return results in Start or the Search box for users without local profiles.
- Fixed an application termination issue caused by the entering of East Asian characters after changing the keyboard layout.
- Fixed an issue that prevented the Mute button from working on devices with the Microsoft Your Phone app.
- Fixed a calendar issue affecting the Samoa time zone.
- Fixed the cause of the error "Remote host method get_WindowsSize is not implemented".
- Fixed a log reading issue using the OpenEventLogA() function.
- Fixed a domain controller registration issue.
- Fixed a sign-in or unlocking issue on Hybrid Azure Active Directory-joined machines that delayed the process by up to 2 minutes.
- Fixed multiple authentication issue in Azure Active Directory environments.
- Fixed a Credential Guard issue that prevented machines with it enabled from joining domains.
- Fixed an issue that prevented some machines from entering Sleep mode caused by Microsoft Defender Advanced Threat Protection (ATP) Auto Incident Response (IR).
- Fixed a performance issue in the Windows Runtime API.
- Fixed an issue that caused Windows.admx templates to miss one of the SupportedOn tags.
- Fixed an issue that prevented applications from closing.
- Fixed an issue that caused the creation of the Storage Replica administrator group with the incorrect SAM-Account-Type and Group-Type.
- Fixed a Windows ecosystem compatibility status evaluation issue.
- Fixed a Microsoft User Experience Virtualization roaming issue.
- Fixed an issue that caused the Network Policy Server accounting feature from working.
- Fixed an issue that prevented standard users accounts configured with maximum UAC control settings from installing Language Features on Demand using System settings.
- Fixed an issue that prevented the connection to virtual private networks.
- Restores the constructed attribute in Active Directory and Active Directory Lightweight Directory Services (AD LDS) for msDS-parentdistname
- Improved support for non-ASCII file paths in Microsoft Defender ATP Auto IR
Windows 10 version 1909
Includes all the changes listed under version 1903 plus the following change:
- Fixed an issue that prevented that the local language setting in the OS image is retained during system preparation.
Microsoft lists no known issues.
I sick of File Explorer crashes in 1909. I have a perfect PC, Win 10 Pro 64bit, with all the updates.
Even after installing KB4541335, I had File Explorer crash today.
I was using Edge and was on Twitter.
A geek friend of mine told this:
“…What is for sure, is that I never looking at Twitter, so it canâ€™t be the culprit itself ; however itâ€™s possible that Edge Chromiumâ€™s rendering engine somehow interferes with Windows Explorer.
Again, I doubt it, because Edge and Windows are on different, and completely distinct, update schedules; itâ€™s more likely that the fixes released in recent builds caused regressions that will have to be fixed in a future update”
Honestly, I think that’s the problem.
I don’t have any problem with explorer and the only difference BTW you and me is that you use edge and I don’t.
Fine here with 1909, by the way I hope all these fixes would be good for version 2004 too because every new ISO releasing is annoying like hell on earth. ðŸ˜£
I’m still on 10/1809 Home and keeping the laptop offline until I’m sure that 1909 is fixed but I’m also waiting on the March 2020 patches and maybe that’s happening shortly if those are not having too many issues. And even though I’m on 10/1809 Home I’ve been offered 1909 from Windows update but really the file explorer and other issues(1903/1909) has me wanting to wait longer but 1809 only has until May 12 2020.
I’ve got other laptops for getting online so I can keep the 1809/Home laptop offline indefinitely for the most part and I’m really worried about 2004 supplanting 1909 as my offered via WU feature update as I’m not ready to make a 2 feature update jump on my laptop. I’d rather get updated to a fixed and stable 1909 and stay with that until next year. I’m really looking at stability first and foremost as that’s what is really needed what with all that’s going on currently.