-
Notifications
You must be signed in to change notification settings - Fork 811
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
Graphics driver problem after installing WSL2 #6323
Comments
First install an Intel driver that works for you and after that use this Troubleshooter to hide the Intel Driver version that comes from Windows Update and has the conflict. |
Unfortunately, no problems detected by Troubleshooter |
@executab1e Double click the downloaded |
You are right, i didn't notice it at first. So, i guess this driver update cause the problem result: now testing the solution. Expecting no problems. It's gonna take day or two, because problem usually appears randomly. |
No problems so far. I'm closing the issue, thx @onomatopellan! |
Environment
Steps to reproduce
Install WSL2 followed by official docs - https://docs.microsoft.com/en-us/windows/wsl/install-win10.
Hardware:
GPU: Intel HD4600, Nvidia M745
Notebook: Lenovo Z710
Dsiplay: internal display and external monitor 24' AOC
HD4600 driver version:
reproduced on V10.18.15.4248-X64-WHQL
(link - https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/ideapad-z-series-laptops/ideapad-z710-notebook/downloads/driver-list/component?name=Display%20and%20Video%20Graphics)
and 15.40.47.5166
(link - https://downloadcenter.intel.com/ru/product/81496/Intel-HD-Graphics-4600)
Expected behavior
No driver problem.
Actual behavior
Intel driver appeared to work incorrectly, even showed laggy when the startmenu appeared. There is no driver settings on right-clicking at the desktop (see screenshot №2), and also there is 3 new displays in Display Settings. (see screenshot №1). Reinstalling drivers doesn't help, because after rebooting problem appears again.
Looks like this problem share common with #4797
№1
№2
The text was updated successfully, but these errors were encountered: