The customer reported this issue after they upgraded from Windows 8 to Windows 10.
A couple of things led to this error.
- They were hosting an Access Database on a Windows Server
- Multiple users were using it concurrently
- They have Windows 10.
Some investigation later, we found that it’s a known bug with Windows 10.
Which Microsoft has been working on since April 2019.
They do have a workaround, which involves disabling file leasing.
Reading a Microsoft note on File Leasing, I think all users of the Windows Server will suffer a performance penalty if we do that.