-
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.
-
Re: Explorer.exe Crash on right click
This appears to be happening again with the Power Archiver 2022 shell extensions.
When I have Use Explorer Shell Extensions enabled in Power Archiver Configuration and right-click on c:\Users\username\Start Menu, (hidden Junction file), File Explorer crashes.
I have version 21.00.15 (03/2022) 64-bit installed in Windows 10 Version 21H2 (Build 19044.1826).
-
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. -
In the latest version of PA, on W11 (latest build/SP) when you try to use the first level context menu - NOTHING HAPPENS (particularly when you do this from Downloads or Documents folders) - however I noticed that it DOES WORK when you use the context menu from the Desktop. Going to the second level context menu does work however.
-
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.
-
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 :)
CRC Error
-
I am coming up with a few CRC Errors in .bh archives. :(
Here: I put one inside this 7z……
attachment_t_1152_0_crc-error.7z -
After more testing, I have found that .bh files are correct until you add or delete any files from the archive. It is then that the CRC Error is created. The archive that I attached was initially too big to send. When I reduced its size by deleting all but one file in the archive, then the error was made.
Here’s where it really gets crazy:
Using the Archive Converter to change any archive type to .bh also creates a corrupt archive. (At least PA sees it as corrupt.) This corrupt archive is always larger than the .bh archive if it were created “new”. (“New” meaning: not Converted from another type, but created from the original files and folders.) Keep in mind that creating new .bh archives always results in a good archive.
Now, if I go back to the corrupt archive, convert it to .zip, .7zip, or .lzh, those archives test Okay!
I am perplexed! Can this be fixed before the final realease? :(
-
Probably PA didn’t update the CRC value after aemnding the archive? ;)
-
@Charles:
I am coming up with a few CRC Errors in .bh archives. :(
…
After more testing, I have found that .bh files are correct until you add or delete any files from the archive. It is then that the CRC Error is created.
…
Using the Archive Converter to change any archive type to .bh also creates a corrupt archive. (At least PA sees it as corrupt.)Your example does test as CRC error.
But I cannot reproduce any of these cases - for me each BH file created is testing OK.
After deleting files I tried both Closing and Renaming Archive.@Charles:
[Converted] archive is always larger than the .bh archive if it were created “new”.
This, however, I can confirm.
Compressing just 5 small wav files.Original as BH file - 1.48 KB (1,525 bytes)
Convert BH to Zip - 1.64 KB (1,686 bytes)Original as Zip file - 1.64 KB (1,686 bytes)
Convert Original Zip to BH - 1.51 KB (1,552 bytes) -
Okay Terry:
Here’s a good .zip archive for you to convert to .bh……
Every time I convert it and then use the test feature to check it I get a CRC Error.
If I convert the .bh back to .zip, the new zip tests just fine.
Try it! It happens every time for me…
attachment_p_5269_0_eddie-sweater-compliment.zip -
Will do
In the meantime - regarding filesize.
Folder containing 22 text files [1.22 MB (1,290,114 bytes)]
Compress to BH -> 376 KB (385,716 bytes)
Compress to TAR.Bz2 -> 310 KB (317,779 bytes)Convert Bz2 to BH -> 1.25 MB (1,310,720 bytes) :eek: :eek: :eek:
Thats larger than uncompressed !!
But it still tests OK. -
@Charles:
Okay Terry:
Here’s a good .zip archive for you to convert to .bh……
Every time I convert it and then use the test feature to check it I get a CRC Error.
If I convert the .bh back to .zip, the new zip tests just fine.
Try it! It happens every time for me…
Yes, confirmed with that zip :confused:
-
Have you caught this thread, Spwolf? :cool:
What do you think? :confused:
-
This may be only because you used Archive Converter with Maximum method. There was a bug and it will be fixed in BETA 4. In all other situations it should work fine - even with Archive Converter - Normal.
-
But Ivan……
When I convert to BH with Normal Mode and try to open the archive, it asks me for a password – and I never added one! :confused:
And don’t forget…
Good BH Archives are corrupted whenever you add or delete files. :eek:Thank you for your attention! :D
I will give it a strenuous testing when Beta 4 comes out! (I promise!) ;)
-
@Charles:
When I convert to BH with Normal Mode and try to open the archive, it asks me for a password – and I never added one! :confused:
Fixed (at least for me) in PA 9.5 beta 4
Edit: Sorry - conversion filesize should be in thread “Another BH Mystery”
http://www.powerarchiver.com/forums/showthread.php?t=1159
moved. -
@Charles:
Okay Terry:
Here’s a good .zip archive for you to convert to .bh {Eddie Sweater Compliment}
Every time I convert it and then use the test feature to check it I get a CRC Error.
…
When I convert to BH with Normal Mode and try to open the archive, it asks me for a password – and I never added one!I could reproduce both using the {Eddie Sweater Compliment} zip.
Now both fixed (for me) in 9.5 beta 4 (BH Maximum / BH Normal).
-
tested and fixed
