Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
22680 Discussions

intel 32.0.101.5510 display glitches

pmaillot
Novice
2 920 Visites

I have had W11 automatically installing intel 32.0.101.5510 display and noticed I get glitches when watching videos, small horizontal bars about 3mm thick. I went back to a previous driver and the glitches were gone.

Now W11 is again trying to push this driver.... Oh well. I guess I'll disable auto updates all together.

Dell 9315, i5, 16Gb mem. W11 latest patches.

 

-Patrick

0 Compliments
1 Solution
pmaillot
Novice
2 702 Visites

Interestingly enough, there was a new W11 update this morning (as part of the insider program [beta releases]) and the intel 32.0.101.5510 display driver was re-installed, along a bunch of other things as part of Windows 11 Insider Preview (10.0.22635.3640) (KB5037867) update, and the glitch issue is (or at least until now, seems to be) gone.

-Patrick

Voir la solution dans l'envoi d'origine

0 Compliments
5 Réponses
Stefan3D
Contributeur émérite II
2 901 Visites

32.x? Are you in the canary channel?

0 Compliments
pmaillot
Novice
2 887 Visites

?? I have no idea [i.e.  I for sure don't see why and don't think so].   I'm just a W11 standard user.

0 Compliments
Stefan3D
Contributeur émérite II
2 881 Visites

Looks like someone at Microsoft was a bit hasty.

It makes no sense to offer you this driver because you cannot use WDDM 3.2 in the general release version of Windows before the next major update.

0 Compliments
Dawid3
Débutant
2 754 Visites

CCzyli co trzeba zrobić? Ja również mam tę wersję sterownika i nie wiem, co zrobić. Ponadto nigdzie nie mogę znaleźć o nim informacji.

0 Compliments
pmaillot
Novice
2 703 Visites

Interestingly enough, there was a new W11 update this morning (as part of the insider program [beta releases]) and the intel 32.0.101.5510 display driver was re-installed, along a bunch of other things as part of Windows 11 Insider Preview (10.0.22635.3640) (KB5037867) update, and the glitch issue is (or at least until now, seems to be) gone.

-Patrick

0 Compliments
Répondre