Hi @BC,
Welcome to the Microsoft Q&A forum.
Thank you for letting us know about the situation. Based on your description, after the December 9, 2025 KB5072033 update, Excel PivotTables connected to Access no longer refresh and show: “[Microsoft][ODBC Microsoft Access Driver] Operation is not supported for this type of object.” We truly appreciate the details you shared and the time you’ve spent investigating this behavior.
This can occur when the update changes how the Access ODBC driver handles certain sources such as saved queries or cursor types. PivotTable refresh depends on operations the driver now blocks, so Excel cannot complete the request. The behavior is more likely when Office and the Access Database Engine have different bitness or when the connection uses older DAO/Jet components.
Below are some alternative steps designed to address your situation effectively:
1/ Begin by reviewing version details and validating that the bitness alignment is correct for compatibility:
- Check your Office build and Windows update history. Ensure Excel and the Access Database Engine use the same bitness, then install the latest matching Access Database Engine redistributable.
2/ Proceed by setting up the connection again through ACE OLE DB to resolve any configuration issues:
- In Excel, create a new connection using Microsoft.ACE.OLEDB.12.0 or 16.0, rebuild the PivotTable from Data > Get Data > From Microsoft Access Database, and turn off Background Refresh. Clear the Pivot cache and test a refresh.
3/ Then, confirm the integrity and availability of the Access source before proceeding:
- Test against a simple table or a basic SELECT query without parameters. In Access, run Compact and Repair, confirm the file path is reachable, and ensure no exclusive locks are present.
4/ Complete the process by validating that the update serves as the intended trigger:
- If your company's policy allows, temporarily roll back or pause KB5072033 to test. If the issue persists, share your Office build number, Access Database Engine version and bitness, connection string/provider used, and whether the source is a table or a saved query so we can tailor the next actions.
5/ As your account is managed by your organization, please contact your IT administrator to check your permission and policies. For a more efficient resolution, we recommend using your administrator account or contacting your IT administrator to submit a support request directly to Microsoft Support team.
They can raise a support ticket by visiting: Get support - Microsoft 365 admin | Microsoft Learn
As community moderators, we appreciate your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.
I hope this information is helpful. Please follow these steps and let me know if it works for you. If you have any updates regarding the issue, please feel free to share them with me.
Thank you for your patience and your understanding. If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you.
I look forward to continuing the conversation.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.