Uniqueid disk id collision in Windows while using multiple nRF9160DKs

[Attila Katona]

Hi,

the following event is generated when I connect two or more nRF9160DKs to a Windows machine: "Disk 2 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue."

In command line starting the program "diskpart" I get the following information:

   DISKPART> select disk 1

   DISKPART> uniqueid disk

   Disk ID: 00000001

or

   DISKPART> select disk 2

   DISKPART> uniqueid disk

   Disk ID: 00000001

If I try to change the uniqueid to another value, I get the following error:

   DISKPART> uniqueid disk ID=00000002

   DiskPart has encountered an error: The request is not supported.
   See the System Event Log for more information.

As a result, the devices and the related COM ports are appearing / disappearing in the device manager.

Do you have any suggestion, how to avoid uniqueid disk collision?

Thank you!

[Albrecht Markus Schellenberger]

Attila Katona said:

I have tried it with these versions with a similar result:

  - Windows 10 Enterprise (64bit)

  - Windows 10 Home (64bit)

Thanks a lot, Attila! 

I connected 2x nRF9160 DKs to my computer running on a Windows 11 distribution and got the same behaviour.

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          xyz GB      0 B        *
  Disk 1    Online           10 MB      0 B
  Disk 2    Online           10 MB      0 B
  
DISKPART> select disk 1

Disk 1 is now the selected disk.

DISKPART> uniqueid disk

Disk ID: 00000001

DISKPART> select disk 2

Disk 2 is now the selected disk.

DISKPART> uniqueid disk

Disk ID: 00000001

Disabling the Mass Storage Device functionality for one or both DKs resolved the issue for me.

Regards, 

Markus