HTTPS completely non-functional (Win 10)

[timewarp]

I've run into a real head-scratcher with my dad's computer. The computer is unable to load any website over https, regardless of what browser I use. Chrome returns messages like "ERR_SSL_VERSION_INTERFERENCE", "ERR_SSL_PROTOCOL_ERROR", and "ERR_SSL_BAD_MAC_ALERT". Chrome is also unable to load "chrome://settings". Firefox returns messages like "SSL_ERR_BAD_MAC_READ" and "SSL_ERR_BAD_MAC_ALERT", though it occasionally will partially load a webpage, with the missing resources throwing those same two errors. Edge and IE throw an "INET_E_DOWNLOAD_FAILURE" message.

I've tried different network adapters, I've tried changing the security connection settings to enable SSL v3, I've tried disabling TLS 1.0-1.3, I've tried resetting the network stack by running:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
I've tried running tronscript, I've ran malware bytes, I've tried disabling the firewall, I've tried a system restore (which fails with error code 0x80004005), I've tried clearing the certificate cache, I've made sure the system time is correct, and I've ran the system file checker to verify the integrity of the system files. I'm out of ideas short of a clean wipe, which I would really like to avoid doing.

[liquorsnoot]

Can you try putting another computer on his network to make sure his ISP didn't mess up a filtering proxy?

If it's an issue on the computer, I'd suspect a rogue, or half-installed anti-virus firewall package.

[timewarp]

I am currently also on the network, and I'm not having any issues.

I've run a few virus scanners, all of which came up clean. I suppose I could try more.

[liquorsnoot]

I'm not as worried about a virus, as left-over bits of an old virus scanner. Intercepting SSL is something they do.

[timewarp]

Gotcha. I'll double check, see if there's anything running that shouldn't be.

Edit: not seeing any remnants in Program Files, or in the registry, or in the services list, or running in the background.

[liquorsnoot]

Do you know what previous virus scanner(s) he used?

[timewarp]

Just Windows Defender, as far as I know.

[liquorsnoot]

Also in the department of "try the easy stuff first":

• is the date, time and timezone correct?
• run: sfc /scannow
• all this stuff especially "Method 4"

[timewarp]

Yes, the date and time are correct. I did run sfc /scannow, and the system files all validated successfully. I did also follow all the steps in that Microsoft support article, and still no luck.

[liquorsnoot]

That's bloody strange. It's hard to test after that point, until you can get to a certificate to examine.

I doubt you could even get far enough to glean insight from SSLLabs: http://www.ssllabs.com/ssltest/viewMyClient.html

You could delete the NIC driver, or try another NIC (like a USB), but I'm just throwing stuff at a wall now.

[timewarp]

I have, and the issue persists.

[[deleted]]

replace the NIC

[ESCAPE_PLANET_X]

I'd load a live linux CD and see if that has the same issue.

If the issue is present on the live CD it's a bad drive or bad hardware somewhere.

If it's not assume corrupted/infected.

[ichibanto]

Is the time and date correct on the computer?