microsoft
Cannot start job. The language mode for this session is incompatible with the system-wide language mode.
When trying to run Powershell (now in Powershell 7) I get the following list of errors. Trying to figure out if this is a usage error from my side, or issue with the module itself.
When trying to run Powershell (now in Powershell 7) I get the following list of errors. Trying to figure out if this is a usage error from my side, or issue with the module itself.
Hello @FoxFuze
I remember someone else having that same issue in the past (#228 )
The issue was the LanguageMode was set to ConstrainedLanguage mode. By default this has to be FullLanguage.
Can you check how is the LanguageMode at your terminal?
$ExecutionContext.SessionState.LanguageMode
@FoxFuze
That was not to change the configuration, was just to see what is the actual configuration of the LanguageMode.
So, it was set to ConstrainedMode?
Apologies, see below.
PowerShell 7.5.1 [Constrained Language AUDIT Mode : No Restrictions] PS C:\Users\bartho.niemand> $ExecutionContext.SessionState.LanguageMode ConstrainedLanguage PS C:\Users\bartho.niemand>
Yep, it should be FullLanguage
let's see if that cmd does the trick:
$ExecutionContext.SessionState.LanguageMode = "FullLanguage"
After that, check again if the LanguageMode have changed and try to run ARI (preferably in a new terminal window)
@Claudio-Merola as stated in the previous output I did change the language mode and still it did not work
Please take a look at my previous comment. Output
@FoxFuze I believe the LanguageMode is being set by an AppLocker policy, that is why is being impossible to change it.
Can you check internally if that is the case?
Hi @Claudio-Merola I checked AppLocker policies and unable to see anything in the local policies. I've tried multiple troubleshooting steps using AI and still no luck. the weird thing is that this use to work without any issues a few months back. and the latest version is only compatible with PowerShell 7.x.x
My last resort will be to install an older module and hope for the best unless you have more guidance?
Hi @FoxFuze
This has to be a policy to enforce the ConstrainedMode, a WDAC perhaps? (Using a system application control policy)
Did you checked on gpedit.msc at: Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Application Control Policies > AppLocker -> Script Rules
There are any rules there?
What about the registry, at: *HKLM\System\CurrentControlSet\Control\SESSION MANAGER\Environment*
There is any key named: "__PSLockdownPolicy" I believe value 4 would be ConstrainedMode
If that is the case I would suggest working with the policy team to workaround these configuration.
Maybe if you delete that Registry key and change the "Application Identity service" to manual, then stop it. and then change the LanguageMode to FullLanguage and then run the script it would work, but I'm not sure.
Also maybe you could try to create a PSSession file (New-PSSessionConfigurationFile), but if this is a security policy, I doubt it will bypass that.
Latest versions of the script won't work with Powershell version 5 and below due to the cmdlets we use in the script.
My friend, please, remove all of your informations from the logs, don't show them to the public....
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @Claudio-Merola , I'm having the exact same issue.
I'm using powershell 7.5.2. I'm running it elevated and I have the necessary access in our azure tenant.
I actually checked the Script Rules before I made this reply and there's no reference to PS in there.
I checked in Registry in the path: HKLM\System\CurrentControlSet\Control\SESSION MANAGER\Environment
There's no PSLockdown entry or key.
When I run the ARI, I get the exact same issues and the output XL is empty.
when I check the language mode:
