15/06/2022
Google recently decided to reign in the free use of sending emails through Gmail while using third party software, or anything that isn’t theirs e.g. Outlook. Added to that I’ve had several customers upgrade some computers to Windows 11, and I know Microsoft love to say how wonderful it is, but from an IT perspective “if you don’t need it, don’t do it”.
Now that Gmail changed their settings any program that needs to send an email using your Gmail account will need to generate an App Password. This is also true if you are using a printer to send scanned emails.
* This next part gets a little bit technical.
However, this one customer of mine had one extra issue, when this customer tried to use Outlook to read their Gmail emails in Windows 11, it fails, but when we test it with the App Password it passes, but still fails to get any emails (or send) with gives us a very ambiguous error code 0x800CCC0e. This took me ages to work out the problem, and after I had done many checks and repairs on Windows and Outlook, and constant reading on Google blogs with information that didn’t quite match, nor work. I eventually found the issue in something called the “Windows Credential Manager”. When you save a password (not your browser) in Windows it gets stored in the Windows Credential Manager which can be found in the Control Panel in Windows. When Windows needs to use the password, it grabs what’s stored, and everything works. However, every day or so Windows 11 decided to create a copy of that stored password, then tries to use it, everything fails, and the user gets the error 0x800CCC0e.
The solution is to remove all copies of that password except the oldest two, which will be the original password that worked, once done everything will work again, no restarts required. The downside is there is no known permanent fix, well not yet, every day or so you will have to reapply the solution. Until Microsoft brings out a fix.
You can try doing a Factory Restore or downgrading to Windows 10. None of this has been tried, but I’m dubious if it will work.
I first saw this bug back in Windows 95, and last saw it in Windows ME (so that's about 20+ years).
If you don’t understand what I said, but can see the same or similar issue, then you can message me or call.