Access Database is getting corrupt again and again

I believe this all surfaced with Windows 10 update KB4100403.

Thanks for the clarification David.  Yes I agree that in large organisations that the IT dept has control over what patches can be applied to both clients and servers but in most cases if they are not willing to apply a client side fix that has little or no side effects, they will not be willing to apply any fix to a shared server where there are known side effects.

I just think it should be made clear in this thread that the Client side fix does in fact work when applied to all Win 10 clients and getting IT depts to apply it is much easier than getting them to apply any server side "fix".

Has anyone developed a Bat file that removes the Disable_Leasing registry keys from the Server (runned with admin priveleges) ?

I wouldn't like to ask the ITs to remove manually these registry entries. I tried a lot to convince them run a single batch file with the disable leasing. Now asking them to remove manualy registry entries will be ... world war 3 !!!

I'm new to this thread.

I'm relieved and not at the same time after reading these 33 pages.

I'm a small-time developer with 500 user sites,

Setup is : Access 97 on a shared drive on a Windows server

and PCs with  VB6 program installed accessing the database.

All going well for 25 years until past 6 weeks when all the clients had to get their PCs updated to Windows 10. 

I now have email phobia!

Just waiting for the next email to announce the dreaded  3343 database corrupt message.

Has anyone had persistent positive feedback on the simple option of  changing the folder of the database file on the server? 

from Daniel Pineault's site:

https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/

MAKE A NEW FOLDER: As astonishing as this may sound, several users have now confirmed that simply creating a new folder (on the same drive) and moving their database to the new folder resolved the issue.

George,

I guess I am amazed and a bit skeptical that just moving the back end database to a different folder on the server and relinking the tables on the front end would resolve anything. I am glad it is working for you and I hope it is not temporary. I am sure there are varying levels of how deep the path goes to the back end database as far as folders and sub-folders if we would survey the people here who are experiencing this problem. So I am wondering what the trick was in your case if this does indeed permanently resolve your problem. Or was there some other change that occurred at the same time such as the frequent compact and repair? I am just a bit puzzled by your results, while at the same time happy it helped you.