Forum Discussion

AIE_KM's avatar
AIE_KM
Copper Contributor
Dec 22, 2021

Access 2016 still broken since last week

Community,   Many of our users are having the issue caused by KB5002099. We've fully installed all updates available from Windows Updates, and I even manually downloaded the latest updates in case ...
2016
access
AIE_KM's avatar
AIE_KM
Copper Contributor
Dec 28, 2021

Karl_Donaubauer 

Thanks for your update on the situation! You gave me so much hope! Unfortunately, our system isn't using DFS and the issue continues even when using the direct path \\servername\fileshare\databasefile. 

 

I see Microsoft added another section to the site, so I'm hoping it will get sorted out soon.

"There are pending fixes for the following builds:

  • Office 2013

  • Office 2016 MSI

  • Office LTSC 2021"

 

Karl_Donaubauer's avatar
Karl_Donaubauer
MVP
Dec 29, 2021

Hi,

 

Meanwhile it is clear that the problem is not only persisting with DFS, but also with other path methods like SUBST or MKLNK. We have a report here in the forum where someone writes that even using the server's IP address would be problematic, although that should work in theory.

 

Microsoft is working to fix some of the issues caused by the security updates. Others will remain as they are now considered a security threat. The information on the Access bug website should be updated soon.

 

If you can wait for all this to happen, then wait for the information and fixes. If you can't, then there are some workarounds depending on what exactly you are using etc. However, generally reverting to an older version of Office (before the security updates) is the only solution that will reliably help.

 

Servus
Karl
Access News
Access DevCon