So I've run into a particularly strange predicament with a new M.2 drive that I've bought, a WD BLACK SN770 2TB. This is my third M.2 I've installed in my PC, and I'm using it strictly for installing VST instruments for music composition software I have. I'm currently running Win11, and this PC was built by me from the ground up, and out of the 6 other hard drives (3 HDDs, 1 SSD, and two M.2s, not including the one I'm dealing with currently) that I've installed, I've never run into any issues like this.
I've installed the M.2 into the third M.2 slot on my mobo, and everything seems as normal, Device Manager detects the drive, Disk Management shows the disk, and I'm able to initialize the drive with no problems, then initiate the partitioning/formatting process as I've always been able to do with the other drives. Then, right after Disk Management shows it's created a new primary partition in the drive, it hangs for a hot minute, then it displays a "The operation failed to complete because the Disk Management console view is not up-to-date..." error (see image, Disk 6 is the drive in question)
If I were to format the drive to create a new volume and assign a drive letter, I get this error:
This same error will also pop up if I try to access the "Properties" of the partition. If I try to just assign a new drive letter, it pops up the first error message.
Using Command Prompt as an admin to run DISKPART, the disk in question (which is labeled "Disk 6," like in Disk Management) has the following attributes:
If I were to clean the drive using the "clean" command, then observe Disk Management while executing the "create partition primary" command, it'll show as if a partition gets created, then DISKPART will hang for a few minutes, then return a time-out error with the following return:
I've also downloaded a third-party software, Macrorit Partition Expert, and attempted to clean the drive, partition the drive, then format the volume and assign it a drive letter, this is the error that pops up:
I've downloaded WD's SSD Dashboard and downloaded the firmware update for the SN770, and I've updated all my drivers for my mobo, and nothing has fixed it.
I've also gone into "Safe Mode with Command Prompt" and attempted to use DISKPART there with the exact same results.
Oddly, however, I have booted Command Prompt in the Windows Recovery Environment (winRE) and attempted to use DISKPART to format the drive, and I'm actually able to go through the whole process of cleaning, intitializing, partitioning, and formatting the drive and then assigning it a drive letter with no problems. However when I boot back to desktop, Windows no longer recognizes the drive is formatted, and keeps producing the same errors as before if I attempt to assign it a drive letter.
I've tried doing all the above steps with the drive initialized with MBR and with GPT and it doesn't change the outcome. I've also tried selecting different file systems and allocation sizes when attempting it in Disk Management with no avail. I've even attempted to discuss this problem with LLM AIs to see if I missed something, and every suggestion it produced I've already attempted, with exception of trying the drive in another computer, which I currently don't have easy access to do so. The ONLY strange thing that somehow AI was able to help me uncover was that in Device Manager, the minute that the partition is created in the drive, an "Unknown Device" pops up in "Other Devices." If the partition is deleted, then the "Unknown Device" goes away. This is separate from the disk itself, as the SN770 shows up in Device Manager before and after. (See images)
Anyone else have any ideas as to what may be the problem?
I've installed the M.2 into the third M.2 slot on my mobo, and everything seems as normal, Device Manager detects the drive, Disk Management shows the disk, and I'm able to initialize the drive with no problems, then initiate the partitioning/formatting process as I've always been able to do with the other drives. Then, right after Disk Management shows it's created a new primary partition in the drive, it hangs for a hot minute, then it displays a "The operation failed to complete because the Disk Management console view is not up-to-date..." error (see image, Disk 6 is the drive in question)
If I were to format the drive to create a new volume and assign a drive letter, I get this error:
This same error will also pop up if I try to access the "Properties" of the partition. If I try to just assign a new drive letter, it pops up the first error message.
Using Command Prompt as an admin to run DISKPART, the disk in question (which is labeled "Disk 6," like in Disk Management) has the following attributes:
If I were to clean the drive using the "clean" command, then observe Disk Management while executing the "create partition primary" command, it'll show as if a partition gets created, then DISKPART will hang for a few minutes, then return a time-out error with the following return:
I've also downloaded a third-party software, Macrorit Partition Expert, and attempted to clean the drive, partition the drive, then format the volume and assign it a drive letter, this is the error that pops up:
I've downloaded WD's SSD Dashboard and downloaded the firmware update for the SN770, and I've updated all my drivers for my mobo, and nothing has fixed it.
I've also gone into "Safe Mode with Command Prompt" and attempted to use DISKPART there with the exact same results.
Oddly, however, I have booted Command Prompt in the Windows Recovery Environment (winRE) and attempted to use DISKPART to format the drive, and I'm actually able to go through the whole process of cleaning, intitializing, partitioning, and formatting the drive and then assigning it a drive letter with no problems. However when I boot back to desktop, Windows no longer recognizes the drive is formatted, and keeps producing the same errors as before if I attempt to assign it a drive letter.
I've tried doing all the above steps with the drive initialized with MBR and with GPT and it doesn't change the outcome. I've also tried selecting different file systems and allocation sizes when attempting it in Disk Management with no avail. I've even attempted to discuss this problem with LLM AIs to see if I missed something, and every suggestion it produced I've already attempted, with exception of trying the drive in another computer, which I currently don't have easy access to do so. The ONLY strange thing that somehow AI was able to help me uncover was that in Device Manager, the minute that the partition is created in the drive, an "Unknown Device" pops up in "Other Devices." If the partition is deleted, then the "Unknown Device" goes away. This is separate from the disk itself, as the SN770 shows up in Device Manager before and after. (See images)
Anyone else have any ideas as to what may be the problem?
Facebook
Twitter
Instagram