none
Cannot read EXFAT drives created on MAC OS

    Question

  • Hello, 

    Have tried to locate this problem all over the internet and on the MS forums.. but the only thing I find is that "it can't be done". I find this hard to believe since MS created ExFat.... 

    I do have MACDRIVE installed on my system and have been able to read any MAC drives handed to me.. until the introduction of ExFAT... Now.. when my clients give me MAC drives formatted with ExFat, my Windows 8.1 Pro system tells me that the "Drive needs to be formatted". If I inspect the volume with DISK MANAGEMENT it tells me that the file system is RAW... any lookups on RAW online say "drive is corrupted"... but this is not the case... I took the drive to someone with a MAC and they read it perfectly.. when I asked what format the drive was in.. the answer.. ExFat. 

    I understand that the problem is MAC is formatting ExFat with some kind of proprietary BOOT STRAP which makes the Win system unable to read it.. but has nothing been done with this? No driver update? For either side? 

    Am I going to have to purchase a MAC system JUST to read ExFat.. which is ironic since it was created for compatibility... 

    Any help with this will be greatly appreciated! 

    Steven 

    Thursday, April 27, 2017 12:10 AM

All replies

  • Hello, 

    Have tried to locate this problem all over the internet and on the MS forums.. but the only thing I find is that "it can't be done". I find this hard to believe since MS created ExFat.... 


    I'm afraid it would be impossible. Because you mentioned "Have tried to locate this problem all over the internet and on the MS forums" and in vain.
    ___________
    Ashidacchi
    Thursday, April 27, 2017 2:18 AM
  • Hi Steven,

    According to my research, Windows can’t read exFAT drive formatted by MAC, but MAC could read and write drive formatted by Windows.

    If it is possible, try to contact with the client and send the file again without format drive with ExFat.

    Or you could search for some third party software on google to open it.

    Best regards,

    Joy.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, April 27, 2017 12:47 PM
    Moderator
  • Hi Steven,

    According to my research, Windows can’t read exFAT drive formatted by MAC, but MAC could read and write drive formatted by Windows.

    If it is possible, try to contact with the client and send the file again without format drive with ExFat.

    Or you could search for some third party software on google to open it.

    Best regards,

    Joy.


    Funny, but I have just the opposite

    external enclosure Raid 0 (2x 3TB) so 6TB formatted as exFAT in Windows 10 (with creators update)

    MacOS  Sierra, Can't read or mount the exFAT.  So I redo the Raid 0 under Mac and format it as exFAT in MacOS. And now this exFAT works on both Mac and Windows 10

    very strange.

    DC

    Edit: I just figure out why in my case.

    When formatting exFAT in Windows 10 from Disk management

    If formats the exFAT using Allocation unit size of 2048 kilobytes

    if you right click on the drive and reformat the exFAT using allocation 1024 kilobytes

    then it will work in MacOS

    DC

    • Edited by DC-2017 Wednesday, May 24, 2017 5:15 PM
    Wednesday, May 24, 2017 4:56 PM
  • This entire proprietary file format bullshit is sheer idiocy. It's about high time microsoft and apple just started supporting each other's formats and stopped screwing their users because of this bullshit.

    Wednesday, September 27, 2017 9:55 PM
  • I just formatted my external drive exfat from within OSX and plugged in to PC running Windows 10. Same issue, but I have managed to fix it:

    Go to computer management and right click drive in question, mark as active and then assign a drive letter. After which, Windows might ask to run a scan and fix, do this and it will work.

    Works for me.

    Sunday, December 24, 2017 9:00 AM
  • Thanks.  This fixed my issue.
    Friday, January 12, 2018 3:42 AM