rdp system something wrong powerShell.exe' is not recognized

When I click on start then i  type powershell.exe nothing happen,i type again powershell without exe and appear this:
when i start powershellscript.bat i receive this error
powershellscript.bat works perfect for my others rdp's

PS C:\Users\Dana> C:\Users\Dana\Desktop\SUCCES-LAST24h.bat
Batch cmd 1
'powerShell.exe' is not recognized as an internal or external command,
operable program or batch file.

Open in new window

I also have a scanner.bat i run it and must stop when finds this line ''-m '' but doesn't stop,works fine for my others 2 rdp's,so what's wrong with this one?how can i fix all this?
john lambertAsked:
Who is Participating?
jmcgConnect With a Mentor OwnerCommented:
The first thing to do to try to debug this situation is to locate powershell.exe on the target system and determine whether its directory is included in the PATH variable.
john lambertAuthor Commented:
Target  and start is this:
my others 3 rdp's have indentical paths and works perfect

My script:
@echo off
pushd %~dp0

REM ... some CMD commands here ...
echo Batch cmd 1
call :callPS PSScript1
REM ... some CMD commands here ...
echo Batch cmd 2
call :callPS PSScript2
REM ... some CMD commands here ...
exit /b

:callPS label

powerShell.exe -ExecutionPolicy RemoteSigned -Command "$script = Get-Content '%~f0'; Invoke-Expression -Command ($script[(($script | select-string '::%1::').LineNumber)..(($script | select-string '::%1End::').LineNumber-2)] -join [environment]::NewLine)"

exit /b


write-host -foreground red Script1
Get-EventLog System | Where-Object {$_.EventID -eq "1074" -or $_.EventID -eq "6008" -or $_.EventID -eq "1076"} | ft Machinename, TimeWritten, UserName, EventID, Message -AutoSize -Wrap  | Out-File Reboot.txt


write-host -foreground green Script2

Open in new window

QlemoConnect With a Mentor Batchelor, Developer and EE Topic AdvisorCommented:
"Target" does not matter in this batch file. PowerShell.exe needs to be found via PATH (or special path set up in the reigstry). So you'll have to check that from inside the failing RDP session.
footechConnect With a Mentor Commented:
Make sure that your Path environment variable hasn't gotten borked.  Check the PATH registry entry under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment is of type REG_EXPAND_SZ.  If it is just REG_SZ it will not be evaluated/expanded and would cause problems.
The target and start-in information that you provided look like what would appear in a shortcut but that is not the method you're invoking with. I agree with Qlemo that you need to see what your PATH variable looks like in the RDP session where the failure occurs.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.