wslview produces a lot of errors and delays commands

[landorg]

Windows Version

Windows 11

Windows Build Number

22631.4317

WSL Version

WSL 2

Distro Version

Arch

WSL Utilities Version

4.1.1

Describe the bug

wslview takes a very long time and produced the errors below. In the end the browser is opened when I run this from terminal (not from emacs). This delays commands like gcloud auth login a lot.

This variable is not set $Env:__PSLockdownPolicy.

❯ wslview https://www.example.com
Cannot set property. Property setting is supported only on core types in this language mode.
At line:1 char:1
+ [Console]::OutputEncoding = [System.Text.Encoding]::UTF8; [Console]:: ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertySetterNotSupportedInConstrainedLanguage

Cannot invoke method. Method invocation is supported only on core types in this language mode.
At line:1 char:59
+ ... ing]::UTF8; [Console]::InputEncoding = [System.Text.Encoding]::GetEnc ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : MethodInvocationNotSupportedInConstrainedLanguage

Cannot invoke method. Method invocation is supported only on core types in this language mode.
At line:1 char:128
+ ... etEncoding(850); [Environment]::GetFolderPath('LocalApplicationData')
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : MethodInvocationNotSupportedInConstrainedLanguage

wslpath: \Microsoft\WindowsApps\22955VineelSai.ArchWSL_qz230bc1wsk9j
Cannot set property. Property setting is supported only on core types in this language mode.
At line:1 char:1
+ [Console]::OutputEncoding = [System.Text.Encoding]::UTF8; [Console]:: ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertySetterNotSupportedInConstrainedLanguage

Cannot invoke method. Method invocation is supported only on core types in this language mode.
At line:1 char:59
+ ... ing]::UTF8; [Console]::InputEncoding = [System.Text.Encoding]::GetEnc ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : MethodInvocationNotSupportedInConstrainedLanguage

Steps to Reproduce

run wslview https://www.example.com

Expected behavior

No errors. Works fast

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[patrick330602]

@landorg Can you try to set $ExecutionContext.SessionState.LanguageMode = 'fulllanguage' in your powershell and see what is the output? I suspect this related to this: https://overflow.seasi.dev/questions/57032747/how-to-change-powershell-mode-to-fulllanguage-mode-from-constrained-mode#57032893

[landorg]

Hi and thanks for your answer.
My PS is in constrained language mode yes. Not completely sure why as I am admin locally and no LockdownPolicy set.

PS C:\Users\username> $ExecutionContext.SessionState.LanguageMode
ConstrainedLanguage
PS C:\Users\username> $Env:__PSLockdownPolicy
PS C:\Users\username> $ExecutionContext.SessionState.LanguageMode = 'fulllanguage'
Cannot set property. Property setting is supported only on core types in this language mode.
At line:1 char:1
+ $ExecutionContext.SessionState.LanguageMode = 'fulllanguage'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertySetterNotSupportedInConstrainedLanguage

If I run PS as admin then it's in full language mode.

I tried to find the group policy that did this but I couldn't find it.

Is there a workaround available for my situation?
Thanks

[patrick330602]

@landorg can you check if you have these set in the system? https://4sysops.com/archives/mitigating-powershell-risks-with-constrained-language-mode/

[landorg]

I think I have AppLocker. Seeing these events in the event viewer:

%OSDRIVE%\USERS\USERNAME\APPDATA\LOCAL\TEMP\__PSSCRIPTPOLICYTEST_NDC1EGZV.XOZ.PSM1 was prevented from running.

[patrick330602]

Can you try to disable the rules using the methods in the article?

[landorg]

I don't think I can. Not sure if this is normal but I can't even see them in gpedit.