The difference between an anonymous file users fear and a tool users pin to the desktop is about two minutes of finish work: a proper icon and filled-in version details. It also quietly helps with antivirus trust and makes every future support call shorter.
You would not hand someone a medicine bottle with no label. Yet most converted tools ship exactly like that - default icon, empty properties, no version. The five PS2EXE fields on this page are the label. They cost one longer command line at build time and pay you back every time the file is looked at, scanned, pinned, or argued about on a support call.
An EXE with the generic default icon looks like every unknown file a user has been warned about. An EXE with a clear icon of its own looks like a tool. Users pin it to the desktop, recognise it in a folder of forty files, and - just as valuable - describe it accurately on the phone when something goes wrong: "the blue broom one" beats a file path nobody can pronounce.
The icon must be a real Windows icon file, .ico. A renamed PNG will not work. A good .ico carries several sizes inside it, so it stays sharp on the desktop and in a small list view; any icon editor, including free ones, can export that format from a simple image.
-title and -description - the name and explanation a human reads in tooltips and the Details tab-product and -company - the family the tool belongs to and who stands behind it; these two lines do quiet trust work with antivirus reputation systems too-version - the build number, the single most useful support field you will ever add-copyright - optional, but its presence is another small signal of a finished, owned toolTogether they are one conversion line: Invoke-PS2EXE -inputFile ".\Cleanup.ps1" -outputFile ".\Cleanup.exe" -iconFile ".\cleanup.ico" -title "Disk Cleanup Tool" -product "Office Toolkit" -company "Technical Anshu" -version "1.2.0".
Number your builds simply - 1.0, 1.1, 1.2, or year-based if you prefer - but bump the number every single time the script changes, and rebuild. The payoff arrives on the first support call: "right-click the file, Properties, Details - read me the file version" instantly tells you whether the user is running your fix or last month's bug. Without it, every stale copy in the wild is indistinguishable from the current one, and you will debug ghosts.
The matching habit: put the same version in the script itself as a comment on line one. Script comment, EXE version and the folder you archive them in should always agree.
.ico, readable at small sizeNone of this changes what the tool does. All of it changes whether people trust it, find it, and can be helped with it - which, for a tool built for other people, is most of the job.
Watch the video to see the icon and details applied during conversion and checked in Properties afterwards.
Watch Full VideoNot directly - Windows program icons must be .ico files. Convert your image with any icon editor (free ones exist) and ask for a multi-size ICO containing at least 16, 32 and 48 pixel versions, so it looks right in list views and on the desktop. Then pass that file to -iconFile.
Start at 1.0 and keep it simple: raise the last number for small fixes, the first for big changes. The exact scheme matters far less than the discipline - every rebuild after a script change gets a new number, and the same number sits in a comment at the top of the .ps1.
They do not override detection, but they remove the anonymity that heuristic systems distrust, and they let reputation attach to an identifiable publisher's files. Combined with signing and consistent distribution they are part of the honest fix - not a trick, just a finished, owned file.