SAS9.4 freezes/non responding when copying

[DrAbhijeetSafai]

Update: The issue seems to be solved for me. So I am happy. Finally it got solved on it's own. Sharing here because I think it is importnat to give updates. Thanks. 

- Dr. Abhijeet Safai

[DrAbhijeetSafai]

Just wanted to document here that it is a very serious and big problem and lot of time is getting wasted as screen freezes. It is very frustrating as well.  I am sure that concerned people must be taking a note of it and must be involved in finding the solution but felt that I should share my experience. Thanks. 

-- Dr. Abhijeet Safai 

[SASKiwi]

@DrAbhijeetSafai  - If you want faster action on this then you really need to open a track with SAS Tech Support. Adding comments on old posts wont necessarily result in any action from SAS. 

[DrAbhijeetSafai]

@SASKiwi Ok. Thanks.

- Dr. Abhijeet Safai

[cminard]

This problem continues to persist. I am experiencing this problem using SAS for Windows version 9.4 TS Level 1M8, X64_11PRO platform. Windows Version 1.0.22621.

Microsoft Windows 11.

I did not have this problem prior to the upgrade to Windows 11.

I have found a solution that is inconvenient, but seems to work. It is NOT a long-term solution, and SAS needs to fix this issue.

SAS usually works well for a bit, but it starts freezing when I want to copy/paste when the "Results" tab starts to get large. When I start to get the freezing, I use the following steps:

1. Click on the "Results" tab. (NOT the Results Viewer)

2. Press <Ctrl> E (this empties the results tab and closes the results viewer)

3. Minimize the SAS window

4. Click on SAS in the task bar to open the program window on your screen

5. Click on your program to open the programming window

This process seems to temporarily resolve the issue until the results tab starts to fill up again. Obviously not ideal, but it seems to help a little.

[SASKiwi]

@cminard - I would advise contacting Tech Support and asking if this is issue is being addressed in SAS 9.4M9 which is due out very soon. The more people who raise this problem officially the more likely something will be done about it.

[cminard]

There have been several Windows updates since my post. This issue seems to have been resolved with at least one of the updates, but I do not know which one.