Microsoft Office 365 was launched in 2011. Since then, it has earned a reputation for itself as a reliable cloud productivity suite for businesses and individuals alike. With its flexible pricing scheme and handy features, it has quickly become popular, allowing users to communicate, collaborate, and access important files with ease.
However, as with all tools and software, one may encounter problems while using it. The error 80090030 while accessing Microsoft Office 365 is probably among the most notorious ones.
What is the Error 80090030?
Are you unable to access Microsoft Office 365 due to the error 80090030? You are not alone. Some Office 365 subscribers have reportedly come across the issue, too. So, what is this error all about?
According to a user, the 80090030 NTE_DEVICE_NOT_READY error appeared after installing Microsoft Office 365. It showed right after the productivity suite prompted for the new password.
This error message may suggest three things. First, the device that is required by the suite may not yet be ready for use. Second, there might be unnecessary product information available when, in fact, much less is needed. Lastly, there might be a problem with your computer’s TPM.
How to Fix Error 80090030
Now, can this error be fixed? Of course! But 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:
Fix #1: Use the Command Prompt
As they say, too much of anything is bad. The same applies to Microsoft Office 365. If there is unnecessary product information available, then errors are likely to arise. To fix this, here’s what you should do:
- Into the Search bar, input Command Prompt.
- From the search results, right-click on Command Prompt.
- Select Run as Administrator.
- Into the Command Line, enter the commands below. Make sure to replace the value of xxxx with the product key:
CD C:\Program Files (x86)\Microsoft Office\Office16
cscript ospp.vbs /dstatus
cscript ospp.vbs /unpkey:xxxx
- At this point, you have successfully removed the unnecessary product information. Restart Microsoft Office 365 to see if the problem persists.
Fix #2: Disable ADAL for Outlook
Some users resolved the error 80090030 by disabling ADAL for Outlook. To do this, follow these steps:
- Close Outlook.
- Into the Search bar, type regedit and hit Enter.
- Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity.
- Find REG_DWORD and set the EnableADAL value to 0.
Fix #3: Turn Off the TPM
A Trusted Platform Module, or TPM, is a special chip embedded in a computer. It stores encryption keys needed by a host system to authenticate hardware. While it may be useful in many situations, sometimes, administrators decide to limit access to this chip as it can cause problems. In this case, the TPM must be disabled.
To disable the TPM, make sure that you are logged on to a computer equipped with a TPM. And then, follow these steps:
- Go to Start > All Programs > Accessories.
- Click Run.
- Into the text field, input tpm.msc.
- Hit Enter to display the TPM Management console.
- Once the User Account Control dialog box appears, confirm your action and hit Continue.
- Navigate to the Actions section and select Turn TPM Off.
- Choose a method for entering your credentials:
- If you don’t have a removable medium that contains your password, select I want to type the TPM owner password. And then, enter your password credentials and click Turn TPM Off.
- If you have a removable medium that contains your TPM owner password, insert it and choose I have a backup file with the TPM owner password. Next, click Browse to find the .tpm file saved on your medium. Tap Open and select Turn TPM Off.
- If you forgot your TPM owner password, select I do not have the TPM owner password and follow the on-screen prompts.
Fix #4: Use Microsoft Support and Recovery Analyzer for Microsoft Office 365
Yes, there is a tool that you can use to fix problems with Microsoft Office 365: Microsoft Support and Recovery Analyzer. It can be used to run diagnostic tests to detect and automatically fix issues with local app configurations.
To use the tool, download it here. Install it and wait as it takes you through the entire installation process. Once completed, you can run the tool and let it resolve the error for you.
Fix #5: Optimize Your Computer for Top Performance
Error messages appear for a variety of reasons: the hardware may be faulty, some PC drivers may be outdated, or your computer is loaded with too many unnecessary programs. Oftentimes, a good restart can fix all this. However, if it doesn’t work, you will have to take a more active approach: optimize your computer!
There are two ways to optimize your computer. The first method involves the manual fixing of outdated device drivers and deleting junk files, such as temporary Sun Java files, Microsoft Office cache, unused issue logs, web browser cache, and a lot more.
Although the first method has been proven time and again to work, it can be time-consuming and risky. Delete the wrong file, and your computer may no longer boot up properly.
The second, and more preferred, method involves using a third-party PC repair tool like Outbyte PC Repair. Simply download and install the tool, and everything will be taken care of. In just a few clicks, all junk files will be removed and your computer will be running as fast and smooth as if you’ve just bought it.
Hopefully, one of the fixes above has helped you resolve the Microsoft Office 365 error 80090030. If you think you’ve done everything already, but to no avail, do not hesitate to ask around. Seek help from Microsoft’s official support team or reach out to your tech-savvy friends.
Do you know other ways to fix the error 80090030? What other Microsoft Office 365 issues have you encountered? Let us know in the comments.