Thanks for help @ScruffR.
Some additional info, all from v1.44 since I wasn’t able to find an older windows installer (recent ones pull latest from repo and just reinstalls).
Doctor seems to be tripped up at identifying the device type. But ‘particle serial list’ returns
Found 1 device connected via serial:
COM4 - Boron
And ‘particle usb list’ returns
<no name> [e00fce68148a1206bf7a45f7] (Boron)
is it odd that this device returns no name?
And ‘particle serial inspect’ returns
Platform: 13 - Boron
Modules
Bootloader module #0 - version 400, main location, 49152 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #1 - version 403, main location, 671744 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
Bootloader module #0 - version 101
undefined module #0 - version 0
User module #1 - version 5, main location, 131072 bytes max size
UUID: 0C07E8644A16xxxxxxxxxxx.....
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #1 - version 403
undefined module #0 - version 0
empty - factory location, 131072 bytes max size
So you’d think device type could be resolved by doctor code.
Any other info needed?
This part should be moved to a separate post, but might be helpful to this topic.
Some background on why this might be. I performed a Factory Reset a couple of days ago, and cannot get the device past setup/listening mode ever since.
Mobile app (iPhone) setup will not progress past Pairing (stops at Error: Unable to find your mesh device…)
CLI/particle setup just returns back to command prompt after providing tips about how to get into Setup mode
CLI/particle flash of bootloader, system, and tinker via serial/DFU seems to work fine, but device stays in Setup mode
Workbench local compile and local flash of Tinker on 0.9.0 finishes with success, but no change in behavior.
Happy holiday!