-
PA2023 Win10, (same problem with older releases but never reported)
PA Soft is installed on partition D. (exclusive for installed progs)
Then I created on my partition G: the folders as configured in PA Settings ‘Folders’.0fcf1b09-1b91-4b74-b250-f8cf908a3348-Ashampoo_Snap_maandag 20 maart 2023_11h54m34s.png
Screenshot 2023-03-20 121152.png
The problem : Any activity on PA is saved in these folders…
PA ignores them and still use the default settings. Whats wrong ? Regards, Pirrbe -
I am still using Powerarchiver 2022 and it does not show pdf markups in the preview. Is there a setting to get version 2022 to show pdf markups in the preview? If not, does this work in version 2023?
-
The question that I have about PA archives is what happens if say ConeXware, as a company, dies in the future? What happens to any PA files that are created today? Can these files be decompressed with a copy of a PowerArchiver that can no longer phone home to the mothership thus can’t be registered or activated?
I mean, I can understand that new PA files wouldn’t be able to be created if the program isn’t registered but what about an un-registered copy because well, the question that I posed above?
It’s questions like this that make me not want to store anything really valuable in PA files out of fear that I, at some point in the future, might lose access to said data inside those files. OK, 7ZIP might not be able to compress as heavily as PA but at least it’s open source and any 7ZIP files will still be able to be read and decompressed ten, twenty, or fifty years from now.
-
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.
-
Is this a known problem? Is there a fix coming? This is a primary reason I buy PA.
I’ve tried both methods I know to extract multiple zips at the same time. 1) Multi Extract feature in the GUI. 2) In Windows File Explorer, select multiple zips, right click, use PA context menu to Extract or Extract To…
Is there a setting I missed? Or maybe it really is processing in parallel, but I can’t detect it? Nothing tells me in the Processes in Task Manager that multiple PA extracts are running. And my CPU, memory and disk resources do not look like a lot of extracts are running.
I’m using PA 2022 Standard version 21.00.18 on Windows 11 Pro version 10.0.22621 Build 22621.
-
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.
-
Is the version Preview 2023 also considered to be tested by the testteam ? In the past we got messages in the forum for testing out version x.x, to be downloaded by fastring, or I missed the one for 2023. (I discovered 2023 on the official web…)
CU, Pirrbe.
-
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 -
Hi there, been a user since 13 years now and in past whenever I had a problem or question I could email, however since 3 weeks it seems like everybody is dead?
Anyway, as kind of a last resort, I post this email a 4th time but in this forum instead now, in the hope for help:
"This is the 3rd time I am emailing you guys as I am missing a working code for the preview of Power Archiver 2023Can you please help me? I am a 13 years lasting customer of yours, and I am shocked thatr for whatever reason my support tickets are ignored now, why?
thanks in advance!
All the best!
Joerg" -
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. -
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.
Two new bugs to report.
-
When renaming a file in a large archive, if you press ‘enter’ twice, or click ‘ok’ once and then click it again, it will generate an error and sort of crash. Its like it somehow has already started the rename process, yet the controls let you try and start it again, and then it crashes. I say sort of, because the program stays open and the archive stays open, but you get an error message, and the listing of the files in the archive disappears from onscreen. I also say ‘large’ archive, as you only get time to try and click twice if you are dealing with a large archive. If it is a smaller one then the process completes and removes the window before you would have a chance to click a second time (although on slower computers this would probably be just as big a problem on the smaller files). I found this out because I had pressed ‘enter’ and then when it took a bit with the window still sitting there, I thought I must have hit ‘shift’ by accident or that maybe ‘enter’ was not accepted, so I then clicked the ‘Ok’ button, and was greeted with the bug. I then tried doing a similar rename, but just clicking the “Ok” button twice, and it does the same thing.
The second bug is concerning password entry. If you drag and drop a file onto a open copy of Power Archiver you will get the “Drag and Drop” window. This particular ‘add’ window seems to have a bug in the password entry validation scheme. If you select any of the encryption methods, and then enter a password, but then re-enter it in the second dialog box incorrectly, it goes away without warning you in with a dialog that the passwords don’t match. I found this out because I was trying to add a file to an archive with password protection and accidentally typed the password wrong in the re-type window, and then clicked to add the file to the archive, whereupon I got the warning that I had selected an encryption option yet had not entered a password, as it had correctly discarded the mismatching passwords, but had not warned me. I have tried other methods of invoking the ‘add’ window, and it seems that only the ‘drag and drop’ version of the ‘add’ window has this bug concerning entering non-matching passwords while trying to apply encryption.
-
thanks - in the future, please report bugs in separate threads, and name the thread accordingly so we can easily indentify which is which…
thanks!
-
Sorry about posting both in one thread, I didn’t realize that it would be a problem. If these should be in different threads though, you will have to split them - as I don’t seem to be able to delete or rename a thread I have started. Also, do give feedback once you have examined/fixed the bug. Its nice to be able to track the progress of things and its interesting to find out what the underlying issues were in the first place.
-
NP, just for the future…
-
thanks!
The issues should be fixed in 10.1.
-
Please check prerelease version 10.1 B1:
http://www.powerarchiver.com/test/alpha100/powarc1010b1.exeAnd let us know if this fixes your issue.
thank you!
-
Well, I can happily report that both bugs are fixed in that latest build that you left a link to. Sorry for taking so long to notice your post! Anyhow, both bugs are properly squashed, and that is good! However, now I have noticed something else odd about the rename dialog. It now correctly disables input once you have begun a rename operation, BUT if you are simply changing one character of the existing name, the file won’t get renamed. If I were to try and rename a file called “beta1.exe” to “beta2.exe” it would not rename it. But if I changed more than one character, such as renaming it to “bEta2.exe” then it would work. Anyhow, thanks for fixing the first two bugs, and good luck squashing this last annoyance.
-
Thanks!
The issue should be fixed in Beta 2.
-
This should be fixed in latest version:
http://www.powerarchiver.com/test/release10/powarc1010.exePlease let us know…
thanks!
