Archiver (WinRAR, 7Zip) Crash When Opening Certain Archives

[christantoan]

Hi,

 

I have a weird problem where my archiver software (I tried WinRAR and 7Zip) would crash if I open archives with special files inside it. What kind of files are needed to crash the software are still unknown to me because it seems to happen at random archives but it happens consistently with the archives. It also doesn't always happen after opening the archive, it also sometimes happen after opening a folder inside the archive (also consistent folders).

But the archives can always be succesfully extracted without errors if I directly extract them and not browsing the archives first.

 

Any clue as to why this happens? I already tried searching the Internet but it seems I don't have the good keyword for this as the results are usually irrelevant.

Thank you very much for the help.

[Guest maut]

Maybe a RAM problem.. have you checked yours?

[kasper]

or hard drive fatality 

test your hard dirve with Crystal disk info or HDtune 

[macnavarra]

Run in command prompt with admin privileges the following command regsvr32 /i shell32.dll  maybe it solves the problemo.

[christantoan]

2 hours ago, maut said:

Maybe a RAM problem.. have you checked yours?

I'll try to check it now.

1 hour ago, kasper said:

or hard drive fatality 

test your hard dirve with Crystal disk info or HDtune 

I don't think it's HDD related because it happens across different drives (and SSDs)

1 hour ago, macnavarra said:

Run in command prompt with admin privileges the following command regsvr32 /i shell32.dll  maybe it solves the problemo.

Sorry. It doesn't solve the problem

 

Thank you for the tips all.

[straycat19]

I have seen that happen when your AV software detects a file it doesn't like, such as a crack or keygen, or a packed dll sometimes.  Try disabling your AV software and then try opening any archives that have crashed every time you attempted to open them previously.

[christantoan]

3 hours ago, maut said:

Maybe a RAM problem.. have you checked yours?

I just finished checking my RAM. It doesn't have any problems.

16 minutes ago, straycat19 said:

I have seen that happen when your AV software detects a file it doesn't like, such as a crack or keygen, or a packed dll sometimes.  Try disabling your AV software and then try opening any archives that have crashed every time you attempted to open them previously.

Sorry. Disabling the AV also doesn't help

[luisam]

Happened to me when the file-name is too long  or contains strange characters like arabic, chinese, russian etc.

[Togijak]

1 hour ago, luisam said:

Happened to me when the file-name is too long  or contains strange characters like arabic, chinese, russian etc.

looks like it is something else than the characters, just tested with arabic without problems

 

[jbleck]

17 hours ago, christantoan said:

Sorry. Disabling the AV also doesn't help

Disabling temporally doesn't do much... due to the "easy to use race" many security companies went silent/auto mode (not really disabled). U have to either remove/restart or check on another system.

[christantoan]

Hi all, thank you for all the helps.
I already found the solution.

Basically, it was because of conflict between PowerISO and Alcohol 120% and their file type association method used.
I solved it by disabling the replace icon option from Alcohol 120%.



Sent from my OnePlus 3T using Tapatalk

[luisam]

5 hours ago, christantoan said:

Basically, it was because of conflict between PowerISO and Alcohol 120% a

 

I do understand that there might be a conflict between PowerIso and Alcohol 120% because both are image burning utilities, both manage images and create virual drives. for the purpose, I only use PowerISO. But it is strange how a conflict between them may affect WinRar and 7zip. The only relationship I see is that WinRar and 7Zip can open ISO image files. i'm not sure if they can open any other image format.

Anyway, it's interesting to know about this issue.

[christantoan]

I will try to explain this the best I can. This is my theory and can be wrong though.

 

One of the clues I noticed is that the archive or the folder of the archive that has been crashing both contain .bin files (though when I try to create .bin file using notepad it doesn't crash).

When PowerISO creates a filetype association, it modifies a key in the registry on that extension to "redirect" the file extension description.

Now when Alcohol 120% tries to create file association, it parses the description and adds its own description (for icon and context menu)

The problem is that Alcohol 120% cannot handle some of the file extension supported by PowerISO, so when WinRAR or 7Zip tries to display the icon for these unsupported files (for example .bin files), it will wait for the icon until it crashes.

 

That is my theory about these problem. Why it doesn't affect File Explorer I don't know but I notice it also affects other programs that can display archive files like ACDSee.