Some Notes on the Machines

This seems to be able to help. It does take down New Outlook and New Teams and any other Webview app first.

taskkill /f /im msedgewebview2.exe
$ResolveWingetPath = Resolve-Path "C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_*_x64__8wekyb3d8bbwe"
    if ($ResolveWingetPath){
           $WingetPath = $ResolveWingetPath[-1].Path
    }
$ENV:PATH += ";$WingetPath"
winget install microsoft.edgewebview2runtime --force --accept-package-agreements --accept-source-agreements

If (when) Outlook bogs down, especially when dealing with multiple accounts in a single profile, disable the existing Send/Receive Group and create a new one, make sure all accounts are included, then set that one to be checked every 30 minutes.

Often we replace Outlook profiles or just OSTs, but there is a much different step. After making sure there are no Outlook.exe processes running, go to the user’s Windows AppData folder:

C:\Users\<username>\AppData

Look for Roaming\Microsoft\Outlook under there, and rename it to Outlook.OLD. Do the same for Local\Microsoft\Outlook if that’s there.

The results are likely to be different :-) You may possibly, also, not have to create a new Outlook profile after doing this. It seems to cause Outlook to replace files which are being corrupted relatively often. This also fixed some mystery IMAP behavior where sync was reported complete but did not bring in new email.

For a very long time, it was thought gospel that Outlook had hard caps on size of PST and OST files, which equals a hard cap on the size of a mailbox that Outlook can see. This has, apparently, changed. 100-gigabyte OSTs are possible, and larger. It is thought that very fast hard drives primarily, and certainly also good CPU and lots of RAM, are needed to reliably handle huge mailboxes and PSTs without corruption. Here is a method by registry entries. It’s also possible by Group Policy.

https://support.microsoft.com/en-us/help/832925/how-to-configure-the-size-limit-for-both—pst-and—ost-files-in-outloo

https://www.msoutlook.info/question/increase-pst-file-size-limit

Today it was found that an Office 2019 installation via 365, did not have any of the registry keys involved. After creating them manually in Regedit, the desired results did occur. These very registry entries are also created by the Group Policy method.

Once you install the Office 2016 templates:

https://www.microsoft.com/en-us/download/details.aspx?id=49030

you can set the maximum sizes:

This creates the same registry entries as the manual method.

Registry deletions! Try this:

https://docs.microsoft.com/en-us/outlook/troubleshoot/domain-management/unexpected-autodiscover-behavior

As of version 2019 (and possibly before), QuickBooks has a new feature: native support of Office 365 webmail and some other major email providers. When users send email via QuickBooks, go to Preferences, Send Forms, and instead of choosing Outlook, choose Webmail, and then set up integration with the user’s Exchange Online account. Works much smoother, faster, more reliably.

Interesting info:

https://superuser.com/questions/1051538/lost-email-after-accepting-invitation/1051542

There is a way:

https://rakhesh.com/windows/enabling-disabled-office-add-ins-automatically/

Sometimes, newer versions of Outlook will hard-fail a plugin, so that none of the standard GUI changes will permit it to reenable. When this happens, you can override by deleting everything here:

HKEY_CURRENT_USER\Software\Microsoft\Office\[version number]\Outlook\Resiliency\DisabledItem

This does enable every plugin, so there is a bit of danger.