Install on new computer is wonky: Can no longer right click for batch, et al

[texasmfp]

I had a great running setup on my old computer (9.4).  Installed on a new computer and its wonky.

When I click on a .sas program, it sends it to batch rather than opening in a windowed environment.  meanwhile, when I right-click on the file, batch submit is not an option, nor is open with SAS Foundation, Enterprise Guide, etc....

BTW, this is installed on my E drive (an NVME SSD drive).  It was also installed on the same NVME on my last computer.

Thanks

[JackHamilton]

I don't have any helpful suggestions for you, but I wanted to sympathize.

Assigning default and optional actions to programs has become progressively harder over the years.  This is mostly not the fault of SAS Institute.  Microsoft has removed some of the tools previously used to manage file types and associations, and added additional restrictions on what can be easily done. 

I say "mostly not" because SAS used to distribute a file types manager with SAS, and no longer seems to  do so (it's not installed here; maybe that was a local choice).  Maybe Microsoft broke it too.

[mkeintz]

@JackHamilton 

I agree that Microsoft is making these things harder, but my recent SAS installation (SAS 9.4m6 on my new Windows 10 Professional, 3 to 4 months ago), did not appear to drop any right-click options.  Among other sas-specific options, I see "Batch Submit with SAS 9.4", "Batch Submit with SAS 94. (UTF8)", "Open with SAS 9.4".   It's based on a software depot from June 2019.

[texasmfp]

Thanks for confirming I am not going crazy, mkeintz.

I note something new:  I clicked on a program and, then right-clicked on open with SAS 9.4 I got an error popup block from SAS that says:

"ERROR: Insufficient authorization to access C:\WINDOWS\system32\PT US Margin.log."

My SAS (9.4 M6) was totally installed on the E drive and the config file was changed so that even the temp file points to the E drive.  Nothing in SAS should be looking to access the C drive.  Any chance this is part of the issue?

[mkeintz]

@texasmfp 

You have quickly reached an issue that goes well beyond my expertise, so so I post the points below just as general observations:

1. Why would sas want to write to a log in c:\windows\system32?   Does it mean you are opening a sas program named PT US Margin.sas also located in that directory?  I guess there could be something in the sas configuration file that points to that directory, but I have no idea why.
   
   
2. if you don't have authorization, you must be running SAS under a non-administrative logon.  This is a good thing, since you shouldn't be authorized to write to areas reserved for systems management when just running a regular sas program.

[texasmfp · Accepted solution]

Tech Support called me and walked me through the solutions.  Turns out, there is a SAS note on this, which includes a neat registry edit tool to fix file associations.

https://support.sas.com/kb/45/779.html

In addition to fixing the registry, refreshing the BASE SAS install solved the issue.