logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Connection Not Private Error Across Chrome, Firefox, IE on Win 7 SP1 System

wierzba123 4506 6
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
| New topic
  • #1 16713812
    wierzba123
    Level 16  
    Hello. I have a problem opening pages. Wherever I come in, a message pops up, the connection is not private. I scanned my computer with anti-malware and other similar no results. I tried to turn off the anti-virus and it does nothing. The problem occurs in all browsers rearranges. Win 7 SP1 system.
    Connection Not Private Error Across Chrome, Firefox, IE on Win 7 SP1 System Connection Not Private Error Across Chrome, Firefox, IE on Win 7 SP1 System
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #3 16713820
    jdubowski
    Tube devices specialist  
    Show what certificate is used there (click "advanced").
    Where do you have internet from? Do you use any proxy?
    Is the date and time on your system correct?
  • ADVERTISEMENT
  • #4 16713822
    Kolobos
    IT specialist  
    Is your date correct?
    Do you have all Windows Update updates installed?

    Include in the attachment logs from scanning from FRST (addition and frst.txt).
  • ADVERTISEMENT
  • #6 16726148
    Kolobos
    IT specialist  
    Comodo is guilty of what I see, get rid of it or set it up as needed.
  • #7 16744761
    wierzba123
    Level 16  
    Problem solved. It turned out that somebody broke the antennas on the network and such circuses took place.
| New topic
Report a violation of the law

Topic summary

The user experienced a "connection not private" error across multiple browsers (Chrome, Firefox, IE) on a Windows 7 SP1 system. Initial troubleshooting included scanning for malware and disabling antivirus software, but the issue persisted. Community responses suggested checking the system's date and time, ensuring all Windows updates were installed, and examining the SSL certificate used. A follow-up indicated that the user uploaded logs from FRST and temporarily resolved the issue. Ultimately, the problem was traced to physical damage to network antennas, which caused connectivity issues.
Summary generated by the language model.
ADVERTISEMENT