So I keep having an issue where OneDrive is stuck at trying to upload a ".lock_#" file that it shouldn't.
I've used a # to indicate that the file's ext seems to be perpetually be changing and in the snippet included it's .lock_15572 and I think that might be part of the issues. I've read that OneDrive should automatically prevent syncing any .lock files (which I honestly know nothing about) and my guess is that because nvidia is generating a number at the end of it with these 0 byte files that OneDrive doesn't seem them as a .lock file type but, in this example file type .lock_15572 as seen in the file properties.
I've tried adding "lock" and "lock_" to the onedrive exclusions, but that hasn't resolved the matter. That exclusion field also prevents some characters from being used, like "" and ".", which I found out when I tried to add an exclusion for "lock" in an effort to exclude and file with an extension that begins with "lock". I also tried creating a directory junction in a non-synced location on the same drive with it's target being a folder that is synced. This folder is where the nvidia overlay (which seems to try and start up with anything that can use hardware acceleration, like discord, edge, excel, etc.) would save any screen shots or video captures it might create, which it would be nice to have sync with onedrive, so you can save them there in case of hardware failure, for sharing, whatever.
Is there some way to add a wildcarded extension to the exclusion list in order to prevent syncing any file extension that begins with lock_ ?