Access Database is getting corrupt again and again

This is crazy,

Tried the DisableLeasing, the 2 PC were running slow, ages to start, lots of blank screens, did eventually load but really made me think what is going on, did not like the feel of this so rolled back again. It might have settled, I don't know, did at least 3 restarts but simply could not risk having the Main Win 8 PC behaving oddly as would be completely dead without it. Never got to really find out if this would work as i'm going away and can't risk the main Win 8 PC having issues so did not put disableleasing in the redg. 

However now back in the position that I need to stop one PC from upgrading again, even though I rolled back last time it was 2 days before it installed again, this is **** madness.

wushowhide I have not been able to use, the 1803 upgrade just happens, never been able to see it ready to install to tell it not to, I do read it does not seem to help anyway as MS intent on forcing this through.

This delay feature should NOT be just something in Windows Prof. perhaps more important on the simple home variety.

3 months after initial problem, surely they have a proper fix on the normal update.

I am a non-tech small business, do not have a tech department to work on this while I'm away. 

MS should be ashamed of themselves but we all know that.

I totally agree that MS should be ashamed of themselves but for a reality check think back to how long it took them to fix the broken scrolling in forms when they introduced that one a while back. From memory it was 3 months or longer so I'm not holding my breath on this one. They are worse than hopeless.

Thanks for you reply,

I won't hold my breath.

Would not be so bad if all versions on WIndows 10 had the deferred update, I have a few Pro's & that's easy

the Home versions were OK, I rolled back & been weeks since its tried to update but now every few days it auto updates.

I have not been able to use wushowhide, perhaps just me but not got the chance.

Am using the metered connection work around but I seem to remember there were reasons that this is not ideal, apart from having to manually check/install updates.

When I have time I will try update and use the DisableLeasing patch but it did not feel right & not being around I could not afford to find it had side effect on the main PC which is still Windows 8.

I wish there was more information on the effects of DisableLeasing in this instance on Windows 10 machines as well as Windows 8, for it to have such a dramatic effect fixing such a messy problem I can't help feeling there is more to it.

Thanks again,

I implemented the DisableLeasing back in the second week of June on our 2012 R2 Server only,  that is where our backend data is housed.  We haven't had anymore corruption issues since.  And honestly I really haven't noticed any speed or performance issues in retrieving data.    I like everyone else is waiting for MS to fix the problem,   DevHut has a little more info on the matter.

Absolutely correct.  MS needs to get on top of this.  We are losing money, productivity and credibility as long as this problem persists.  I cannot be remoting in to users' systems multiple times a day to fix their back-end databases.  I'm glad I found this thread though because I wasn't sure if the problem I'm encountering was happening to others in mid-August 2018.  It all started around August 13.

Clients do NOT like me suggesting applying fixes to their servers and I would never presume to do it myself. I'm their database designer, not their IT manager.  Not all of my clients even have IT managers.