Intune Device Driver Updates show up as available but don't deploy

[William Cunningham]

I switched over to a Microsoft 365 Business Premium account and then set up a policy for my test machine in the new Driver Update section of the Intune update section.

The policy picks up my machine and is displaying a list of available drivers both recommended and other.  

However, when I release/approve the drivers, they never get deployed to my computer.  I suspected initially it was because my Windows 11 Update Ring has Windows Drivers set to "blocked".  However, when I unblocked it for a test run, it still didn't deploy those drivers.  

Reports show nothing is wrong, so there's no errors to see.  It's like there's a policy that needs to be activated/disabled before it can deploy those drivers.  Anyone else have this issue?

[#2]

@William Cunningham did you enable the windows drivers settings in your update rings policy ? 

[#3]

@eliekarkafyI normally have that disabled, but I did turn it on for 24 hours and it still didn't update.  However, I wasn't sure if it relied on that or not as the documentation seems to indicate it doesn't need that setting enabled (which may just be my misinterpretation).  If it is required, I'll enable again and let it be for longer than 24 hours.

[#4]

it is required so the update rings schedule handle the drives updates as well . keep me posted .

[#5]

@eliekarkafy Thanks!  I'll re enable it and test again then.

[#6]

Hi, I am having the same issue: Did enabling the 'allow' driver updates in the Windows 'Updates rings' policy work e.g. the 'Driver updates' approved were then deployed?

(I have re-read the Intune Driver updates configuration guide and I cannot see if this setting affects/undermine the 'Driver updates' approvals from deploying. My way of thinking - and maybe yours was/is too - is that this is separate from 'Update rings' setting and if device has a 'Driver updates' policy assigned, then the setting is applied to download driver updates, as I don't want to deploy update that are not approved if something is setup wrong.

Maybe the devs are assuming we know what is going on and how it works in the backend, but I dont want the 'Update ring' to be a SOE policy that has driver update 'allow' and then have PCs that are not in the Driver update groups, start pulling down un-approved updates if a group is misconfigured/deleted etc.; just the way I look at it.)