PE Explorer crashes

[Merlin]

Hey guys!

I needed to change the text in a title bar of an app that I don't have source code to. I used FlexHEX to change it but it increased the file size by 8 bytes and obviously the checksum changed. So I got a copy of PE Explorer to modify the checksum but everytime I try to save the file PE Explorer crashes...every time.

Here is the Event log:

CODE

Faulting application name: pexplorer.exe, version: 1.99.5.1333, time stamp: 0x4906ef0c
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdb3b
Exception code: 0xc0000374
Fault offset: 0x000cdcbb
Faulting process id: 0x13f8
Faulting application start time: 0x01ca4ca163ab3160
Faulting application path: C:\Program Files (x86)\PE Explorer\pexplorer.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: b1cf549e-b894-11de-834e-002215044560

My OS is Win7/64.
Any ideas?

Thanks

[TechMan]

If the app you are trying to modify is 32-bit, please send your file to support - @ - heaventools.com, and we will try to address the issue.

If your app is 64-bit... Well, the current version of PE Explorer simply doesn't support for 64-bit executables.

At any rate, I guess that modifying the checksum after the file size increased won't do the trick.

[Merlin]

Hi Techman,

Thanks for the reply. Indeed the file is 32-bit, and as my system is 64-bit that could be part of the issue.

Why do you not thing that modifying the checksum will work? The reason I need to update the checksum is that as soon as I save the file from the hex editor, my AV application kills it because of the incorrect checksum.

Is there something else you think could be triggering it?

Thanks.

[TechMan]

Please do send us your file. We hate it when PE Explorer crashes.

Regarding the checksum: if you turn your AV app off, will the modified exe run? If yes, then OK. However, adding extra 8 bytes might change all possible offsets within the app, and make the app invalid. In this case, the checksum won't help much. On the other hand, PE Explorer calculates and updates the real checksum. It doesn't fake it. So if your app verifies its own integrity, it will detect modifications to the file anyway.