-
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.
Back up full of errors again if tested but not if extracted.
-
Backup full of errors again. :(
Just ran my backup in PA 11.50.37 (Beta 2)
At first I though it could be back to where we were in This Thread maybe even worse this time.
After I ran my backup I tested it and it did not even ask for my password, off it went and at the end I got the message:- Warning: 2287 Error(s) found in the archive: My Backup-27-03-2009.zip
So I thought oh no here we go again.
But no. If I extract the archive I get asked for my password as usual and it extracts fine.
So I guess somebody somewhere has broke something. :D
Luxor
-
what happens when you run it next time?
-
and what do the errors say?
-
Same next time I run it.
and what do the errors say?
All it says is –> CRC ERROR
And at the end.
Warning: 2287 Error(s) found in the archive: My Backup-27-03-2009.zip
-
create new name for the backup and try it and then try it again, see what happens then please…
-
Ok spywolf.
Firstly I have tried with some of the backup archives I have created over the past month. Same error every time, so it’s not just newly ceated ones.
Created new name tried again and again, same error.
Created a new backup, same error.
Created another one with just one folder from My Docs, same error.Changed my backup type to 7zip and it works fine.
Asks for my password, tests the archive and no errors. Like my usual zip archives it extracts fine too.So it seems to be a problem with zip archives only as far as I can tell.
Luxor
-
send us your pbs, it will explain few things.
You are testing archive in backup? What happens if you test the same archive inside PA later on?
-
send us your pbs, it will explain few things.
I have created a new one specially for you, very small just a few files in 1 folder. Same settings as my normal backup. Nothing private to worry about.
I will attach it here for quickness if that’s Ok.You are testing archive in backup?
No. Just testing the archive itself. Opening it up in PA and clicking on test.
-
eh, you should have said you were testing the file :-).
It seemed as if it was happening in backup, not actual PA. -
eh, you should have said you were testing the file :-).
Thought I did.
@Luxor:After I ran my backup I tested it and it did not even ask for my password, off it went and at the end I got the message:- Warning: 2287 Error(s) found in the archive: My Backup-27-03-2009.zip
Sorry for the misunderstanding but I thought it was clear in my explanation.
Luxor
Windows 10 Home 64-bit
Intel Core i7 6700HQ @ 2.60GHz
12.0GB Dual-Channel DDR3 @ 798MHz -
Just noticed if I browse to the file in explorer and use shell extension Test. Then that is fine.
Password box appears and it runs with no error. -
basically no pass is asked for testing, hence the errors… if you open single file, password will be saved for the session and it will work fine.
-
Ok now you’ve lost me.
For years now I have been running my backup script. Then opened the resulting archive in PA then hit the test button and always had to put in my password. The test runs and I get the report.
If I understand you correctly, I now having to open my archive then open a single file, then put in my password to the view the file and only then I can test the whole archive. :confused:
To do that rather than just with one click (the way I have always done it) seems a bit long winded to me.
Windows 10 Home 64-bit
Intel Core i7 6700HQ @ 2.60GHz
12.0GB Dual-Channel DDR3 @ 798MHz -
Ok now you’ve lost me.
For years now I have been running my backup script. Then opened the resulting archive in PA then hit the test button and always had to put in my password. The test runs and I get the report.
If I understand you correctly, I now having to open my archive then open a single file, then put in my password to the view the file and only then I can test the whole archive. :confused:
To do that rather than just with one click (the way I have always done it) seems a bit long winded to me.
its a bug, not an feature :-).
archive itself is fine though, which is the important part.
thanks!
-
-
Please check beta 3 via web update or download page and let us know if this issue has been fixed… thank you!
-
Fixed in beta 3
