Today a customer had their 3 windows 7 PCs install an update that caused all of them to blue screen when they tried to use ATE to Telnet to the server. We are not sure of the details but rolling the systems back to the previous day and turning off automatic updates solved the issue.

This is the Windows Update you're talking about, right? I don't suppose anything was captured in the ATE ashlog.log file, although it might be worth taking a look. I'll see if I can track down a Windows 7 machine that has done that update to see if I can reproduce it.

I was just warning our group to perhaps save them some time if they ran into the same problem. There was nothing to report since the workstation crashed before it really got started in ATE and I wouldn't have you waste time on this unless it happens again. The outside IT guys who solved this did not provide any details so I don't have anything to tell you anyway.

Unfortunately I haven't had any success in confirming this. My one Windows 7 machine had had the automatic updates turned off (to prevent Microsoft from auto-updating it to Windows 10), but when I tried to manually update it, the online update system was either down (perhaps because of this problem) or otherwise never responded. My guess is that there may have been a bad update which has since been corrected, but it's hard to know for sure.

I can say that no one else has reported this, so I'm guessing it is an isolated occurrence.