English English  Deutsch Deutsch

Frequently Asked Questions

For your convenience, a list of frequently asked questions is provided below. Please be sure to review this list, as it is very possible that your question has already been answered here. If the solution you seek is not here, feel free to contact our easy going Technical Support.

Also note that another important source of information is the extensive Help system that has been provided with PE Explorer. The Help system is well-organized and very easy to use. Moreover, by taking a few moments to review the help, you will better familiarize yourself with the program and learn more about all the features available. See also our Getting Started articles.


Common Questions

File Open

File Save

Resource Editor

Export Viewer



Common Questions

What is the difference between the trial version and the full version?

Your evaluation copy of PE Explorer is a fully functional time-limited demo with a few restrictions. This means that the same capabilities available in the registered software are present in the non-registered software. This allows you to try out all the basic features in PE Explorer to confirm that they work to your satisfaction.

Some minor functions are disabled until PE Explorer is registered: the "Save all resources at once", "Remove relocations", "Remove debug information", and "Save disassembly" menu commands do not work in trial mode. It is also limited to the number of days you can use the software. Please buy a license to remove these limitations.

Why is PE Explorer so expensive over a free alternative like Resource Hacker?

Let's make it clear: PE Explorer is not a resource editor. It's different. It's better. Even though it contains the resource editor, PE Explorer is meant for "heavy lifting" and has nothing to do with Resource Hacker, just like Notepad is not exactly a free viable alternative to MS Word. PE Explorer is intended to be used in various scenarios such as software development, forensics practice, reverse engineering, extensive binary security analysis and binary auditing processes, and the resource editor is only a tiny fraction of the PE Explorer features. When you utilize all the different tools PE Explorer integrates, you will agree that $129 is definitely an awesome price.
Check out The Feature List

If you want to edit resources only but don't need the extended functionality of PE Explorer, Resource Tuner is the right product for you.

PE Explorer fails if I use it to examine itself. Is this intentional?

Yes. It was our intent.

It claims to be an editor, yet doesn't let me edit the program code. Why?

PE Explorer is not a binary code editor. PE Explorer edits the internal structure of PE files, including resources. If you want to edit the program code, you need a hex editor, such as Flex HEX Editor.

How can I change something in an EXE or DLL file?

Most people asking how to open/edit .EXE or .DLL files are actually not really aware of what they are trying to deal with. EXE and DLL files are not plain, traditional text ASCII files that you can easily read and edit. You cannot simply open up an .EXE like a text file and start editing or reading the contents. Opening an EXE file is equivalent to opening the television box to look at the circuitry inside, instead of using your remote to change the channels. Sometimes the only meaningful information inside executable files is Vendor information (copyrights, trademarks, origins) and Product Version information. These binary files have a complex nested structure defined by the Portable Executable format, and they are not intended to be editable by users, neither are DLLs meant to be opened separately from the programs they belong to.

However, if you do want to change something in an EXE or DLL file for whatever reason, you may be able to do this by changing their resources with Resource Tuner. But still you will not be able to modify the actual code in any way: resources are separated from the program code. This way, you can make significant changes to the interface of the program while leaving the code untouched. You may also be able to translate the program interface into another language.

I couldn't even open a single dll file. All that popped up when I opened it was a whole bunch of numbers.

That's what DLL's are all about. If you expect to see a comics inside, forget it. PE Explorer provides the most useful representation of the data. What you do need is a good understanding of programming functions, and at a minimum the ability to read and understand those numbers.

What is a PE file... I heard of them but thought my OS couldn't run them? Am I likely to have one on my PC? And if so would I want to explore it?

"PE" in this context stands for "Portable Executable", the file format used by EXEs, DLLs, ActiveX controls, and other executable files on 32-bit Windows. The term "Portable Executable" was chosen because the intent was to have a common file format for all flavors of Windows, on all supported processors.

A PE file is a 32-bit executable developed by Microsoft for NT (and W9x) platform. The other notable executable types that run on MS platforms are "MZ" (DOS), "NE" and "LE" — but those 16-bit formats are obsolete (but they will still run). Open an exe file in a Hex Editor and the first two values in the file will be 'MZ' — yes the DOS header is still there. Scan down 128 bytes and you should find the values 'PE' — this is where the PE format takes over.

For greater detail download PE Explorer and consult the extensive Help system that has been provided with PE Explorer. The Help system is well-organized and very easy to use. Moreover, by taking a few moments to review the help, you will better familiarize yourself with the program and learn more about all the features available.

Not all PE files have the 'exe' extension. Other notable PE files have the extensions "dll", "scr", "sys", "cpl" and "ocx", and even "msstyles" featured in Windows XP. Also note that not all PE files will run on their own — dll's for example. PE files that run on their own include exe, scr and cpl.

More detailed information can be found in the Microsoft Developer Journal article, February 2002: An In-Depth Look into the Win32 Portable Executable File Format by Matt Pietrek.

Is PE Explorer a developer tool, or is this something a general computer user would use?

Everyone can benefit from this software. Being an affordable developer tool, PE Explorer makes every person who is interested in looking inside of Windows programs a potential buyer. The program is an easy-to-use tool for all users, but some functions require advanced programming knowledge to comprehend. Using PE Explorer assumes some basic knowledge of the internal structures of PE files.

See also: User Testimonials

Will there be a version for 64-bit exe files in the future?

Yes. We will come up with 64 bits in the version 2.

Any plans to localize PE Explorer in German and/or other languages?

Yes. The version 2 will have the multilingual interface.

File Open

I got an immediate error of something like "This file is likely damaged, packed or compressed". What can I do?

Nothing. This is not viewed as a bug. We are not going to defeat the security attempts of other software authors. PE Explorer automatically unpacks only files compressed with UPX, Upack and NsPack.    More on File Open Errors...

What are packers?

Packers are utilities that compress Windows portable executables (EXE, DLL, etc) significantly while leaving them 100% functional. They achieve this by modifying executables to include a decryptor routine that is executed first. The result is a smaller executable overall with an extra section inside, and that section is executed upon startup to decompress the file, allowing the executable to run as usual. Many packers encrypt data and resources, providing protection against reverse engineering for executable files.

I got an immediate error of something like "Incompatible" and "of type NE". What is a "NE" type file?

PE Explorer works with PE files only. An NE (or "New Executable") file is a 16-bit application intended to run on old Windows versions 3.xx.

Will the PE Explorer work with NE and other 16-bit files?

No. The NE format is obsolete.

If PE Explorer doesn't work on NE type files, do you have a product that does?

No. At any rate, knowledge of 16-bit format makes less sense, especially since the 64 bit processors have hit the market.

PE Explorer doesn't work with .Net files, why?

PE Explorer does not handle .Net assemblies. It is designed to work with unmanaged 32-bit PE files. While some .NET files may share the PE format, PE Explorer does not fully support .NET assemblies.

Your tool says it has some internal error and hence opening in SAFE MODE. Why?

If opening a file produces an error, PE Explorer opens that file in Safe mode. While in Safe mode, the data that caused the error can not be operated on. This does not guarantee that the excluded file data is error free, but in many cases allows you to work with damaged files (e.g. compressed files). For example, if the Import section follows the Resource section, you normally cannot open such a file in a binary analyzer. PE Explorer provides a solution by enabling you to to work with damaged/packed/crypted files and examine the inner workings of applications and dll's.

File Save

If I open an executable file with PE Explorer and then go to 'Save As' and save the executable under a different name WITHOUT making ANY changes to it, and then I compare the two files with a hex editor, there are MANY changes to the file. Why are there changes even though I didn't make any?

PE Explorer automatically performs two functions when opening a file: unpacking files compressed with UPX, Upack, and NsPack, and error checking.

If your target file was packed with UPX, it was automatically unpacked and saved unpacked. PE Explorer does not re-pack previously packed files. Which is why the original file size is increased. Check out the logfile for details.

The next thing PE Explorer does is re-compiling the file's resources according to the MS PE file specification. That may also be the reason why the original file size is changed after a simple "Save As..." operation.

If you don't want any changes to be made, just do not save.

When I try to save my DLL file in the Program Files folder, PE Explorer reports a save file error. What may be the problem? How can I solve this issue?

The issue you're encountering is due to permission restrictions in the Program Files folder. Windows prevents modifications in this folder to protect system files. To resolve this issue, follow these steps:

1. Copy your file to another location on your computer, such as your Desktop or Documents folder.
2. Make the necessary changes to the file and save them.
3. Copy the modified file back to the Program Files folder.

You'll likely need adminstrative permissions to paste the file back into the Program Files folder.

When I try to save my DLL, I get the following error: Can't create new image file, the original file has been probably packed. Any hints?

Most likely, you are attempting to save the file under the Program Files directory. For security reasons, modern Windows versions (7, 8, 10, 11, and newer) restrict users from saving files in the Program Files folder. To address this issue, try saving the modified DLL in a different directory outside of the Program Files folder.

Please note that your DLL might indeed be packed. Our software unpacks only files compressed with UPX, Upack, and NsPack. If your DLL is packed using a different packer, look for instructions or tools to manually unpack it before proceeding with modifications. Otherwise, you may encounter issues creating a new file and saving your changes.

Resource Editor

How can I get started editing PE file resources?

This page: Resource Editor Tutorials covers some of the most popular features of the Resource Editor. Find out how Resource Tuner can help you have a personal touch on your favorite applications.

How do I export all resources, edit them and import them back?

The current version of the Resource Editor has no import feature. We recognize the potential value of this feature, but this will be available only in future versions.

It seems to only handle regular Win32 resources. Do you have a version that handles .NET resources in managed assemblies?

No. Or not yet.

Why does PE Explorer tell me that the icons I have selected to replace do not have the same size and the same bits and color depth? Can you fix it?

This is not a program error. When replacing icons, you must make certain that the replacement sources are the same size and have the same number of colors as the item to be replaced (e.g. a 16x16 4-bit icon can not be replaced with a 32x32 8-bit icon).

Why? Because icons are not just single images. Icons in an EXE file can come in various sizes and color depths, and they are organized in groups called "Icon Groups".

Here's an example of an Icon Group found in the Notepad application:

Notepad IconGroup

Each Icon Group can contain multiple icon images, each with a different size and/or color depth. Common sizes include 16, 32, 48, and 256 pixels square, color depths include 32-bit (24-bit with 8-bit alpha channel), 8-bit (256 colors) and 4-bit (16 colors).

When Windows displays an icon, a desktop shortcut for example, it selects the appropriate image from the Icon Group based on specific criteria. If the replacement icon doesn't match the original icon's size and color depth, it could lead to inconsistencies in how the icon is displayed in different contexts.

If you encounter a mismatch error while attempting to change an icon that appears to have the same size and bits, it indicates that the source icon's color depth is not the same (24-bit and 32-bit icons may look similar but have different color depths).

How can I edit resources from the command line?

Resource Tuner Console, a command line batch processing version of the resource editor is available for download.    More on RT Console...

I need a command-line tool to change the Icon in an exe file. Do you have that?

Yes, we have Resource Tuner Console. It allows you to change the icon in an exe file via command line. Since there may be multiple icons in an exe file, the tool supports Icon resource files (files with a .ICO extension) that contain one or more images, which may be at different pixel sizes and/or color depths. If an .ico file contains more than one image, the entire icon set will be added or changed (depending on the EditMode and ChangeMode settings) at once. RTC accepts input from a script file, and sample scripts can be found within the Resource Tuner Console package.

Export Viewer

How do I get parameters on function exports? I have the function name, but that is near useless unless I can figure out the parameters.

If you don't have the source code and API documentation, the machine code is all there is. PE Explorer provides a Disassembler tool that can assist you in this task. However, there's no automated way to determine the parameters. There's only one way to figure them out: run the disassembler and manually analyze the disassembly output. Unfortunately, this task of reverse engineering the interface cannot be automated.

PE Explorer includes descriptions for 39 different libraries, including core Windows operating system libraries like KERNEL32, GDI32, USER32, SHELL32, and WSOCK32, as well as key graphics libraries like DDRAW and OPENGL32. However, PE Explorer may not cover all libraries or functions ever developed.


What is a disassembler?

A disassembler is a computer program which translates machine language into assembly language, performing the inverse operation to that of an assembler. A dissasembler differs from a decompiler, which targets a high level language rather than assembly language. Disassembly, the output of a disassembler, is often formatted for human-readability rather than suitability for input to an assembler, making it principly a reverse-engineering tool. Though this may not do you any good unless you know assembler already.

Is true decompilation possible?

No, of course not. Fully automated decompilation is not possible — no decompiler can precisely reproduce the original source code.

While PE Explorer does disassemble code, converting machine code into assembler, it does not generate C or C++ code from the disassembled output. Decompiling code into higher-level languages like C or C++ is a task of great difficulty.

It spits the results out in assembly format, which I don't understand at all. Do you have other products or plugins that can provide the output in English?

Obviously, the original source language syntax no longer exists in the executable. It would be very difficult for a decompiler to interpret the series of machine language instructions (ASM) that exist in an executable file and decide what the original source instruction was.

I have just run the disasembler on an exe file and want to change some code in it. But how do I put it back into an application format like it was?

The results generated by the PE Explorer disassembler are intended for reference and comparison purposes only. The generated output cannot be recompiled as is into an application format like the original executable. Additionally, the disassembly output has not been optimized for memory and processor usage.

If you want to make changes to the code, you would typically need to manually modify the source code or use a hex editor to patch the executable directly.

Why couldn't be the disassembler slightly more usable (a list of API functions etc)?

It will be improved — in future versions. The "what-to-do" list is mile long and seemingly never-ending.

What are the benefits of the disassembler if all it gives you just an unreadable assembly format?

The disassembly listing uses Intel mnemonics. A familiarity with Intel mnemonics helps with reading the listings. A solid grasp of the PE file format also helps. A description of the format can be found in the PE Explorer help.

The PE Explorer Disassembler provides addititional processing for the section header data of a PE file. The disassembler translates the binary machine language digits that form the PE file into assembly language instructions and displays the results as a best approximation of how the original instructions might have appeared to the person who wrote them. The interpretation introduces imprecision just as a letter written in English then translated into Chinese and then translated back into English might contain errors.

The PE Explorer Disassembler handles common variants by default and can be set to handle uncommon variants as well. The benefit of having the disassembly listing is proportional to one's grasp of assembly language.

A description of Intel mnemonics, cpu architectures and assembly language in general can be found elsewhere at intel.com.


How can I write my own custom plug-in for PE Explorer?

See the PE Explorer help for the plug-in API.   More on the plug-ins

Have More Questions?

Feel free to contact our easy going Technical Support and submit your request.


Start Exploring Your Applications Now!

Give PE Explorer a trial run!Give PE Explorer a trial run for 30 days free! Once you try it, we think you will find it hard to go back to other PE file hacking utilities. For maximum editing and inspecting power, purchase a Personal license now for $129.00. The Business license is available for $229.95.