DLGDIAG 1.37 Cannot detect eSATA MyBook physical drives

I tried to run DLGDIAG 1.37 for windows on 2 different eSATA connected MyBook on 2 different PC’s, but DLGDIAG 1.37 fails to list them in the Physical drives list, it only shows the logical volumes and there is no way to start the diagnostics if it is not listed in the Physical drive list.
The PC’s are a DELL XPS 8300 and an MSI-GT70-0NC, both machines have eSATA ports that work fine in normal operations, the only problem is with DLGDIAG that does not list them as Physical drives. I tried the same drives on the same PC’s using a USB connection and got the exact same problem.
I then tried on a third PC Dell XPS 8700 using a USB connection and in that case the same drives seems to be detected correctly and appear on the Physical drive list, I could run both the quick and extended diagnostic in that case. There is no eSATA ports on the Dell XPS 8700, so I could not try that connection.

What prevents DLGDIAG 1.37 from detecting the Physical drive on eSATA and/or USB ports ?
This does not make any sense given that the drives work fine on the eSATA and USB ports on the first 2 machines listed above. So I tried to leave the eSATA drive disconnected and then the ones connected to the USB port worked correctly and showed up in the physical drive list of DLGDIAG.
DLGDIAG is run as administrator as suggested, but it doesn’t make any difference.
Systems are all running Windows 10 Pro X64, Ver. 20H2, Build 19042.662
Why is DLGDIAG having these issues with eSATA ?
The MyBook drives with eSATA ports are from Western Digital, why is the Western Digital diagnostic not handling the WD eSATA drives correctly ?
To isolate the problem I tried a different eSATA enclosure (iDsonix) with a WD drive in it, that works fine with DLGDIAG 1.37, the drive shows up in the Physical device list and I can run all the diagnostics and display the SMART drive info.
This means that the problem is in the WD MyBook eSATA interface.
Seems like definitely a design mistake in WD MyBook, I wonder if there is any new firmware for MyBook to fix the problem ?