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

Continue on 0x80070490 error - caused by third-party driver #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Taiwan22
Copy link

@Taiwan22 Taiwan22 commented Feb 8, 2024

When you install MPLAB X IDE, it will install some USB drivers, and then DriverUpdater fails when uninstalling drivers, leaving you with an unusable Windows installation. Maybe in some future update it will be good to remove just SurfaceDUO drivers...

@gus33000
Copy link
Member

gus33000 commented Feb 21, 2024

Hi, such issues are generally caused by third party vendors doing incorrect driver installations on their own. Drivers must be removable, such failures indicate that the vendor did something wrong. We previously had a tiny discussion on the matter on telegram that I will verbatimly copy here:

Gustave Monce:
are you one of these people that installed some piece of software which installs drivers incorrectly? think i saw a comment on this one day

which explains these

winerror.h: 0x80070490
ERROR_NOT_FOUND
Element not found.

dism /Image:<Drive Letter>: /Get-Drivers /Format:Table

scroll til you see oem195.inf

should be third party

Jorik:
oem195.inf     | dlusbaudio.inf                               | No    | MEDIA                 | DisplayLink Corp.     | 8/10/2023  | 11.2.3084.0

Gustave Monce:
yeah this isn't from us

Jorik:
Indeed, I did download Displaylink drivers myself

Gustave Monce:
yeah sounds like displaylink is breaking something of their own which breaks the dism api's uninstall function

Jorik:
So can I just delete that .inf and retry?

Gustave Monce:
if it even let's you remove it

so far that's failing offline with dism

Jorik:
Why do third party drivers need to be removed in order to update your Duo driver packs? And if this is necessary, can't DriverUpdater do a check for third party drivers before actually starting the uninstall process (which makes it unable to boot into Windows after the error to fix it online). I know I should've thought of it myself, but just wondering.

Gustave Monce:
>Why do third party drivers need to be removed in order to update your Duo driver packs?

They don't need to

>  And if this is necessary, can't DriverUpdater do a check for third party drivers before actually starting the uninstall process (which makes it unable to boot into Windows after the error to fix it online

There is no easy way for me to know what drivers are third party vs what drivers are our own, that's why this isn't possible to both not remove them rn, and also add a warning, it would require even more work that i don't have the time at the moment to handle, not to mention, this is a bit of a work around the real issue at play behind the scenes here that we have to fix another day

ideally, display link would also ship non broken driver packages

I don't think ignoring the failures is the right thing to do either. Ideally we really need a good way to know which drivers are ours to only touch ours. I do want to know for example when my drivers fail to be serviced, and I also think it's about time we stop un installing old drivers this way and do it a bit better as this causes issues. Leaving this open because I'm not too sure on this still.

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