Windows 10: I found a null pointer access bug in fat, exfat and cdfs filesystem driver in windows kernel

I have implemented a minifilter driver that attempts to deny access to the removable device volume content for the OS, until a specialized antivirus application scans the volume content. This causes a BSOD in:

:)

 

App Error - Null Pointer

Same to me i get application error,details Null pointer java/lang/Null pointer exception in my nokia c1 when i try to access my mails

 

Extended FAT (ExFat) and Windows 10

Because NTFS has a lot of dependencies on it that ExFAT doesn't haven. Access Control List, certain programs like Office require it, not to mention third party programs, developer tools and even server software. Parts of Windows are also specifically optimized
for NTFS.

 

NTFS vs ExFAT for a non-system SSD

You don't have to use FUSE to use ExFAT on Linux.

I use this kernel module to read/write ExFAT filesystems when the need arises.
dorimanx/exfat-nofuse · GitHub


The point is though, that NTFS read/write is supported in the kernel, and is enabled by default on most distributions.
ExFAT however is not supported in any way in the kernel, and requires compiling a third-party kernel module and inserting it into the kernel. This is only feasible on a system which you have total control over, and if you understand how Linux, compiling, and kernel modules work.

Android can only use ExFAT if the OEM has purchased a license for the filesystem. Since android uses the Linux kernel, I'm sure you can cross-compile to module I linked above and slip it into the firmware, but that requires a rooted phone, and far more knowledge of Android/Linux/Whatever architecture processor your device has.