A dedicated converter is not the only way to ship a script like a program. Windows hides one tool already, PowerShell has its own wrapper, and sometimes the best wrapper is none at all.
The video shows the converter route, and for portable tools it is usually the right one. But a good technician knows the neighbouring options and when each beats a converted EXE: IExpress, built into every Windows; PS2EXE, for scripts that should be PowerShell anyway; and the unglamorous champion, scheduled tasks, for machines you manage. Compared honestly, including the limit they all share.
Type iexpress.exe on any Windows PC and a wizard appears that has shipped with Windows for decades. It builds a self-extracting package: your files are compressed into an EXE which, when run, unpacks them and launches a chosen install command - which can be your batch file. It is free, signed by Microsoft’s own ecosystem, and present everywhere, which makes it attractive for deployment packages.
The honest limits: it is a packaging tool, not a script compiler - the same extraction-to-temp behaviour applies, the interface is dated, options are few, and there is no tidy icon and version workflow compared with a dedicated converter. For a quick internal installer it is perfectly respectable; for a polished tool, the converter wins on finish.
If your automation is growing - real error handling, objects instead of text scraping, Windows APIs - the better move may be to rewrite it in PowerShell and wrap it with the free PS2EXE module: Install-Module -Name ps2exe -Scope CurrentUser, then ps2exe -inputFile tool.ps1 -outputFile tool.exe. You gain a far stronger language and an EXE with icon and version options of its own.
The same honesty applies with interest: PS2EXE is also a wrapper, the script text is recoverable, antivirus heuristics watch PowerShell even more suspiciously than batch, and signed PowerShell with proper execution policy is the professional destination - not a wrapped script with the policy bypassed.
For machines you manage, the cleanest “program-like” delivery often needs no conversion: a scheduled task that runs the BAT with the right account and triggers, plus a shortcut with a proper icon for manual jobs. The script stays readable - which in a managed environment is a feature, because the next technician can audit exactly what runs. Group Policy and tools like Endpoint Central deploy such tasks centrally. Conversion earns its place when files leave your control and travel to unmanaged PCs; inside your own estate, transparency usually beats packaging.
Pick the converter for portable tools handed to people outside your control. Pick IExpress for simple self-extracting packages where a built-in tool matters. Pick PowerShell plus PS2EXE when the job has outgrown batch - and plan the move to signed scripts. Pick scheduled tasks for your own managed machines. And whichever you choose, repeat the sentence that governs this whole series: a wrapper changes presentation, never trust - if the contents must be secret, none of these four is the answer.
The video covers the converter in depth - use this comparison to confirm it is the right route for your tool before you build.
Watch Full VideoYes. iexpress.exe is a built-in Windows component that creates self-extracting packages through a wizard. It unpacks your files and runs a chosen command, which can be a batch file - the same wrapper principle as a converter, with fewer polish options.
No. PS2EXE is also a wrapper and the PowerShell script inside is recoverable. Its advantage is the PowerShell language itself - better error handling and access to .NET - not secrecy.
On machines you manage centrally, prefer scheduled tasks or deployed scripts that stay readable and auditable. Conversion is for tools that travel to unmanaged PCs, where a single tidy file with an icon and manifest is worth more than transparency.