Hi,
I have not reported this before, as I had seen posts discussing the issue I will describe. I assumed the oddity would disappear, but it never did during the couple of years this has been going on.
When I save a file to a shared folder, from within a remote PC desktop to my local disc on my Mac... the resulting file seemingly always gets a Date Modified set to 29 Nov 2076 at 09:54.
It is a small irritation, but over the years, I have become pretty bitter of it persisting as it does. I am not a fan of Microsoft, and am reluctant to give feedback, as I see others have mentioned this without any effect. This has been across different laptops I have had, differens Mac OS iterations and obviously multiple versions of the Microsoft Remote Desktop App
What is this kind of bug actually? Something is stamping those files with that one date and time, stuck in the future...
3 Comments
I am also seeing this as well and it's through the Windows App that replaces MS Remote Desktop App.
I've been seeing this for a long time as well.
Presently, I'm running the Microsoft Remote Desktop version 10.8.4 (2111) on my MacBook Pro running Ventura 13.4.1 to access a Windows 10 Pro machine (22H2).
What makes this issue more disturbing, is that if I have a folder redirected from my Mac as read-only and I copy a file from that read-only folder to the remote Windows machine, not only is the timestamp of the copy on the Windows machine set to Nov 2076, but also the timestamp of the original file on the Mac is modified to Nov 2076.
I know some people don't have a high regard for timestamps on files but the act of copying a file from a read-only share should never modify anything about the original file.
Please could someone look into this issue?
I'm seeing the same as well. Would MSFT please step in and assist?
