![](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)
Outlook | Windows | Classic Outlook for Windows | For home
Using Classic Outlook on Windows for personal email, calendar, and contact management
I thought I would just post a follow up to my original post and to some of the responses on this thread.
I seem to have solved the problem.
As I mentioned, I have went to some pretty extreme measures to solve this issue. I will list my details below in case it helps anyone else with this issue.
- I have completely repartitioned my OS drive and reinstalled Windows 10 6 or 7 times trying different fixes after the OS install. It may be more than 7. I actually can't remember now how many times. In each case it was after build 2004 was rolled out, and the standard windows installer that is downloaded from the web installs a fresh version of 2004. My previous build was 1909. I had been having some OS issues after an update sometime earlier this year on a previous update and decided to stop fighting the system and just start fresh. It's important to note that I have many years under my belt as a system manager, software support and even software product management.
- My installation of MS365 was completely up to date at the time I rebuild the system. Microsoft 265 (Office 365) was working just fine prior to the OS re-install.
- My Microsoft 365 is purchased through GoDaddy.
- I started with all the password and TOM issues as soon as I reinstalled MS365 on the new OS.
- I called GoDaddy several times and while they tried to help, they had no idea what the problem was.
- I tried using Microsoft help both with chat and phone calls. After many times waiting in excess of 4 hours I gave up trying to get help from them.
- I have several other systems running both Widows 7 and Windows 10. Some have a TPM module - some do not. Even after upgrading my Windows 10 systems to 2004 they were not having the same problems I have been having with this system.
- I kept getting the TPM malfunction error even thought my system initially didn't have a TPM module installed. After working with my workstation manufacturer we decided to see if installing a TPM module would solve the issue. So I purchased and installed a TPM module. I still got the same errors and password problems.
- I tried all the fixes listed on this thread as well as a number of other workarounds that can be found on the web. Nothing fixed the problems.
- I finally decided that I should just go back to build 1909 and see if MS365 works correctly on that build. I do have an installer for 1909 on a USB so I rebuild the OS drive again with build 1909. I have been running all my apps now for about a week with no issues at all. I have not taken the plunge yet to upgrade to build 2004 using the windows update, but I will do that soon. I suspect that my system will work just fine like my other systems that updated to build 2004. If I was to guess - based on my 3 months of research on this issue and the fact that my other systems have no problems - I would guess that this system will work normally after the update. I could be wrong. If so I will post my results.
- I can't answer the reason why others are having these problems, but in my case it seems that the core problem was a fresh install of build 2004. It's too bad there is no way to get a MS engineer to do this all work and get a definitive answer. I'm just happy now that I have a functioning system again.
- Good luck to all.
