-
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?
[BUG] PA 11.60.22 triggers "Windows - No Disk" error on startup
-
PA 11.60.22 on Windows XP SP3
I have a floppy drive in my system. There is no disk in it and I have not used it in about a year.
When I launch PA via Windows Start menu (i.e. as opposed to double-clicking an archive), I get a “Windows - No Disk” message, because PA tries to access my floppy (A:) drive, when it should not be.
This bug did not exist in 11.60 RC4.
-
try using reset to defaults… does that help?
Do you have explorer view on? -
Haven’t used PA for a week or so (on a course). But started PA (60.20) today and I got same error (identical - even parameter string). Also after web update (60.23)
@spwolf:try using reset to defaults… does that help?
Do you have explorer view on?Default - PA restarts in Classic ?? But no error message.
Change to Modern View- Explorer with folders
- Start folder system default
Close PA
Start PA
Error appears again - the access LED on floppy Drive A: is activating
Note:
“Try again” just “loops” with error
“Continue” and PA works.
. -
probably change the startup location to documents/desktop and see what happens then.
then go into explorer view, click on my computer or C:\ and see when does the error show again (when is PA querying the A: drive).
-
probably change the startup location to documents/desktop and see what happens then.
Yes, choosing specific folder seems to avoid problem.
@spwolf:then go into explorer view, click on my computer or C:\ and see when does the error show again (when is PA querying the A: drive).
[Folder View]
Select “My Computer” - error message
… Continue
Select any folder on C:
Select “My Computer” - error messagerepeatable loop :p
-
Yes, choosing specific folder seems to avoid problem.
[Folder View]
Select “My Computer” - error message
… Continue
Select any folder on C:
Select “My Computer” - error messagerepeatable loop :p
so basically it is when clicking on my computer?
-
Yes - but don’t forget initial start as well as “my computer” in folder view.
-
I am using Explorer view
For me, the startup location is set to “Last open archive.”
But when I startup, “Desktop” is the folder that initially appears in the Explorer view folder drop-down, followed shortly by PA trying to access my A: drive and failing. Then I get the error message and when I click on “Continue,” it then finally goes to my D: drive, which is the actual “last open archive” folder.
So it’s the “Last open archive” folder option that’s not working as it should and instead appears to be needlessly scanning drives on it’s way to selecting the correct folder.
-
I am using Explorer view
For me, the startup location is set to “Last open archive.”
But when I startup, “Desktop” is the folder that initially appears in the Explorer view folder drop-down, followed shortly by PA trying to access my A: drive and failing. Then I get the error message and when I click on “Continue,” it then finally goes to my D: drive, which is the actual “last open archive” folder.
So it’s the “Last open archive” folder option that’s not working as it should and instead appears to be needlessly scanning drives on it’s way to selecting the correct folder.
it does not matter what is the option (last open archive, default, etc), but what folder it ends up opening… if that folder sees A:\ directly, it will try to read it to see if it has any files on it.
-
it does not matter what is the option (last open archive, default, etc), but what folder it ends up opening… if that folder sees A:\ directly, it will try to read it to see if it has any files on it.
I believe you’ve misunderstood my explanation.
POINT #1: The last open archive folder is D:. That is the last folder where I opened an archive. That is the folder explorer view should default to when I launch PA from the Start menu, given that the “Last open archive” option is set.
POINT #2: Even though, as stated in POINT #1, D:\ was the last open archive folder, when I launch PA, it initially opens the Desktop folder before going to D:, and it is in that process of starting with Desktop then going to D:\ that it scans A:\ drive. This should not happen. Go directly to D:\ drive and don’t try and access any other drive. This is what SHOULD happen but is NOT happening, and that is why I get this error.
-
can someone send us their PA registry, to support at conexware . com? HKCU\Software\PowerArchiver.
thanks
-
Registry file sent.
-
do you mind testing several versions to see which ones has it working properly? and we can go back to that… as we currently can not find any computer that we can reproduce it on…
-
Sure. Give me the links and I’ll give it a go.
-
Sure. Give me the links and I’ll give it a go.
we got it - well, reproduced it… sent bug reports to perspective companies… hopefully it will be fixed within a week or.
It has been like that for a while though, at least a month…
-
we got it - well, reproduced it… sent bug reports to perspective companies… hopefully it will be fixed within a week or.
Great. Thanks.
It has been like that for a while though, at least a month…
Seems about right. I know I skipped some builds, and I assumed the last PA release I installed, prior to the final, was RC4, because I have the setup file on my system, but I could be wrong considering that I did not encounter the bug until I installed the final build.
-
Should be fixed in 11.60.25 build:
http://bit.ly/4snT7Hcheck it out and let us know… thanks!
-
Start folder system default
Reset to this setting with 11.60.23 - error appears.
Upgrade to 11.60.25 - no more error message(s).So fixed (for me).
-
Partially fixed by 11.60.25:
1. PowerArchiver still accesses the A: drive. This slows down population of the explorer view, as the A: drive is waited unnecessarily waited on.
2. The error message is now gone.
Why not just go directly to the last open archive folder? Why start from Desktop and drill down, drive by drive?
