A feature update 1803 causes an Access database to become corrupted in shared environment. It appears to be a SMB protocol change and does not affect versions of Windows before the 1803 update (including Windows 7 and 8). This is an ongoing issue, which surfaced at the end of May/early July. Microsoft has acknowledged the issue on a forum, but is curiously silent in terms of a resolution. I am wondering if anyone else is experiencing this issue and if so, did 1809 eliminate the problem. We have users that were “magically” updated to 1803 even though we have delayed updates. Here is more detailed information:
There are no conversations