Windows is the fussiest about tiny issues. But, you can do it with gdisk and mkfs for exfat.
Sudo gdisk
Select the drive
Type o to make a new partition table that Windows will like.
Type n to make a 250MB partition of type 0c01, Windows reserved
250MB is 512,000 sectors,
Type n again to partition the rest of drive as type 0700, Microsoft basic data.
I don't know why you need that tiny partition in front, but every windows volume has it. It's not normally visible. So don't think it disappeared.
Now hit w to write the table. If there is stuff you want on the drive, copy it to another drive, because w will write a new partition table. All the existing files will be gone.
Windows likes monster-sized clusters on large, homebrewed at least, exfat drives. I use
Mkexfatfs -n some_name -s 1024 /dev/sdxy
That gives you a mount point name you can remember (-n) and 512k clusters.
Sector=512 bytes, 2 sectors =1kbyte. 1024 sectors = 512kbytes/cluster.
The process should require 15 minutes the first time. But, there is a caveat. Let's say you use rsync to load GBs onto the exfat drive in Linux.
Rsync will exit when the space for each file has been allocated. But most of them might not be written yet. Flash drives are slow, so, after rsync tells the file system what goes where, the machine can write the files in the background.
But, if you see rsync finished, so you use umount to eject the flash drive, for some reason it will unmount before the files are written. The directories will be visible in a file manager, so you'll feel confident you can pull the drive out, and take it to wherever you want to put those files.
You'll find the directories mostly gone. You can plug it back into the linux box, and mostly everything on you put on the drive will have disappeared.
But actually it was never there. You saw placemarkers, which in a file manager look like folders and files, even with thumbnails for photos. But the files were not written yet, because umount for fuse is not quite up to the task for exfat.
So, after you copy over all the files, you have to force the system to write the files, with the sync command. After rsync, or whatever else exits, run sync. It might run for 15 min to 1/2 hour. After sync exits, then your files are written.
Now you can umount, and remove the drive.
And you don't need to change ownership or permissions on exfat. It has now effect, because the metadata for it isn't really there. Exfat for Linux makes it look like it's there, so Linux doesn't freak out. But if you start using chmod and chown, you'll make ground beef out of it! Then you have to pull out the exfat drive and put it back.
ExFAT is only a useful option for a rare corner case. If you need for some reason to regularly move data in chunks larger than 4Gb, on a one off basis, between multiple random Windows (XPSP2. ExFAT is supported by the following operating systems: Windows 10 Mac OS 10.6.5 and newe If your operating system doesn't support exFAT we recommend you upgrade your OS to the newest Windows or Mac OS to ensure compatibility. Final cut x to premiere cc. ExFAT is supported in Windows XP and Windows Server 2003 with update KB955704, Windows Embedded CE 6.0, Windows Vista with Service Pack 1, Windows Server 2008, Windows 7, Windows 8, Windows Server 2008 R2 (except Windows Server 2008 Server Core), Windows 10, macOS starting from 10.6.5, Linux via FUSE or natively starting from kernel 5.4, and iPadOS starting from 13.1. External drive cannot be read.
Exfat Format Windows
Is Exfat Compatible With Windows 10
Adobe reader what is it. 1.5 Windows CE and TexFAT. TexFAT is an extension to exFAT that adds transaction-safe operational semantics on top of the base file system. TexFAT is used by Windows CE. TexFAT requires the use of the two FATs and allocation bitmaps for use in transactions.