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.
Version 1.16.0.818
10 November 2025
I've changed the way Win 11 is handled. Firstly, SDIO will no longer set the virtual OS if
Win 11 is detected. If it detects Win 11, you will see Win 11 in the System Information
panel. You can still set the virtual OS yourself if you choose. Secondly, because Win 11 is
not yet directly supported in the driver packs and because Win 10 drivers are compatible
with Win 11 anyway, when Win 11 is detected, SDIO will search for Win 10 drivers.
* Sam Driver Packs 25.11.1
* Show Newer is off by default
* Added available driver version, date and marker to driver list items.
* ForceWin10 option removed
* No longer set virtual os version when win11 is detected
* Because win11 is not currently supported in the driver packs, search for compatible win10 drivers
* Added Detect OS version to System panel context menu
* Updated translations
* Added checks to make sure script engine is initialised
* Added environment variable expansion to script directories (%appdata% etc)
* Updated list of known inf markers
I just tried the new version appears to be working well so far, but it's not recognising Windows Server 2025, screen shot attached
ive looked all over this site and can not find a link to install snappy
https://www.glenn.delahoy.com/snappy-driver-installer-origin/ive looked all over this site and can not find a link to install snappy
Hello Glenn,
Sorry if this sounds a bit noob, but I installed the latest SDIO via your webpage 'download link', but I downloaded 'Sam's Drivers' via your separate torrent link (as it was quicker than your SDIO torrent link - which automatically ran when I started the application).
So I transferred this torrent_downloaded 'Drivers' folder (46.5gb of zipped files) into the SDIO folder.. & renamed the empty 'Drivers' folder that was already in there as driver.old_empty. But I noticed another folder named UPDATE & when I opened that one, it had a dir named SDIO_update with another 'Drivers' folder with 38.6gb of zipped files. Where did these come from.. as the only 'DRIVERS' I downloaded were the Sam's Drivers, via a separate torrent link? Should I leave them both alone.. as I now have 2x DRIVERS folders, one with 46.5gb & a 38.6gb DRIVERS folder in the update folder? I was going to transfer the SDIO to a USB thumb drive.. as I wanted to install Win XP Pro (with AHCI slipstream).iso to an older laptop onto an SSD SATA3.
Hope that all makes sense.
PS: I also noticed that SDIO recommended the 'newer' AMD Link File for my AMD powered NUC box, but seeing other users comments about BSOD.. I've not installed it.
@x_y The Update folder is the temporary area where the torrent downloads are written. When the torrent is complete, the files are moved to the correct location. When the torrent does not complete some files may be left behind in the Upload folder. It is safe to empty that folder if you wish.
ps: good thing you're paying attention!
@glenn Thanks for the prompt answer, but I originally used 'qBittorrent' to download Sam's Drivers (46.5gb).. & they downloaded to my 'win11 Download folder'. So had to manually move them to the SDIO folder, as SDIO didn't do any of this. Thats when I noticed the UPDATE folder.. (with SDIO_update & containing another 'Driver folder' with 38.6gb of drivers. Were these automatically transferred from the 'Sam'd drivers folder?
