issue https://github.com/Microsoft/BashOnWindows/issues/552
explication https://blogs.msdn.microsoft.com/wsl/2016/06/15/wsl-file-system-support/

Inodes in Linux have a number of attributes which don’t exist in Windows, including their owner and group, the file mode, and others. These attributes are stored in NTFS Extended Attributes associated with the files on disk. The following information is stored in the Extended Attributes:

Mode: this includes the file type (regular, symlink, FIFO, etc.) and the permission bits for the file.
Owner: the user ID and group ID of the Linux user and group that own the file.
Device ID: for device files, the device major and minor number of the device. Note that WSL currently does not allow users to create device files on VolFs.
File times: the file accessed, modified and changed times on Linux use a different format and granularity than on Windows, so these are also stored in the EAs.

In addition, if a file has any file capabilities, these are stored in an alternate data stream for the file. Note that WSL currently does not allow users to modify file capabilities for a file.

The remaining inode attributes, such as inode number and file size, are derived from information kept by NTFS.
Interoperability with Windows

While VolFs files are stored in regular files on Windows in the directories mentioned above, interoperability with Windows is not supported. If a new file is added to one of these directories from Windows, it lacks the EAs needed by VolFs, so VolFs doesn’t know what to do with the file and simply ignores it. Many editors will also strip the EAs when saving an existing file, again making the file unusable in WSL.

Additionally, since VFS caches directory entries, any modifications to those directories that are made from Windows while WSL is running may not be accurately reflected.

C'est nul. ils pourraient mieux synchroniser les fichiers sans EA plutot que les ignorer.

ce problème la est chiant aussi.
https://github.com/Microsoft/BashOnWindows/issues/729