> ## Content Index > Fetch the complete content index at: https://nolongerset.com/llms.txt > Use this file to discover other available public pages before exploring further. # Access Bug Alert: Errors When Opening Network Database Files - URL: https://nolongerset.com/bug-alert-file-in-use-could-not-lock-file/ - Published: 2021-12-18T03:14:58.000Z - Updated: 2026-05-08T13:00:19.000Z - Description: If you started receiving the error "File in use" or "Could not lock file" in December 2021, you may be the victim of an Access bug. Here's how to fix it. - Author: Mike Wolfe - Tags: Bug Alert, #Import 2026-05-20 02:59 If you started receiving either of the following error messages beginning on December 14, 2021 ("Patch Tuesday"), then you are likely the innocent victim of a Microsoft security fix with unintended consequences. [Error in Access when opening a database on a network file share![](https://support.microsoft.com/apple-touch-icon.png)![](https://support.content.office.net/en-us/media/de3fefbe-fd78-4990-a1eb-5764b9b1aa21.png)](https://support.microsoft.com/en-us/office/error-in-access-when-opening-a-database-on-a-network-file-share-6cbc1560-62c2-46e7-9980-d079a46f5acc) ## Sample Error Messages ### File already in use ![Error message, "Could not use '\\dev\d$\BE.accdb'; file already in use.](https://storage.ghost.io/c/eb/d7/ebd732c1-5f03-4f07-b386-5d08557e15c9/content/images/2021/12/image-41.png) \- > Could not use '\\\\path\\to\\backend.accdb'; file already in use. ***UPDATE*** *\[2022-01-08\]: I wrote an article with details about how to create a silent install to deploy the bug fix for a large number of computers. For my sample, I used the Access 2013 Runtime fix, but the same steps should apply for pushing the bug fix for other Access versions:* [Patching Access 2013 Runtime to Fix “File Already In Use” BugStep-by-step process to patch the 2021 Holiday Bug for Office/Access 2013\. These same steps can be adapted to patch other versions, too.![](https://nolongerset.com/favicon.png)No Longer SetMike Wolfe![](https://storage.ghost.io/c/eb/d7/ebd732c1-5f03-4f07-b386-5d08557e15c9/content/images/2022/01/workers-5246640_1920.jpg)](https://nolongerset.com/patching-holiday-bug-access-2013/) ### Could not lock file ![Error message, "Could not lock file."](https://storage.ghost.io/c/eb/d7/ebd732c1-5f03-4f07-b386-5d08557e15c9/content/images/2021/12/image-42.png) \- > Could not lock file. ***UPDATE*** *\[2021-12-29\]: There is a partial workaround for the "Could not lock file" error as it relates to the DBEngine.OpenDatabase method:* [Partial Workaround for the “Could not lock file” BugThis experimental function could help you avoid the “Could not lock file” error when running the OpenDatabase method of a DBEngine object.![](https://nolongerset.com/favicon.png)No Longer SetMike Wolfe![](https://storage.ghost.io/c/eb/d7/ebd732c1-5f03-4f07-b386-5d08557e15c9/content/images/2021/12/Could-Not-Lock-File-Workaround.jpg)](https://nolongerset.com/could-not-lock-file-workaround/) ## Affected Versions The problem is introduced in the following updates: - KB 5002104 for Office 2013 - KB 5002099 for Office 2016 - Office 2019 Version 1808, build 10381.20020 - Office LTSC 2021 Version 2108, build 14332.20204 **Microsoft 365 Apps**: - Current Channel Version 2111, build 14701.20248 - Monthly Enterprise Channel Version 2110, build 14527.20340 - Monthly Enterprise Channel Version 2109, build 14430.20380 - Semi-Annual Enterprise Channel (Preview) Version 2108, build 14326.20692 - Semi-Annual Enterprise Channel Version 2102, build 13801.21086 - Semi-Annual Enterprise Channel Version 2008, build 13127.21842 ## Working Versions The problem has been fixed as of the following versions: - Current Channel Version 2111, build 14701.20262 - Current Channel (Preview) Version 2112, build 14729.20170 - Monthly Enterprise Channel Version 2110, build 14527.20344 - Semi-Annual Enterprise Channel (Preview) Version 2108, build 14326.20702 - Semi-Annual Enterprise Channel Version 2102, build 13801.21092 - Semi-Annual Enterprise Channel Version 2008, build 13127.21846 ## Installing the Fix While the latest versions of Office fix the bug, the fix may not be applied automatically. Instructions for installing Office updates are available here: [Install Office updatesLearn how to update Microsoft Office on PC and troubleshooting tips for installing Office updates.![](https://support.microsoft.com/apple-touch-icon.png)![](https://support.content.office.net/en-us/media/b20ce35a-1341-40a6-adc1-b46072710d6b.png)](https://support.microsoft.com/en-us/office/install-office-updates-2ab296f3-7f03-43a2-8e50-46de917611c5) ## Rolling Back to a Previous Version This bug was introduced as a side effect of a **security fix**, so the best course of action is to update Office as described above. That said, if you *cannot update Office* for some reason, you can roll back to a previous version as a workaround to avoid the error. Here is the documentation for how to rollback to an earlier version: - For MSI builds, see: [Information about the ability to uninstall Office](https://docs.microsoft.com/office/troubleshoot/office/ability-to-uninstall-office) - For Microsoft 365, see: [How to revert to an earlier version of Office 2016 Click-to-Run](https://support.microsoft.com/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic) ## Further Reading ***UPDATE*** *\[2022-01-08\]:* I think the best page on the internet discussing this error is over at Danieal Pineault's site. As of today (2022-01-08), the article includes nearly 100 comments from users reporting their own unique experience with this bug, along with some of the fixes that worked for them: [Access – Lock File Issues | DEVelopers HUTA potential new bug has surfaced, “This file is in use. Enter a new name or close the file that’s open in another program” & “Could not lock file” ...DEVelopers HUTDaniel Pineault](https://www.devhut.net/access-lock-file-issues/)