Schannel errors on Windows 7

I have Windows 7 Home. After updating Avast Free to the latest I’m getting a bunch of Schannel errors. It looks like it is happening when Microsoft Outlook pulls down new emails.

Avast Info

Avast version installed: 21.10.2498 (build 21.10.6772.706)
Virus definitions version: 211206-2
Number of definitions: 27,657,412
UI version: 1.0.679

Windows system log info

Event: 36887
Description: The following fatal alert was received: 70.

  • System

    • Provider

    [ Name] Schannel
    [ Guid] {1F678132-5938-4686-9FDC-C8FF68F15C85}

    EventID 36887

    Version 0

    Level 2

    Task 0

    Opcode 0

    Keywords 0x8000000000000000

    • TimeCreated

    [ SystemTime] 2021-12-06T11:27:20.997342700Z

    EventRecordID 780308

    Correlation

    • Execution

    [ ProcessID] 980
    [ ThreadID] 4044

    Channel System

    Computer Steve-MYTH

    • Security

    [ UserID] S-1-5-18

  • EventData

    AlertDesc 70

===================================

Here’s my Windows 7 Home System Info:

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name STEVE-MYTH
System Manufacturer CLEVO
System Model P15xEMx
System Type x64-based PC
Processor Intel(R) Core™ i7-3630QM CPU @ 2.40GHz, 2401 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1.02.17(11), 1/24/2013
SMBIOS Version 2.7
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = “6.1.7601.24545”
User Name STEVE-MYTH\Steve
Time Zone Central Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 9.55 GB
Total Virtual Memory 31.8 GB
Available Virtual Memory 21.6 GB
Page File Space 15.9 GB
Page File C:\pagefile.sys

Hi,

Would you mind disabling Mail Shield (Protection > Core Shields > Mail Shield) and see if there is a difference?

First I went to the Windows 7 system log and cleared its contents so I was starting from a clean slate. I turned off Mail Shield. I logged into my ISP’s web mail and sent an email to myself. After it was received by web mail I then used MS Outlook 2013 to retrieve the mail from my ISP’s mail server. There was no schannel error. I did the same thing again but this time Mail Shield was on and there was no error.

Mail Shield on. Next, I l sent another email from my ISP’s web mail to myself and while in web mail I refreshed the screen and there was the email I sent to myself. I went to my Outlook on Win 7 and retrieved email from the server. Then I checked the system log and no schannel error. However, next I selected the email in Outlook and did a Shift-Delete which deletes the email permanently rather than move it to the trash folder. I checked the Windows system log again and there was a bunch of schannel errors.

Hi,

So it only happens when you select the email in Outlook and do a Shift-Delete. Could you temporarily uninstall Avast and test it again, please?

This problem seems to have vanished because I haven’t seen it in the system log in a few days. I did not reinstall Avast either.

Hi,

So the issue resolved itself without any changes from your side?

Apparently so because I never “knowingly” did anything. It just showed up for a week or two. I wish some of Microsoft’s error reporting gave more information. I’m clueless where these schannel errors stem from.

Hi,

Thank you for the clarification.

I spoke to soon. The problem has resurfaced. Got a bunch of schannel 70 errors again just now. I was doing MS Outlook 2013 deletions with Shift-Delete again. I don’t know if it matters but I got an update to Avast Free this morning.

For months my Win 7 computer was taking forever to shutdown. I could never figure out what was causing it. Then yesterday I uninstalled Avast Free Antivirus and removed all traces of it from C:\ProgramData. I downloaded and installed Avast One successfully. Now my computer shuts down quickly once again. I thought perhaps it would also cure the schannel errors that started this thread in the first place; but no, I got another one a short time ago. However, yesterday I got none.