-
when clciking on powerarchiver update from within powerarchiver we get a windows for the update but it nows sayes script errors. I think it could be due to windows update in windows 10 can you look into it. By pressing cancel it seems to be ok. It seems that the page being displayed as erros on it.
-
From within PA on the extract popup, buttons are hidden, I must resize the window to get access to the OK/Cancel buttons. Tried on the default notebook screen (Macbook M1 Max 14") as well as on my external monitor (4k).Screenshot_2022-05-12_10-02-10.jpg
-
Just uncompressed a RAR file that has a folder within, PA created the folder but the files inside are not being saved into folder because directory separator is a BACKSLASH (Windows style) instead of SLASH (macOS).Screenshot_2022-05-12_09-59-08.jpg
-
Hello,
When clicking on the main ribbon for a new version I get a script error message.
Actual version: 21.00.15 - French version
OS: W10 21H2 19044.1645Best regards
WilfridPS: Keep building such good software
-
Ho già contattato il supporto con il modulo presente qui https://www.powerarchiver.com/it/contact/ da settimane ma non ho ricevuto riscontro e ora che ho aggiornato alla versione 21.00.15 ho notato che il problema persiste.
Quando clicco PDF Encrypt & Sign nel tab Crittografia appare la schemata riportata sotto come se mancassero le funzionalità.I’ve already contacted support with the form here https://www.powerarchiver.com/it/contact/ weeks ago but I haven’t received any feedback and now that I’ve updated to version 21.00.15 I’ve noticed that the problem persists.
When I click on PDF Encrypt & Sign in the Encryption tab the schematic below appears as if the functionality is missing.de9b4a2d-07e7-4323-a5a3-1b91e73dafc0-image.png
-
I have tried to burn a DVD with PowerArchiver 2022 Final, but it didn’t work because PA didn’t found the external DVD-Burner.
I have tried several burners from Sony, LG, Dell.
I have connected the burners with several USB-Ports but unfortunately without any success.
With other burning software, e. g. Nero, all burner worked perfect on each USB-Port.
The same problem occured with PA2018 and it was solved with an update, but I don’t remember the detailed software version.
Could you check the possibility of an bug, please?
Thank you for your support in advance! -
Quando creo un archivio zip con un altro programma ad esempio Winrar se apro il file con Winrar vi sono visualizzati anche le date originali di Accesso e Creazione.
Se ottimizzo quel file zip con la funzione Ottimizza archivio di PowerArchivier (o creo un nuovo archivio) il file risultate non ha più le date originali di Accesso e Creazione.
C’è una opzione per preservare questi dati? (Non l’ho trovata nelle impostazioni del programma e ho già abilitato le opzioni “salva info complete cartella” presente in “Profili di compressione”)
/
When I create a ZIP archive with another program such as Winrar, if I open the file with Winrar, the original Access and Creation dates are also displayed.
If I optimize that zipper file with the Optimize Archive function of PowerArchivier (or create a new archive) the resulting file no longer has the original Access and Creation dates.
Is there an option to preserve this data? (I haven’t found it in the program settings and I have already enabled the “save complete folder info” options in “Compression Profiles”) -
Upgraded from 2021 to 2022. Selecting ‘backup’ no scripts are showed. Only after editing and saving an existing script (explorer) it shows up in the PA backup folder.
So is the ‘backup’ icon to open the Backup screen only for creating ‘new’ ones. This means that you have to open ALL your old pbs files and to save them again… not user friendly.
No way to improve this ? Thank you.b606f084-9d96-461e-b93b-6ba9310a0f6c-image.png
-
PowerArchiver 2022 - Final Version - 21.00.15
Download:
https://powerarchiverdl.cachefly.net/2022/powarc210015.exeInformation about PowerArchiver 2022 - 21.00.15:
https://www.powerarchiver.com/2022/04/05/welcome-to-owerarchiver-2022/Thanks everyone for your assistance!
-
Hi,
I have a 31" 4K screen with 3840x2160 pixel, which PA is able to handle - except of a scaling other than 100%.
Access violation at address 0000000..DF47A4 in module 'powerarc.exe'. Schreiben of address 0000...00330.
When changing scaling for this screen to 125%, starting PA brings the following exception:After closing this message, PA seems to work fine.
PA version 21.00.15 (03/2022) 64bit (tested with Win 10 and after upgrade Win 11)Is there any chance to avoid this access violation or this message?
Thanks and regards,
Karsten -
Example file: http://www.kk5jy.net/smalldv-v1/Software/smalldv-1.0-beta-20180619a.txz
PA 21.00.13 doesn’t seem to see the contents unless I change the extension to .tar.xz
-
This are the steps :
in Options, select ‘configure clouds’ try now to quit this option…
No way, everything is locked up, the only way is using the task manager to quit PA.
(version 2021-20.10.02)
4205a809-353e-46f4-90ab-0bad062c2ccc-image.png -
When adding a file into an existing archive, in the add file window, if you click in the breadcrumb bar to navigate to a parent directory, the file list does not change. The directory Up button works.
Running x64 on Win 11
Image1.jpg
-
blue text over graphic: (graphic too low?)
PA210013About.png
(Running on 64 bit Windows 7) -
In PA 21.0.13, when I try to open an archive with the new Windows 11 context menu item “Open with PowerArchiver”, a PowerArchive instance is opened, but the archive is not loaded.
-
Hi,
the new Windows 11 context menu is not localized in PA 21.00.13.
While the classic context menu is localized, when it’s opened on a file on my desktop, it’s English, when it’s opened from a file on my C drive.@Mili Are there updated localization files available?
-
Hi,
I thought, I’ll give it a try and upgrade my PA 2018 Toolbox on my production machine to PA 2021 (20.10.03)
Sending registration codes in your order recovery doesn’t seem to work at the moment (I also checked my junk folder), online activation works Using registry to disable modules (for example HKLM\SOFTWARE\PowerArchiverInt\General\DisableBurning) doesn’t work as expected with modern ui. The module is visible, but I’ll get the trial nag, if I try to open it. It’s almost fine in classic and ribbon mode.7989017c-3cd2-4a99-a1f6-06ce62329dec-image.png
“DisableClouds” and “DisableExplorer” seem not to be respected at all, while the classic UI seems to respect the setting to disable any other unused module:
In settings I won’t be able to access the SmartAI settings and the settings for the internal editor if the FTP module is disabled
89843f23-ad89-45bf-92bc-406b1a11dfc9-image.pngcc40877b-d8d0-404c-b7f8-d5ae0a1ee445-image.png
Extract to dir;PA can't handle;dir's created anyway
-
try to extract an exe file through the context menu, when PA shows you the “extract to” option…sometimes it’s a file PA can’t handle.
also in those cases, if you chose to extract into a folder, that folder will be created.
wouldn’t it be better for it to be deleted, as the extraction process failed so you surely will delete the new dir manually?
-
What happens if some files were extracted and some were not? Or if folder is already present and file doesnt work? Prefferably, we wont delete files or folders that we dont have to since that is just asking for some bug to kreep in and delete your files.
thanks,
-
What happens if some files were extracted and some were not? Or if folder is already present and file doesnt work? Prefferably, we wont delete files or folders that we dont have to since that is just asking for some bug to kreep in and delete your files.
thanks,
you’re sort of right, spwolf…yes, that would lead to problems if the dir was already present.
then…maybe a popup win saying “would you like to delete the dir XXX (which was just created)”?
what do you think?
-
I have fixed so now if folder was created by PowerArchiver and no files were extracted due broked archive (or unsupported SFX file) will be removed by PoweArchiver automatically.
-
I have fixed so now if folder was created by PowerArchiver and no files were extracted due broked archive (or unsupported SFX file) will be removed by PoweArchiver automatically.
you rock, man! thank you so much! :D
-
Hi,
here is the latest TEST version, 9.00.34 with fix for this bug. Please let us know if it fixes the issue and if you notice anything else at all. You can install this version over the last one and restart your computer.
Download TEST version 9.00.34:
http://www.powerarchiver.com/test/powarc90034.exethank you!
-
let me corrupt an archive with WinHex…and I’ll check! :cool:
-
let me corrupt an archive with WinHex…and I’ll check! :cool:
Bug gone…but not completely!
Gone, because PA now tells me at once that the file’s corrupted, and does not create any new dir! :D
WELL DONE!“not completely” because I have to click TWICE on “OK” to close PA warning messages, it seems two identic messages come out.
FYI, the “double click bug” was there in .33 as well…check it! ;)
-
What double click bug - it wasn’t something mentioned in this thread?
-
no, I had not mentioned it anywhere before…yet it’s related to the bug I opened this thread for.
when a corrupted file fails to extract, no folders are created, ok, problem solved.
but PA tells you TWICE that the file’s corrupted and can’t be extracted, and you have to click TWICE on “ok” to get rid of the warning message…I think you can reproduce that behaviour quite easily…let me know!
-
Still cannot reproduce double dialog. Can you please tell me exact message being shown and maybe send me smallest file you are having this problem with - since double dialog does not show on any corrupted archive.
-
download the following file:
http://user1.7host.com/maiuebsait/mix/corrupted.7z
uncompress and see the avi I created.here’s the corrupted zip file I used:
http://user1.7host.com/maiuebsait/mix/CorruptedArchive_TestPurpose.zipso…could you reproduce it now?
pls let me know!the problem persists with v9.01.01 as well!
-
@ivan: did you read my last message? what do you think?
-
Thanks!
I will check it.
-
with the pre-release 9.01.02 PA is back to the situation I reported at the beginning of this thread:
-if you try to extract the corrupted file via “extract here”, you’ll see the extraction windows complete its task but then nothing will be extracted.
-if you choose “extract to \filename” the filename dir will be created, empty
-if you open the archive in PA it will show you the name of the file inside, and if you try to extract or open it from there, you’ll be given the “unexpected end of zip file”, and you’ll have to click twice on the message window to get rid of it.
so, I have to say 9.01.01 was better…ok, you had to click twice on the message win as well, but at least it found out the archive was corrupted, and the message would always pop up!
-
with the latest 9.02.00, nothing has changed with regards to my previous post… :(
@dev’s: is it going to be fixed any shortly? thanks!
-
with the pre-release 9.01.02 PA is back to the situation I reported at the beginning of this thread:
-if you try to extract the corrupted file via “extract here”, you’ll see the extraction windows complete its task but then nothing will be extracted.
-if you choose “extract to \filename” the filename dir will be created, empty
-if you open the archive in PA it will show you the name of the file inside, and if you try to extract or open it from there, you’ll be given the “unexpected end of zip file”, and you’ll have to click twice on the message window to get rid of it.
so, I have to say 9.01.01 was better…ok, you had to click twice on the message win as well, but at least it found out the archive was corrupted, and the message would always pop up!
9.10.06: bug still there, unfortunately :(
W*nR** handles that properly, prompting about the archive being corrupted. -
9.10.06: bug still there, unfortunately :(
W*nR** handles that properly, prompting about the archive being corrupted.9.11.01: still no improvements about this bug…
-
9.11.01: still no improvements about this bug…
9.20.04…bug has not been solved yet :(
@spwolf…it’s annoying! why is it taking it so long…and you seemed to had solved it with the old 9.00.34 (read the first posts here…)
-
I am sorry, we just want to make sure we give it a proper testing, which is what only 9.5 can do…
thank you and I promise 9.5 will fix it!
-
I am sorry, we just want to make sure we give it a proper testing, which is what only 9.5 can do…
thank you and I promise 9.5 will fix it!
ok, thank you! :)
-
I am sorry, we just want to make sure we give it a proper testing, which is what only 9.5 can do…
thank you and I promise 9.5 will fix it!
you are a man of your word! ;)
In 9.5b4 the problem is gone, now no empty dirs are created for corrupted archives anymore! :)
