Answer by Kamil Maciorowski for fdisk - Hex codes list - which ones are NTFS or FAT 32 among the below list?

It depends on what exactly you are asking.

1. If you're asking what partition types can hold a filesystem of the type NTFS or FAT32, the answer is any. The type of a partition is only to "encode" the purpose of the partition in the partition table itself, i.e. without any need to examine data inside the partition (and this is usually a filesystem). One is not obliged to create a "matching" filesystem, technically it can be anything.

   However, some tools do expect specific filesystems inside partitions of specific types. While it's possible to create an arbitrary filesystem (or anything) inside a partition of an arbitrary type, some combinations may cause trouble.

   ^{E.g. I managed to break my Debian by assigning the type "Linux temporary data" (it's not on your list, newer fdisk knows it) to a partition, not creating any filesystem there and rebooting the OS. Then systemd tried to mount it to /var/tmp/, failed, screamed and (effectively) died. I fixed this from a live USB distro. This was before I learned about Discoverable Partitions Specification.}

   And this brings us to…

2. If you're asking what partition types were created with NTFS or FAT32 in mind, then:

   • Microsoft basic data (EBD0A0A2-B9E5-4433-87C0-68B6B72699C7) for sure, although it may hold exFAT or other types of filesystems as well.

   • Windows recovery environment (DE94BBA4-06D1-4D40-A16A-BFD50179D6AC), I guess.

   • EFI System (C12A7328-F81F-11D2-BA4B-00A0C93EC93B), kinda, but not strictly.

     The EFI system partition is formatted with a file system whose specification is based on the FAT file system and maintained as part of the UEFI specification; therefore, the file system specification is independent from the original FAT specification. The actual extent of divergence is unknown: Apple maintains a separate tool that should be used, while other systems use FAT utilities just fine.

     ^(source)

   • Probably Lenovo boot partition and similar types.

   • …

     I mean there probably are other types created for FAT32 or maybe for NTFS. Or there will be. Your question lists 82 types; in September 2023 fdisk in my Kubuntu knows 200 types. There is room for more. I see no point in even trying to identify them all, you don't need to know them all. When you're trying to read a filesystem, only the actual type of the filesystem matters. In other words NTFS is NTFS regardless of what the partition table tells you about the partition. When you're creating NTFS or FAT32, you just need to know one thing which is…

3. If you're asking what partition type you should choose when creating a partition where you are going to create a general-purpose NTFS or FAT32, then the answer is definitely Microsoft basic data (EBD0A0A2-B9E5-4433-87C0-68B6B72699C7).

There is that other answer, IMO quite peculiar:

It is Apple TV recovery, No 44 in the list. fdisk on Kubuntu shows ntfs (in KDE Partition Manager displayed as ntfs and definitely is ntfs) as Apple TV recovery.

Along with few comments, that answer sounds like Apple TV recovery was the type for NTFS. This begs for being addressed specifically.

Apple TV recovery+ NTFS is technically possible (see the point 1 above). Somebody or something chose Apple TV recovery for the partition and (later or earlier) (the same or another) somebody or something created NTFS inside the partition.

Maybe even this is by design, I mean maybe even NTFS is the expected filesystem for such partition type (see the point 2 above). I totally don't know Apple TV, I cannot tell.

But the fact such combination exists somewhere in the world does not mean you or anyone should choose Apple TV recovery for a partition holding a general-purpose NTFS.