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 errors
Is 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.
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.
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.
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
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.
Span attempt yields error: "Some files were in use and were skipped"
I tired to create a spanned archive of a 24GB .tib file, which was generated with ‘Acronis True Image Home 10’ backup software. PowerArchiver gives me the error, “Some files were in use and were skipped.”
I can’t imagine what app would be ‘using’ that file. Is there maybe something else about the file that PowerArchiver doesn’t like (i.e. size, type)? I want to break/split it into pieces to burn to DVD.
Thanks for your help.
Windows Vista Home Premium
try using 7zip - it might be that file is actually in use, and zip engine will not compress it in that case while 7zip will.
of course, use very low compression on 7z for speed.
Thanks for the reply! I took your advice and tried 7z. There must be something special about that filetype, because I get the same error when I try to archive any of them. But, at least I finally figured out how to get True Image, which generates the .tib files, to split them.
One thing to mention have you tried the 7zip file manager in case its pa that has the problems jusyt so we can check if it is pa and rule that out.
… have you tried the 7zip file manager …
What is that?
At this point I suspect something is happening between Vista and/or ‘Acronis True Image Home 10’ software and the file, because I am also having trouble burning the file to DVD. I get ‘file in use’ type errors.
did you try restarting your computer?
Yes, I did try after restarting the computer. PA gives me this message:
“Some files were in use and skipped.”
RJWaring last edited by
Acronis True Image Home 10 does keep a regular check in the background just like a virus checker!
Depending on your settings I think there might be something to disable background monitoring “have a look if you can” for example is the backup timed to run at the start or shutdown of every session? if thats the case Acronis may cause a conflict with accessing current archives.
Possible solution would be to delete your current settings for backing up and create a new backup profile to run on command? also does your back up amend current archives? or does it create new archives for the date and time?
Actually, I don’t have any backups scheduled. I like to do backups after shutting down Windows and using the Acronis rescue disc (or whatever it is called).
I don’t have backups scheduled either, but I still have the “Acronis Scheduler2 Service” service running. It’s possible that it might be interfering with your PA somehow.
I stopped the service “Acronis Scheduler2 Service”, and also the process tree “TrueImageMonitor.exe”. I tried again to split the file, but got the same message. ;-( I’ll ask the True Image people if there are other things I should stop as well. Thanks alot for your help!