Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow wslg performance with Intel integrated graphics #967

Open
rommeswi opened this issue Jan 27, 2023 · 5 comments
Open

Slow wslg performance with Intel integrated graphics #967

rommeswi opened this issue Jan 27, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@rommeswi
Copy link

Windows build number:

10.0.22621.0

Your Distribution version:

22.04

Your WSL versions:

WSL version: 1.0.3.0
Kernel version: 5.15.79.1
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1105

Steps to reproduce:

  1. Update Windows on a laptop with Intel integrated graphics
  2. Intel drivers are rolled back (this happens consistently after Windows updates)
  3. Observe slow WSL performance (Wayland): lags in display updating after making an input (windows apps do not experience such a decrease in speed)
  4. Update Intel drivers
  5. Observe normal speeds

WSL logs:

No response

WSL dumps:

No response

Expected behavior:

Apps are laggy with the standard drivers provided after Windows update. Response times are so large that even text editors become almost unusable.

Actual behavior:

This post is primarily to guide users to one root of the problem when WSL is laggy. I doubt the wslg crew can convince Microsoft that it is a terrible idea to automatically roll back drivers every time you update Windows.

@rommeswi rommeswi added the bug Something isn't working label Jan 27, 2023
@aki-k
Copy link

aki-k commented Jan 28, 2023

@rommeswi
Copy link
Author

Unfortunately that does not work. It simply does not find updates to hide.

The fault is not with wslg though. It is just Microsoft who keeps "updating" the Intel drivers to a two year old version on its Surface Pro models, ignoring drivers directly installed from Intel. The reason why I posted this here is so that Surface Pro users know how to fix these performance issues: reinstall the Intel drivers after every. single. Windows. update.

@aki-k
Copy link

aki-k commented Feb 17, 2023

Did you follow the instructions on the page? It wants you to restart the computer. It worked for me.

@aki-k
Copy link

aki-k commented Feb 20, 2023

It can be simpler to:

  • first uninstall the device from Device Manager selecting the checkbox "Delete the driver software for this device"
  • then use DriverStore Explorer to delete the driver files from the Windows Driver Store
  • reboot the computer
  • use the "Show or hide updates" troubleshooter to hide the driver update coming from Windows Update

Maybe Windows doesn't properly remove them when uninstalling the device

@aki-k
Copy link

aki-k commented Mar 8, 2023

I ran into this same problem with Windows downgrading the Intel graphics driver on my Dell Latitude 7490 :(

But I think I found a solution to this problem, which I'll describe below:

  1. I installed the Intel graphics driver from their website.
  2. Then after a reboot, I started PC Settings app and selected Windows Update where I saw it already getting the previous driver
  3. At this point I let it continue installing, but before rebooting I went into Control Panel/Device Manager where I selected "Display Adapters/Intel(R) UHD Graphics 620" and then right click/Properties.
  4. In the Driver tab, I clicked on "Roll Back Driver" and then wrote there the reason why I wanted to roll back the driver to a previous driver.
  5. Then after a reboot, Windows Update didn't any more offer to install its own selected driver, but let me keep the driver installed from Intel's website.

I hope this also helps you.

Edit: oh and that troubleshooter cab wushowhide.diagcab doesn't work :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants