We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Hello.
I am asking this because I have little experience with w11. I have ran SDIO on a w11 laptop and it says there are no drivers available (everything is up to date) which I find weird by checking current installed drivers. Of course I double-check "newer" and "more optimal" where checked.
I will keep doing tests.
SDIO supports Windows 11. I can't say the same for the drivers. Of course I have no control over the drivers. Others may have thoughts on this, unless I'm missing something I believe the manufacturers are yet to update their drivers to officially support Windows 11. Now we know that Windows 11 is pretty much Windows 10 with a new number and a bit of a facelift. By default SDIO looks for drivers that are compatible with the Windows version. You can tell SDIO to assume Windows 10 instead. Right click on the system information box in the top left of the display and select Windows 10. Be cautious.
Thanks. I assume it works. It seems w11 did get all proper drivers for this Lenovo laptop though.
Good day.
I have tested SDIO on a different w11 computer and it shows no available drivers. Standard SDI works just fine with same drivers and indexes.
see above
Its probably because of a separate issue on w11 where SDIO sees all available drivers as unsigned. I just raised a separate thread about it. To check, open up options and show 'Worse match' drivers. You should see available drivers labelled as 'Updated driver available (no signed)'. Oddly, SDIO also seems unable to read the signatures of drivers installed outside of their packs (e.g. via Windows Updates).
Then I suspect there's something else going on...