-
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.
Extraction problem
-
I am going to have to offer this post. However, I cannot send more information or do further testing right now. Sorry.
I know this will not make you happy. For that reason, I almost didn’t offer the post at all. Yet on the off chance this might help some other user . . .
I went back to 2010. I will try 2011 again after the full release is out and has gone through a couple of updates, perhaps late spring.
Here’s why. Using 2011, even for the past week, has gotten my home and work computers out of sync – and I just discovered it. It will take some effort to determine exactly what files were not updated.
I move files back and forth from home to work via archives, built by PBScripts.
I just discovered early this morning that 2011 was not extracting all the files as it should. But there was no error message warning me of the problem. It just didn’t extract them. So I was not keeping the files in sync as I want.
I know it wasn’t extracting pst files. I am fairly sure it wasn’t extracting at least some other files as well. But I am not certain.
Once I uninstalled and reinstalled 2010, everything was fine. All the files extracted as exactly as they should.
The plausible inference, is that 2011 has a glitch, or else that there is some obscure setting.
BTW, I did have UAC elevation checked (I believe it is checked by default).
Again, I just cannot do more right now other than offer this report.
If this is more hassle to you than it is worth, let me know and, in the same circumstances, I will keep silent.
My hope was that some other user might be able to see the problem as well, and help you find a solution.
-
can’t say I’ve encountered anything of this nature since installing it buddy…done quite a bit of compressing and extracting but from what I can see all is working fine on that level of testing…if I do have a similar issue I will post back here.
-
I do remember experiencing transfer issues with PA 2011 during Alpha testing. This was reported and how we had to resolve this was going through all the settings again and applying.
Now this resolved the issue for me, but not sure if its the same for you.
-
Here’s why. Using 2011, even for the past week, has gotten my home and work computers out of sync – and I just discovered it. It will take some effort to determine exactly what files were not updated.
I move files back and forth from home to work via archives, built by PBScripts.
I just discovered early this morning that 2011 was not extracting all the files as it should. But there was no error message warning me of the problem. It just didn’t extract them. So I was not keeping the files in sync as I want.
Can you send us an example archive?
Did you have both computers using PA2011 or?
Actual extraction engine should be the same as in 11.71 (with some updates that shouldnt have anything to do with extraction of files).
-
was it not compressing files properly or not extracting them? I assume you used PA 2011 backup via pbs for compressing and then PA 2011 for extracting?
or did you use PA 2010 backup for compression and then PA 2011 for extracting?
Also, what version of PA 2010?
thanks a lot!
-
@Sir:
I do remember experiencing transfer issues with PA 2011 during Alpha testing. This was reported and how we had to resolve this was going through all the settings again and applying.
Now this resolved the issue for me, but not sure if its the same for you.
what you had was old PBS not working in PA 2011 Backup… what he is reporting is that not all files are being compressed/extracted as they should.
It could be million things, hard to say right now… could be something in the zip engine (although they should be very similar), there could be that one of the pbs settings is not applied and hence files are not filtered properly… or maybe it is extraction engine? :-)
-
Unfortunately, without (at least) the PBS files socrates used; I don’t think there is much that can be tested/checked. The number of possible variations is daunting!
All we know is that the PBS files were used “to synchronise” between computers (Windows 7).
We can infer that the archive (unknown format) was created - maybe using some form of date/modification check, maybe not.
Then an extraction, again maybe checking/maybe not?
Unless someone else “stumbles” across the problem… -
due to Luxor’s post in another thread, we found an issue with extracting selected folders and fixed what we could reproduce and what luxor could reproduce.
please check with 12.00.38 RC2, get it via patchbeam….
thanks!
-
I had a free half hour, so I did a test.
The central problem appears to be the handling of .pst files. (I think there might have been other problems too. But with the help of Luxor, you may have solved them.)
The problem, I now see, is not only – or even primarily – extraction, but how I use 2011 to built the archive. If my transfer archive includes my .pst file AND that PST file was open when PA copied it, then that file will not successfully extract to the other computer.
However, if I rebuild that archive when Outlook is closed (so VSS isn’t required), it copies . . . and extracts . . . the PST file just fine.
That suggests that VSS within PA does not successfully handle PST files.
The problem appears to be PA’s use of VSS since I have successfully copied PST files with at least two different programs using VSS.
That’s my best guess at the moment.
No time for more tests for a week or three.
Sorry.
-
to make PST work with VSS, you have to enable always use: .pst VSS option… otherwise it will not work properly.
Using VSS is slow, so we dont want to have (in PowerArchiver), option that will “always” use VSS because we make assumption that a lot of people will use it without need… thats why the option is there.
-
to know that VSS has worked, you will get UAC prompt once VSS activates, that will elevate PA to Admin so UAC can be used.
-
I did have that option set (always use with .PST).
I did not get a pop up window for UAC elevation.
-
just did a backup on a 64bit machine, VSS enabled, Added outlook.pst to backup tracklist while outlook is open, clicked “Do Backup”, Uac appeared and clicked YES, in a few seconds compression started and all was fine.
Worked the same on a 32bit machine as well.Do the other programs you tried VSS with show UAC?
can you try another locked file to see if it works with PA?
