-
PA 2023 22.00.08
Long time no seeing. So I start up the new year with a first problem : the virtual driver cannot be installed. Reason : it is missing in the Fast Ring PatchBeam Update Service…
Virtual driver PA 2023-01-28 152607.png
It seems a standard problem with new releases :-)
Can I have a link or can it be fixed. Thank you. CU later -
When the function for testing archives is invoked via the shell context menu (PowerArchiver > Test) then all the files in the archive get extracted to the current folder.
The test dialog reports as many errors as there are files in the archive but it fails to give any hint as to which files are supposed to be erroneous or what the nature of the problem might be. Comparing the extracted files to the originals shows no differences at all.
The .7z in question was produced with maximised compression settings in 7zip (taking forever but resulting in smaller archives than .7z produced by PowerArchiver with maximised settings). Therefore I wanted to see whether PowerArchiver can at least test .7z that it produced itself. Hence I had PowerArchiver convert a .pa with the same contents to .7z. There weren’t any errors reported but the resulting .7z contained fewer than half of the files contained in the .pa (137 of 366), so I scratched that test.
Performance is abysmal when testing via the context menu (e.g. almost 2 minutes for testing a .7z that 7zip tests in 4 seconds), but that is most likely due to the fact that the extracted files are written to disk. Testing the same .7z in the PowerArchiver GUI takes only 8 seconds but causes the mysterious appearance of a UAC dialog, as reported elsewhere.
The testing function is vital because PowerArchiver has a history of producing archives that it cannot unpack without errors or that do not conform to the respective file format standards (e.g. ZIP) so that other programs report them as erroneous.
The point of creating archives is that the files in them will most likely have to be extracted at some point. If the extraction cannot be guaranteed to produce correct results then the whole program is absolutely pointless. Actually, worse than pointless - it causes data loss and hence damage.
-
In PowerArchiver 2023 22.00.06 configuration, the option labelled “Start PowerArchiver 2023 Starter when my computer starts” seems to be redundant.
I am only allowed to change this option when PA Starter is disabled, and then it seems to be ignored.
When I enable PA Starter this option is forced to the enabled state.
I think it’d be good to remove “Start PowerArchiver 2023 Starter when my computer starts” completely. I’ve always found it confusing having both options.
Added later: However i don’t particularly want to use queue but I do like having the PAStarter icon in my tray area.
-
W10 Pro 22H2 - 64 -bit
PA 22.00.06 (PA 2023)
It has been the case with previous versions of PowerArchiver, but I had hoped that the latest might behave differently. Not so, I’m afraid.
I have, for various obscure reasons, created a few .pa archives, mainly in the hope that they will save me some more space. From time to time, I use the “Test” option to check that important archives are OK and uncorrupted.
With every .pa archive I’ve tested, the process runs through OK but then reports that there are errors. This is always the number of files in the archive e.g. if 11 files, then 11 errors reported.
In the .pa, I can:-
preview the files (usually PDF) extract some or all files and look at or use them convert the .pa to a .zip or .zipx archive, which then works fine and tests without errorsIs it the case that the Test routine isn’t designed for .pa archives, or is there another reason? Although the .pa seems to function properly, despite the test reporting errors, I would like to be sure that every .pa is OK and not “broken”.
Some of the .pas are quite old and produced with earlier PA versions (they are truly “archives”). If I extract all the files in the old .pa, create a new, fresh .pa and add back the files to that, then test the new, no errors (at least in the .pa I’ve tried this on) are reported. This would suggest a mismatch between old .pas and newer versions of PA itself.
-
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files. -
Clipboard02.jpg
See the, supposedly, blank space where the green box is? It’s like that in Modern Light theme too. I can toggle it, but it’s missing text or shouldn’t be there I guess?
Thanks :)
-
Dear @Alpha-Testers and all of our users,
time has come for testing of PowerArchiver and PACL for macOS.
Please let us know here if you have Mac and can test latest builds.Features implemented:
PowerArchiver 2020 - tabbing, opening, extracting, adding, testing, favorite folders, support for multiple languages, opening via Finder, explorer mode, installer.
PACL 10 - support for most formats and features in Windows version.Upcoming: Tools such as archive converter, batch zip, multi-extract.
To start testing, please sign up here in this thread, and we will send you latest build.
thank you!
Ashampoo_Snap_Wednesday, November 20, 2019_12h54m56s_008_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m05s_009_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m14s_010_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m30s_011_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m39s_012_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m49s_013_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h56m00s_014_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h54m43s_007_.png
76e97ab9-8d75-4175-9ce8-446500031f38-image.png
-
For some reason, the PowerArchiver functions in the Windows 11 context menu no longer work after the last Windows Update. Only the functions in the classic context menu function as they should.
I’ve tried uninstalling PowerArchiver and using RevoUninstaller to remove all bits and pieces that were left behind and did a clean install of PowerArchiver, it didn’t fix the issue. Other items in the Windows 11 context menu work.
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!
