Here's what's been fixed and what's broken in Windows 10 Insider build 14942

Microsoft has just released Windows 10 Insider build 14942 for PC, and with it comes a whole host of new fixes and improvements. Of course, alongside general fixes all around, build 14942 also contains a known issue to be aware of.

Here's the breakdown of what's been fixed and improved in Windows Insider build 14942 for PC:

• We've updated Narrator's reading order for Windows 10 apps which display an app bar on the bottom of the app, for example OneDrive, so now the contents of the page will be read before the contents of the app bar.
• We fixed an issue where running sfc /scannow in an elevated command prompt would fail at 20% with the error "could not perform the requested operation."
• We fixed an issue resulting in certain areas of Windows 10 app notifications not doing anything when clicked, rather than opening the corresponding app.
• We fixed an issue resulting in Personalization > Background Settings page crashing or showing a blank context menu when right clicking one of the recent images .
• Fixed an issue resulting in Windows Defender's Antimalware Service Executable sometimes using an unexpectedly large amount of CPU.
• We fixed an issue resulting in the Devices and Printers page in Control Panel loading slowly for users with certain audio devices.
• We fixed an issue resulting in a small set of users seeing the NTFS partition of their external hard drive incorrectly showing up as RAW format.
• Going forward from Build 14942, custom printer names will be preserved across upgrades. We've also addressed an issue where the printer queue name wasn't preserved across upgrade for some printers.
• Improved framerates when Game Bar is enabled for full screen games.

And here's the lone known issue and its workaround in build 14942:

• Insiders doing web development may find themselves their local intranet server unreachable, as service host separation will leave the IIS World Wide Web Publishing Service (W3Svc) unable to start successfully. To fix this issue:
• Run the following from an admin cmd line (or edit the registry accordingly):
• REG ADD HKLM\SYSTEM\CurrentControlSet\Services\W3SVC /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
• REG ADD HKLM\SYSTEM\CurrentControlSet\Services\WAS /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
• Reboot the system, so that the W3Svc and WAS services share a service host process.

Update:: There is a new 'known issue' discovered including a temporary workaround

These are just the general fixes and known issues in this build. For more, also be sure to check out all of the new features added in this Insider build.