Shulou(Shulou.com)11/24 Report--

CTOnews.com Back in August, Microsoft released a support document describing an issue that caused Outlook to crash or stop responding at startup. After investigation, the company discovered that this problem occurs when the EmailAddress string data value under the Office identity remains empty.

Therefore, the company devised a solution to bypass the problem by manually entering values using the same method. Microsoft also recommends that users disable support diagnostics in Outlook using Registry Editor, and Microsoft recommends that users use the age-old trick of logging out and logging back in to automatically refill entries.

Recently, Microsoft finally fixed this issue, which is now successfully resolved in Outlook 2209 (Build 15629.20156) and Semi-Annual Enterprise Channel (Preview) version 2208 (Build 15601.20158).

When Outlook Desktop starts, it briefly opens by loading profiles and processing, then stops responding.

You can confirm that this is a problem when Outlook stops by reviewing the Windows Event Viewer application log for Event 1000 or Event 1001 and the following event details:

Error Application Name: OUTLOOK.EXE, Version: 16.0.15427.20194, Timestamp: 0x62 e9be45

Fault module name: mso20win32client.dll, version: 0.0.0.0, timestamp: 0x62 e4fd3c

Exception code: 0x01483052

Error tolerance offset: 0x0000000024074d

Failure Process ID: 0x1328

Application startup time error: 0x01 d8acfa5984509d

Application path error: C: \Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE

Fault module path: C: \Program Files\Common Files\Microsoft Shared\Office16\mso20win32client.dll

This issue occurs when the EmailAddress string data value under the Office identity is null.

Registry path: Computer\HKEY_Current_USER\Software\Microsoft\Office\16.0\Common\Identity\Identities

Outlook Close:

Outlook does not close:

Status: Repaired

Fixed in current channel version 2209 (build 15629.20156) and Semi-Annual Enterprise Channel (Preview) version 2208 (build 15601.20158). As these builds reach other channels, the fix will follow.

Solution:

We don't know why the EmailAddress key isn't set correctly. It's best for the Office application to set this key, so it's best to use the most supported option first.

To resolve this issue, try the following suggestions:

Log out of Office, and then log in to Office to repopulate identity registry settings. For more information, use Sign In Office.

If the identity is not set correctly, you can turn off Support Diagnostics, which turns off the option to submit an In App ticket using Help, Contact Support, and their feature paths, triggering Outlook to stop responding. For more information, use Disable Support Diagnostics in Outlook.

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options\General]

"DisableSupportDiagnostics"=dword：00000001

You can try manually setting the e-mail address to the identity of the user who saw the problem in the registry path referenced in the problem details above.

CTOnews.com has learned that Microsoft has also fixed Outlook's inability to display contacts in People view, Outlook IMAP or POP server unexpected termination of connection server outages

Issue: After updating to Outlook Desktop version 2209 build 15629.20156, when you select People to display contacts, you will find that the People view is overwritten by a contact card and contacts cannot be accessed.

Status: Temporarily avoided

The Outlook team is investigating this issue in order to develop a fix. We will update this topic as soon as we know the status of the fix.

There are two possible solutions:

To fix this problem, disable the Reading pane.

Select View in the People pane, then select Reading pane, and set it to Off.

If the View menu is overwritten, click Alt + Spacebar and choose Restore. This will bring you back to the minimized state and you can now perform the Reading pane changes in step 1.

Another workaround is to revert to build before the changes that caused the problem.

Open a command prompt using the administrator context. To search for a command prompt in the Windows search box, right-click the command prompt and select Run as Administrator.

In the Command Prompt window, type/paste the following two commands and press Enter after each command:

cd %programfiles%\Common Files\Microsoft Shared\ClickToRun

officec2rclient.exe /update user updatetoversion=16.0.15601.20148

Problem: Outlook stops connecting to the mail server. You may see the following error: "The connection to the server has been lost. "

Error (0x800 CCC 0F) reported for task Username-Receive: Connection to server lost. If this problem persists, contact your server administrator or Internet Service Provider (ISP).

"The server unexpectedly terminated the connection. Possible causes include server issues, network issues, or prolonged inactivity.

Status: Temporarily avoided

Upon further investigation, we will see two solutions that help resolve these errors:

Workaround #1: If you receive an error in the section above, it may indicate a problem with the application password. This can happen on Windows 10 or Windows 11. To fix your app password, sign in to your IMAP email provider's Web email, then go to Account Information> Security and create a new app password.

To repair app passwords on email accounts in Outlook, do the following:

Select File in Outlook, click the drop-down list under Account Information, and select the IMAP account with the error described above.

Select Account Settings> Server Settings.

On the IMAP account settings, paste the new app password in the Password box.

Select Next, then Finish.

Workaround #2: We tested further and found that TLS 1.3 might cause the above error if Windows 10. Our tests found that Windows 11 TLS 1.3 should work with Outlook. If you are working on Windows 10, use the following steps to disable TLS 1.3 to resolve the error in the above article.

This problem may occur if the computer has been updated to configure TLS 1.3. To resolve this issue, do the following to remove TLS 1.3 settings:

Click Start, search Regedit and open the application

Navigate to this path in the registry:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

See if you see TLS 1.3 under the protocol. If you do, right-click Protocols and click Export to save the configured registry export in case you need to restore it for any reason.

If you see TLS 1.3 under the protocol delete the key and its subkeys.

Restart Outlook. If you still don't see sync starting to work, restart Windows.

After making the changes, the registry should display the following without displaying any TLS 1.3 keys.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.