Encountering Error code 80090030 while having access to Microsoft Office 365 may be irritating. This errors normally factors to an trouble with the tool’s TPM (Trusted Platform Module) or needless product statistics saved on your machine, but the problem may be fixed through some troubleshooting methods.
What is Error Code 80090030?
Error code 80090030 is one of the common errors that people usually come across during the use of attempted access to Microsoft Office 365. This may be in form of hardware unavailable or complications associated with TPM.

It is usually accompanied by NTE_DEVICE_NOT_READY that explains a situation where a device needed for authentication isn’t ready.
How to Fix Error Code 80090030
Before you try any of the solutions we have listed below, log in to Microsoft Office 365 first using another device.
If you can successfully pass through the login section without any problems, then it is possible that an underlying hardware issue has triggered the 80090030 error to occur, which means you need to have it fixed by a certified technician.
Otherwise, feel free to proceed with the recommended fixes below:
Method 1: Use Command Prompt to Remove Unnecessary Product Information
Sometimes unnecessary product data in Microsoft Office 365 can cause errors. To resolve this:
- Open Command Prompt as Administrator. Enter these commands:
CD C:\Program Files (x86)\Microsoft Office\Office16cscript ospp.vbs /dstatus
cscript ospp.vbs /unpkey:xxxx (replace xxxx with your product key)
- Restart Office 365 and check if the issue persists.
Method 2: Disable ADAL in Outlook
Some users found that disabling Active Directory Authentication Library (ADAL) resolved this error:
- Close Outlook.
- Open Registry Editor by typing regedit in the search bar. Navigate to:
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity - Set the EnableADAL value to
0.
Method 3: Turn Off TPM
TPM (Trusted Platform Module) stores encryption keys but can sometimes interfere with Office 365. To disable it:
- Press Windows + R, type
tpm.msc, and press Enter. - In the TPM Management Console, select Turn TPM Off.
- Follow the on-screen prompts to disable TPM.
Method 4: Use Microsoft Support and Recovery Analyzer
Microsoft has an utility called the Support and Recovery Analyzer that identifies and even fixes common issues with Office 365.
Download the utility from Microsoft’s official website and run it. Follow the on-screen instructions to run the scan and see if it resolves your issue.
Method 5: Optimize Your Computer
There are two ways to optimize your computer: the manual fixing of outdated device drivers and the deletion of junk files, including temporary Sun Java files, Microsoft Office cache, unused issue logs, web browser cache, and many more.
Although the first way has been shown time and again to work, it is cumbersome and at times hazardous. Misdelete any one file, and your computer may no longer boot properly.
Another, and more preferred, way is by the usage of third-party PC repair tools such as those provided by Outbyte PC Repair. Just download and install the tool, and everything will be taken care of.
In a couple of mouse clicks, all junk files will be removed, and your computer will run fast and smooth as if just bought.
Learn more and keep improving your PC:
How to Fix the Error Cpde 0x80040115 in Windows 10/11?
What is the LiveKernelEvent Code 141 and How to Deal With It?
Fix Windows 10 Update Error 0x800703F1
FAQs
What causes error code 80090030?
This error is often caused by TPM issues, unnecessary product information, or software conflicts within Microsoft Office 365.
Can I fix this error without professional help?
Yes, most of the time, you can fix it yourself using methods like Command Prompt, disabling TPM, or optimizing your system.
What is ADAL and why should I disable it?
ADAL is a Microsoft library that handles authentication. Disabling it can help resolve login issues with Office 365.
Can updating my system drivers help?
Yes, outdated drivers can cause software conflicts, so updating them using tools like Driver Updater might resolve the issue.





