Microsoft Surface drivers not available for download
deadpoint opened this issue · comments
Driver Automation Tool 7.2.3
Regardless of which OS version I select when the Manufacture is Microsoft I get "No matches found. Please try another OS/Build". I've updated/replaced OEMLinks.xml with the file/fork from https://raw.githubusercontent.com/ajn142attamu/DriverAutomationTool/msSelfHostCatalog/Data/OEMLinks.xml, but that does not change the issue.
Hey, that's me! Haven't seen this, though we're not running 7.2.3 (my fork of the 7.2.2 code with W11 23H2 support patched in instead). Let me see if I can replicate.
So, my experience with 7.2.3 is that I find no models for W11 22H2 or 23H2, but find 27 models for W11 21H2. Running my fork of the 7.2.2 source, I find no models for W11 23H2 (seems to match the contents of the Microsoft catalog from OSDeploy), 12 models for W11 22H2, and 27 models for W11 21H2 (same as 7.2.3). I don't see the same behavior with any manufacturer except Microsoft, so I can't guess why it's happening, and the 7.2.3 source hasn't been shared.
All I can do is plug my fork, which has all the same features as 7.2.3 and can be run side-by-side with 7.2.3. To use my fork, you can copy https://github.com/ajn142attamu/DriverAutomationTool/blob/master/Current%20Branch/7.2.2/DriverAutomationTool.ps1 into C:\Program Files\MSEndpointMgr\Driver Automation Tool. I recommend clearing the C:\Program Files\MSEndpointMgr\Driver Automation Tool\Temp directory. After that, just run the script from an admin PowerShell window, instead of launching the .exe
maybe we need a fork that will just use the catalogs from "https://github.com/OSDeploy/OSD/tree/master/Catalogs" they often update them and last one was the surface one to include the latest models
maybe we need a fork that will just use the catalogs from "https://github.com/OSDeploy/OSD/tree/master/Catalogs" they often update them and last one was the surface one to include the latest models
That’s what I was doing in my fork, yes, along with some other bug-fixes. I’ve ported those on top of the 7.2.3 source that was released last week here. Additionally, I PR’d OSD last week and got them to add about 7 Surface models that were missing from their catalog, including the latest Surface Laptop Studio 2 and the Surface Go 4.
To use the updated 7.2.3 version of my fork, instructions are the same, URL changed slightly, you can copy https://github.com/ajn142attamu/DriverAutomationTool/blob/master/Current%20Branch/7.2.3/DriverAutomationTool.ps1 into C:\Program Files\MSEndpointMgr\Driver Automation Tool. I recommend clearing the C:\Program Files\MSEndpointMgr\Driver Automation Tool\Temp directory and nuking the C:\Program Files\MSEndpointMgr\Driver Automation Tool\Settings\OEMLinks.xml file, and letting the script recreate those as needed. After that, just run the script from an admin PowerShell window, instead of launching the .exe
something else that could be optimised i think is the whole package/source/content cleaning process...
something else that could be optimised i think is the whole package/source/content cleaning process...
Without a doubt. I'm hopeful for improvements on that in the 8.0 rewrite, though I may make an effort to address in my fork if I can find the work hours to attempt it. No promises though, as all my efforts are based on addressing bugs that get in my way.