'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix OneNote Repeatedly Asking for Password on Embedded Excel Files
Question details
Users need a solution for an authentication bug where opening password-protected embedded Excel or Word files in OneNote triggers multiple password prompts and results in blank windows.
- Product
- Microsoft OneNote and Excel
- Device & OS
- Windows
- Scenario
- Opening an embedded, password-protected Excel or Word document from within a Microsoft OneNote notebook.
- Observed behavior
- OneNote prompts the user for the password multiple times (e.g., 3 times) before opening the embedded file, and sometimes displays a completely empty Excel window with no gridlines.
Ensure you have saved all active work in OneNote and Excel, and verify that you have administrator privileges on your computer to run the Command Prompt utility.
Roll Back Microsoft 365 to a Previous Version
Reverting your Microsoft 365 installation to a stable previous build (such as 2404) bypasses the update bug causing the repeated password prompts.
This issue is frequently caused by a glitch introduced in recent Microsoft 365 update channels (like build 2410). Downgrading to a previously working build restores normal authentication behavior for embedded files.
Ensure that OneNote, Excel, Word, and any other Microsoft Office applications are completely closed.
Click the Start menu, type 'cmd' or 'Command Prompt', right-click the application, and select 'Run as administrator'.
Type the command 'cd %programfiles%\Common Files\microsoft shared\ClickToRun' and press Enter.
Type 'Officec2rclient.exe /update user updatetoversion=16.0.17531.20120' and press Enter. Wait for the Office update dialog to download and apply the older version.
Open Microsoft Word or Excel, navigate to File > Account, click the 'Update Options' button, and select 'Disable updates' to prevent the buggy version from reinstalling automatically.
Update to the Latest Office Build
Check if Microsoft has released a newer patch that resolves the compatibility bug between OneNote and embedded Office files.
Try WPS Office for Bug-Free Document Management
If recent Microsoft 365 bugs are disrupting your workflow and causing password authentication issues, consider switching to WPS Office. It provides a lightweight, highly compatible alternative to easily manage your spreadsheets and documents without unexpected glitches.
Frequently Asked Questions
Why does OneNote ask for my Excel password multiple times?
This is a known authentication bug introduced in recent Microsoft 365 updates (such as build 2410). The update disrupts the security handoff between OneNote and the embedded Excel or Word application, causing it to fail to cache the password properly.
What does it mean when the embedded Excel window opens completely blank with no gridlines?
A blank window without gridlines indicates that the embedded file failed to decrypt and render. This is a direct symptom of the version incompatibility bug preventing the file from actually opening.
Can I fix this issue by changing my Trust Center settings?
No, adjusting Trust Center settings does not resolve this specific version-related bug. The most effective troubleshooting step is to roll back your Microsoft Office installation to an earlier, stable build.
