Fractal Design Pop Air RGB Black TG review
Palit GeForce GTX 1630 4GB Dual review
FSP Dagger Pro (850W PSU) review
Razer Leviathan V2 gaming soundbar review
Guru3D NVMe Thermal Test - the heatsink vs. performance
EnGenius ECW220S 2x2 Cloud Access Point review
Alphacool Eisbaer Aurora HPE 360 LCS cooler review
Noctua NH-D12L CPU Cooler Review
Silicon Power XPOWER XS70 1TB NVMe SSD Review
Hyte Y60 chassis review
Bug in Windows 10 Insiders-build crashes games
There's a big nasty bug in the insiders-build version of Windows 10 that has an effect on PC gamers. Likely a good number of you guys have that build installed, hence this news-item. Microsoft shares word that PC gamers should pay attention with updates as a number of big games like Fallout 4 and Assasin's Creed can crash.
The bug presents itself in the fast-ring update for Windows 10. These are alpha versions of the OS. The big exposes itself and appears when the user will go from windowed mode towards full-screen mode. Numerous games will then crash completely.
Microsoft already stated that titles like The Witcher 3, Fallout 4, Tomb Raider, Assassin’s Creed and Metal Gear Solid V are effected but also states it's likely a wider range of games involved.
Microsoft on Thursday released build 11102 which only hold small updates.
JonasBeckman
Senior Member
Posts: 17562
Joined: 2009-02-25
Senior Member
Posts: 17562
Joined: 2009-02-25
#5221924 Posted on: 01/22/2016 01:52 PM
Yeah it's listed clearly in the list of known issues with this latest insider build (Although if you skip that and just use WU to get the new build without reading up on it that might be a annoyance since you wouldn't know the current issues with said build.) and insider is a test branch and not intended for standard OS usage or how to say plus they recently even clarified how faster releases will now happen on the fast ring so people should expect more bugs so either skip the insider program or keep to the slow ring.
EDIT:
https://blogs.windows.com/windowsexperience/2016/01/21/announcing-windows-10-insider-preview-build-11102/
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.
Oh please... This insider preview build. Bugs and issues are to be expected and this exact reason is why they test these things before pushing them for everyone.
Yeah it's listed clearly in the list of known issues with this latest insider build (Although if you skip that and just use WU to get the new build without reading up on it that might be a annoyance since you wouldn't know the current issues with said build.) and insider is a test branch and not intended for standard OS usage or how to say plus they recently even clarified how faster releases will now happen on the fast ring so people should expect more bugs so either skip the insider program or keep to the slow ring.
EDIT:
https://blogs.windows.com/windowsexperience/2016/01/21/announcing-windows-10-insider-preview-build-11102/
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.
Fender178
Senior Member
Posts: 4198
Joined: 2004-09-28
Senior Member
Posts: 4198
Joined: 2004-09-28
#5221932 Posted on: 01/22/2016 02:20 PM
To me since the insider version of Windows 10 is for developers and testers of beta builds it is only going to effect them and not the standard users like us. It is only going to be a annoyance to testers and developers. So it is really not a major problem.
To me since the insider version of Windows 10 is for developers and testers of beta builds it is only going to effect them and not the standard users like us. It is only going to be a annoyance to testers and developers. So it is really not a major problem.
Denial
Senior Member
Posts: 13755
Joined: 2004-05-16
Senior Member
Posts: 13755
Joined: 2004-05-16
#5221938 Posted on: 01/22/2016 02:26 PM
Lol there were so many people complaining they weren't releasing insider builds fast enough, so they speed up the process and as a result there are more bugs. Now Gabe's twitter is filled with people complaining about this bug.
No matter what Microsoft does they basically lose.
I kinda wish they'd detail the changes to OneCore more. They are currently only listing UX changes but Gabe said there were over 1200 changes from the last insider build to to this one. Obviously some of them have to do with the graphics stack.
Lol there were so many people complaining they weren't releasing insider builds fast enough, so they speed up the process and as a result there are more bugs. Now Gabe's twitter is filled with people complaining about this bug.
No matter what Microsoft does they basically lose.
I kinda wish they'd detail the changes to OneCore more. They are currently only listing UX changes but Gabe said there were over 1200 changes from the last insider build to to this one. Obviously some of them have to do with the graphics stack.
Illnino
Senior Member
Posts: 603
Joined: 2007-09-07
Senior Member
Posts: 603
Joined: 2007-09-07
#5221939 Posted on: 01/22/2016 02:34 PM
Well that's it I'm rolling back to MSDOS
Well that's it I'm rolling back to MSDOS
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 182
Joined: 2011-11-10
Yes, it's only on the latest build 11102... MS refers and explains that bug on the notes...
It only affects some games... RS Siege for example crashes at start, BF4, BFH and SWBF are working fine (at least on my nvidia card)