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

Correct the Build Number for Win11-22H2 at line 13375 #489

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

ajn142attamu
Copy link

Previous value listed was 10.0.21621, value taken from a running Win11-22H2 system and the Microsoft update catalog is 10.0.22621.

Previous value listed was 10.0.21621, value taken from a running Win11-22H2 system and the Microsoft update catalog is 10.0.22621.
@ajn142attamu
Copy link
Author

Behavior under current 7.2.2 EXE

Error, "No matches found. Please try another OS/build"
image

Behavior under 7.2.2 PS1 downloaded from this commit.

Successful, "Found (8) models"
image

ajn142attamu and others added 2 commits June 22, 2023 13:54
Re-point OEMLinks.xml to the more frequently updated OSDeploy/OSD repository directly.
This reverts commit 8bd93d6 on the
patch-1 branch. This commit should have been made to the master branch.
@sebastiancrago
Copy link

Hi. I have made this change manually but I'm not able to replicate your results. With this change it's not returning me any models and is still erroring.

Is this still working for you?

@ajn142attamu
Copy link
Author

Yes. I think we've had to make other changes related to OEMLinks.xml to accommodate changes to Microsoft and Dell's driver catalogs in the time since I posted this though.

image

@sebastiancrago
Copy link

Is there any chance you'd be willing to share those? We have a use case to get the surface pro 9 working and it's only available under 22H2.

@sebastiancrago
Copy link

Never mind. Please ignore my request. I found your other comment that noted you need to run the script in powershell manually. I hope this pull request gets included for the next release.

@ajn142attamu
Copy link
Author

I hope so too! No worries, i'm glad you got it sorted. Been a rough bit at work and i havent had the time or energy to revisit this in depth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants