Skip to main content
Super User

Return to Answer

Fixed spelling, fixed formatting for readability.
Source Link
edit approved Aug 28, 2013 at 17:29
user201262
edit approved Aug 28, 2013 at 17:29
user201262

I think you just have to persistantalypersistently tell it no, and a force manuel.
Locate manually
Let Me pick from the list
Have disk
Browse, find the INF
and whatever other persistant manuel is nessisarymanual installation.

Follow these steps:

  1. Locate manually
  2. Let Me pick from the list
  3. Have disk
  4. Browse, find the INF and whatever other persistent manual is necessary.

With enough persistancepersistence you can even install a completlycompletely wrong driver into a driver slot, very rarely you could even cause a no-boot situation. Hopefully you know what it is and what belongs there for sure before forcing it in.

I think you just have to persistantaly tell it no, and force manuel.
Locate manually
Let Me pick from the list
Have disk
Browse, find the INF
and whatever other persistant manuel is nessisary.

With enough persistance you can even install a completly wrong driver into a driver slot, very rarely you could even cause a no-boot situation. Hopefully you know what it is and what belongs there for sure before forcing it in.

I think you just have to persistently tell it no, and a force manual installation.

Follow these steps:

  1. Locate manually
  2. Let Me pick from the list
  3. Have disk
  4. Browse, find the INF and whatever other persistent manual is necessary.

With enough persistence you can even install a completely wrong driver into a driver slot, very rarely you could even cause a no-boot situation. Hopefully you know what it is and what belongs there for sure before forcing it in.

Source Link
Psycogeek
Psycogeek
  • 9.1k
  • 7
  • 52
  • 74

I think you just have to persistantaly tell it no, and force manuel.
Locate manually
Let Me pick from the list
Have disk
Browse, find the INF
and whatever other persistant manuel is nessisary.

With enough persistance you can even install a completly wrong driver into a driver slot, very rarely you could even cause a no-boot situation. Hopefully you know what it is and what belongs there for sure before forcing it in.