>Thanks Al,
>
>The other server (2008 R2) is setup as a RDP. We were hesitant about running this "fix" on it since the registry settings in Win10 that show these settings weren't coming up in 2008 R2.
>
>
>
>>> I haven't seen anything myself, but:
>
>- Some corruption issues can be caused by SMB configuration settings as alluded to in your MSDN link. This link adds one more registry entry that should probably be set: http://www.alaska-software.com/community/smb2.cxp
>
>- Those types of corruption are generally caused by workstation SMB settings, not server (unless the server is an RDS server; in that case the registry settings should be applied there as well). AFAIK the server version should make no difference
>
>- Is it possible the sites where you're seeing issues have Windows 10 machines that have just been updated to the new 1903 feature version? You can check this by running WinVer from the search box or a CMD prompt. If any machines have been updated, it might be worth checking if any SMB registry settings that had been previously applied, were rolled back by the update

We have found that changing the compatibility of the executable icon (not the executable itself) the windows 7,corrects certain issues caused by version 1809 (I have not installed 1903 yet but I am sure it contain new chalenges.