Windows 10: Outlook 2013 fails, if virtualization software is installed

[German]Today a blog post about a crude problem reported to me by a user (thanks for pointing it out). The Microsoft Outlook 2013 used in the environment seems to have problems under Windows 10 from version 2004, if one is installed with virtualization software and an upgrade is performed from an older build. The mail client can no longer connect to an Exchange server.


The observed error

German blog reader Mario O. just contacted me and described in an email a rather crude error related to Microsoft Outlook 2013. The environment used where there are problems:

  • Microsoft Outlook 2013
  • Microsoft Windows 10 Version 2004 and 20H2
  • Microsoft Exchange Server 2013

Actually nothing unusual for a corporate environment. Unfortunately, a nasty bug occurs with the reader in this environment: Outlook can no longer connect to the Exchange Server. Curious is the condition when the bug occurs. Here's what the blog reader writes about it:

When a machine running Windows 10 1909 or older has virtualization software installed (tested with VirtualBox and Hyper-V) and is upgraded to Windows version 2004 or 20H2 via feature update.

Once the upgrade is through Outlook no longer works, it cannot connect to Exchange Server (Exchange 2013).

The reader suspects that the problem seems to be the virtual network cards. They no longer allow Outlook to connect to Microsoft Exchange Server 2013. However, he has not found any problems when testing with VPN tools that also use virtual network cards. The virtual network cards work without any problems.

There are workarounds

After some trial and error, the blog reader then found two workarounds to get Microsoft Outlook 2013 to communicate with Microsoft Exchange Server 2013.

Workaround 1: Reset Windows network settings.


After a reboot it works again. However, the error seems to occur sporadically again which requires a new reset.

Workaround 2: Uninstall virtualization software.

Afterwards Outlook works normally again. The question remains, if anyone of you has encountered something like this before and if a solution is known.

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Office, Virtualization, Windows and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *