Bug/Issue Save crash indicating file permission issue, able to reproduce in single player as well as multi

Windows 10, Stardew latest Steam version

Symptom:
When saving after going to bed, the game crashes. Save game filenames are mangled and require fixing before the save shows up in the Load or Co-op screen anymore. Error log is created with an access denied message, but it does not log what path access is denied to.

Things I've tried:

• Changing folder permissions of my co-op save folder - no change
• Taking ownership of the co-op save folder - no change
• Running steam as admin - Fixes the issue but not a good solution
• Deleting the save folder and letting Stardew recreate it - Made worse; this caused the issue to occur not only in the co-op save but in a previously working single player save as well
• Deleting the entire Stardew Valley folder in %AppData%\Roaming\ and letting Stardew recreate it - no change
• Deleting the entire Stardew Valley folder in %AppData%\Roaming\ and letting Stardew recreate it, having started Steam as admin - no change
• Reformat and reinstall of windows 10, replacement of save files in appropriate folder - Fixes issue

Attached:
Typical error log

I realize that Windows 10 is a trash fire, but Stardew is the only game I'm seeing this behavior in.

 

Some research into this further following the fact that SetRenameInformationFile is what is failing, according to Prodmon:
https://social.technet.microsoft.com/Forums/windows/en-US/74edb0cb-3153-4479-a313-f465125aebdd/very-strange-file-rename-problem-with-redirected-documents-folder?forum=w7itprogeneral Similar issue with redirected windows user profile folders
https://github.com/prometheus/prometheus/issues/1628 describing an app inappropriately closing a file before trying to manipulate it
https://www.pcreview.co.uk/threads/sometimes-access-denied-whilst-saving-changes-to-source-files-on-network-drive-mapping.1236415/ describing antivirus interference

Attached: Procmon log showing API operation SetRenameInformationFile failing

 

Can also now confirm this does not persist after a flatten and reinstall