Here are the Known Issues in Windows 10 for PCs Build 11102

Here are the Known Issues in Windows 10 for PCs Build 11102

Today, Microsoft released a new Windows 10 build to the fast ring, Windows 10 for PCs Insider Preview build 11099. It’s the first Redstone build that we’ve seen that actually has new features. Well, a new feature.

This is, in fact, the third Redstone build. Up until now, I’ve been recommending that people not install the new Redstone builds. After all, there’s no new features, so you’re making yourself susceptible to known issues without any benefit.

Of course, there are still no new Redstone builds for Windows 10 Mobile. In fact, we don’t even know if we’ve seen the last Threshold 2 build for Windows 10 Mobile, as Microsoft is still trying to work that out.

Gabe Aul had promised to begin publishing known issues in the Insider Hub, but due to an issue, they decided to publish these on the Windows blog, making everyone’s life easier, if just for this build. Also, they seem to have stopped publishing what’s been fixed.

So without further adieu, here are the known issues for Windows 10 for PCs Insider Preview build 11099.

Known issues:

When we went live with last week’s PC build, Insiders discovered a bug where the cache for Insider Hub wasn’t properly refreshing – preventing new content from showing up in a timely manner. We’ll include known issues with our blog posts as well as in Insider Hub until the bug is resolved.

  • Some PC games will crash switching from windowed mode to full screen, upon game resolution change, or upon launch due to a bug in Windows graphics stack. We have observed this with The Witcher 3, Fallout 4, Tomb Raider, Assassin’s Creed, and Metal Gear Solid V but it may occur with other titles as well.
  • With this build (and with the last build), applications such as Narrator, Magnifier, and third-party assistive technologies may experience intermittent issues or crashes. If you rely on screen readers or other software, you should not use this build. This issue will be fixed with the next build.
  • You might see a WSClient.dll error dialog after logging in. We’re working on a fix for this but as a workaround, you can run the following in Command Prompt with administrative rights: schtasks /delete /TN “\Microsoft\Windows\WS\WSRefreshBannedAppsListTask” /F
  • While attempting to update to this build, your PC may show a message that your wireless card is not compatible with Windows 10. The workaround is to visit the support page for your PC or wireless card and install the newest driver that is available.
  • The Connect button does not show up in Action Center.

 

About the author
Rich Woods

Being a computer programmer wasn't enough to fulfill his love of technology. In 2013, Rich founded For the Love of Tech and has been writing about his love of tech ever since.