OEM drivers after upgrading to a new Windows 10 release

%3CLINGO-SUB%20id%3D%22lingo-sub-1908112%22%20slang%3D%22en-US%22%3EOEM%20drivers%20after%20upgrading%20to%20a%20new%20Windows%2010%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1908112%22%20slang%3D%22en-US%22%3E%3CP%3EComputers%20are%20managed%20through%20MEMCM%2C%20on%20prem.%3C%2FP%3E%3CP%3EAn%20issue%20we%20see%20on%20laptops%20regularly%2C%20after%20upgrading%20to%20another%20Windows%2010%20build%2C%20is%20that%20we%20generally%20need%20to%20deploy%20various%20model-specific%20drivers%2Fapps%20(otherwise%20the%20%22FN%22%20keys%20such%20as%20%22mute%22%20or%20%22screen%20luminosity%22%20won't%20work%20for%20example).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20expected%20%3F%20(all%20the%20other%20drivers%20are%20automatically%20migrated%20and%20works%20well)%3C%2FP%3E%3CP%3EIs%20Microsoft%20working%20with%20OEMs%20to%20find%20a%20more%20maintainable%20solution%20where%20we%20don't%20need%20to%20deploy%20model-specific%20drivers%20manually%20after%20upgrading%20Windows%2010%20build%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1908112%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20Hours%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1908210%22%20slang%3D%22en-US%22%3ERe%3A%20OEM%20drivers%20after%20upgrading%20to%20a%20new%20Windows%2010%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1908210%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F50128%22%20target%3D%22_blank%22%3E%40Lucas%3C%2FA%3E%26nbsp%3BAs%20a%20matter%20of%20fact%2C%20we%20are.%20%3A)%3C%2Fimg%3E%20We%20recently%20posted%20in%20the%20Windows%20IT%20Pro%20Blog%20on%20this%20very%20subject%20regarding%20the%20innovations%20in%20this%20space.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-it-pro-blog%2Fredefining-manual-driver-updates%2Fba-p%2F1829715%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-it-pro-blog%2Fredefining-manual-driver-updates%2Fba-p%2F1829715%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1908381%22%20slang%3D%22en-US%22%3ERe%3A%20OEM%20drivers%20after%20upgrading%20to%20a%20new%20Windows%2010%20release%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1908381%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F153765%22%20target%3D%22_blank%22%3E%40Steve%20Thomas%20(GLADIATOR)%3C%2FA%3E%26nbsp%3B%26nbsp%3BThanks%20for%20the%20link.%20It's%20still%20work%20in%20progress%20if%20I%20understand%20correctly.%3CBR%20%2F%3E%3CBR%20%2F%3E%22For%20IT%20professionals%20managing%20drivers%20on%20behalf%20of%20their%20organizations%2C%20there%20will%20be%20no%20change.%20The%20changes%20described%20above%20applies%20only%20to%20machines%20that%20are%20open%20to%20receive%20driver%20updates%20directly%20from%20Windows%20Update.%22%3CBR%20%2F%3E%3CBR%20%2F%3EI%20hope%20there%20will%20be%20something%20for%20MEMCM%20too.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Computers are managed through MEMCM, on prem.

An issue we see on laptops regularly, after upgrading to another Windows 10 build, is that we generally need to deploy various model-specific drivers/apps (otherwise the "FN" keys such as "mute" or "screen luminosity" won't work for example).

 

Is this expected ? (all the other drivers are automatically migrated and works well)

Is Microsoft working with OEMs to find a more maintainable solution where we don't need to deploy model-specific drivers manually after upgrading Windows 10 build ?

 

Thanks

 

 

2 Replies

@Lucas As a matter of fact, we are. :) We recently posted in the Windows IT Pro Blog on this very subject regarding the innovations in this space. 

 

https://gorovian.000webhostapp.com/?exam=t5/windows-it-pro-blog/redefining-manual-driver-updates/ba-p/182... 

@Steve Thomas (GLADIATOR)  Thanks for the link. It's still work in progress if I understand correctly.

"For IT professionals managing drivers on behalf of their organizations, there will be no change. The changes described above applies only to machines that are open to receive driver updates directly from Windows Update."

I hope there will be something for MEMCM too.
www.000webhost.com