Access Database is getting corrupt again and again

Has anyone employed the workstation registry hack provided here by ITYIPMan and found it to work without combining it with the DisableLeasing workaround on the server?

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/934

I couldn't agree more with the last few posts.  While we appreciate some bugs can take longer to fix than others, this is a long time for an issue with such a serious impact on existing systems.  I, like many posting here, am a Microsoft Partner and it is embarrassing that Microsoft are giving the impression of doing nothing by their almost complete absence of information or action on the matter.  As suggested, contact a poster here and see if Microsoft Engineers can examine systems where this is happening and 'reproducible'.  In a marketplace which is becoming evermore competitive, this issue is simply adding to the difficulties of selling an Access solution to clients.  Microsoft are always sending out surveys asking questions like 'How easy do we make it to do business with Microsoft?'.  Well, on this matter, it is making life very difficult.  Feedback, any feedback from Microsoft engineers as to the stage of their progress/testing a fix would at least let your paying customers (Mostly Office 365 E3 in my case) know that there is some light at the end of the tunnel.

Agreed.  Whether Microsoft likes it or not, Access is still the best tool for many applications.   Believe me, I've tried converting to other formats and the ease and speed of development and the responsiveness it gives me to my clients' requests cannot be matched.  Not all applications are sales force applications; not all applications need to be scalable .  We deal with complex data manipulation and it's getting harder to maintain customer confidence when dealing with this particular issue.

I couldn't agree more with the last few posts.  While we appreciate some bugs can take longer to fix than others, this is a long time for an issue with such a serious impact on existing systems.  I, like many posting here, am a Microsoft Partner and it is embarrassing that Microsoft are giving the impression of doing nothing by their almost complete absence of information or action on the matter.  As suggested, contact a poster here and see if Microsoft Engineers can examine systems where this is happening and 'reproducible'.  In a marketplace which is becoming evermore competitive, this issue is simply adding to the difficulties of selling an Access solution to clients.  Microsoft are always sending out surveys asking questions like 'How easy do we make it to do business with Microsoft?'.  Well, on this matter, it is making life very difficult.  Feedback, any feedback from Microsoft engineers as to the stage of their progress/testing a fix would at least let your paying customers (Mostly Office 365 E3 in my case) know that there is some light at the end of the tunnel.

Hi Shane. Ok, I take back the "bozo" term but a LOT of people are extremely frustrated by this issue. It is having a very negative impact on both developers and their clients and has been present for a very long time.

I don't understand how you can say that the problem is not reproducible. This issue has many people tearing their hair out. I question the amount of resources that are being deployed to find a fix.

Seems that Shane has a sense of humor and took it OK.

Large companies are typically not on the cutting edge so as to never have to deal with exactly this type of issue!  Normally, they hold back 6 months to a year, or a generation or 2 behind to ensure stability (amongst other things).

The issue I've faced with my smaller clients isn't me requesting a registry change, most apply it immediately or let me do it, but the real issue is down time because of the issue.  It can take hours or days of this repetitive issue before they call me in.  So countless hours where mission critical systems are down, employees are being paid, but effectively can't work, telling clients "our system is down please call back later", ...  to the point that I am just finishing up migrating one client's Access db (been running flawlessly for 8-10 years now)  to another platform because it impacted his business so much.  After a couple botched updates that took them down previously and then this, the owner said enough is enough.  He figures the investment will pay itself off with just one more such issue out of Redmond.  It is sad, because he was very satisfied with the database otherwise, but business people don't have time for these issues!  I'm actually surprised with all the issues relating to Win10 and Office 2016/365 that we haven't heard of any class action lawsuits.