(16-08-2024, 09:08 PM)king1 Wrote:(16-08-2024, 02:31 PM)SueDonim Wrote: The original problem at the beginning of this thread started after a Thunderbird update and resolved when a Windows update came through. So although I was open to suspecting Norton being the problem, I have no real evidence that it was.
Could be, equally possible Norton pushed out an update in the background and it wasn't until the restart for the windows update that it took effect... One of the irksome things about IT is that it is quite often difficult to pin down exactly which component has failed on you - sometimes you just gotta take the win when it is back to normal...
That sounds perfectly logical. When the Thunderbird update came through nothing seemed to change at the time, then did after the Windows update. Which does bring me back to my earliest comment which was to suspect that something was a temporary mismatch and would sort itself, but seemed to be taking longer than I expected. That's when I started to get nervous and look a bit more closely.
I'm well aware of how difficult in can be to pin things down. I spent many years being the systems person and expert in our specialist applications whilst needing IT for the bigger picture and when things really went wrong and I know that it can all get very complex.