We've helped others with the same issue - the sashost.dll is read from and/or replaced several times during various Update-in-Place processes, and this can lead to brief locking of the file by on-demand security endpoint software scanning.  As you found, if you've verified that all SAS Client/Service processes were stopped prior to the update attempt - and there are no locks being held on that file - renaming it to .old or _old.dll, etc. and hitting "Retry" in the SAS Deployment Wizard is a possible workaround. ... View more

Good afternoon!   This exact error message (especially when you see an Application Error from jproxy.exe in the Windows Event log each time Base SAS/SAS Foundation is launched) is usually caused by antivirus software blocking the startup of the SAS Private Java Runtime Engine Have your I.T. team add the exclusions noted in SAS Support - Base SAS® shows the message, "ERROR: The java child process terminated unexpectedly: status -1073740940" (service-now.com) and test opening the application again.   Note: This has been seen 99% of the time with SentinelOne, because it will often times block the application without raising an error to the user/logs. ... View more

Glad to hear that worked for you as well, @King-JZF.   Note: If your organization requires that specific service to stay disabled in an environment (i.e., you wouldn't be able to print anyway) there is a startup option in the SAS 9.4 Windowing Environment that could also be used.  Contact SAS Technical Support to create a Case if so, and we can help you further diagnose. ... View more

Here is one other method of resolution that has worked for me in stubborn situations before (you may need I.T. assistance), but doesn't require quite so many edits to the registry.  Again, always back up the registry before, just in case!   Open regedit, as that Windows User having the issue Navigate to the "HKEY_CLASSES_ROOT" registry node, then look for the ".sas" folder underneath it Look at the Data value for the "(Default)" key Make sure it is set to "SAS.Program.701" - instead of the incorrect value of "sas_auto_file"   Close regedit and go back out to your Windows Explorer   Right-Mouse click on any .SAS file, and choose the 'Open With' option You should now see 'The SAS System for Windows' program (with the grey triangle) in the list Note: Select the checkbox option to "Always use this program" Now - if the issue is with any other file type other than .sas - note the folder name underneath each file type on the left (expand the node) - there is a pattern in which the folder name equates to that Data Value for the "(Default)" Key.   So, for example instead of 'SAS.Program.701', for a .sas7bdat file, you would specify 'SAS.DataSet.701'. ... View more

Hey there, @catchnight    By chance, are you running the SAS 9.4 platform on Windows 10?  Did you get the issue resolved?   My team did see a couple instances where - if you had a certain Windows Update applied - and your Windows Print Spooler service was either stopped/disabled, the SAS Windowing Environment may not open.   Thanks ... View more

Hello Kc2 - SAS does note a workaround for the visual issues with the "Window Bar" component of the SAS 9.4 (SAS Windowing Environment) client with the TS1M7 release:   If you run the client in Windows 7 (or Windows 8 )  Compatibility Mode by adjusting the shortcut properties, this appears to be an acceptable workaround for most users for the time being.   http://support.sas.com/kb/67211 ... View more