-
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
-
PA Queue does not compress file optimally with same parameters if used in Queue mode.
Being able to save advanced option, and set a default profile and archive type for compression so I can save clicks.
The above two are majorly affecting my efficiency with archiving stuff with PA 20.10.03.
Can someone confirm if they are resolved with the 2022 RC1?
HELP! Shell integration completely broken.
-
Ok, first, the windows zipfldrs is completely broken, which is in no way the fault or even the responsibility of powerarchiver.
But I really NEED shell integration to unzip multiple ZIP files, doing them one at a time is not an option and neither is interacting with a GUI. I’m certainly capable of making the correct associations. However since the zipfldr method which powerarchiver attaches to is completely fscked, is it possible to use command line args instead? If so, what are the args? I have in mind something like the following(in the registry)….
powerarc.exe /x “%1”
The arg is obviously not “/x” since I tried it and it failed. What I want to achieve is the equivalent functionality of “Extract here” … which means unzip the files & close without any nags (as PA would do if zipfldrs worked correctly).
Please do not suggest fixing zipfldrs, it’s not possible without a complete OS re-installation (2 days work, many many apps), which this fix would help me avoid.
-
Welcome to PowerArchiver forum, Sigh!
first, PowerArchiver does not use Windows’ Zip Folders. PA creates it’s own association. you can repair it in Configuration > File Formats > Associate now.
Also you don’t need to reinstall windows to fix zip folders association. just right click any file > Send to >Compresses zipped folder… Then windows will ask you if you want to associate files. click Yes.
-
also, please make sure that you have enabled Shell extensions in Configuration > Shell extensions.
-
BTW: to extract multiple archives you can use the Multi Extract tool in PowerArchiver…
-
@NTFS:
also, please make sure that you have enabled Shell extensions in Configuration > Shell extensions.
Just to re-enforce this suggestion - if you choose the “Add as Submenu” option, then this should be available even when Zip files are NOT associated with PowerArchiver.
-
@NTFS:
Welcome to PowerArchiver forum, Sigh!
first, PowerArchiver does not use Windows’ Zip Folders. PA creates it’s own association. you can repair it in Configuration > File Formats > Associate now.
Also you don’t need to reinstall windows to fix zip folders association. just right click any file > Send to >Compresses zipped folder… Then windows will ask you if you want to associate files. click Yes.
1st, yes powerarcher uses the zipfldr REGISTRY ALIAISING LINK, not the zipfldr.dll.
2, I’m really fcuking pissed that you dumbed down my real problem with some simpleminded filetype association newbee moron idiocy.
The REGISTRY for the entire shell extension integration is FCUKED! I’m NOT asking you for help on that. It’s beyond you, waaaaaaaaaay beyond you.
What I want is the command line arguments for powerarc.exe …what are the command line switches? That’s all I want to know. NOTHING ELSE!!!
-
This post is deleted! -
@NTFS:
also, please make sure that you have enabled Shell extensions in Configuration > Shell extensions.
Yeah, IT’S FCUKING BROKEN IN THE FCUKING REGISTRY. Maybe you could suggest some magic “registry heal thyself” button.
I’ve run “regsvr32 zipfldr.dll” also run direct .reg scripts to restore all zipfldr functionality to its original condition, but to no avail, there is no shell integration on zipfldrs. When I install powerarchiver, it does all the right things, all the registry settings seem to be 100% correct, but guess what, STILL NO FCUKING SHELL INTEGRATION MENU. If it doesn’t work with zipfldr, just how the fcuk do you think it will work with powerachiver, which uses the same registry attachment technique as zipfldr.
If powerarchiver used actual command line arguments, then I could restore shell integration, but becuase powerarchiver attaches thru a registry key, {d03d3e68-0c44-3d45-b15f-bcfd8a8b4c7e} to be specific, shell itegration will not work.
So what are the command line args to powerarc.exe?
That’s all I want to know, nothing more, nothing less.
-
Just to re-enforce this suggestion - if you choose the “Add as Submenu” option, then this should be available even when Zip files are NOT associated with PowerArchiver.
Duuuuhhhh, NO FCUKING censoredcensoredcensoredcensored. But it does NOT.
That whole registry mechanism is totally fcuked. It’s beyond hope, totally not even a consideration at this point. I don’t want help with it, I don’t even want to mention it again.
All I want to know is the powerarc.exe command line switches. If I had those the rest would be a frickin cakewalk.
-
For command line use please try PowerArchiver Command Line:
http://www.powerarchiver.com/pacl/
It is free to registered PowerArchiver users.It contains all the documentation you need.
-
but here is what you want:
ShellExt Command line args for powerarc.exe:
Extract to…: -et
Extract here: -e
Add to archive…: -aZIP
Add to FileName.zip: -aZ -
Duuuuhhhh, NO FCUKING censoredcensoredcensoredcensored. But it does NOT.
That whole registry mechanism is totally fcuked. It’s beyond hope, totally not even a consideration at this point. I don’t want help with it, I don’t even want to mention it again.
All I want to know is the powerarc.exe command line switches. If I had those the rest would be a frickin cakewalk.
you should be a lot nicer to people trying to help you deal with your issue. NTFS has correctly answered to your issue (-e).
