I am having the same issue, I have been for about2 months and I have not been able to find a fix. Rather than simply get the standard answers that are read out of the customer support handbook let me explain what I have done and the results. Maybe someone
has found a real fix - not just a temporary "do this and go away so I can get back to playing ping pong", answer.
Just so everyone knows - I have been on hold with MS Tech several times for over 4 hours trying to contact someone to help me. I have ran the support & Recovery tool many times. Please dont respond telling me to do these things again.
I have a fairly new workstation built by a well known commercial workstation builder. I replaced my OS SSD back in June and of course needed to install the OS. At that time the only option for a complete fresh install was build 2004. My previous SSD was
build 1903.
After the install I updated all the MS updates that were needed and then installed Microsoft365 prior to installing any other software products. After that install I keep getting prompts to re-enter my password and then frequently it would end with this
error message regarding a TPM malfunction. I have never seen that error before and it's important to know that my system actually did not have a TPM module installed. I began working with my hardware support group and over the course of 3 weeks I reformatted
and reinstalled fresh copies of Windows10 build 2004 a total of 6 times - each time thinking that maybe I goofed up something. Now, it's important to know that I have many years under my belt supporting computers and specialized engineering software products
- so I have done this many times in the past.
I finally purchased a new TPM module for my system and installed it alone with a fresh install of Win10. I then verified that the TPM was working correctly and have even cleared it a couple of times in the hope of solving this problem.
I have created a new Outlook profile. I have done everything that I can find. I think I have even gone to some pretty extreme measures to fix this issue.
Does anyone have a real solution to this problem that seems to have started on build 2004?