Help with weird problem related to 8.3 filename and filrsystem convert

The maximal FAT32 volume size is 2 terabytes with a sector size of 512 bytes and the maximum FAT32 volume size is 16 TB with a sector size of 4,096 bytes.

Samuria is right FAT32 does not include direct built-in support for long filenames, but FAT32 volumes can optionally hold a VFAT for long filenames in addition to short filenames in exactly the same way as VFAT long filenames have been optionally implemented for FAT12 and FAT16 volumes.

AOMEI can do NTFS->FAT32 and FAT32->NTFS, you do not specify which operation you used.

I'm sorry that I cannot bring a solution to your problem, It looks like Aomei NTFS to FAT32 had problems dealing with the VFAT on your Drive and if the drive is converted to FAT32, I'm pretty sure there is no remnant of the converted MFT left.

In the other Case then Aomei had problem converting the VFAT to MFT and the same situation occurred with the current MFT.

You should have performed this on a copy of your drive "in case" something goes wrong.

The safest way to do this (The only way I do it): is to use another drive format it and copy the files from the other file system to it.

This way there is absolutely no chances that you will end loosing anything.

Thank you all for your help I will try the batch rename thing
but before that
I want to know how windows knows the previous name when I changed only the"g" in "PN3"
see the example
please note that this will happen only on the original drive I tried to copy and cant remember the original name

MaloK said:

Samuria is right FAT32 does not include direct built-in support for long filenames

Sorry, I'm going to disagree once again with this statement. To prove it, do this:

Format a thumb drive with FAT32. Create a file and rename it to something like "This is a file with a long filename.txt".

I just did it, no problem whatsoever.

hsehestedt said:

Sorry, I'm going to disagree once again with this statement. To prove it, do this:

Format a thumb drive with FAT32. Create a file and rename it to something like "This is a file with a long filename.txt".

I just did it, no problem whatsoever.

Yes of course, but your thumb drive also contains a secondary partition called VFAT that contains the long file names.

Without it Fat32 does not support long file names, as every other FAT file systems.

In fact Any systems that are not VFAT aware cannot read long file names in any of them.

That is why I suggested that something went wrong when converting the VFAT to MFT or the opposite.

mam2 said:

Thank you all for your help I will try the batch rename thing
but before that
I want to know how windows knows the previous name when I changed only the"g" in "PN3"
see the example
please note that this will happen only on the original drive I tried to copy and cant remember the original name

Your drive Partition table is corrupted, one way, or another. Copy the files to a sane File system before trying to rename them.

MaloK said:

Yes of course, but your thumb drive also contains a secondary partition called VFAT that contains the long file names.

Without it Fat32 does not support long file names, as every other FAT file systems.

In fact Any systems that are not VFAT aware cannot read long file names in any of them.

That is why I suggested that something went wrong when converting the VFAT to MFT or the opposite.

Okay, I understand your point now. But regardless of the mechanism, VFAT is still a part of FAT32 in any modern OS. I guess that we were simply looking at this from different angles, but I now understand and agree with what you were saying so it's all good

hsehestedt said:

Okay, I understand your point now. But regardless of the mechanism, VFAT is still a part of FAT32 in any modern OS. I guess that we were simply looking at this from different angles, but I now understand and agree with what you were saying so it's all good

Absolutely, but it is still a FAT add-on that has to be processed correctly by migration software.

Agreed. I just considered that a given, kind of like having to be able to understand the MBR, etc. But point taken. Thanks for the clarification.

MaloK said:

Your drive Partition table is corrupted, one way, or another. Copy the files to a sane File system before trying to rename them.

to ntfs or fat32 ?

it is now ntfs
it was before fat32
so before the problem
ntfs--->fat32(problem)--->ntfs

it will not recognize the original name after copying to ntfs file system or fat32
just on the original drive
is the "Partition table" fixable ?