Uniqueid disk id collision in Windows while using multiple nRF9160DKs

RE: Uniqueid disk id collision in Windows while using multiple nRF9160DKs

Attila Katona — Wed, 29 Jun 2022 06:53:31 GMT

Hi Markus,

thank you for the solution. It has solved the issue with the same disk identifiers.

Best regards,

Attila

RE: Uniqueid disk id collision in Windows while using multiple nRF9160DKs

Albrecht Markus Schellenberger — Fri, 24 Jun 2022 11:29:20 GMT

[quote user="Attila Katona"]

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

- Windows 10 Enterprise (64bit)

- Windows 10 Home (64bit)

[/quote]

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

RE: Uniqueid disk id collision in Windows while using multiple nRF9160DKs

Attila Katona — Fri, 24 Jun 2022 07:16:02 GMT

Hi Markus,

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

- Windows 10 Enterprise (64bit)

- Windows 10 Home (64bit)

Best regards,

Attila

RE: Uniqueid disk id collision in Windows while using multiple nRF9160DKs

Albrecht Markus Schellenberger — Fri, 24 Jun 2022 07:12:52 GMT

Hello Attila,

Which Windows version are you using?

Regards,

Markus