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.
when it downloaded SDIO it put it on the desktop as soon as onedrive got full it stopped downloading and when i tried to start again i got this error i turned off onedrive and the error went away not sure if this is what is happening to everyone
i usually dont use onedrive when i installed windows i dont think there was a choice not to use it anymore
I had that issue too. But just the "Exception: std::bad_cast" Error Screen
For me, it helped to completely end the process in Task Manager
(or wait for it to close automatically)
and then restart it.
It’s best to run SDIO as an administrator and disable Defender (or whatever antivirus software you use) while using it.
Than restarting the SDIO worked perfectly.
But I know what caused the bug: During the index download, i activated "expert mode" on the left and enabled the "newer drivers" option... Apparently, the application can't handle doing that during the download.
errors
I concur,
unfortunately, ever since R830 release, when doing bulk update for the SDIO drivers, I constantly get error " Exception: std::bad_cast " - which causes SDIO to crash ! never saw this error with R829 ...
If I reduce the downloads to 3.9gb - 4.5gb per session I don't usually get that error ... although when compiling the new drivers - SDIO sometimes locks up - Not Responding ... and need to force a close window and re-launch SDIO ...
phooey, ... and SDIO just crashed out again with completion of a 3.1gb download session " Exception: std::bad_cast "
Also, I have an Acer Nitro 15 running win11x64 - recently I am noting SDIO is presenting 10x64 drivers - which often do not install - even though SDIO reckons install completed ...
... and how come there are recently so many bulk driver updates to the SDIO driver list ??
... recently when a new bulk drivers download list is available - if select - This PC Only, shows zero drivers, yet after all drivers downloaded, now displays more than 20 new drivers available for my machine - peculiar ...
attached screenshot - these drivers did not install , and crashed again ...
[ I wonder IF the crashings are related to last couple of M$ windoofs updates causing conflicts with SDIO ??? ]
... a progress update to my previous report,
last week found another bulk update, but even directly running with admin privileges, both the 32bit and 64bit SDIO struggled to download the files - even with selecting the minimum amount of downloadable files - SDIO continuously crashed ...
( I tried both SDIO32 & SDIO64 to make sure it was not a fault with the 64bit only )
... and this morning a mega drivers update - 26 driver files,
- I selected all files, and to my surprise the download fully progressed to 94% [over 12gb] before SDIO crashed - with that now usual error - " Exception: std::bad_cast " ;
... fortunately this time after resuming, today's drivers package completed with only that single crash .
PS.,
- the 2 drivers shown in my previous screen shot are still present , and still don't install - even though installer states install complete, those 2 drivers show up again ...
@trog7 Fun and games!
Fortunately a solution is close. Watch this space (or some other) for news...
Same issue here. i've noticed in task manager when trying to open SDIO that the 'system' task absolutely skyrockets in disk usage, enough that my PC (5800X/6750 XT) will momentarily freeze. I've seen it hit near 2Gb/s probably trying to read drives for the driver packs.
@glenn ,
oh dear, another bulk update, and today sdio wont comply with downloading any files without crashing ...
all I've managed to get were the index file and a couple others from the top of the list ...
but when restarting sdio, the index file returns again as a download option ...
is this possibly a checksum problem ?
regards,
We are in 2026, IPv6 was released since 2012, and more officially in 2017, but SDI(O) stills doesn't support it:
removed link
removed link
This issue has been consistently linked to IPv6 connectivity problems. Windows applications attempt to connect using IPv6 first if it’s enabled, but many of its update servers lack IPv6 (AAAA) DNS records. As a result, the connection fails and triggers the std::bad_cast exception.
A quick workaround is to disable IPv6 so that Windows defaults to IPv4, which the servers fully support.
Steps to Disable IPv6 Temporarily:
Press Win + R, type ncpa.cpl, and press Enter.
Right-click your active network adapter and select Properties.
Uncheck Internet Protocol Version 6 (TCP/IPv6).
Click OK, then disconnect and reconnect to your network.
Run SDI again — the update process should now work without crashing.
Example in PowerShell:
Disable-NetAdapterBinding -Name "Ethernet" -ComponentID ms_tcpip6
(Replace Ethernet with your adapter name.)
If you need IPv6 for other applications, re-enable it right after using SDI:
Enable-NetAdapterBinding -Name "Ethernet" -ComponentID ms_tcpip6
While this resolves the immediate problem, it’s a limitation in SDI’s current handling of mixed IPv4/IPv6 environments. The root cause is that Windows prefers IPv6 when available, but SDI’s update hosts only respond over IPv4. Until the developers implement proper IPv6 fallback or detection, disabling IPv6 remains the most reliable fix.
For long-term stability, adding an IPv4-only mode toggle in SDI settings would prevent such crashes without requiring this workaround.
