-
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?
PABACKUP.EXE Crashes
-
Hello,
Lately I’ve been experiencing application crashes with with PABACKUP.EXE. Here is the Event information offered by the Windows Application Log (let me know if you need more details):
Faulting application name: PABACKUP.EXE, version: 12.0.24.1, time stamp: 0x2a425e19
Faulting module name: PABACKUP.EXE, version: 12.0.24.1, time stamp: 0x2a425e19
Exception code: 0xc0000005
Fault offset: 0x000041da
Faulting process id: 0xcd4
Faulting application start time: 0x01cc5fb1ffa1369e
Faulting application path: C:\Program Files (x86)\PowerArchiver\PABACKUP.EXE
Faulting module path: C:\Program Files (x86)\PowerArchiver\PABACKUP.EXE
Report Id: 3d59a85f-cba5-11e0-bbed-7071bce3eb99This started happening under version 11.71 and continued after I upgraded to version 12. I have even uninstalled version 12 and re-installed from scratch.
I’m running Windows 7 64-bit and I launch my PA backup jobs using Splinterware’s System Scheduler 4.17.
In System Scheduler I use the Sequence of Events scheduling type in order to launch multiple backup jobs sequentially (I switched to this method when the PA Queue feature proved too problematic with frequent failures).
Thanks in advance for any help with this.
-
You will most likely be asked by the devs if you have the same problem if you don’t use “Splinterware’s System Scheduler 4.17” So it would probably help them to know that.
-
Hi Joe,
I’ve installed splinterware system scheduler and scheduled a pbs script there to be run.
Once the selected time came up, the script ran and created my backup with no issues.Does this error occur for you with all pbs scripts or just one?
If you can, please send us a sample script which does not work for you along with a screenshot of the settings for that scheduled event/script in Splinterware System Scheduler.You can send it to support at conexware dot com
Thanks!
-
Hi Mili,
Thanks for your reply and thanks for your help.
This issue is becoming a real brain teaser as I am pouring over the Windows event log to find anything that could cause this crash.
Just like you, I can’t duplicate the crash at will. System Scheduler is not the culprit here, as it does exactly what it is supposed to do. As a matter of fact, it ran successfully at 2:30am this morning - no crash this time.
I am currently looking at the possibility of some sort of conflict with VSS. The VSS service stops due to idle timeout and perhaps that causes a problem when PABACKUP.EXE starts.
I was hoping the crash information provided through the event log might help you pinpoint some sort of problem area. If that is not the case then there is not much else you can do at this juncture.
I will keep plugging away at this and will provide updates here.
If you have any thoughts on the VSS angle please let me know.
Thanks!
-
VSS was not used with PA 2010 though, so it should be not influencing factor with the issue.
Did you try using different compression? What are other PBS settings, for instance are always new files created, or is old backup file updated?
-
is there another process running in the background when pa backup is used.
does differnt backup scrips work ok?
when did you create the backup script i mean what version of pa was the backup script made in.
-
I’m closing this thread. Thank you to all for your replies. :)
As it turns out the System Scheduler utility has failed to properly execute an automatic Windows login, so when PABACKUP is scheduled no user is logged in, causing PABACKUP to crash (perhaps not very elegant programming!).
Before I run all of my backup scripts, I schedule a series of housekeeping activities (closing applications, running CCleaner) followed by a system restart. System scheduler has a setting to automatically initiate a Windows auto logon and this works well in Windows XP, but has stopped working in Windows 7.
I’ve had to find a different way to initiate a forced Windows auto login (I’m not relying on System Scheduler for this any more). Problem solved.
Thanks again. :)