What does it means this?
You won't have any control over the permissions anymore and you will not have the safety of the "windows_names" option but it should mount when you log into your system.
The udisks command is how Linux mounts a partition when you select it in the file manager. There are built in rules on how ntfs partitions are mounted when you use this default method. The default method mounts a partition somewhat like this:
UUID=3E20491C2048DD11 /media/Disco ntfs defaults,uid=1000,umask=077 0 0
You are the owner of the mounted partition ( uid=1000 ). But you are the only one that can access it ( umask=077 ). The "7"'s remove access to "group" and "others". That's what I meant when I said you will no longer have control over permissions. Linux can't change linux permissions on an NTFS partition outside of the "view" created by a mount.
It also has no idea what the "windows_names" option does. If this was just an isolated ntfs partition in all Linux machine it wouldn't matter. But this is a dual boot with an active Windows OS installed. Linux can create a file with a file name containing characters that Windows cannot interpret so when you log back into Windows that file is lost. The "windows_names" option prevents Linux from saving the file with a bad name so the issue is avoided. That's what I meant by safety. A bad choice of words in retrospect since it's not going to damage anything - Just be careful how you name files.
I don't understand which process starts before /etc/fstab and keep it busy?
That is the question that I admittedly am not smart enough to answer. The output of all the diagnostic commands I asked you to run indicate that it is not mounted before fstab is executed. I just don't know the answer.
Successfully mounted the partition using the udisks command I gave you in Startup Application is another way to mount partitions at login but it should not be necessary if everything was working correctly.