PDA

View Full Version : Operating Memory Unpack Error


Dazed_and_Confused
June 17th, 2004, 07:13 PM
I just happened to be looking through my NOD32 scanner logs. When I right-click a scan event in the log, and then details, I am able to see the results of previous scans. Each of them have a message about an Operating Memory Unpack Error. What is this, and how can I fix it? The text pasted below is the first few lines of the detail of one the scans.

Scan performed at: 6/15/2004 2:00:40 AM
Scanning Log
NOD32 version 1.789 (20040614) NT
Command line: c:\ /clean /ah /all /subdir+ /heur+ /scanfile+ /scanmem+ /scanboot+ /scroll+ /arch+ /pack+ /mapi- /pattern+ /scanboot+ /scanmbr+ /heurdeep /log+ /prompt /quit
Operating memory - unpack error

Bandicoot
June 18th, 2004, 11:01 AM
Hi D&C,

There is a packed file running on your system somewhere. Could you email a complete copy of your log file to support@nod32.com please? Also put a link to this thread.

Thanks.
Bandicoot. ;D

Dazed_and_Confused
June 18th, 2004, 05:05 PM
Looking through my log, I did see this entry:

c:\Program Files\WormGuard\wguninst.dll »PECompact v1.67 - unpack error

Is this what is causing the problem? If not, I'll email the entire log. Thanks

Arin
June 18th, 2004, 05:33 PM
someone had the same unpacking error in this very forum. its a legitimate file and you shouldn't be worried. you could try mailing that file so that ESET can fix this error.

Dazed_and_Confused
June 18th, 2004, 10:35 PM
-{ Quote: "someone had the same unpacking error in this very forum. its a legitimate file and you shouldn't be worried. you could try mailing that file so that ESET can fix this error." }-
Thanks. I recognized the name WORMGUARD, so I figured it was a legit file. If this is the problem, I just find it hard to believe that as long as WG has been on the market that Eset has not addressed this yet. I'll be glad to send the file if they want me to.

snowbound
June 18th, 2004, 10:40 PM
-{ Quote: "someone had the same unpacking error in this very forum." }-

That would be me, ;)

http://www.wilderssecurity.com/showthread.php?t=33730


snowbound

Dazed_and_Confused
June 19th, 2004, 11:50 AM
-{ Quote: "That would be me, ;)

http://www.wilderssecurity.com/showthread.php?t=33730


snowbound" }-
Thanks, Snowbound. After reading your thread, I guess I'll ignore the problem as well.

JacK
June 19th, 2004, 12:27 PM
Hello,

ESET does not handle a lot of runtime packers, just some UPX versions and a few other packers.

Regards,

Dazed_and_Confused
June 19th, 2004, 12:31 PM
-{ Quote: "ESET does not handle a lot of runtime packers, just some UPX versions and a few other packers." }-
Hello, Jack. Pardon my lack of knowledge here, but are you saying that NOD32 cannot unpack the file because it does not have much unpacking capability? Are packed files the same thing as zipped or compressed files? Thanks. :)

Arin
June 19th, 2004, 03:54 PM
NOD32 can unpack files very well. its just that DCS is using a special packer. packed files are different from other archives. when you run a packed file it unpacks on-the-fly. means it decompresses itself directly to memory.