'%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 Windows Requesting a 7-Digit Verification Code Instead of 6
Question details
The user receives a 6-digit verification code from Microsoft, but the Windows prompt asks for a 7-digit code, preventing successful sign-in.
- Product
- Microsoft Account / Windows
- Device & OS
- Windows
- Scenario
- Verifying a Microsoft account on a Windows device during system sign-in, account recovery, or app authentication.
- Observed behavior
- The Windows security prompt requires exactly 7 digits, making it impossible to input the standard 6-digit code sent by Microsoft via email or SMS.
Ensure you are connected to a stable internet connection and verify that you are attempting to log into the correct Microsoft account before requesting a new code.
Wait and Request a New Verification Code
Since this mismatch is typically caused by a temporary service-side issue with Microsoft servers, waiting and generating a new code is the best first step.
This mismatch between the requested 7-digit code and the provided 6-digit code is usually caused by a temporary glitch in Microsoft's verification service. As it is a server-side problem, local computer fixes or system restarts will generally not resolve it.
Click the 'Cancel' or 'Back' button on the current Windows verification window to close the stalled sign-in attempt.
Wait at least 15 to 30 minutes to allow any temporary Microsoft server desync issues to resolve themselves.
Initiate the sign-in process again and select 'Get a new code' to have a fresh verification code sent to your alternate email or phone number.
Use Microsoft Account Recovery or Contact Support
If the issue persists and you remain locked out, you will need to bypass the standard prompt using Microsoft's official recovery tools.
Work Uninterrupted with WPS Office
While you are troubleshooting Microsoft account lockouts or verification issues, you can continue working on your documents, spreadsheets, and presentations using WPS Office. It is entirely free, lightweight, and requires no complicated account setups to get started locally.
- 1. Download the installer: Visit the official WPS Office website and click the free download button for Windows.
- 2. Install the software: Run the downloaded executable file and follow the brief on-screen instructions to install the suite.
- 3. Start working immediately: Open WPS Office and instantly create or edit your existing Word, Excel, or PowerPoint files without mandatory sign-ins.
Frequently Asked Questions
Why does Windows ask for a 7-digit code when I only get 6?
This is typically a glitch on Microsoft's server end where the prompt expects a 7-digit authenticator or legacy code, but the automated email/SMS system mistakenly sends the standard 6-digit format.
Can I use an authenticator app to bypass the 7-digit email code?
Yes, if you previously linked the Microsoft Authenticator app to your account, you can select 'Use a different verification option' at the prompt and approve the sign-in directly from your phone without entering any digits.
Will resetting my computer fix the verification code error?
No, resetting your PC will not resolve this issue because the mismatch is caused by Microsoft's remote account verification servers, not your local Windows system settings.
