Latest posts by Michael Pietroforte (see all)
- Author and member of the year 2019 – Why DevOps still doesn't rule the IT world - Wed, Jan 1 2020
- Results of the 4sysops member and author competition in 2018 - Tue, Jan 8 2019
- Why Microsoft is using Windows customers as guinea pigs - Reply to Tim Warner - Tue, Dec 18 2018
DriverView is useful for troubleshooting hardware issues because it allows you, with just a mouse click, to view drivers that are currently loaded. The free tool presents all loaded drivers in a table view with the following columns: driver name, address, file type (system driver, network driver, etc.), version, company, product name, modified date, create date, filename, and file attributes.
If your organization doesn't own an inventory solution that supports hardware inventory, and if you are not afraid of scripting, then you can use DriverView to collect hardware information in your network. The command line version allows you to store driver information in a text file in various formats (plain text, HMTL, XML).
I tested DriverView v1.25 on Windows 7.