[ad_1]
Starting from the old, the 18343 (19H1) build is passed on to Windows insiders who subscribe to the fast ring. It mainly includes general changes, enhancements, and fixes, instead of adding new features as some versions do. It is important to note that Intel has fixed a problem that causes computers with certain Intel processors to hang.
"We solved the problem of Connected Standby which was blocking computers equipped with Intel64 Family 6 Model 142 and Intel64 Family 6 Model 158 processors. If your PC could not use this week's 18342 version because of one of these models, you should be able to take this flight, "says Microsoft.
Looking further, Microsoft is shipping version 18841 to Windows Insiders who have chosen to receive Skip Ahead versions. It is worth noting that Microsoft jumps up in 2020 from 19H2 to experience and testing 20H1.
This release also focuses on general improvements and bug fixes, many of which are for the reworked Sandbox. These specific fixes are as follows:
- Windows Sandbox now supports configuration files! These files allow users to configure certain aspects of the sandbox, such as vGPU, networking, and shared folders. A blog post explaining this new feature is available here.
- Windows Sandbox now captures keyboard shortcuts in full screen.
- Issue resolved: Windows Sandbox could not start on localized versions.
- Improved error report in Windows Sandbox. Now the error dialog includes the error code and a link to the comment hub.
- Issue resolved: Windows Sandbox generated an unexpected error due to reference to a deleted file on Windows.old.
The most recent issue mentioned on the support history page prevented some users from retrieving Windows updates.
"Windows Update clients have recently been affected by a network infrastructure event caused by a global outage of the external DNS service provider.A software update on the external vendor's DNS servers resulted in the distribution of the server." Corrupt DNS records that affected connectivity to the Windows Update service, the records were restored on January 30, 2019 (00:10 UTC), but the downstream effects continued, "says Microsoft.
Microsoft thinks the problem is now fully mitigated. However, anyone still experiencing download problems should contact their ISP, says Microsoft.
[ad_2]
Source link