Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Surface Drivers for Windows 11 now missing (catalog update script from "everydayintech" in use) #198

Closed
spotopolis opened this issue Jan 16, 2025 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@spotopolis
Copy link

On a device running Windows 11 and on/in the desktop environment, if I try and run the "Update-OSDCloudSurfaceDriverCatalogJustInTime.ps1" script, it looks like it only sees my device as a Windows 10 device.

I initially ran into this issue in WinRE, so I wanted to test it on a separate system in the Desktop environment to verify the issue was not with the image.

On this device, I have a fresh install of OSD. No modifications have been made. It will no longer pull Windows 11 driver links.

Image

It looks like Windows 11 driver packs are not being merged into the catalog for this model (and possibly others?)
This is a Windows 11 24H2 system. This is what I have found so far digging though the catalogs

driverpacks.json has the driver packs listed:

Image

However, CloudDriverPacks.json and MicrosoftDriverPackCatalog.json are now both missing Windows 11 drivers for this device while still listing Windows 10 drivers for these devices.

Image

Image

@OSDeploy
Copy link
Owner

Thanks for sharing ... I'll check this later tonight to see if I can track down the issue.

@OSDeploy
Copy link
Owner

Also be aware this Repo doesn't have the drivers, they are part of the OSD Module so issues posted in this Repo may not be seen. Here's the OSD Repo https://github.com/OSDeploy/OSD

@spotopolis
Copy link
Author

spotopolis commented Jan 16, 2025

Thanks for sharing ... I'll check this later tonight to see if I can track down the issue.

Thanks for the response. I found that the issue happened in the current OSD v25.1.14.1. I looked back at v24.11.13.2 and the driver references for Windows 11 were present.

@spotopolis
Copy link
Author

Also be aware this Repo doesn't have the drivers, they are part of the OSD Module so issues posted in this Repo may not be seen. Here's the OSD Repo https://github.com/OSDeploy/OSD

Sorry. My mistake. I have them both starred in my github for quick reference. Didnt notice I was on the wrong repo

@OSDeploy OSDeploy transferred this issue from OSDeploy/OSDCloud Jan 16, 2025
@OSDeploy
Copy link
Owner

Thanks for sharing ... I'll check this later tonight to see if I can track down the issue.

Thanks for the response. I found that the issue happened in the current OSD v25.1.14.1. I looked back at v24.11.13.2 and the driver references for Windows 11 were present.

I have a script that runs to build these, but I don't validate the links to make sure it ran properly (no time), so thanks for pointing this out

@spotopolis
Copy link
Author

Thanks for sharing ... I'll check this later tonight to see if I can track down the issue.

Thanks for the response. I found that the issue happened in the current OSD v25.1.14.1. I looked back at v24.11.13.2 and the driver references for Windows 11 were present.

I have a script that runs to build these, but I don't validate the links to make sure it ran properly (no time), so thanks for pointing this out

Just verified. I booted up a test Surface Laptop 5 and stopped the startnet.cmd from running. I then made an edit to "Initialize-OSDCloudStartnet.ps1" in the existing OSD v24.11.13.2 baked into my WinRE image.

I commented out lines 146 - 159 to keep the OSD module from updating. I then saved the script, and ran startnet.cmd again. After it had finished going through WiFi and got me to my image menu, I was able to call the surface driver catalog update and then download the correct windows 11 drivers for this SL5

@OSDeploy
Copy link
Owner

OSD 25.1.16.2 is released with updated Surface Drivers. Closing this Issue!

Image

Image

@OSDeploy OSDeploy self-assigned this Jan 17, 2025
@OSDeploy OSDeploy added the bug Something isn't working label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants