Yes, that service lists an error (with TO BE from the “TO BE FILLED BY OEM” string that’s listed in several places, such as the About tab on the Home tab in the Dashboard).
On the boxes that work, the logs say:
OnStart()
Service started successfully.
CreateNewAlertManager: Creating Alert Manager.
CreateNewAlertManager: Connecting Alert Manager.
Detected model number WDBLGT
AlertMgrConnectionOpened: Alert Manager is now connected.
ClearPowerAlerts: Clearing all existing Power alerts.
On the box that doesn’t work, the logs say:
OnStart()
Service started successfully.
CreateNewAlertManager: Creating Alert Manager.
CreateNewAlertManager: Connecting Alert Manager.
AlertMgrConnectionOpened: Alert Manager is now connected.
Detected model number TO BE
ClearPowerAlerts: Clearing all existing Power alerts.
Unable to retrieve system profile for model TO BE
I guess I can hunt through the registry for “TO BE FILLED BY OEM” on one box and WDBLGT on the other and compare. I’ve already tried running the WDEnclosureMapSetup and WDEnclosureSetup MSI files directly from the latest update as a repair and as a uninstall, reboot, reinstall.
I’ve found “To be filled by O.E.M.” all over the registry:
HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\BIOS\
- BaseBoardVersion
- SystemFamily
- SystemManufacturer
- SystemProductName
- SystemSKU
- SystemVersion
SystemProductName on the working box has the actual model number, but otherwise both boxes are the same (“TO BE FILLED BY OEM”).
HKEY_LOCAL_MACHINE\SOFTWARE\Western Digital\Sentinel\
- ModelNumber
- SerialNumber
The box that works lists an actual model number and serial number at those two keys. The box that works has “DX4000” for Model, and all 0s for ModelId. The broken box has DS6100 for Model and a UID for ModelId. I don’t know why this box would be thinking it’s a DS6100 with no serial number.
TO BE FILLED BY OEM is also listed here: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SystemInformation\
- SystemManufacturer
- SystemProductName
The box that works also has TO BE FILLED BY OEM for the SystemManufacturer, though it has the correct SystemProductName. The same is true of CurrentControlSet, but not ControlSet002 (no SystemInformation key in ControlSet002).
WDBLGT (on the working box) is found in one additional place not listed above:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQMClient\Windows\CommonDatapoints\1012
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQMClient\Windows\CommonDatapoints\ is empty on the broken box, while the working box has a ton of keys.