PS2EXE-GUI: "Convert" PowerShell Scripts to EXE Files with GUI

Overworking of the great script of Ingo Karstein with GUI support. The GUI output and input is activated with one switch, real windows executables are generated. With Powershell 5.x support and graphical front end. Now here:
4.7 Star
37,694 times
Add to favorites
E-mail Twitter Digg Facebook
  • Start multiple other associated processes at the same time?
    2 Posts | Last post August 16, 2019
    • Can you set up in PowerShell Scripts to start multiple associated processes at the same time after starting the application? For example, start at the same time
      C: Windows splwow64.exe
      C: Windows System32 Server Manager Launcher.exe
    • Hello xenapp,
      I do not if I get your question right. PowerShell is processing commands sequentially. You can start processes in scripts by calling their names or with Start-Process, but that's only nearly at the same time.
  • Script compiled into EXE got detected as malicious
    5 Posts | Last post August 15, 2019
    • Hi Markus, I`m looking for your assistance.
      I wrote a simple script which just checks some WMI system objects and then executed windows commands, no network access, no registry changes, file creations \ deletions. 
      I got a few detections from Kaspesky AV, and uploaded exe to virus total:
      I tried to sign the exe but this not really changed the situation.
      As I`m pretty sure that script itself is not an issue, I tried to use Powershell Studio to compile script...  and it is working well:
      Could you please help me determine the possible reason for this?
    • turning off "-requireadmin" lowered amount of detections.. but still
    • Hello MaksymSo,
      I think I cannot help you. I compiled a sample script and checked it with Virustotal, two scanners thought of it as suspicious. That's not unusual.
      You could send your compiled script to Kaspersky so they can check it. Maybe you should not execute programs with names like "invoice.exe" or "important_document.exe" in your script because this IS suspicious.
    • I do not use such names - virustotal change name of the checked files.
      Okay, thank you.
    • Hello MaksymSo,
      sorry, I didn't know that Google uses those strange names in their sandboxes.
  • Powershell Script Converted to EXE fails when ran as Scheduled Task
    3 Posts | Last post August 14, 2019
    • I have a simple powershell script that uses robocopy to move files from directory to directory. I have ensured all the logging robocopy would typically do in the console is moved instead to a log file. I can run this exe and it works as expected when ran manually however when ran as a scheduled task I get the following issue: error: 3762504530 Application: test.exe
      Framework Version: v4.0.30319
      Description: The process was terminated due to an unhandled exception.
      Exception Info: System.InvalidOperationException
         at System.Windows.Forms.MessageBox.ShowCore(System.Windows.Forms.IWin32Window, System.String, System.String, System.Windows.Forms.MessageBoxButtons, System.Windows.Forms.MessageBoxIcon, System.Windows.Forms.MessageBoxDefaultButton, System.Windows.Forms.MessageBoxOptions, Boolean)
         at System.Windows.Forms.MessageBox.Show(System.String, System.String, System.Windows.Forms.MessageBoxButtons, System.Windows.Forms.MessageBoxIcon)
         at ik.PowerShell.PS2EXE.Main(System.String[])
    • Unchecking noConsole got rid of the error for me. Now the exe says it ran but it doesnt actually do anything.
    • Hello CodeBroJohn,
      there seems to be something different between your interactive environment and the environment of scheduled tasks and the program wants to tell you what. Please pipe the output and the error channel to a text file and see what's going wrong.
  • Passing arguement
    5 Posts | Last post August 09, 2019
    • Hi Markus, I used PS2exe for converting .ps1 file. My ps1 file takes 2 arguments during installation. ie, .\my.ps1 "arg1","arg2". arg1 is used by an exe for installation. When I run from ps1, the exe takes arg1 as per the required logic but when I run ps2exe converted exe it takes both the arguments(arg1 and arg2)as input parameter which is causing issue. I verified the same by running process explorer. It would be very kind of you if you could help me.
    • Hello Abby Potter,
      I can explain this behaviour, but can not do anything about it because it's not under PS2EXE's control. When you pass "arg1","arg2" to a PowerShell script, an Array is passed to the script. If you pass "arg1","arg2" to an executable, the shell passes a string to the executable. So the string with the value "arg1","arg2" is the first parameter.
      Is it possible for you to set a blank after the comma? Could you omit the comma? This might work.
    • Hi Marcus, I believe I found the issue. When I was compiling to EXE I was using an older PS2EXE.ps1 powershell and not the one that was in your folder. When I tried your PS2EXE.ps1 the parameters now work.
      The path of my environment variable was kicking off another version of PS2EXE. 
      Thank you for all your help :)
    • Hello Alice Martini,
      are you sure you're answering to the correct question?
    • Oops, sorry for the wrong post. 
  • Include multiple files.
    2 Posts | Last post August 07, 2019
    • How can i modify this script so that i can include multiple files in the exe?
    • Hello Jerald4lyfe,
      I think I cannot fulfill the wish you have. There are to many things PS2EXE would have to determine or could not predict: the path to a sub script might have to be evaluated at runtime, variables might have a (sub) script scope, parameters to sub scripts have to be handled, script variables might have different values in sub scripts...
      Maybe a tool that generates self extracting archives would be better for you.
  • Thank you, Markus!
    2 Posts | Last post August 07, 2019
    • I compiled the script on a Win7 PC and the EXE is working perfectly. It's no problem for us to have a separate EXE for Win10 and one for Win7. I appreciate your advice, thanks again!
    • You're welcome.
  • Adding to my question
    2 Posts | Last post August 04, 2019
    • Sorry, I don't see an edit button for my previous post. I do have .Net Framework 4.7.2 on the Windows 7 PCs. The PowerShell version on the PC in question is 2.0.
    • Hallo Carl,
      PowerShell 2.0 always runs with .Net 2 up to .Net 3.51 and cannot use .Net 4.xx. You have two options:
      1. Compile your script with PowerShell 2.0 on your Windows 7 PC (this executable will fail on your Windows 10 PC if there is no PowerShell 2.0 present)
      2. Install WMF 3 or up on your Windows 7 PC, so PowerShell 3 or up are present
  • EXE crashing only on Windows 7
    2 Posts | Last post August 04, 2019
    • Hi Markus!
      I'm guessing that my Windows 7 PCs are missing a prerequisite but I'd like to run this by you just in-case.
      The Posh script that I converted to EXE is
      Copy-Item "C:\Users\$env:UserName\Appdata\Roaming\Microsoft\Sticky Notes\StickyNotes.snt" -Destination "Z:\Userdata\StickyNotes\StickyNotes.snt"
      The EXE runs and copies the data on Windows 10, but it fails on Windows 7. The error message that I get is
      Faulting module name: KERNELBASE.dll, version: 6.1.7601.24499, time stamp: 0x5d0115f1
      Exception code: 0xe0434352
      Fault offset: 0x000000000000b87d
      Please advise if you can, thank you!
    • Answer above...
  • Providing parameters to the EXE
    4 Posts | Last post August 02, 2019
    • After 'compiling' the PS to EXE I can't find a way to pass specific parameters as I could when it was a PowerShell script. Normally I could do: 
      SQL.ps1 -Tablename Employee -ACCNO 43214...
      Now that it's an exe it doesn't accept the paramter name. 
      Is there a way to pass specific named parameters to the executable? 
    • Hello Alice Martini,
      parameters are passed to the executable the same way as you pass it to a powerShell script, for your example:
      SQL.exe -Tablename Employee -ACCNO 43214...
      But there is a - for same cases big - restriction since it is an executable: all parameters are interpreted as of type [STRING]. There is nothing I can do about this, it is a restriction of way executables are called.
    • Thank you so much Markus for the quick response :)
      Unfortunately when the exe is compiled, the exe treats the paramter name as the actual value: 
      Here's my Powershell (x.ps1) that I convert to an EXE:
      write-host $name
      write-host $sex
      After compilation when I try to put in parameters x.exe -name Marcus -Sex male but i get the following
      the value of $name = "-Name" 
      the value of $sex = "Marcus"
      I've tried everyithing I could. the only thing that works is: x.exe Marcus Male
      (without any paramter names).
    • Hello Alice Martini,
      I'm sorry I to have to say I can't recreate your problem. In my environment everything's working fine.
      How do you call the executable x.exe? What PowerShell and what Windows version you are using? Are you sure you did not copy the code out of Word or another application and are unintentionally using "EN DASH" characters (ASCII code 0x96) instead of the regular "hyphen minus" (ASCII code 0x2d)?
  • How to suppress display of parameter and minimize the console
    2 Posts | Last post July 26, 2019
    • Hi Markus, I used PS2EXE.ps1 for converting my ps1 file to exe. My ps1 takes arguments, and when I pass the arguments to exe file it displays argument value in the console which I don't want. Also I want to minimize this console during installation. I can minimize the windows using "-WindowStyle Minimized" in PS1 file. 
      Could you help me.
    • Hello Abby Potter,
      are you sure you want a console program? Maybe you compile your script with the Parameter -NoConsole?
      But remember, every output will generate a message box then.
51 - 60 of 184 Items