Snappy Driver Insta...
 
Notifications
Clear all

We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!

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.

[Sticky] Snappy Driver Installer Origin v1.17.6

7 Posts
4 Users
3 Reactions
447 Views
Glenn
(@glenn)
Member Admin
Joined: 7 years ago
Posts: 1834
Topic starter  

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


   
Quote
Topic Tags
(@stigg)
Eminent Member Registered
Joined: 5 years ago
Posts: 27
 

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?

This post was modified 1 week ago 2 times by Stigg

   
Glenn reacted
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 7 years ago
Posts: 1834
Topic starter  

@stigg To rebuild indexes: Close SDIO, go to the SDIO/indexes directory and delete the contents, start SDIO, it will rebuild the indexes.


   
ReplyQuote
(@stigg)
Eminent Member Registered
Joined: 5 years ago
Posts: 27
 

Posted by: @glenn

@stigg To rebuild indexes: Close SDIO, go to the SDIO/indexes directory and delete the contents, start SDIO, it will rebuild the indexes.


Thanks, Glenn.
I had two folders in there. SDI and SDIO.

But it's worked.

Thank you.

 


   
Glenn reacted
ReplyQuote
(@elreymon)
Active Member Registered
Joined: 9 months ago
Posts: 9
 

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)]

   
Glenn reacted
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 7 years ago
Posts: 1834
Topic starter  

@elreymon Thanks for the report. More wackiness in the realtek inf files  😆 fixed in the next update.


   
ReplyQuote
(@patch)
Active Member Registered
Joined: 2 weeks ago
Posts: 6
 

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.


   
ReplyQuote
Glenn's Page