[Clipper87]

I probably would have better created just 1 post for the locale issues:

Here too the date is misrepresented:

Autorun/Program/Creation & Last write time
Browser helper objects/Creation & Last write time
Scheduled tasks/Last run
Databases/... Creation & Last write time
MMC snap-ins/... Creation & Last write time

HARDWARE

Bios/date
Devices/Driver date
Network adapters/driver date
Video/driver date
Ports/Disk & Volume stamp
Virtual Machines/VirtualBox Creation & Last write time

There should be only 1 date (& time) format throughout the program to avoid confusion; right now several formats are used depending on the report section / item / entry

A date like 2018-06-07 is difficult to interpret (for all users)

Thx

[gtopala]

There should be only 1 date (& time) format throughout the program to avoid confusion; right now several formats are used depending on the report section / item / entry

Some date values are just strings, independent of locale.
For example (my old Lenovo T510 laptop)

• the BIOS date is stored as "09/26/2012"
  
• the Video Adapter BIOS date is stored as "03/25/11"
  

A date like 2018-06-07 is difficult to interpret (for all users)

ISO 8601 is a popular standard.

[Clipper87]

A date like 2018-06-07 is difficult to interpret (for all users)

ISO 8601 is a popular standard.

Agree but then there should not be a mix of date formats throughout the program; eg in Software/OS/Updates/Installed updates dates are show in the dd/mm/yyyy format whereas in -most- other places you stick to yyyy-mm-dd

[Clipper87]

With regards to dates stored as strings (such as in hardware) there's obviously not a lot you can do. In all other cases it would be helpful to have all dates represented in iso 8601 format

[gtopala]

With regards to dates stored as strings (such as in hardware) there's obviously not a lot you can do. In all other cases it would be helpful to have all dates represented in iso 8601 format

SIW 2019 v9.0.015
Date/Time updated to ISO 8601