False alert about KB2983588 (duplicate disk ID) in Windows 10?

Introduction

Windows 10 is a powerful operating system that comes with a lot of features and functionalities. However, sometimes it can encounter issues that may cause it to slow down or malfunction. One such issue is the false alert about KB2983588, which suggests having duplicate disk IDs. This blog post will explore this issue and provide insights into what may be causing it and how to fix it.

Possible Causes of False Alert about KB2983588

The false alert about KB2983588 is usually caused by a bug in Windows 10 that incorrectly detects duplicate disk IDs. However, in some cases, it may be caused by actual duplicate disk IDs. For example, if you have cloned a disk or created a virtual machine, you may end up with duplicate disk IDs, which can cause this issue.

Another possible cause of this issue is GPT partitions. GPT partitions are a newer partitioning scheme that is used on modern hard drives. They are designed to replace the older MBR partitioning scheme, which has limitations. However, GPT partitions can cause issues with some older hardware or software, which may result in false alerts about duplicate disk IDs.

How to Fix False Alert about KB2983588

If you are experiencing a false alert about KB2983588, there are several things you can do to fix it. Here are some solutions you can try:

Update Windows 10

The first thing you should do is to ensure that your Windows 10 is up to date. Microsoft regularly releases updates that fix bugs and issues, including false alerts about KB2983588. To check for updates, go to Settings > Update & Security > Windows Update and click Check for updates.

Check for Duplicate Disk IDs

If your Windows 10 is up to date and you are still experiencing the issue, you should check if you have duplicate disk IDs. You can do this by using the Diskpart command-line tool. Here are the steps:

1. Open Command Prompt as an administrator.
2. Type “diskpart” and press Enter.
3. Type “list disk” and press Enter. This will show you a list of all disks connected to your system.
4. Type “sel disk X” (replace X with the number of the disk you want to check) and press Enter.
5. Type “uniqueid disk” and press Enter. This will show you the disk’s unique ID.

Repeat steps 4 and 5 for each disk listed in step 3. If you find duplicate disk IDs, you can try changing them using the “uniqueid disk ID={new ID}” command. However, be careful when using this command as it can cause data loss if not used correctly.

Convert GPT to MBR

If you have GPT partitions and are experiencing the false alert about KB2983588, you can try converting them to MBR partitions. Here are the steps:

1. Open Command Prompt as an administrator.
2. Type “diskpart” and press Enter.
3. Type “list disk” and press Enter. This will show you a list of all disks connected to your system.
4. Type “sel disk X” (replace X with the number of the disk you want to convert) and press Enter.
5. Type “clean” and press Enter. This will erase all data on the disk, so make sure you have a backup before doing this.
6. Type “convert mbr” and press Enter. This will convert the disk to MBR partitioning.

Repeat steps 4-6 for each disk that has GPT partitions. However, be aware that converting GPT to MBR will erase all data on the disk, so make sure you have a backup before doing this.

Disable Fast Startup

Fast Startup is a feature in Windows 10 that allows the system to start up faster by saving the system state to a hibernation file. However, this feature can cause issues with some hardware or software, which may result in false alerts about KB2983588. To disable Fast Startup, follow these steps:

1. Go to Control Panel > Power Options.
2. Click “Choose what the power buttons do” on the left side.
3. Click “Change settings that are currently unavailable”.
4. Scroll down to “Shutdown settings” and uncheck “Turn on fast startup (recommended)”.
5. Click “Save changes”.

Conclusion

The false alert about KB2983588 can be frustrating, but there are several ways to fix it. Updating Windows 10, checking for duplicate disk IDs, converting GPT to MBR, and disabling Fast Startup are some of the solutions you can try. However, be careful when using the Diskpart command-line tool or converting GPT to MBR as they can cause data loss if not used correctly. If the issue persists, you may need to seek further assistance from Microsoft support.

Currently, it seems that there is no resolution available for the issue. The most informative piece of research that the author has come across is a source where a Seagate engineer’s comments are cited:

The issue seems to be related to BOT vs UAS. On new machines with UAS you get the same Unique ID, it appears to be handled by UPnP. There doesn’t appear to be anything we can do about it. It appears to have something to do with the UAS driver as this does not happen when the same drives are connected via BOT. We would like to advise reaching out to Microsoft as well because this appears to be how the host bus handles Bulk Only Transport (BOT) and USB Attached SCSI (UAS) in Windows. The issue is not seen when connected to a host via BOT and is only seen when connected via UAS. So it appears to be dependent on the hosts bus and some underlying logic of the bus in Windows. It is something that Seagate cannot control