-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
MS Surface Pro 9 Win 10 file not found #487
Comments
Same. I checked MS and it shows the files: |
Hey, I think my fork might fix the Surface driver issue, we had the same issue with Windows 11 22H2. I haven’t figured out compiling the .exe or .msi like the repo owner, so you have to run the .ps1 directly from an Admin Powershell window. Let me know if that helps and I can see about putting in a PR. |
This works correctly! thanks! |
I have your ps1 a try and it does not solve the issue. it looks like the Dev needs to update the json file with new information. |
You may find the master branch (or possibly the SelfHostMSCatalog branch) on my repo more helpful. In short, my patch fixed the issue at-the-time, but like you found, DAT also depends on a catalog, and if the catalog is outdated, you're hosed. In the time since I posted my initial patch, both Dell and MS have changed their download site format, and MS has released new driver packs as well. From what I worked out, Maurice uses a tool called OSDeploy/OSD to generate the catalogs, and then hosts his own catalog files in this repo. My main branch changed that, and points at the OSDeploy repo instead, where those catalogs are updated ~1x/week to 1x/month. |
We also ran into issues where I didn't 100% grasp the logic used to decide whether to fetch the latest catalogs and OEMLinks.xml file, and we found a good workaround there was to manually replace the OEMLinks.xml file in your working directory with the one from my repo, but it's possible there may be additional issues in place. AFAICT pull requests etc., aren't frequently merged here, so my repo is getting fixes for issues as we run into them, but if we haven't encountered a particular issue then we also won't have attempted fixing it. Still a great tool overall, I dang sure couldn't have built it, I know just enough to tinker w/ things until they're fixed (aka enough to be dangerous). |
Thanks I got is to download with your selfhosted ps1 file. going to test it tomorrow |
Sounds good. My self-hosted files *may* be out of date, if I have time today I’ll commit new catalogs and stuff.
…________________________________
From: ChemKroonri ***@***.***>
Sent: Wednesday, September 13, 2023 10:28:28 AM
To: maurice-daly/DriverAutomationTool ***@***.***>
Cc: Nelson, Andrew ***@***.***>; Comment ***@***.***>
Subject: Re: [maurice-daly/DriverAutomationTool] MS Surface Pro 9 Win 10 file not found (Issue #487)
Thanks I got is to download with your selfhosted ps1 file. going to test it tomorrow — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented. Message ID: <maurice-daly/DriverAutomationTool/issues/487/1717858539@ github. com>
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Thanks I got is to download with your selfhosted ps1 file. going to test it tomorrow
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/maurice-daly/DriverAutomationTool/issues/487*issuecomment-1717858539__;Iw!!KwNVnqRv!G8JEyft5ipFLpkMLYkynPXVtOI30o8puzE8vRq36GkgFXAskFP4hpRMrqM2tyvGTjPrh9rgJajwqSOIjGeyl6rOlMw$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AU47NXPK37MQTYZHSMKJNRDX2HGJZANCNFSM6AAAAAAYVQCXUU__;!!KwNVnqRv!G8JEyft5ipFLpkMLYkynPXVtOI30o8puzE8vRq36GkgFXAskFP4hpRMrqM2tyvGTjPrh9rgJajwqSOIjGewhhlYMMg$>.
You are receiving this because you commented.Message ID: ***@***.***>
|
@ajn142attamu are you able to update the catalog again? Thanks! |
Workaround for the catalog here: #508 (comment) |
@cjmx2000 I'm sorry, I've been stuck buried under other problems at work, but I may revisit soon. In the meantime, if you change line 26 of your OEMLinks.xml to the value below it should fix things.
|
This catalog is current? |
@ajn142attamu Thanks! this is the link I have already It tries to download from here and never connects |
Yes @GeoSimos updated as of 2 days ago. https://github.com/OSDeploy/OSD/blob/master/Catalogs/MicrosoftDriverPackCatalog.json ETA: OSD is the tool Maurice uses to generate the catalogs he hosts, this change just redirects DAT to look at their repo instead of his for the catalog. |
This is not the same filename, have you cleaned any cached files from the tool and restart it? |
@GeoSimos this is the correct link per @ajn142attamu https://raw.githubusercontent.com/OSDeploy/OSD/master/Catalogs/MicrosoftDriverPackCatalog.json removed all files and started over. Success! thanks for the assistance, I should have started with that.
|
Glad it worked for you, have pulled my hair some times and this was the solution ;-) |
download from https://download.microsoft.com/download/e/9/a/e9a35d1b-7b4c-48d4-8619-5301d4c09f65/SurfacePro9_Win10_19044_22.101.15507.0.msi
file not found. Any help would be appreciated.
The text was updated successfully, but these errors were encountered: