logo
search
Office Settings & Configuration

Fix Microsoft Access Runtime Quick Access Toolbar Resetting After Update

Camila MilosovichCamila Milosovich Oct 9, 2026 870 views

Question details

The user needs to resolve an issue where the Quick Access Toolbar resets its position after an update.

Fix Microsoft Access Runtime Quick Access Toolbar Position Reset After Update
Product
Microsoft Access Runtime
Device & OS
not provided
Scenario
Updating Microsoft Access Runtime to version 2311 while trying to maintain custom UI settings.
Observed behavior
The Quick Access Toolbar position unexpectedly resets to 0 (above the ribbon), ignoring custom Ribbon XML configurations and registry settings.
Before you start

Verify your current Microsoft Access Runtime version in the application settings and ensure your custom Ribbon XML code is properly formatted before proceeding.

Solution 1Recommended

Report the Bug and Monitor for Microsoft Updates

Since this behavior is a known bug introduced in version 2311, the most effective action is to report the issue to Microsoft and wait for an official patch.

The Quick Access Toolbar reset in version 2311 occurs because the update contains a bug that forces the toolbar position to 0, completely ignoring user-defined Ribbon XML and registry entries. As this is an internal application issue, local configuration changes will not provide a permanent fix.

1
Document the issue details

Gather your system information, specifically noting that you are using Microsoft Access Runtime version 2311, and copy your current custom Ribbon XML code.

2
Submit a bug report

Navigate to the official Microsoft Feedback Portal or use the feedback option within your Microsoft 365 admin center to submit a detailed bug report.

3
Check for upcoming patches

Regularly check the Microsoft Office update release notes to see if a newer version of Access Runtime has been released to patch the toolbar positioning bug.

Report the Bug and Monitor for Microsoft Updates
Temporary Workaround: If the custom toolbar position is critical for your workflow, consider rolling back your Access Runtime installation to a version prior to 2311 until Microsoft releases a fix.
Free Microsoft Office alternative

Try WPS Office for a Stable and Customizable Experience

While waiting for Microsoft to resolve Access Runtime UI bugs, consider using WPS Office for your other productivity tasks. It provides a free, lightweight, and highly compatible alternative to Microsoft Office, featuring a familiar interface and seamless migration.

  1. 1. Download the installer: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install the suite: Run the downloaded installer and follow the on-screen instructions to set up WPS Office.
  3. 3. Customize your workspace: Open WPS Spreadsheet or Writer and confidently customize your toolbars and ribbon settings without worrying about unexpected resets.
Highly compatible with Microsoft Office file formats like DOCX, XLSX, and PPTX.Reliable and stable user interface that retains your custom toolbar configurations after updates.Free and lightweight, ensuring fast performance even on older devices.
microsoft office alternative - wps office

Frequently Asked Questions

Why does the Quick Access Toolbar move above the ribbon in Access Runtime 2311?

This is caused by a recognized bug in version 2311 where the system ignores custom Ribbon XML and registry settings, forcing the toolbar position value to reset to 0, which corresponds to the area above the ribbon.

Can I fix the toolbar position using the Registry Editor?

In this specific version (2311), modifying the registry settings is ineffective. The internal bug overrides any configured registry values related to the Quick Access Toolbar position.

Will downgrading Access Runtime restore my custom toolbar?

Yes, uninstalling version 2311 and rolling back to a previous, stable version of Access Runtime will restore the application's ability to read and apply your custom Ribbon XML and registry settings correctly.