This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When I try to add a new Office 365 email to my outlook I get the error below. I think it's because of my "Work or school account" which I want to remove. I'm not sure how my email was signed up for this second account. I set up this computer for home use only, I won't be using any of the Microsoft Azure features.
My question is, what will happen when I remove my “work account” and leave my Microsoft account? Everything is backed up on Onedrive, I just don’t know what to expect because when I went to remove it, it warned me about losing data and settings.
Any help would be appreciated. Thank you!
Using Classic Outlook on Windows for personal email, calendar, and contact management
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
George,
Just create a new user profile. That's what I did and it seems to be working.
My team and I have encountered the "80090016" TPM error many times. Come to find out, the DWORD key of "EnableADAL" needs to be added with a hex value of "0" in the registry under "HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common". After this you will need to shutdown (not restart) the computer and power it back up. You will then not encounter this error again.
This is needed because of the new O365 "Modern Authentication" requirements. O365 and Outlook version 2016 and later require this registry key. You can also deploy it in your network using GPO. That way during a migration you do not get halted by this error.
"Microsoft | Docs - Modern Authentication configuration requirements for transition from Office 365 dedicated/ITAR to vNext"
According to KB3480364 all we can do is uninstall 2004 and revert back to old W10 version for those that haven't been messing with this for a month of Sunday's and not missed to timing out of this option or just wait for MS to correct and issue update
Known issues in this update
| Symptom | Workaround |
|---|---|
| Users of the Microsoft Input Method Editor (IME) for Japanese or Chinese languages might experience issues when attempting various tasks. You might have issues with input, receive unexpected results, or might not be able to enter text. | For more information about the issues, workaround steps, and the currently resolved issues, please see KB4564002 |
| System and user certificates might be lost when updating a device from Windows<br> 10, version 1809 or later to<br> a later version of Windows 10. Devices<br> will only be<br> impacted if<br> they have already installed any Latest<br> cumulative update (LCU) released<br> September 16, 2020 or later and then<br> proceed to update to a later version of Windows 10 from media<br> or an installation<br> source which does<br> not have<br> an LCU released October<br> 13, 2020 or<br> later integrated.<br> This primarily<br> happens when managed<br> devices are<br> updated using<br> outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft<br> Endpoint Configuration Manager. This<br> might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.<br><br><br><br><br><br>Note Devices<br> using Windows Update for Business or that connect directly to Windows Update are<br> not impacted. Any device connecting to Windows Update should<br> always receive the latest versions of the<br> feature update, including the latest LCU, without<br> any extra steps. | If you have already encountered this issue on your device, you can mitigate it within the<br> uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window<br> might be 10 or 30 days depending on the<br> configuration of your<br> environment and<br> the version you’re updating<br> to. You<br> will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the<br> uninstall window, you<br> can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You<br> must make this change before the<br> default uninstall window<br> has lapsed. For more<br> information, see DISM operating<br> system uninstall command-line options.<br><br><br> <br><br>We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks. |
I have had this problem on 3 machines now - all HP. 2 are ProBook 450 G3s one HP Pavillion 15. They all had the issue immediately after updating to 2004. These systems belong to dealers and so all of my troubleshooting has been over remote control. They are local Windows users using Office365 apps provided centrally by us - we're not currently using MFA but intend to.
I tried pretty much everything I could find with no luck - the ADAL registry key, clearing the TPM, uninstalling & re-installing Outlook credential manager etc. The only thing I didn't try, because of the amount of work to get them set back up again, was to re-create the users windows profile.
I rolled them back and all Office apps, OneDrive etc working fine again.
I found this potential fix and sharing it here in case it helps anyone.
https://www.linkedin.com/pulse/solving-modern-authentication-issues-office-365-chris-leet/
I'm hoping to test it on one of the systems that's playing up since the 2004 update was applied over the weekend and I'll let you know if it works for me.
Microsoft you really need to acknowledge that this is an issue affecting a lot of people and post a fix. The ADAL key, re-creating the user profile or indeed rolling back the updates are not solutions.
I 100% agree with you Laura! Microsoft needs to resolve this in either an update or patch because this is ridiculous. What I have done to workaround this problem is adding a GPO to add this DWORD. At least on my end, this happens when I migrate between domains. As soon as I add the DWORD I do not encounter this problem.
I hope that Microsoft is monitoring these and can understand the severity of this issue. Because of this and other issues is why many companies are considering moving or have moved into Google's suite of productivity tools and services. Microsoft, you need to get your act together!