Windows 10: external ntfs partition recognised by one computer, but not the other

I have a 2TB disk in USB 2 housing which I formatted on my desktop computer as an NTFS volume. It is still recognised by this machine as an NTFS volume even when I plugged it in just now. However on my laptop it is just seen as a raw volume. I swapped it into different housing and tried again, just in case there was a firmware issue, but it still isn't recognised as NTFS.

I had an issue yesterday where a volume on another disk wasn't recognised as an NTFS volume by either computer, but Seagate Seatools told me that this was because the drive itself had failed. However running the short test in Seatools hasn't given me any indication that the drive in question today is in trouble. And as I said, on my desktop computer I can mount the drive and browse the folders without difficulty.

So I'm assuming that yesterday's issue and today's aren't connected, or am I wrong? How can I get my NTFS partition recognised by my laptop?

:)

 

What about bluetooth3+HS in Symbian Anna ?

how is that possible ? I tested my external drive which is only 300gb and ntfs and its not recognised . Also I hear people saying their ntfs drives are not recognized . Are you sure your drive is ntfs ?

 

USB External Drive formatted in FAT32 is not displayed in windows 10

Hi,

This external drive is new.

This drive is 1T formatted in FAT32 and contains some data.

This drive works perfectly with a Mac.

The drive connection is via USB 3.0.

My other external drive works perfectly on the same USB port but this other drive is formatted in NTFS.

I tried all USB ports of my computer: same results, not displayed.

After connected this new disk via USB, I can see it in "Device Manager->Disk Drives"

I can see it too in "Storage->Disk Management" but without assigned letter.

It's not possible to assign one (only delete volume action is possible).

No format type is displayed. For the others I can see NTFS.

Here is the visible information of this disk on "Disk Management"

Disk1: Healthy EFI System Partition 200MB, Healthy Primary Partition 931.19 G, Unallocated 128M.

How to fix it?

 

UPDATE:
I tried again and this time the partition was recognised (I had already tried several times before this). So the immediate crisis has been averted, but if anyone has any insight into why Windows can be so finicky about this, it might help someone in the future.