Windows 10: Microsoft acknowledges dGPU issue in Windows 10 version 1903

As we reported last month, a number of Surface Book 2 owners claimed that Windows 10 May 2019 Update causes GPU performance issues on their devices. According to users reports, Windows 10 May 2019 Update causes the dGPU (discrete graphics processing unit) to disconnect at random times on Surface Book 2.

Many users have reported the problem and Microsoft has finally acknowledged it as a known issue in its support document. According to the tech giant, a bug in Windows 10 version 1903 causes the dGPU to disappear from device manager on certain models of Surface Book 2.

The company says Surface Book 2 devices with Nvidia discrete graphics processing unit (dGPU) are plagued with this problem. The bug crashes graphics-intensive apps or games such as Adobe Photoshop and video editor on Surface Book 2. Some apps or games may also fail to launch.

Microsoft has applied a compatibility hold on affected Surface Book 2 devices with Nvidia dGPUs and Windows 10 version 1903 won’t be offered until this issue is resolved.



Fortunately, Microsoft has shared an easy workaround that you can follow to stop dGPU from disconnecting on Surface Book 2:

1. Open Cortana/Search.
2. Search for Device Manager.
   
3. Click on ‘Scan for hardware changes’ icon located on the toolbar.

Microsoft is advising the Surface Book 2 owners to avoid Media Creation Tool or other forced upgrade methods until this issue has been resolved.

The post Microsoft acknowledges dGPU issue in Windows 10 version 1903 appeared first on Windows Latest

Weiterlesen...

 

Local profile issue after upgrading to 1903


Hi roblinb

Not listed in the Known.

Known issues for Windows 10 May 2019 Update version 1903


As far as Wifi any chance it is Qualcom inside USB adapter, if Qualcom then yes known issue.


I might create another user (Local) and when if try again see if this issue occurs on both users.

Would also suggest you run the first 5 steps in this tutorial to see if you have any corruption with current build.

Use DISM to Repair Windows 10 Image


Ken

 

Can't open Windows Sandbox Error 0x80070002


Microsoft has acknowledged this issue now:

Windows Sandbox may fail to start with error code “0x80070002”Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.


Affected platforms:

• Client: Windows 10, version 1903

Next steps: We are working on a resolution and estimate a solution will be available in late June.

 

Microsoft Acknowledges Gaming Performance Issues Under Win 10 Creators Update

Microsoft made considerable noise on their vaulted Game Mode, a Windows feature which made its appearance in their latest Creators Update version of Windows 10. Game Mode was one of the foremost features in the latest Windows update, which was supposed to deliver improved performance in gaming or other full-screen 3D applications, by enabling more of the available CPU and GPU resources to be tapped into by specific applications. Specific CPU (through winding down of non-crucial processes) and GPU (through prioritization of game-related graphics memory allocation) improvements were baked into this latest version; supposedly, only performance improvements should result from this effort on Microsoft's part.









However, things are not as rosy as they should be, and users soon started reporting performance issues with stuttering and lower than expected frame-rates under the latest version of Windows - which didn't occur prior to the Creators Update. Microsoft has been mum on the issue; until now. The company has now officially acknowledged that there are indeed situations where gamers could experience frame-rate and stuttering issues, and has even issued a fix for one such situation with the latest, fast-ring build 16273 and above versions of Windows. However, this has fixed only one of multiple origin points for the reported issues.

Some users are reporting that disabling the Xbox Game DVR feature eliminates the issues, but this isn't working for every user that remains affected. Likely, the issue lies with Microsoft's Game Mode interface and Xbox interface additions to Windows 10 with the Creators Update. It's somewhat of a paradox: at the same time that Microsoft introduces specific CPU and GPU workload optimizations for full-screen applications, they introduce an additional interface layer on top of your 3D application, enabling additional Xbox-based functionality (such as the aforementioned DVR capability). Likely, that's the culprit of the whole performance issues; it remains to be seen whether all sources of the performance issues will be fixed through windows updates, or if users will have to wait until the Fall Creators Update for a fully resolved scenario.





Sources: MS PowerUser, Windows Feedback Hub, via Neowin