After due windows update all POP3 accounts in Outlook 2010 report error 0x800CCC1A your server...

[Guest JerkKuston]

Symptoms

 

The set of windows updates (15 "important updates") were released on May 15th 2014. After their installation (and reboot) Outlook 2010 POP3 fetch fails with 0x800CCC1A error code. Removal of the updates via Control Panel -> System and Security -> View Installed Updates does not cure this issue.

 

 

I had to restore the last disk image I take regularly for backup purposes in order to get rid of this issue.

 

My system: Windows 7 Professional, Service Pack 1, 64-bit.

 

 

Troubleshooting Method

 

I installed the updates in question one by one making system-wide snapshots before and after installation with Regshot 1.9.0 x64.

 

 

Cause

 

The issue was caused by Security Update for Windows 7 for x64-based system (KB2871997).

 

 

Resolution

 

The update affects 19 files in Windows\SysWOW64 folder. After the update removal, a half of those files was not restored back (file size based comparison). Therefore, booting from CD/DVD and copying those files from backup image (taken before the update) was the only remedy. After this was done, POP3-fetch worked again.

 

 

I used the following script executed as >pop.bat D:\Backups C:

 

----------------pop.bat

 

rename %2\Windows\SysWOW64\adprovider.dll adprovider.dll.old

rename %2\Windows\SysWOW64\capiprovider.dll capiprovider.dll.old

rename %2\Windows\SysWOW64\cngprovider.dll cngprovider.dll.old

rename %2\Windows\SysWOW64\credssp.dll credssp.dll.old

rename %2\Windows\SysWOW64\dimsroam.dll dimsroam.dll.old

rename %2\Windows\SysWOW64\dpapiprovider.dll dpapiprovider.dll.old

rename %2\Windows\SysWOW64\kerberos.dll kerberos.dll.old

rename %2\Windows\SysWOW64\KernelBase.dll KernelBase.dll.old

rename %2\Windows\SysWOW64\msv1_0.dll msv1_0.dll.old

rename %2\Windows\SysWOW64\ncrypt.dll ncrypt.dll.old

rename %2\Windows\SysWOW64\ntkrnlpa.exe ntkrnlpa.exe.old

rename %2\Windows\SysWOW64\ntoskrnl.exe ntoskrnl.exe.old

rename %2\Windows\SysWOW64\objsel.dll objsel.dll.old

rename %2\Windows\SysWOW64\schannel.dll schannel.dll.old

rename %2\Windows\SysWOW64\secur32.dll secur32.dll.old

rename %2\Windows\SysWOW64\sspicli.dll sspicli.dll.old

rename %2\Windows\SysWOW64\TSpkg.dll TSpkg.dll.old

rename %2\Windows\SysWOW64\wdigest.dll wdigest.dll.old

rename %2\Windows\SysWOW64\wincredprovider.dll wincredprovider.dll.old

 

pause

 

copy /Y %1\Windows\SysWOW64\adprovider.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\capiprovider.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\cngprovider.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\credssp.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\dimsroam.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\dpapiprovider.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\kerberos.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\KernelBase.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\msv1_0.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\ncrypt.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\ntkrnlpa.exe %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\ntoskrnl.exe %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\objsel.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\schannel.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\secur32.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\sspicli.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\TSpkg.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\wdigest.dll %2\Windows\SysWOW64\

copy /Y %1\Windows\SysWOW64\wincredprovider.dll %2\Windows\SysWOW64\

------------cut

 

 

Conclusion

 

In order to preserve Windows Update consistency, it is important to remove the KB2871997 update so as nothing in Windows would rely on the updated version of the files going forward.

 

 

At this point I had to just hide KB2871997 and sacrifice its benefits to be able to use POP3 with accounts @

 

live.com

 

gmail.com

 

gmx.at

 

However, due to lack of the information found on internet regarding this issue I suspect it may be specific to few malconfigurations in the field. So, I would appreciate if someone from Microsoft could kindly look into this.

 

 

Thank you.

 

 

Vitaly Zuevsky (uk.linkedin.com/in/vzuevsky/)

 

Continue reading...