-
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?
SOLVED [BUG] UAC support broken in PowerArchiver 2018
-
Hi,
I’ve some problems with UAC in PowerArchiver 2018:- I’ve already reported problems for PA2017 and you fixed some problems.
- I’ve noticed again problems with UAC: The problematic archive is a 7zip. Opening it with PA2018 and directly clicking on extract, triggers an UAC prompt as expected. Selecting single files and trying to extract them to the same place (a subfolder of C:\Program Files) fails with an error (there are already older versions of the files in the same place to be overwritten).
- I’ve done further tests with other formats, via shell extension (Extract to…):
My test archives contain 1 file: test.txt
If the file does not already exist:
UAC prompt: 7z, pa, tar, lha
Access error: zip, rar, cab, bh
If the file already exists in the destination folder, no UAC prompt is triggered in any case. I confirm overwriting the files and it fails with an access error.
I’ve used PA 18.00.46 x64 on Windows 10 1709. - The x86 Shell extension behaves differently:
All but the rar archive triggers an UAC prompt if the file doesn’t exist in the destination folder; if I deny the UAC prompt, the shell extension crashes in most cases.
Are you going to fix this in PA2018 soon or should I revert to PA2016, again?
-
@BigMike said in [BUG] UAC support broken in PowerArchiver 2018:
By the way, silently failing if the UAC prompt is denied, is a real problem, as it’s possible to configure UAC settings to deny an UAC request automatically:
GPO setting: User Account Control: Behavior of the elevation prompt for standard users
If you set it to “No Prompt”, UAC requests will be automatically blocked. And with the actual behavior a user would get no feedback, that the operation failed!Please check with .04:
http://dl.powerarchiver.com/2018/powarc180104.exeThere should be an error, but lets make sure it does not appear at wrong time.
As to the changes, it does nothing to actual extraction code/engine, it checks if it can write file, and if not, it starts compression/extraction from another/elevated version of powerarc.exe… where before it elevated specific existing thread, which did not work reliably with engines that use multiple threads.
Thanks!
-
thanks for the details on this one @BigMike
confirmed it and logged it in -
Can you estimate when the UAC problems will be fixed?
I like the new features of PA2018 very much, but I’m using the shell extension pretty often, so this is very disturbing. -
@bigmike said in [BUG] UAC support broken in PowerArchiver 2018:
Can you estimate when the UAC problems will be fixed?
I like the new features of PA2018 very much, but I’m using the shell extension pretty often, so this is very disturbing.I will raise this again at next build discussions… for upcoming week we have PACL, PAOP builds first and then we will look at PA again. Thanks!
-
Thank you :-)
-
@spwolf Any news here?
-
@BigMike said in [BUG] UAC support broken in PowerArchiver 2018:
@spwolf Any news here?
not yet… we have new building coming soon, let see if we can squeeze it in. For 2019 we will likely rewrite shell from scratch, we will see. Thanks for keeping track of it!
-
Keeping track of it is easy - I’m regularly reminded of it, when I forget about the bug and try to use the shell extension for a protected folder. :crying_face:
But thank you for the information. -
Sorry, but in favor of a working context menu, I’m switching back to PowerArchiver 2016, giving up the full x64 version, explorer mode and PA format.
-
@BigMike said in [BUG] UAC support broken in PowerArchiver 2018:
Sorry, but in favor of a working context menu, I’m switching back to PowerArchiver 2016, giving up the full x64 version, explorer mode and PA format.
actually we are just working on it… lets see what we can do, problem/difference is that in 2017 we have been using more threads for faster speed and that messes up UAC elevation in some cases.
-
I’ll happily test the new version and get all the other features back.
-
@BigMike said in [BUG] UAC support broken in PowerArchiver 2018:
I’ll happily test the new version and get all the other features back.
as long as we can improve it… I will let you know, @ivan already spent few days on it alone. Thanks!
-
@BigMike Check out his release:
http://dl.powerarchiver.com/2018/powarc180103.exeIt elevates complete PowerArchiver instead of the thread, since 7z/PA formats use multiple threads. This might create some issues so test it out both in main and shell please!
thanks!
-
First: Thank you for your efforts :-)
UAC handling seems to work fine, but I encountered some problems, while I prepared my test:32bit: Shell extension:
- Adding two files to a new zip archive; user has no write access to the destination folder; UAC dialog was shown and confirmed; but the rights were not sufficient afterwards (Windows 10 Controlled Folder access blocked it): Instead of giving an error, PowerArchiver launched one process after another to create the archive; Not tested in x64 as my test Windows is to old (No Controlled Folder access)
32bit: Application:
- Convert archive PA -> Other: TAR; Exception TList<System.Classes.TComponent> in module POWERARC.EXE at 000B94E4; This works in x64
64bit: Application:
- Convert archive PA -> Other: RAR; Conversion is done, but a message is displayed, that some archives couldn’t be converted (RAR executable 5.50 x64); Not tested on x86 since no RAR executable there…
Test scenario:
Test archives containing two files, try to extract to a folder, which is read only for users, administrators have full access. Passed means: UAC prompt confirmed --> asked to overwrite files --> no error displayed
Actually, there seems to be no error if I deny UAC promptShell Extension x64 Passed: 7z bh cab lzh pa rar tar.gz zip zpaq
Application x64 Passed: 7z bh cab lzh pa rar tar.gz zip zpaq
Shell Extension x86 Passed: 7z bh cab lzh pa rar tar.gz zip zpaq
Application x86 Passed: 7z bh cab lzh pa rar tar.gz zip zpaqFailed: None
Is this version reasonable stable to be used on a production machine? Actually, from your description, it seems you changed a lot in the extraction processes.
-
By the way, silently failing if the UAC prompt is denied, is a real problem, as it’s possible to configure UAC settings to deny an UAC request automatically:
GPO setting: User Account Control: Behavior of the elevation prompt for standard users
If you set it to “No Prompt”, UAC requests will be automatically blocked. And with the actual behavior a user would get no feedback, that the operation failed! -
@BigMike said in [BUG] UAC support broken in PowerArchiver 2018:
By the way, silently failing if the UAC prompt is denied, is a real problem, as it’s possible to configure UAC settings to deny an UAC request automatically:
GPO setting: User Account Control: Behavior of the elevation prompt for standard users
If you set it to “No Prompt”, UAC requests will be automatically blocked. And with the actual behavior a user would get no feedback, that the operation failed!Please check with .04:
http://dl.powerarchiver.com/2018/powarc180104.exeThere should be an error, but lets make sure it does not appear at wrong time.
As to the changes, it does nothing to actual extraction code/engine, it checks if it can write file, and if not, it starts compression/extraction from another/elevated version of powerarc.exe… where before it elevated specific existing thread, which did not work reliably with engines that use multiple threads.
Thanks!
-
Now I get error messages as expected.
-
@BigMike said in [BUG] UAC support broken in PowerArchiver 2018:
Now I get error messages as expected.
thanks for your help Michael!