I would like to know how Windows behave in that case.
It closes and cancels and removes the parts of the file it didn't fulle transfer from target source only if it is a controlled cancellation (e.g. you press cancel, or Windows enforces a cancel for some reason)
A crash is not considered a controlled cancel, but as Lister said, Windows won't delete a file until it is actually (fully) transferred.
On an uncontrolled cancel corrupt/incomplete files may be present on the target destination. The safest way to address it is to simply move the remaining files in the source-storage and tell Windows to REPLACE duplicates.
Note though, that data loss still might have occurred, since the file transfer also has complicated hardware-wise factors that the operating system can't control/monitor in every aspect (such as HDD internal cache etc).
I'm really interested to know how a potential data loss can translate,
assuming it crashed while copying a txt file of a few bytes - missing
file ? Corrupted file?
It all depends on what kind of file it is and how and what for it is used.
As an example: a text file may still be readable, yet some part of it missing. This could be alright, unless this text file is used by some program to read setting or other stuff that might crash the program if incomplete.
You can't really know for sure if there's been any data-loss if you don't have the original set of files to compare total amount of files, exact total size etc.