On a typical Windows 10 installation there's quite a number of unrecognized Device Interface Classes. Some are genuine, others seem to be setup classes (so these are supported too?) or some other guids.
As a further improvement, we should list those and try to resolve all or most of them, learning on their nature in the process.
Done. There are two remaining which are completely obscure (no mention in the google nor in latest SDK) + a number of hyperv-related class guids which we don't care about.
Original report by me.
On a typical Windows 10 installation there's quite a number of unrecognized Device Interface Classes. Some are genuine, others seem to be setup classes (so these are supported too?) or some other guids.
As a further improvement, we should list those and try to resolve all or most of them, learning on their nature in the process.