@gauravbajpai4622

God bless you man, finally someone with a genuine solution

@takashiimai8215

Thank you for this video. It worked perfectly for me. I made sure that the shortcut key wasn't assigned to anything else beforehand.

@ethanaerni8938

The only free method I’ve seen. Thank you!

@lakshmikanth4550

After so much research found this video and worked like a charm

@Wyldfyre.84

Fantastic video. Thank you for this solution!

@brucelee1457

I initially didn’t pay close attention to the details in this video. I created the .ps1 PowerShell file, converted it to an .exe file, and tested it by running the application directly. The .exe worked perfectly when clicked manually! However, when I tried to schedule the .exe with Task Scheduler, it failed to work.

After following the steps in the video more closely, I found the solution: using Task Scheduler to directly execute the .ps1 file instead of the .exe file. The key was to set the "Action" field to "powershell -executionpolicy bypass -file C:\path\to\your\powershellscript.ps1". This allowed the script to run successfully.

@monsayavatrasresth8262

Million thanks!!! This really worked for me.

@kirand9459

its worked for me. Thank you AIP

@zechariahlaughlin1388

Having trouble with this. Help would be very much appreciated. The ps1 file presses the keys however it does not trigger the flow only default action if any.

@xnbet

Thanks for sharing. However, it's not working. I follow the steps, and when running, only the Command prompt appears and disappears without any other action.

@rohanbhattacharyya6600

I tried this. It is working if I execute the powershell script but it is not working from Task Scheduler. I also tried to put the powershell logic in a batch file and trigger the batch file. Same issue. If I double click the batch file it is working but not working from task scheduler. Not giving any error also. The shortcut I am using is Ctrl + Alt + Q. Any help will be appreciated.

@Deepakbhogle

Thanks for video

@MohammadShahin-vd3oi

it's working fine , many thanks.but a question? is this way working if I logout from the virtual machine??

@hoangvo8637

thank you for your video helps me alot but can you explain for me how can I get the file file.ps1 and which content that file.ps1 have? Thank you alot

@brianramdhani6345

After I save the file Program can't run, any same problem?

@yenc1898

Am sending Ctrl + Shift + X, what is the command?

@piratoraman

lets give it a try. nice hack :)

@kudanmedia

Mine was also failing to work but then managed to fix it: 

Keys to start the flow:
(Ctrl + Shift + P)

#Powershell script:

[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
[System.Windows.Forms.SendKeys]::SendWait("^{+P}")

Then on the task scheduler i had to put the full part for power shell, I had to first test in manually first in cmd to see it it work and it worked fine and started the flow.

C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe

Then on the argument:
-executionpolicy bypass -file C:\path\to\your\powershellscript.ps1

The only change I'm now facing is that when the flow start they is a input variable pop up which appears which needs user intervention for the flow to start, how do i solve this.

@iFFU17

Is there any way when i open batch file it directly execute pda flow and if any system exception (user not logged)occurs write to text file or email..