You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Medicat_installer.exe & medicat_installer.bat
ran each from explorer with 'Run as Administrator'
run from admin instances of cmd, powershell, and Powershell 7.
I found if I removed the call to a 2nd script for my powershell profile it no longer gave the error.
This is the line that is in my "C:\Users\a\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1" profile. . "C:\Users\a\Documents\WindowsPowerShell\Powershell-WinDefault\Microsoft.PowerShell_profile.ps1"
Commenting that out and then running it goes to the menu. I've attached a screenshot of the powershell error; perhaps this is the same issue as issue #23 ?
See attached:
The text was updated successfully, but these errors were encountered:
I think that using powershell.exe -NoProfile -Command would make sense in Medicat_Installer.bat -- the potential for interference and conflict is present when a custom profile.ps1 is loaded, and some profiles can take seconds (or longer) to load, so each powershell.exe call can add up.
Also - is there a reason that Medicat_Installer.bat is setting the execution policy for the entire machine rather than using powershell.exe -ExecutionPolicy Bypass for each powershell command? Would you consider capturing the current execution policy in the .BAT script (using either a foreach loop or reg.exe /query) then resetting it back to its original state when the installer finishes?
I have tried:
I found if I removed the call to a 2nd script for my powershell profile it no longer gave the error.
This is the line that is in my "C:\Users\a\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1" profile.
. "C:\Users\a\Documents\WindowsPowerShell\Powershell-WinDefault\Microsoft.PowerShell_profile.ps1"
Commenting that out and then running it goes to the menu. I've attached a screenshot of the powershell error; perhaps this is the same issue as issue #23 ?
See attached:

The text was updated successfully, but these errors were encountered: