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
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.
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.
PowerArchiver 2022 - Final Version - 21.00.15
Information about PowerArchiver 2022 - 21.00.15:
Thanks everyone for your assistance!
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,
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?
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.
“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
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?
Apparent glitch with some encryption via shell
I say “apparent,” 'cause perhaps I missed something. But I tried it three times . . . and had the same problem every time.
I have created a Profile called “ZIPX + PAE” – all with optimal settings. (I have a similar one for 7ZIP + PAE). The problem happens when I am tying to create a new PAE file using the former profile – in one cases.
Here’s what I found – all within the shell (highlight the files, then select PA and Compress To).
- the 7 zip/pae profile worked just fine – even if I renamed the file.
- the zipx worked fine if I did not rename the file.
- But if I tried to rename the file, it would not create the archive to be encrypted – it went straight to the encryption window . . . without having first created the archive.
I may just be missing something. But, as I said, I tried it thrice with the same result.
I did go back and recheck the definition of the profile. Everything looks to be in order.
hmmm, lets give it a check
Thanks. I am really not 100% sure. I may be overlooking something obvious. But it kept happening when it wasn’t happening with the parallel 7Z profile.
I appreciate it.
It happened ONLY when I renamed the file. I thought it might be a problem with the name (had a dash). But the 7Z profile worked.
Could you email me the .reg settings please?
Also, you’re changing the name in the full path field in the compress options menu or?
Also#2, is a PAE file created at the end or there’s no PAE file at all?
I tried it again. Every worked fine with the 7zip + PAE profile. But this time, I couldn’t even get the encryption window to open with the ZIPX +PAE profile. But these were different files, including different files types. That may have made a difference.
I attached a pic of the zipx profile in case I am missing something simple.
I am changing the name in the add window, which standardly opens first, and then - after the archive is created - the encryption windows (normally) opens. But not now with ZIPX +.
No PAE2 is created.
great, we’ll replicate and post the results. thanks!
I deleted the profile. Create a new one – exactly like the old.
It worked just fine.
So somehow that profile must have been corrupted, although the settings looked fine.
But maybe if you peek, you can figure out what.
Or prudence may demand ignoring it.
Attached is a comparison of the two:
The “new one” has “Use current folder as temp” (which is what I usually have set).
Could this have made the difference?
hmmm, i’ve tried using both ways and both work fine for me. But when I use your .reg settings, I get the issue you referred to.
I’ll be logging it in and do some further investigating to see what the culprit might be.
thanks very much for the details!
So a culprit lurking in the reg settings. The mystery deepens.
I went fishing in my config settings.
I discovered the cause of my problem reported a month ago (that you could not duplicate). Perhaps it is source of this problem as well.
Burning support was set to “autodetect.”
I changed it to SPTD, and the .iso window open exactly as it was supposed to – no 38 sec delay!
Maybe it is also causing this problem?
I have no idea how the setting got switched . . . it has always been SPTD. Maybe it was with one of the updates?
Actually, glad to know that I was not nuts claiming there was a 38 second delay in having the iso windows open!