Variable name: HzShrMemBase
Variable value: 1912602624
However under windows 10 this prevents access to the ILS application but adding and removing the variable fixes it as does running the app in legacy mode for Windows XP SP2 but this is temporary. After a reboot the issue remains persistent. Doing file system scans (SFC) and check disk also occasionally resolves the issue, but the issue remains persistent and comes back after a couple shutdown and restarts.
After doing some intense investigation into this matter it appears to be related to security and application permissions. Unfortunately thus far the only resolution I could find had to do with running the ILS application as an administrator and for staff convivence disabling UAC.
Step 1. - Make the user using the application a local admin as shown below.
Make use a local admin
Step 2. - Set the app to run as administrator
Step 3. - Change UAC (Reason for this is to prevent the popup prompt)
After running the ILS application like this for 3 weeks I am confident that the issue has been mitigated. Do I recommend running an application like this? No. However it was consuming IT resources having to go back and disk scanning, adding/removing system variables to get the report to run. There is extra security precautions put on to the system for monitoring and firewall blocking. For now that is all that can be done until an application update.
Make use a local admin
Step 2. - Set the app to run as administrator
Step 3. - Change UAC (Reason for this is to prevent the popup prompt)
After running the ILS application like this for 3 weeks I am confident that the issue has been mitigated. Do I recommend running an application like this? No. However it was consuming IT resources having to go back and disk scanning, adding/removing system variables to get the report to run. There is extra security precautions put on to the system for monitoring and firewall blocking. For now that is all that can be done until an application update.