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.
Version 1.17.6.827
1 February 2026
NOTE The new hash algorithm will change index behaviour. You need to make sure your indexes are rebuilt. Older versions of SDIO may not be able to read the new indexes. Make sure you are running the latest version of SDIO.
* Samlab Driver Packs 26.00.0
* SDIO Driver Packs 26.01.5
* Experimenting with a different hash algorithm to try to avoid collisions across indexes
* Fixed bug not finding 10.0.1 type section names
* Added Serbian language courtesy of Bojan Maksimovic
Version 1.17.6 is broken for me.
No drivers are displayed, no matter whether I select Windows 10 or Windows 11.
How do I rebuild indexes?
@stigg To rebuild indexes: Close SDIO, go to the SDIO/indexes directory and delete the contents, start SDIO, it will rebuild the indexes.
Seems that the file rtu53cx22x64.sys is missing to USB\VID_0BDA&PID_8153&REV_3001 from DP_SDIO2_26015.7z 🤔
! sto: Skipping missing driver package file 'rtu53cx22x64.sys'.
! sto: Skipping missing driver package file 'rtu53cx22x64.sys'.
! sto: Skipping missing driver package file 'rtu53cx22x64.sys'.
flq: {FILE_QUEUE_COMMIT} 12:32:22.042
flq: Copying 'c:\users\ramon~1.esp\appdata\local\temp\sdio\realtek\11x64\rtl8153xx64_1153.21.20.1009\rtu53cx22x64sta.inf' to 'C:\Users\RAMON~1.ESP\AppData\Local\Temp\{8ce1cf98-e243-ae47-837e-bc4c1e9e650e}\rtu53cx22x64sta.inf'.
flq: Copying 'c:\users\ramon~1.esp\appdata\local\temp\sdio\realtek\11x64\rtl8153xx64_1153.21.20.1009\rtu53cx22x64.cat' to 'C:\Users\RAMON~1.ESP\AppData\Local\Temp\{8ce1cf98-e243-ae47-837e-bc4c1e9e650e}\rtu53cx22x64.cat'.
!!! flq: Error installing file (0x00000002)
!!! flq: Error 2: The system cannot find the file specified.
! flq: SourceFile - 'c:\users\ramon~1.esp\appdata\local\temp\sdio\realtek\11x64\rtl8153xx64_1153.21.20.1009\rtu53cx22x64.sys'
! flq: TargetFile - 'C:\Users\RAMON~1.ESP\AppData\Local\Temp\{8ce1cf98-e243-ae47-837e-bc4c1e9e650e}\rtu53cx22x64.sys'
!!! cpy: Failed to copy file 'c:\users\ramon~1.esp\appdata\local\temp\sdio\realtek\11x64\rtl8153xx64_1153.21.20.1009\rtu53cx22x64.sys' to 'C:\Users\RAMON~1.ESP\AppData\Local\Temp\{8ce1cf98-e243-ae47-837e-bc4c1e9e650e}\rtu53cx22x64.sys'. Error = 0x00000002
!!! flq: SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
!!! flq: Failed to commit copy queue. Error = 0x000003e3
!!! flq: FileQueueCommit aborting
!!! flq: Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
flq: {FILE_QUEUE_COMMIT - exit(0x000003e3)} 12:32:22.087
!!! sto: Failed to copy driver package to 'C:\Users\RAMON~1.ESP\AppData\Local\Temp\{8ce1cf98-e243-ae47-837e-bc4c1e9e650e}'. Error = 0x00000002
sto: {Copy Driver Package: exit(0x00000002)} 12:32:22.089
sto: {Setup Import Driver Package - exit (0x00000002)} 12:32:22.094
!!! ndv: Driver package import failed for device.
!!! ndv: Error 2: The system cannot find the file specified.
ndv: {Update Device Driver - exit(00000002)}
!!! ndv: Failed to install device instance 'USB\VID_0BDA&PID_8153\000001'. Error = 0x00000002
<<< Section end 2026/02/02 12:32:22.101
<<< [Exit status: FAILURE(0x00000002)]
@elreymon Thanks for the report. More wackiness in the realtek inf files 😆 fixed in the next update.
The program distribution package is located in a network folder, from where it is launched on workstations. And almost always the same situation arises: during the process of updating the network adapter driver, the program crashes because access to the network is lost for a short time. Please add a forced pause for a few seconds after updating network drivers so that access to the network folder can be restored.
I finally got around to researching this issue and it goes like this:The program distribution package is located in a network folder, from where it is launched on workstations. And almost always the same situation arises: during the process of updating the network adapter driver, the program crashes because access to the network is lost for a short time. Please add a forced pause for a few seconds after updating network drivers so that access to the network folder can be restored.
When Windows runs an executable, it keeps a handle to the exe file so it can swap code bits in and out of memory on the fly. When the exe file becomes unavailable that handle is no longer valid and Windows shuts down the process. Installing network drivers involves taking down the network. So, if you're running the application from the network, and you install network drivers, the network goes down, your application process becomes invalid, the application is terminated.
The best I can think of at the moment is to detect if you're running from a network share and if you're about to install a network driver and warn you that bad things are about to happen.