Note driver version now 27.20.100.8935 - so far so goodġ1) Accept the reboot device prompt exe - doesn't matter as both fail to stick)Ĭlick on the "delete driver from this device" optionĦ) scan for changes (device now shows as "Microsoft Basic Display Adapter") - note at this point if you haven't turned off network/wifi then windows will beep as it will have automatically reinstalled the vulnerable 26.20.100.7261.ħ) reboot. Until they do we get to keep the drivers that have the vulnerability that allows command privilege escalation. Razer or Intel need to update the drivers that they have on MS driver update. Windows therefore grabbed those by default rather than the generic drivers.įinally this update brings updated intel control panel, so go into programs and features to uninstall the older Intel Graphics Control panel. The fix is to device manager, uninstall, (clicking the option to uninstall Intel drivers completely) and then reinstall.Īctually mine skipped a step and automatically reinstalled the newest version rather than OEM because I'd already downloaded and unzipped the zip drivers and attempted a manual install. (which 26.20.100.7261 clearly is earlier and hence wouldn't be overwritten) Basically OEM DCH drivers < 26.20.100.8141 couldn't be overwritten by non-OEM Intel driver later than that. My concern initially was that the reason for my inability to upgrade the drivers was because it had already been exploited on my PC. It bothered me even more when recently I found this article suggesting a vunerability for versions less than 26.20.100.7584 - which clearly the OEM drivers were. Rebooting would then result in another nag. It was bothering me that Intel driver update wizard kept nagging me on each reboot for Intel UHD graphics driver update, but when running - it would install and then uninstall and driver version remained stuck on 26.20.100.7261. Surprised this isn't being talked about more, or I've missed the thread so I've created this here.
0 Comments
Leave a Reply. |