> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-actions/produceexe.md). # ProduceExe ## Description Create an executable file. Enter a file name for the new executable file. Usually this command is used after patching (see actions `PatchByte`, `PatchWord`) to obtain a patched version of the file. IDA produces executable files only for: * MS DOS .exe * MS DOS .com * MS DOS .drv * MS DOS .sys * general binary * Intel Hex Object Format * MOS Technology Hex Object Format For other file formats please create a difference file (the Create DIFF file command; action `ProduceDiff`). {% hint style="info" %} Only Change byte... and Change word... commands (see actions `PatchByte`, `PatchWord`) affect the executable file contents, other commands (including the Manual... command) will not affect the content of the disassembled file. {% endhint %} EXE files: Output files will have the same EXE-header and relocation table as the input file. IDA will fill unused ranges of the EXE file (e.g. between relocation table and loadable pages) with zeroes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hex-rays.com/ida-actions/produceexe.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.