Windows 10: WSL scripts not working when called from windows

I am hoping to run wsl bash scripts from windows so that my windows task scheduler can run wsl scripts as well.I set my task scheduler to call wsl.exemy windows task scheduler is not calling the scripts correctly.when I type from power shellwsl.exe <name_of_script> such aswsl.exe wsl_upgI get:/bin/bash: wsl_upg: command not foundThis only happened to my desktop computer recently.It was working fine before I reinstalled WSL.calling the scripts while I am in wsl works though.what I tried:I tried setting default user usingubuntu2004.exe config --default-user andyI edited the PATH variable o

:)

 

PowerShell scripts not working with Call operator

Hi,



Thank you for writing to Microsoft Community Forums.



I understand that you are facing issues while developing a PowerShell script using the Call operator. I would suggest you to refer the articles

The Windows PowerShell ISE.



However, as the issue is related to developing PowerShell scripts, I would suggest you to post your query on

MSDN forums, where we have expertise and developers who are well equipped with the knowledge of developing PowerShell scripts in Windows.



Regards,

Prakhar Khare

Microsoft Community – Moderator

 

WSL in windows Store

Actually, this is a consumer-oriented forum for general Windows 10 questions.

As WSL concerns mostly developers and Enterprise, I suggest asking there.

 

PowerShell scripts not working with Call operator

Hello

I have been developing a Powershell script using Powershell ISE, and for the most part i am very happy about it, however i have encountered what i believe to be a bug in the call operator (&).

When i use the call operator followed by a "pure" string everything works as it should, the command works and ISE runs as usual, but when i use the call operator followed by a variable, the command executes correctly, however ISE will no longer use the
intellisense function to automatically show a drop-down list of possible variables when using "$". It is still possible to press ctrl + space to force the drop-down to appear. This error will disappear when you delete the call operator or the variable.

Here is an eksample:
(This courses the problem)
$c = 'C:\Path\To\Script'
& $c

(This does not course the problem)
& 'C:\Path\To\Script'

I hope someone is able to help me understand what is happening here, and if it is a bug then give me an alternative solution to executing a script on the local PC though a script.

I use Powershell version 5.1.17763.503

***Original title: The Powershell call operator breaks my ISE***