Outlook: Send/receive error (0x800CCC13) after upgrading to Windows 10. ‘Cannot connect to the network. Verify your network connection or modem.’

Over the last few weeks, we have seen Windows 10 begin to roll out to computers across the world.  As people have begun to take advantage of the free upgrade offered to them, some of our clients have come to us with a peculiar error that prevented Microsoft Outlook from being able to send email after they completed their Windows 10 upgrade.

Users first notice that no emails they send are getting through, and a small SEND/RECEIVE ERROR is displayed in the bottom right of the screen:


When expanded, this error shows itself in more detail:
Sending reported error (0X800CCC13).  ‘Cannot connect to the network.  Verify your network connection or modem.’


Upon verifying that all the SMTP, username and password settings, were correct, we eventually came across the solution; running a command in order to correct missing or corrupt system files in Windows.  This command is known as the System File Checker, and below I will run through the process involved in invoking the program using a command prompt command:

  1. First of all, we need to open the command prompt.  Right click the Windows button in the bottom left of the screen, and select Command Prompt (Admin).
  2. Enter the following command:

    sfc /scannow

SFC Scnannow

Once completed, you will receive a message confirming that Windows found some corrupt or missing files, and that it has repaired them successfully.

Load up Outlook, and check that your emails are now sending!

If you are still having issues, there is still hope.  Another command that other users have found helped them out is using the NetShell utility from the command prompt, similar to the solution we provided above.

  1. Open the command prompt once more by right clicking the Windows button in the bottom left of the screen, and select Command Prompt (Admin).
  2. Enter the following commands:

    netshwinsock reset

This handy set of commands will reset your network adapter to its default settings, and hopefully get you going again.

Authored by Ian


Ian Johnson is a Director of OJ Networks. He has been working in IT since 1995. Mentored by the best, Ian started as Technical Support Officer for an innovative dialup ISP in Brisbane “Hub Communications”. He progressed to become a Web Design and Programmer in ASP, ASP.NET and PHP during his time at “The Lab Development Group” with David Vandenberg amonst others. Ian has been working as a Consultant on the Sunshine Coast since 2001 and became a Microsoft Certified Information Technology Professional (MCITP) Server Administrator in 2010 after which he formed OJ Networks. He has assisted numerous small businesses to reach their potential through IT Infrastructure Planning and Implementation and Web design, Development and Web Marketing. You can connect with Ian on Linked In.

Share This:
  • Asoka Mahinda P

    Thanks, it’s working