-
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 -
-
-
-
-
-
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?
-
I’m running W10 Pro on an HP i-7 machine with now 32gb of RAM. The system drive is an SSD.
In the course of sorting out some inconsistencies in a couple of my .pbs jobs, I’ve been paying close attention to the system CPU resource and power consumption of PA Starter, as shown by the various resource management tools. I’ve also been trying to identify why my system seems rather sluggish despite some extensive tuning for speed etc.
When I have enabled Starter as a start-up programme, to use the PA Queue facility, I see that Starter consistently uses between 10-13% of CPU, with High Power consumption indicated. It runs, consuming this resource, irrespective of what may be happening with PA and any pbs script jobs.
I can understand a need to use a good chunk of CPU when Starter is actually handling PA jobs, but it shouldn’t sit and consume this amount when it really isn’t doing anything but wait for a job to start and for which it is needed.
Perhaps I’ve missed a way of lessening Starter’s impact, but in the meantime I’ve adjusted my set-up to running PA without it.
Suggestions, please.
PA RC1 Patchbeam
-
Patchbeam crashes when run under WinXP
“Access Violation at address 0046B870 in module PATCHBEAM.EXE. Read of address 0000001C”.
Also, there is an empty square after each column name.
I cannot change skins or toolbars. I don’t mean to be funny, but is Win XP supported? I have, like many, ‘fixed’ my XP to continue to get the fixes. It is just an install I use for fun.
Regards
DrT
-
should be, I will check it out and let you know whats happening.
-
I have some further info that should help. If I install RC1 on top of the last v13 (which is uninstalled automatically as far as I can see) I cannot change the toolbars or icons - this time this was on win 7 x64. The icons always remain the modern blue-line only look. If I select classic toobar, the toolbar vanishes. None of these issues happened when I installed the 16.00.40 version on top of v13 and then upgraded to v16 RC1. Naturally, happy to supply any info you want so ask away.
DrT
-
I have some further info that should help. If I install RC1 on top of the last v13 (which is uninstalled automatically as far as I can see) I cannot change the toolbars or icons - this time this was on win 7 x64. The icons always remain the modern blue-line only look. If I select classic toobar, the toolbar vanishes. None of these issues happened when I installed the 16.00.40 version on top of v13 and then upgraded to v16 RC1. Naturally, happy to supply any info you want so ask away.
DrT
that makes sense, probably update over v13… since it uninstalls it but it keeps the setting.
We will check it out. Sucks that my test lab’s 8 core keeps going dead in the past 2 weeks, just when it is needed the most. Oh well, core-m is doing great replacing it, who would have thought.
-
Please check out the different results depending on which v of 2016 was used to upgrade.
These days, I tend to rely on installers to tell me if settings or an uninstall is needed.
I have no problem in removing the ‘old’ settings to see if that fixes the issue. Juts let me know what you want as always.
DrT
-
can you tell me what settings you had in 2013? Default 2013 to 2016 works fine. Did you have classic or modern toolbar?
-
I honestly cannot tell you other than to say that all instances of PA were identically configured. The only common denominator that I can tell is the version of PA 2016 used to upgrade.
Would it be helpful if I were to send you the current settings of the setups of PA that are okay and “broken”?
DrT
-
I honestly cannot tell you other than to say that all instances of PA were identically configured. The only common denominator that I can tell is the version of PA 2016 used to upgrade.
Would it be helpful if I were to send you the current settings of the setups of PA that are okay and “broken”?
DrT
broken one would help, cab and email please, thanks!
-
Done. Sent to ‘support@’.
DrT
-
Done. Sent to ‘support@’.
DrT
Cool, I will check it out now, thanks for sending it.
Just to confirm - upgrade process in Windows Installer will not delete your previous settings, it is not supposed to.
Sometimes when we change important parts of PA, there could be old setting that clashes with new PA. We test this usually so for instance default values will always work fine but it is up to us to make sure it works properly, there is not automated way.
In this case with PA 2016, toolbar component is completely new, so it has everything different compared to old one and we manually adjusted settings to match.