Laptop not able to access sites using SSL

[Duranis]

Not sure if this is the best section but here goes.

 

I have a Windows 7 Pro laptop here that is no longer able to access any HTTPS website using either IE or Chrome.

This laptop is connected to the Admin network (Vanilla server 2008 R2) that is pretty much just default settings.

The laptop was taken to another school and used yesterday, since then it has had this problem.

 

What I have tried so far:

• In IE under Options>Advanced>Security. Ticked "Use SSL 2.0" and "Use SSL 3.0"
  
• Checked date and time are correct.
  
• Tried multiple accounts, including admin account.
  
• Checked other computers on the same network are ok (they are).
  
• Under the same settings tried disabling all TLS.
  
• Tried combinations of SSL and TLS versions being enabled/disabled.
  
• In IE under Options>Content - Hit the clear SSL State button. Did this also after making changes.
  
• In IE Under SecurityTrusted sites - Added the HTTPS site I was trying to access (Gmail) and set security level to low.
  
• In IE hit every Reset/Default settings button I could fine
  
• Reregistered DLL files as described here: https://www.techsupportall.com/solved-cannot-access-secure-sites-https-websites-not-opening-view/
  
• Reregistered the same DLL files using the microsoft auto fix.
  
• Tried IE, Chrome and firefox - All the same issue.
  
• Did a system restore back to last week when it was working ok.
  
• Disabled WiFi and used only cable connection (we have had some wifi issues here so was just ruling that out).
  
• Enabled IMAP on his gmail account and set up outlook. This will not connect either using SSL, TLS "worked" but was blocked by gmail.
  

 

I'm now pretty much out of things I can think of to try other than a complete reinstall from scratch (which seems like a bit of a sledge hammer solution). Anyone else got any ideas that I can try?

Edited April 19, 2016 by Duranis

[win]

uninstall IE and then re-install

[Duranis]

Update:

Well I did nothing more to it and the next day it was working normally again... No idea what was going on there.