Windows 10 version 2004 update KB4571744 with massive list of fixes released
Microsoft released KB4571744 for Windows 10 version 2004 as a preview. The fixes will be integrated in the cumulative update for Windows 10 version 2004 that Microsoft will release this September.
The update is beta and designed for testing purposes, and for Microsoft to receive Telemetry data from systems the update is installed on to fix last minute issues that the company's automated systems detect.
Administrators need to go to Settings > Update & Security, and click on the optional updates link on the page that opens, and on the next page on "other updates" to display the preview update. Long gone are the times in which these preview updates were pushed directly to systems when administrators activated the check for updates button.
You can check out the support page here, or head over to the Microsoft Update Catalog website to download the update manually if you prefer not to use Windows Update. The update is not made available via WSUS automatically, but administrators may import it.
KB4571744 is a non-security update. It includes the following fixes and improvements:
- Fixed an issue in Microsoft Outlook with pinned add-ins that made the program become unresponsive.
- Fixed a PeerDist-encoded content rendering issue in IE and Edge.
- Fixed an unnamed issue that could prevent ActiveX content from loading.
- Fixed a black screen on sign-in issue in Windows Virtual Desktop.
- Fixed an issue that prevented apps from working in certain scenarios if they use the custom text wrapping function.
- Fixed an issue with Start Menu apps and tiles in virtual desktop infrastucture environments.
- Fixed an issue that generated an error when printing to a document repository.
- Fixed an issue in Visual Basic 6.0 apps that prevented them from using ListView in MSCOMCTL.OCX.
- Fixed a Visual Basic 6 runtime error.
- Fixed a stop error issue caused when the initialization of the graphics adapter failed.
- Fixed a issue to reduce the likelihood of missing fonts.
- Fixed an issue that prevented users from resizing windows in some cases.
- Fixed a touch keyboard issue that caused it to close when a key was touched.
- Fixed a keyboard layout issue that added an unwanted layout as the default.
- Fixed an issue that prevented applications from closing.
- Fixed an issue that prevented the taking of screenshots using the PrintWindow API.
- Fixed a memory leak in ctfmon.exe.
- Addressed an issue that truncated the list of characters when users type in Simplified Chinese input method editor.
- Fixed a key recognition issue in DataGridView cells.
- Fixed an application that use msctf.dll stop working issue with 0xc0000005 (Access violation) exceptions.
- Fixed a memory leak issue in Dynamic Data Exchange.
- Fixed a Cortana Smart lighting issue that prevented it from working.
- Fixed an issue with folder redirections of user profiles that caused IME user dictionaries from being used.
- Fixed an issue that caused Microsoft Office apps to close when the Korean IME is used.
- Fixed a folder properties display issue for paths that are longer than MAX_PATH.
- Fixed an issue that caused sign-in screens to be blurry.
- Fixed a Windows Update becoming unresponsive issue.
- Fixed an issue that caused the correct lock screen to appear if the following policies are set:
- Policy "Interactive Logon: Do not require Ctrl+Alt+Del" set to "Disabled"
- HKLM\SOFRWARE\Policies\Microsoft\Windows\System
- DisableLockScreenAppNotifications = 1
- DisableLogonBackgroundImage = 1
- Fixed an issue that caused File Explorer to stop working when browsing folders with RAW images (and other unspecified file types).
- Fixed stop errror 0xC2 in usbccgp.sys.
- Fixed an issue in the Event Viewer Microsoft Management Console that caused it to stop working if a secondary monitor was above the primary monitor.
- Fixed a Windows Remote Management service startup type migration issue.
- Fixed an unnamed issue with object performance counters.
- Fixed a roaming issue of Microsoft User Experience Virtualization settings.
- Fixed an issue that prevented users from setting REG_EXPAND_SZ keys in (some) automated scenarios.
- Fixed an EnhancedAppLAyerSecurity node in modern device management issue that prevented settings from being applied correctly to client systems.
- Fixed a memory leak in Lsalso.exe.
- Fixed a delayed sign-in or unlock issue on Hybrid Azure Active Directory-joined machines.
- Fixed an issue that caused hash signing from working correctly.
- Fixed an issue that displays the previous users username hint in the smart card sign-in box.
- Fixed a TMP communication issue that caused it to time out and fail.
- Fixed an AppLocker issue that prevented it from running an app even though a publisher rule allowed it.
- Fixed another AppLocker issue that prevented applications from loading software modules.
- Fixed an issue that caused the promotion of a server to a domain controller to fail.
- Fixed an issue that prevented users from unlocking devices if a space was typed before the username.
- Fixed an unnamed issue that caused systems to stop working and throw 7E stop codes.
- Fixed an issue that caused application load times to be very long.
- Fixed classification issues caused by the wrong User Principal Name.
- Fixed an issue in cluster scenarios that caused handles to .vmcx and .vmrs files to become invalid after storage failover.
- Fixed an issue with interrupt targeting.
- Fixed shutdown delay issues that happened when the Microsoft Keyboard Filter service was running.
- Fixed an issue that caused machines to request a new IP address after authentication.
- Fixed a Background Intelligent Transfer Service issue that made it download data in cellular mode without explicit user permission.
- Fixed an Always On VPN issue that prevented it from automatically reconnecting from Sleep or Hibernate.
- Fixed an Always On VPN tunnel issues that made it use incorrect certificates.
- Fixed an Always On VPN issue that occurred when user and device tunnels were configured to use the same endpoint.
- Fixed a VPN app stop working issue when enumerating VPN profiles.
- Fixed a drive optimization issue in the Optimize Drives dialog.
- Fixed an issue that failed to turn off the host memory buffer when the device is shut down forcefully.
- Fixed an issue that prevented apps from downloading an update or opening.
- Fixed an issue that caused the stop error (0xC00002E3) at startup.
- Fixed an issue that could cause stop error 7E in nfssvr.sys.
- Fixed an issue with Server Message Block that incorrectly logs the Microsoft-Windows-SMBClient 31013 event.
- Addressed an issue that causes SMB to incorrectly use the original, cached non-Continuous available handle to a file.
- Fixed a data loss issue for written data when an application opened a file and wrote to the end of the file in a share folder.
- Fixed a Microsoft Input Method Editor for Chinese and Japanese languages in Microsoft Excel and other apps.
- Blocks accounts from a different tenant from signing in to a Surface Hub device.
- Time Zone information for Yukon, Canada updated.
- Improved the user experience for face and fingerprint setups on Windows Hello enrollment pages.
- Improved the tablet experience for convertible and hybrid devices in docked scenarios.
- Added the option to use Dolby Atmos for Headphones and DTS Headphone: X to be used in 24-bit mode on devices that support it.
- Added the option to sync Microsoft Edge IE Mode unidirectional session cookies when an admin configures it.
Microsoft lists just one known issue: users that use the Microsoft Input Method Editor for Japanese or Chinese languages may experience various issues. Affected users may check out this support article for guidance.
Now You: Do you install preview updates?
Summary
Article Name
Windows 10 version 2004 update KB4571744 with massive list of fixes released
Description
Microsoft released KB4571744 for Windows 10 version 2004 as a preview. The fixes will be integrated in the cumulative update for Windows 10 version 2004 that Microsoft will release this September.
Author
Martin Brinkmann
Publisher
Ghacks Technology News
Logo
upgraded to win 10 ver. 2004 and have a TON of issues. Even did a rese to no avail. Takes my very fast (was) machine from 45 sec. to boot to 6 minutes. After I finally can get online I run task manager and my memory stays “pinned” at 100% for very long time. Called my computer geek and he knew my issue before I even told him that my memory usage was “stuck” at 100% even when I am doing NOTHING on my machine. He said his shop is doing 2 machines a day with this same issue and others. He said solution to fix my 1 week old update was to update again to version 20H2. spoke to a Microsoft agent who said he would transfer me to an “expert” on this issue and was on hold for over an hour and hung-up. What customer service. They force updates on users that don’t work and then they are gone. BTW Mcrosoft case # is 1012749459. Looked online for this symptom and did not see my issue described as I just described it, but see a massive number of errors and no solutions. I want a Microsoft tech service person to call me and tell me if my issues can be done with remote access to my laptop as I have read 20H2 upgrade has issues of it’s own. Wish I had bought an Apple…..
Windows 8.1 never seems to have these problems.
Does this update bring back the classic file explorer seach like 1903?
If not, is there any way to enable it?
I installed it to fix the damn SSD defrag bug.
I installed this on my 6 computers right away because Windows 10 can’t get any worse. It needs every update and it needs them faster than fast. I don’t care if they’re good or not, hand them over! Nothing exploded, my files are intact, internet works. Life is good.
Same here, except I have 25 Windows 10 computers. With that many computers, I’m hoping I’ll have at least one working computer after this update.
A few more updates and maybe Windows 10 might be ready for release.
well Martin at least with KB4571744, the MS defrag app now remembers its previous defrag status after a reboot instead of forgetting it
So is Win10 vers.2004 now debugged enough to adopt?
I did install version 2004 on a HP laptop and HP desktop and it runs without any problems here. The only thing is the update took a long time to download and install, about two hours, with several restarts.
seems a common issue: https://www.tenforums.com/windows-10-news/157138-known-resolved-issues-windows-10-may-2020-update-version-2004-a.html
In on Enterprise and we haven’t seen a hint of it.
That’s for you to decide. I’ve been using 2004 since ISOs got published and don’t have any issues with this build.
But to be fair I always update my Windows whenever ISOs get released and I never had any issues worth mentioning with Windows updates.
That is a long list!
Wednesday I went ahead with the 2004 install. I used the .iso file and Daemon Tools Lite for installation.
The upgrade changed a few simple things like removing “copy to,” “move to,” “Take Ownership” from the Context Menu, but I use the UWT to put it all back.
I haven’t really noticed any major problems; had to change a couple of default apps.
So I guess for now I’m good.
Install on laptop and desktop.
Yikes…you know that Win 10 can natively mount .ISOs? Just right click, “Open with Windows Explorer”. One of the best features of Win10. No need for Demon tools, PowerIso etc….
Sheesh, what a massive list of bugs…I mean fixes. They realize if/when these bugs occur the user doesn’t know what’s causing them, so runs around trying all sorts of other fixes like a chicken with its head cut off. ‘blurry screen’….’applications won’t close’…’prevented resizing windows’ etc. Then find out it might be Win2004 bugs. What a lunacy.
I wonder if the SDD defragmentation issue is solved in this update. Thanks @Martin! :]
I can confirm it works fine now. The date at which the last trim was done is recorded.
It is.
it seems ok now