Wmic disk health code#

The third implements events based on the SMART status and the fourth provides methods that can be used to configure a SMART drive and initiate a test. The second provides the SMART data that this decision was based on but the format used varies according to the make of the drive and no information

The first provides information on the state of the drive similar to the state property already described. The only information available can be found in anĪrchived paper on the Micorosft site which describes four objects: MSStorageDriver_FailurePredictStatus MSStorageDriver_FailurePredictData MSStorageDriver_FailurePredictEvent MSStorageDriver_FailurePredictFunction There are (at least) four WMI objects that provide access to SMART but lack of

Wmic disk health code#

Yes 'so code not really relevant to my question' would be a common reply unless the explanation below seems to nullify that your code is accurate.

My code is fine, was from a fellow person on this forum - and I have checked what WMI is giving me using various tools such as WMI explorer - so code not really relevant to my question Thank you both for your replies - was mainly just trying to make sure that WMI was inaccurate rather than just me being inaccurate :) The image below shows what results I get from doing this - so will be much more informative than relying on WMI Smart Status value Think I will amend my code and start retrieving SMART values (specificallyĥ, 196, 197 and 198) - this along with smart overall health and ATA error values should give me a much more accurate report of the health of a drive I think from further testing tonight it is just retrieving the SMART overall health value and using that, which it appears from testing several faulty drives is more often than not still showing as not reporting any issues despite a disk have multiple bad

Yes I have done that and also used various other WMI tools to check the values I am receiving and it is definitely showing OK for status - so it seems whatever WMI is actually checking hardware wise is just inaccurate