https://bugs.winehq.org/show_bug.cgi?id=47349
--- Comment #1 from Lorenzo Ferrillo lorenzofer@live.it --- Created attachment 64825 --> https://bugs.winehq.org/attachment.cgi?id=64825 testcase
Ok, I was looking a bit into this. There seems to be two problems: First SetFileInformationByHandle should delegate the information setting to NtSetInformationFile.
Now NtSetInformationFile has a limited capabilities for setting file attributes, but that's not important for this bug. What's important is when I try to set timestamps. Timestamps are setted (the old timestamp differ from the new timestamp), but are setted to a different value that the one I specified, while this testcase when running on the testbot, seems to show that Windows return the exact setted value when querying the timestamp. Now this may be or may be not a serious problem. If the setted timestamp use a monotonic function (so bigger is the timestamp passed to the function, bigger is the timestamp setted), there should0nt be any problem, otherwise there may be issues to programs that use file timestamps as a sort of ordering (for example Bethesda Games for mods and DLCs load order)
Also seems that ChangeTime timestamp is not setted at all.