Is Microsoft ever going to fix the "incorrect hdd" issue in Windows 10?

  • Thread starter Thread starter N7ck
  • Start date Start date
N

N7ck

Guest
66617c2a-b8c9-4c1a-86ea-0c327ab25290?upload=true.png

Description Disk drive
Manufacturer (Standard disk drives)
Model Samsung SSD 860 EVO 500GB
Bytes/Sector 512
Media Loaded Yes
Media Type Fixed hard disk
Partitions 1
SCSI Bus 5
SCSI Logical Unit 0
SCSI Port 1
SCSI Target ID 0
Sectors/Track 63
Size 9.10 TB (10,000,830,067,200 bytes)
Total Cylinders 1,215,865
Total Sectors 19,532,871,225
Total Tracks 310,045,575
Tracks/Cylinder 255
Partition Disk #3, Partition #0
Partition Size 9.10 TB (10,000,812,474,368 bytes)
Partition Starting Offset 16,777,216 bytes



5fdc18ed-254a-4a43-8e73-208990946d74?upload=true.png

Description Disk drive
Manufacturer (Standard disk drives)
Model ST10000VN0004-1ZD101 (10 TB)
Bytes/Sector 512
Media Loaded Yes
Media Type Fixed hard disk
Partitions 1
SCSI Bus 2
SCSI Logical Unit 0
SCSI Port 1
SCSI Target ID 0
Sectors/Track 63
Size 3.64 TB (4,000,784,417,280 bytes)
Total Cylinders 486,401
Total Sectors 7,814,032,065
Total Tracks 124,032,255
Tracks/Cylinder 255
Partition Disk #1, Partition #0
Partition Size 3.64 TB (4,000,785,104,896 bytes)
Partition Starting Offset 1,048,576 bytes



How exactly is Windows managing to get this wrong?

Does it not use the Hardware ID's anymore?

Continue reading...
 
Back
Top