I have tried all of these workarounds, and none has worked for me, including the "tkelsproxy.exe" fix, futzing with firewalls and anti-virus, system restore, etc. I called SAS support today, and the tech I spoke with had no workarounds other than the "open SAS, close SAS, open SAS" method which has not worked for me. The SAS technician mentioned they use Windows 7. I suspect they will become more aware of the problem as more users upgrade to Windows 10. This is a serious problem that hopefully SAS is working feverishly on. While it only affects SAS functions that use JAVA such as ODS, those are some very important SAS functions. ***Update May 27*** I spoke with a SAS support manger on May 26. He convinced me that fixing this is a top priority for them and said they will be following up with everyone who filed a ticket on this issue.
... View more