Timeline for "Security Alert" certificate in windows, finding the problematic program
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31 at 15:33 | vote | accept | Web and Flow | ||
| May 26 at 9:46 | answer | added | Daniel B | timeline score: 0 | |
| May 24 at 21:02 | comment | added | Web and Flow | @DanielB That did the trick! And since it's available through Microsoft it's "prescribed" in a way (however externally authored). No need for weird third party tools or log analysis. Please submit it as an answer and I will gladly mark it correct. Thanks! | |
| May 24 at 20:07 | comment | added | Daniel B | It's highly likely the windows are associated with the app that caused them. Use something like Process Explorer, with the crosshairs tool, to try and find it. | |
| May 24 at 17:31 | comment | added | Ramhound | You have some software running on your machine trying to make a secure HTTPS connection, due to the certificate being invalid, Windows is preventing that connection. | |
| S May 24 at 17:16 | review | First questions | |||
| May 24 at 17:19 | |||||
| S May 24 at 17:16 | history | asked | Web and Flow | CC BY-SA 4.0 |