Windows 10: driverquery output dates messed up

Not sure when this happened but I believe it was before the Creators Update. The link dates for drivers shown by the driverquery command are no longer correct or useful. For instance, here are the first few lines of output from my 15063.540 Win 10 Pro X64 system.

Code: Module Name Display Name Description Driver Type Start Mode State Status Accept Stop Accept Pause Paged Pool(bytes) Code(bytes) BSS(bytes) Link Date Path Init(bytes) ============ ====================== ====================== ============= ========== ========== ========== =========== ============ ================= =========== ========== ====================== ================================================ =========== 1394ohci 1394 OHCI Compliant Ho 1394 OHCI Compliant Ho Kernel Manual Stopped OK FALSE FALSE 4,096 204,800 0 12/10/2006 4:44:38 PM C:\WINDOWS\system32\drivers\1394ohci.sys 4,096 3ware 3ware 3ware Kernel Manual Stopped OK FALSE FALSE 0 81,920 0 5/18/2015 6:28:03 PM C:\WINDOWS\system32\drivers\3ware.sys 4,096 ACPI Microsoft ACPI Driver Microsoft ACPI Driver Kernel Boot Running OK TRUE FALSE 155,648 405,504 0 10/1/2096 3:53:06 AM C:\WINDOWS\system32\drivers\ACPI.sys 24,576 AcpiDev ACPI Devices driver ACPI Devices driver Kernel Manual Stopped OK FALSE FALSE 8,192 8,192 0 12/7/1993 6:22:19 AM C:\WINDOWS\system32\drivers\AcpiDev.sys 4,096 acpiex Microsoft ACPIEx Drive Microsoft ACPIEx Drive Kernel Boot Running OK TRUE FALSE 36,864 61,440 0 3/1/2087 8:53:50 AM C:\WINDOWS\system32\Drivers\acpiex.sys 4,096 acpipagr ACPI Processor Aggrega ACPI Processor Aggrega Kernel Manual Stopped OK FALSE FALSE 4,096 4,096 0 1/24/2081 8:36:36 AM C:\WINDOWS\system32\drivers\acpipagr.sys 4,096 AcpiPmi ACPI Power Meter Drive ACPI Power Meter Drive Kernel Manual Stopped OK FALSE FALSE 8,192 4,096 0 11/19/2006 9:20:15 PM C:\WINDOWS\system32\drivers\acpipmi.sys 4,096 acpitime ACPI Wake Alarm Driver ACPI Wake Alarm Driver Kernel Manual Stopped OK FALSE FALSE 8,192 4,096 0 2/9/1974 7:10:30 AM C:\WINDOWS\system32\drivers\acpitime.sys 4,096 ADP80XX ADP80XX ADP80XX Kernel Manual Stopped OK FALSE FALSE 0 1,101,824 0 4/9/2015 4:49:48 PM C:\WINDOWS\system32\drivers\ADP80XX.SYS 4,096 AFD Ancillary Function Dri Ancillary Function Dri Kernel System Running OK TRUE FALSE 323,584 118,784 0 3/25/2096 12:36:43 PM C:\WINDOWS\system32\drivers\afd.sys 8,192 ahcache Application Compatibil Application Compatibil Kernel System Running OK TRUE FALSE 147,456 12,288 0 7/29/2004 12:52:50 AM C:\WINDOWS\system32\DRIVERS\ahcache.sys 4,096 AmdK8 AMD K8 Processor Drive AMD K8 Processor Drive Kernel Manual Stopped OK FALSE FALSE 90,112 49,152 0 6/16/2040 3:17:43 AM C:\WINDOWS\system32\drivers\amdk8.sys 4,096 AmdPPM AMD Processor Driver AMD Processor Driver Kernel Manual Stopped OK FALSE FALSE 90,112 45,056 0 12/23/2077 4:48:10 PM C:\WINDOWS\system32\drivers\amdppm.sys 8,192[/quote] See the date ranges from 1974 to 2096. Yet if you look at them on the hard drive they are correct:
Code: C:\Users\rrkurtz>dir C:\WINDOWS\system32\drivers\amdppm.sys Volume in drive C is Lenovo_C Volume Serial Number is FC29-1F8F Directory of C:\WINDOWS\system32\drivers 03/18/2017 04:56 PM 172,544 amdppm.sys 1 File(s) 172,544 bytes 0 Dir(s) 136,170,500,096 bytes free[/quote] Where is driverquery getting it's information from and why is it so messed up?

How do I get Microsoft's attention on this as it is a real hindrance to debugging BSODs.

Note: This is not just my system, it is ALL WINDOWS 10 SYSTEMS.

:)

 

E51 messes up the date!

Thank you for your reply but that option is already set to off in my phone.

 

E51 messes up the date!

I've seen this on my e71. It happens in certain cellsites. The only workaround is to turn "network operator time" off and set the date/time/timezone manually.

 

Long before, apparently...

https://social.technet.microsoft.com...7itprohardware

 

It's gotten much worse in later Windows 10 builds with dates 20, 30, 40 or 50 years in the future. Why can't Micorsoft comment on this and why can't they fix it.

The driver dates were being reported correctly for ther initial; Win 10 releases up through ther Anniversary update. I think it was after that they went completely screwy.

 

yea. driverquery is broken. Use driverview from Nirsoft instead. (Under View, you can customize column output as well)

 

That works great. driverview /stabular drivers.txt gives a decently formatted output that can be sorted as needed.
Driverview can be redistributed as long as nothing is left out or changed.

Thank you @ComputerGeek.