Authentication Failed Invalid Request Please Close the Window and Try Again
"AADSTS9002313: Invalid request. Request is malformed or invalid." when trying to log in to Office
Ane of our users (on Win 7) get the following mistake when trying to log in to Outlook, Excel and so on.
AADSTS9002313: Invalid request. Request is malformed or invalid.
We have tried deleting the Outlook profile, MS credentials simply nil works.
@ChristinelaFontaine-7534
Which version of Function is this user using?
-
From the perspective of Office, I would suggest you go to Registry Editor, if this user has Office 2013, please locate to
Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\xv.0\Common\Identity, dorsum up the registry for restoration in case issues occur, then remove the folders under "Identity", such equally "Profiles", "Identities".
(Please notation, for Role 2016, Microsoft 365 apps, the version number is 16.0) -
And then choose "Identity", cheque whether there are "EnableADAL" value.
If not, please right-click > New > DWORD (32-bit) Value > Name information technology "EnableADAL", set the value information every bit 1.
Besides, equally the AADSTS error code and error message are related to Azure AD Hallmark, to better assist you, I would add the tag "azure-ad-authentication" and "azure-agile-directory". Thanks for your understanding.
If an Answer is helpful, delight click "Have Respond" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related electronic mail notification for this thread.
@emilyhua-msft thank y'all for this.
It is version xvi.0. I deleted the folders in Identity and created the EnableADAL value, restarted the computer but however same error:
Should I delete the other values in the Identity folder?
Edit: Only tried creating a new user for him and logging in to Function on this new business relationship. This time no mistake after inbound user name, but information technology was not activated correctly. We have checked his license several times, no changes to this - but Office cannot activate.
It was activated correctly an worked fine for several years, then a month or two agone he got a bulletin maxim "We are having bug confirming your MS 365 subscription status because of a network mistake or a temporary service issue". Later he got "Your subscription could not exist confirmed" and now "AADSTS9002313: Invalid asking. Asking is malformed or invalid."
Here is the result:
PRODUCT ID: 00265-60000-00004-AA650
SKU ID: 3d0631e3-1091-416d-92a5-42f84a86d86
LICENSE NAME: Office sixteen, Office16O365Busine
LICENSE DESCRIPTION: Function 16, RETAIL(Grac
BETA EXPIRATION: 01-01-1601
LICENSE Condition: ---NOTIFICATIONS---
ERROR CODE: 0xC004F009
Fault Description: The Software Licensing S
expired.
Concluding 5 characters of installed production key:
PRODUCT ID: 00219-40000-00000-AA630
SKU ID: e13ac10e-75d0-4aff-a0cd-764982cf541
LICENSE NAME: Office 15, OfficeVisioProVL_K
LICENSE Clarification: Office 15, VOLUME_KMSC
BETA EXPIRATION: 01-01-1601
LICENSE Condition: ---NOTIFICATIONS---
ERROR Lawmaking: 0xC004F056
ERROR Description: The Software Licensing S
d not be activated using the Key Management
Last 5 characters of installed product central:
DNS auto-discovery: KMS proper name non av
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
2 people in my arrangement accept the same error.
Request Id: 20894b50-a4b5-4600-a681-606c02fc9f01
Correlation Id: 62d336de-9764-4598-9ffb-2039a03006da
Timestamp: 2021-08-05T14:10:26Z
Message: AADSTS9002313: Invalid request. Asking is malformed or invalid.
I am a educatee version user and I got the same result. I have been using it on this account for at least last 3 years. I am also using it in 2 dissimilar devices, same account. It started a message "you need to re-sign to prove you are the user." I simply did ignore the message for months. Then information technology started xxx days inaugural to lift my licence on the product and it did it. When licence was lifted I tried to login in to my PC however I can non login to my business relationship. I checked I still got licence right by the university about Office Licence. I cannot edit anything on my documents because of non being able to login. Delight urgent help.
Request Id: d970d44f-9cc8-4645-9d0a-858cc89a5a01
Correlation Id: 60144299-a21f-4c08-bd49-427caf7dbf82
Timestamp: 2021-08-05T18:29:04Z
Bulletin: AADSTS9002313: Invalid asking. Request is malformed or invalid.
0 Votes 0 ·
A solution. It worked on mine. I tried to login to a different account, I saw the "countersign" screen on Microsoft Role Login Application. In that screen I didn't enter to that account of mine, clicked on "Login with a different account" and then tried my other -unlogginable- account. Further, I saw the password screen for the one that I cannot see with this problem. I entered my password and everything is solved.
This did not work hither, thanks though.
0 Votes 0 ·
This (or a version of this) worked for us cheers. On the sign in screen, we entered a non-existant user (username2@domain.com) and on the next screen changed it back to the real user (username@domain.com) and clicked Next and then (and simply and then) did we get to enter a password. Later on this, all skilful.
We besides did the registry deletion and setting of EnableADAL above, but this solitary did non resolve.
Thanks
0 Votes 0 ·
Hey folks, so I figured out what was doing this in our environment.
If your org setup checks all of these boxes, this comment will most likely exist your prepare:
- 365-based Office subscriptions for private users (i.eastward. Role licensed with users' accounts and not a generic account)
- 2-cistron authentication for 365 accounts
- A timed password reset policy (i.due east. reset every ninety days)
- Windows 10 computers (side note for Win7/Win8 at the finish)
Context:
There is a long-standing issue with Azure/OAuth tokens in Windows with 2FA-enabled accounts when users hit "Yeah" to the "Use this account everywhere on your device" prompt when signing into any Microsoft service. What happens is that their 365 business relationship gets added to the "Work or School accounts" section of Windows 10 as well as beingness signed into Role or whatever other Windows 10 app they are using. This is fine until the password resets, and then what happens is that the main application that is beingness used (i.east. Part) calls out for a new credential, only the Work or School account entry does not take the ability to do so and instead creates a conflict with whatsoever applications that are trying to attain out for a new credential. This volition generate the common "Outlook TPM mistake" in which Outlook tells yous that your Trusted Platform Module hardware chip has failed (lies). It can as well cause a more vague issue where Office apps enquire for credentials only won't permit you put them in. This specific thread however, is a more spicy accept on this effect. This specific issue is the same as in a higher place except that the account entry is hidden from Windows and tin only be establish and removed from inside of the specific Windows 10 app that the user signed into. More info below.
The fix:
To fix the generic Azure/OAuth token issue in Windows, nosotros would have to remove the Work or Schoolhouse account from Windows settings similar so:
Outset > Settings > Accounts > Access Work or School > Click on the 365 account entry > Remove > Ignore alert > Sign dorsum into Part or whatever awarding was failing before > Choose "This app simply" at the "Use this business relationship everywhere on your device" prompt then that it doesn't happen again.
Immediately afterwards authentication will start working once again... Unless you're having the specific consequence with error: "AADSTS9002313: Invalid request. Request is malformed or invalid" when trying to log in to Function, which ways that at that place might exist some other secret Work or Schoolhouse business relationship entry subconscious somewhere else in Windows.
What I needed to do for this specific issue was search through every non-365 Microsoft app (i.e. from the Microsoft store) that the person used to see if any were withal signed in after purging the other Work and School account entry in the location mentioned above. Eventually I found that the OneNote app that comes built into Windows 10 was the culprit. There is a divide "Business relationship" section inside of the OneNote app that had the authenticated/declining Work or Schoolhouse account entry and for some reason that account only showed up in the OneNote app and NOT in the Windows x settings. I hitting "Sign Out" for that account from inside of the OneNote app and the second that declining account entry was removed the issue immediately went away.
This is a very specific consequence, only in my experience many orgs are setup like this nowadays then it might be more than mutual than information technology would seem at first glance. I promise this info helps someone out there.
Alternatives:
If y'all are using Windows 7 or 8, you'll nevertheless want to check on all Microsoft apps to make sure none of them are stuck failing sign in (considering they will work similarly regardless of Windows version), still you may instead need to clear credential managing director entries to get this same consequence. While some builds of Windows 8 have something similar to the account settings mentioned above, information technology will be adept to go on in mind that older versions of Windows heavily relied on the credential manager for this sort of thing. If your org isn't prepare with the settings mentioned at the beginning of this mail, this info could still be helpful, just your results volition most probable vary greatly.
For anyone who is wondering I had this consequence on a win seven desktop (optiplex 9020) using version 2008 of office.
I concluded upwards backing up his files to an external Hard disk and deleted his user profile in control console and had him sign back in re creating his profile and syncing upwardly his licenses again.
notation: This is in a corporate environment likewise. I spent a month on trying to get this event resolved.
Hope this helps. Skillful luck out there everyone!
Hi,
If it is Office365 applications or whatsoever other apps which is online cheque your AppData folder where folders like: identityCache, identity or something like that everything which referring to credentials, move them on desktop and then cheque your possibilty to login on business relationship which take license.
In that mode I solve problem with logging and activation Office365 Home and Business organization on reckoner Windows 10 20h2.
If won't work endeavour to fully reinstall office, disconnect azure account from settings and everything which referring to this ane account, restart the PC.
Why deleting profiles is working for this?
It'south probably caused because this folder not exist so user is able to login.
I hope it works for you!
Source: https://docs.microsoft.com/answers/questions/498404/34aadsts9002313-invalid-request-request-is-malform.html
@ChristinelaFontaine-7534
If Part was not activated correctly, was there any error message?
Does this user accept Microsoft 365 apps?
Please run following command in Control Prompt (Run it as administrator) to cheque the Function information.
cscript.exe "%ProgramFiles%\Microsoft Office\Office16\ospp.vbs" /dstatus(If you are running 32-bit Role on a 64-chip operating system)
cscript.exe "%ProgramFiles(x86)%\Microsoft Role\Office16\ospp.vbs" /dstatus0 Votes 0 ·
Information technology was activated correctly an worked fine for several years, so a month or two ago he got a message maxim "We are having issues confirming your MS 365 subscription condition considering of a network error or a temporary service effect". After he got "Your subscription could not be confirmed" and now "AADSTS9002313: Invalid asking. Request is malformed or invalid."
Here is the result:
PRODUCT ID: 00265-60000-00004-AA650
SKU ID: 3d0631e3-1091-416d-92a5-42f84a86d86
LICENSE NAME: Function 16, Office16O365Busine
LICENSE DESCRIPTION: Office 16, RETAIL(Grac
BETA EXPIRATION: 01-01-1601
LICENSE Status: ---NOTIFICATIONS---
ERROR Lawmaking: 0xC004F009
ERROR DESCRIPTION: The Software Licensing Southward
expired.
Last 5 characters of installed product fundamental:
Product ID: 00219-40000-00000-AA630
SKU ID: e13ac10e-75d0-4aff-a0cd-764982cf541
LICENSE Proper name: Office fifteen, OfficeVisioProVL_K
LICENSE Clarification: Office 15, VOLUME_KMSC
BETA EXPIRATION: 01-01-1601
LICENSE STATUS: ---NOTIFICATIONS---
Fault CODE: 0xC004F056
ERROR DESCRIPTION: The Software Licensing S
d not be activated using the Key Management
Last five characters of installed production fundamental:
DNS auto-discovery: KMS name non av
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
0 Votes 0 ·