Here’s what’s fixed, improved & outstanding for Windows 10 RS4 build 17123
2 min. read
Published on
Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more
As with most Insider releases, there’s always room for improvement and the Windows team has recently updated its blog to include Fast Ring build 17123’s list of fixes and general improvements.
- We fixed an issue from the last flight on PCs with the Dolby Access app installed and expired Dolby Atmos license, where the Windows Audio service (audiosrv) would crash with a stack overflow exception and the PC won’t have sound.
- We fixed an issue resulting in a bug check with the error message SECURE_KERNEL_ERROR in recent flights.
- As of Build 17063, a change was made that may have caused some older drivers to not load properly. This may have caused update failures or bugchecks (GSODs) shortly after the PC was rebooted. This build includes fixes for this that should prevent these update failures and bugchecks from occurring.
- Thanks everyone who’s shared feedback about our Embedded Handwriting Panel so far – we’re making a change such that if you clean install, reset your PC, or upgrade straight to this build from the Fall Creators Update this experience will be turned off by default. The setting will remain on for Insiders who have upgraded from previous builds where it was enabled, and can be turned on by anyone with a pen capable device via the “Write directly into text field” option under Pen & Windows Ink Settings.
The previous build for Fast Ring testers was declared to have had no known issues, so the list of fixes and improvements is unsurprisingly short and welcomed for some.
However, there is one issue Insiders might experience with this latest preview, but fortunately, it’s a rather small one relatively speaking.
- If you had your phone linked to your PC prior to upgrading, you’ll find it has become unlinked after upgrading. You can relink your phone from Settings > Phone.
We don’t know the numbers on how many people are toying with this option but I think its safe to say it’s probably not going to affect that many testers in any meaningful way.
User forum
0 messages