Recent Topics
-
UNSOLVED PA 19.00.57 (and earlier) Duplicate files possible in .pa archive in some cases.
Tech Support3 -
Fast Ring: PowerArchiver 2019 19.00.51/54/57
Tech Support6 -
UNSOLVED GUI: In need of a complete overhaul
Tech Support3 -
UNSOLVED GUI: move label
Tech Support3 -
UNSOLVED GUI: too much frames
Tech Support2 -
UNSOLVED PowerArchiver shell extensions possibly crashing windows explorer.exe
Tech Support10 -
UNSOLVED Encrypt files inside archive that has already been created [.zipx]
Wishlist3 -
UNSOLVED PA 19.00.51 / Access Violation
Tech Support7 -
SOLVED PA 19.00.51 - bug / unwanted code execution
Tech Support8 -
SOLVED Strange file size seen in 2019 portable
Tech Support5 -
SOLVED Fast Extract large files directly to target directory
Wishlist4 -
UNSOLVED Forums: double Search option in the settings (left side hamburger menu)
Tech Support1 -
SOLVED Serpent-256 Encryption for PAE/PAE2
Wishlist14 -
UNSOLVED Moving Files in to a 7Zip archive
Tech Support2 -
UNSOLVED hang when using the Test function with 7z archives
Tech Support5 -
UNSOLVED Some buttons in "Modern Look" are too small
Translations3 -
Fast Ring: PowerArchiver 2019 19.00.30/31/32/33/39/40/41/43/44/46/47/48/49
Tech Support23 -
UNSOLVED Searching for the specific Regkeys needed to default new installations in Modern Windows 10 not dark view
Tech Support2 -
UNSOLVED E-Mail problem
Tech Support7
Trying to extract encrypted PAE file from SFX
-
Trying to create an encrypted SFX file with extraction in current directory. Then test the executable extraction causes SFX to crash.
See Video.
http://www.cyberblob.net/CrashSXA.wmv
PA version 11.61.07
-
I can confirm this in Windows 7 Ultimate 64bit…
screen-shots below give additional details…
-
Are you using the latest SFX?
http://www.powerarchiver.com/blog/2009/12/17/new-7zip-sfx-for-those-who-need-it/
-
great! Thanks!
-
this is for PAE i think…
-
Even after replacing the PASZIPSFX.DAT with the new version. I get that error.
Yes, i am trying to extract an encrypted PAE file that has been converted into a self extracting archive that has current directory selected so the user does not have to find a directory to store the files.
The current directory selection looks like where the error is.
If i don’t select that function and use the standard TEMP location it works fine.Thanks guys…
I love my PA…
-
new sfx is for 7zip, so thats why ;-)… we logged it in, thank you for the report!
-
Please check if following pre-release fixes the issue:
http://www.powerarchiver.com/test/release10/powarc116202.exeand let us know… thank you!
-
error still occured for me in Windows 7.
-
Same here… Just converted OS to Win7. Still crashes.
version 11.62.03Unhandled exception at 0x776b8549 in New Text Document.exe: 0xC0000005: Access violation writing location 0x00090ffc.
Ok. This is what i have found if you create a real directory called “current Directory” in the execution location it will work by asking you the password.
It is looking like it thinks that the directory it needs is Current directory instead of getting the current directory and filling that variable.
The funny thing is in Ollydbg if you attach to the executable it will create the directory “Current directory” once you click decrypt.
It looks like it is taking it literally.Please check if following pre-release fixes the issue:
http://www.powerarchiver.com/test/release10/powarc116202.exeand let us know… thank you!
-
Same here… Just converted OS to Win7. Still crashes.
version 11.62.03Unhandled exception at 0x776b8549 in New Text Document.exe: 0xC0000005: Access violation writing location 0x00090ffc.
Ok. This is what i have found if you create a real directory called “current Directory” in the execution location it will work by asking you the password.
It is looking like it thinks that the directory it needs is Current directory instead of getting the current directory and filling that variable.
The funny thing is in Ollydbg if you attach to the executable it will create the directory “Current directory” once you click decrypt.
It looks like it is taking it literally.my mistake, it was not fixed in 11.62, there were some other sfx issues fixed so i thought this might be it without reading too much…
-
Issue was not fixed in 11.63.13.
