-
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 -
-
-
-
-
-
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?
UNSOLVED Cloud Folders as Upload Target Folders-not working?
-
PA 2018 - 18.00.32 Win7
This seems to be a continuation of a problem I experienced in PA 2017.
I have OneDrive, Dropbox and Googledrive clouds. In each of the clouds, there are a number of subfolders; for example <Googledrive>/TAX, <Googledrive>/BILLS and so forth.
When I run a backup via a .pbs script, I want the archive to be written into the cloud subfolder I’ve specified when creating the script (see screenshot).
In this case, I have defined my Google cloud target as “TAX”, but whatever I do, the archive is always uploaded into the root folder of the cloud drive, so I have the folders TAX, BILLS and so forth listed in My Drive, with the uploaded archive as a solitary file in the root folder.
I have tried defining the cloud folder TAX with forward slashes, backslashes, on it’s own and several other ways, but it makes no difference; the archive always ends up outside its targeted folder.
Of course, I can get around this by getting the pbs script to write the archives into the local cloud My Computer folders; in this case my main My Documents Archives folder plus the 2 additional cloud upload folders e.g. C:\Users\Peter\Google Drive\My Stuff . I then do an upload to cloud via the Google, Onedrive or other upload utility, which sweeps up any other files I’ve updated in the upload source folders as well as my PA archive. The PA archive will then arrive in the correct cloud target folder.
It would be nice if the pbs script would upload the archive direct into the named cloud folder, as I need the upload automated somehow.
If I open the archive locally, and then use File>Clouds>Upload to Clouds >Googledrive and then select the TAX folder interactively, it works fine.
-
I created a Test folder in dropbox and then configured in PA the Destination Directory as this :
(only the name of the folder without slashes)I runned the backup script and the ‘zip’ file is posted directly in my dropbox Test folder.
When you want to create a subfolder in the folder do not use ‘spaces’.
Underscores work !
I hope this solves your problem. -
Thanks for the responses.
I had tried using the folder name without slashes, for Googledrive. It still piles up several copies of the uploaded archive in the root folder. I presume that it doesn’t overwrite them as they have the same name and size, but different dates and times.
I’ve tried the same thing in Dropbox, but all I get is a “Not Responding” message. However, if I use the desktop Dropbox uploader, the file is successfully uploaded from my local \User\Dropbox folder.
Using OneDrive, it seems to start working but exits within seconds without uploading anything to anywhere in the OD cloud. Again, the desktop OD uploader works fine.
I have deleted the three Clouds in PA, cleared credentials and set them up anew, but this doesn’t make any difference.
So, to summarise:-
Google - uploads, but only to root of cloud folders
Dropbox - errors out
OneDrive - runs, exits, does nothingI have no idea why this should be, but I’ll try odd things like running PA with Admin privileges to see if that alters anything. However, I suspect that a direct upload to clouds from PA isn’t going to work for me, for reasons I cannot fathom.
I should say that although I haven’t tried all three (just ODrive), I can upload the file interactively from PA archive open to cloud upload. It’s just running these via pbs which causes problems. I have looked at the pbs for GoogleDrive and it has my target cloud folder correctly given there.
-
@pa_fan hereby my actual status :-(
dropbox : works perfect and .pbs scripts UL files to defined folders
google : uploads, only to root
ondrive : uploads, only to root
what the hell… -
thanks for the input all!
We’ll check this out and see what’s going to figure how to improve it. Any further details are welcome.
Thanks!
-
@mili Google’s direct sync folder works perfect to overcome the root filing problem. It’s a plan B but finally I have my PA backups in the google cloud, where I want them :-).
For onedrive : microsoft helpdesk referred me to PA helpdesk to solve the root cloud problem, not their problem as a third part is involved…