Windows 10 2004 has reached the end of testing so and in the course of getting final touch before rollout. The last step Windows 10 Release Preview Build 19041.208 has come to an insider now. Microsoft made this decision to deliver this as the closing build (KB4558244) in order to fix one more issue before making the availability of May 2020 update.
It includes all the features of 20H1 along with the fixes from the Slow ring. However, this cumulative update also has some issues that the team will fix up in the upcoming servicing releases. So explore the below section to find out the details of this patch.
Windows 10 Release Preview Build 19041.208 KB4558244 Changelog
Here is the list of fixes that Windows 10 Release Preview Build 19041.208 update KB4558244 offers –
- This patch incorporates all the features of 20H1 moreover carries all the fixes that were released to Slow ring Windows Insiders in Build 19041.21 through Build 19041.207.
- In addition, the release also resolves a complication that fails to send NPLogonNotify API notifications from the credential provider framework.
Following are some issues that might affect a small group of users which the team will fix up in the upcoming servicing releases –
- For several users, Windows Mixed Reality might fail to function perfectly on Windows 10 Release Preview Build 19041.208 KB4558244. If you are frequently using this feature, its best to hold off the May 2020 Update through Release Preview. The team is working on the resolution and will soon come out with a fix in early May.
- The most useful DISM tool might not always fetch the correct status while repairing corruption on systems. This servicing release KB4558244 will provide a fix for this.
- Certain applications utilize the “ImeMode” property to control the IME (Input Method Editor) mode for individual text entry fields to improvize typing efficiency. This specific feature does not function accurately currently in the May 2020 Update. For instance, a number field will not all by itself switch to a mode that is best optimized for Japanese numerical input. This problem will get a solution in the forthcoming servicing update. To solve this issue temporarily, either manually switch the input mode when typing, or set the Compatibility “Use previous version” checkbox for the impacted keyboard via Windows Settings => Time & Language.
Source – Windows Blog