MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.

Run the "DriverGrabber 2.0.exe" and watch it Grab all of the drivers from your system and place them into a "Drivers" folder!

It now even grabs drivers that are no longer in use... For instance... a Printer Driver that is no longer physically connected to your system while you perform a backup.

Also... you can now use DriverGrabber on a Windows PE disk like LiveXP! It auto detects if it is being executed in a PE environment... it will attempt to auto detect the Windows Drive you wish to backup as well.

Fixed - A few bugs in the code causing DriverGrabber to fail finding the correct path to grab some driver files.

Changed - DriverSearch is now set to Off by default. If anyone has issues with backups I suggest they try to turn DriveSearch on and then post their log on the forum so I can make sure their drivers are properly backed up in a future release of DriverGrabber. We are still in Beta... and I'd like to have DriverGrabber functioning as well as I can without the need for DriveSearch.

Please test this version of DriverGrabber out and report back any issues. When reporting issues please try to post your DriverGrabber.log file to help narrow down a problem. If you get a "Not Found!" error on a specific file that can not be grabbed... please run a search on your entire system to verify the file even exists anywhere on your computer.

Share this post

Link to post

Share on other sites

Some "generic" advice, prompted by your post on reboot.pro (if I may ):

I'm not one to want to re-invent the wheel. So I don't want to copy someone elses work. I don't feel like I need to find out how someone elses program works. I'm pretty sure I'm on the right track as it is.

I'd rather have some honest feedback from fellow users and try to implement requested features that would benefit DriverGrabber. I don't want to change DriverGrabber to function just like another program.

A lot of [soviet Army soldiers] ask me how one can become a constructor, and how new weaponry is designed. These are very difficult questions. Each designer seems to have his own paths, his own successes and failures. But one thing is clear: before attempting to create something new, it is vital to have a good appreciation of everything that already exists in this field. I myself have had many experiences confirming this to be so.

Share this post

Link to post

Share on other sites

Fixed - A few bugs in the code causing DriverGrabber to fail finding the correct path to grab some driver files.

Changed - DriverSearch is now set to Off by default. If anyone has issues with backups I suggest they try to turn DriveSearch on and then post their log on the forum so I can make sure their drivers are properly backed up in a future release of DriverGrabber. We are still in Beta... and I'd like to have DriverGrabber functioning as well as I can without the need for DriveSearch.