-
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.
-
-
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).
-
-
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.
UNSOLVED PA 19.00.43...47 stops me moving .tar.xz, .tar.gz, .7z and .iso files.
-
PA 19.00.43 stops me moving .tar.xz files.
They have to stay in my download directory (or wherever they are) until I uninstall PA!
(I’m running Windows 7 x64)
Later: Found out that if I wait some minutes (around 5 mins I think) after opening source folder PA eventually releases the file and it can be moved.
Later still: Seems to have stopped doing it now?!
Next day: It’s doing it again! -
Still happening in .44
-
Getting same problem with .7z files too.
-
Tested by creating a tar.xz archive in the Downloads directory and was able to successfully move it to another folder.
Should we test another way so that we may reproduce this? Please let us know.
Also please send over your settings to support, we’ll import those as well as there maybe a setting that causes it.Thanks for letting us know.
-
@Mili Maybe it’s Windows 7 and/or 64 bit specific. I think refreshing the explorer window that shows the file makes it do it (again?). It may be Windows 7 and/or 64 bit specific.
Same problem present with .tar.gz as well. -
@Mili Are you still unable to reproduce this?
-
Same problem wirh .iso files too.
-
Any news about fixing this? It can be really annoying.
-
Hey, sorry for the delay.
No luck reproducing so far, gonna give it another go and report back -
Funny… Isn’t the virus scanner locking the file? I tried everything to reproduce, but no luck. Any change you can use a locking tool to see what process is locking the file?
-
@guido said in PA 19.00.43...47 stops me moving .tar.xz, .tar.gz, .7z and .iso files.:
Funny… Isn’t the virus scanner locking the file? I tried everything to reproduce, but no luck. Any change you can use a locking tool to see what process is locking the file?
It says they’re locked by SearchProtocolHost.exe.
-
@Brian-Gregory SearchProtocolHost.exe is part of windows and generates indexes for faster search. As a test, you could disable the index for the downloads folder. Turn of the checkmark below and try again.
-
I’m using Windows 7.
Well I changed some settings to tell it not to try and index the conetnts of the file types I was having a problem with and re-make the index and so far so good.
I was waiting for the complete index to be rebuilt but it’s taking days!
But it looks like that’s cured the problem.
Thank you.
-
Well that’s just typical.
As soon as I say it seems to be fixed it does it again.But this this time ProcessExplorer says no process has locked the file!
But it won’t move in to the recycle bin!
WTF? -
I hate Windoze SO MUCH at the moment.
-
@Brian-Gregory said in PA 19.00.43...47 stops me moving .tar.xz, .tar.gz, .7z and .iso files.:
Well that’s just typical.
As soon as I say it seems to be fixed it does it again.But this this time ProcessExplorer says no process has locked the file!
But it won’t move in to the recycle bin!
WTF?What if, at that point, you restart the computer? Is it still locked after trying to delete it immediately after restarting?
-
@Mili said in PA 19.00.43...47 stops me moving .tar.xz, .tar.gz, .7z and .iso files.:
@Brian-Gregory said in PA 19.00.43...47 stops me moving .tar.xz, .tar.gz, .7z and .iso files.:
Well that’s just typical.
As soon as I say it seems to be fixed it does it again.But this this time ProcessExplorer says no process has locked the file!
But it won’t move in to the recycle bin!
WTF?What if, at that point, you restart the computer? Is it still locked after trying to delete it immediately after restarting?
Yes restarting fixes it. Also waiting a few minutes fixes it. Plus it doesn’t do it anywhere near as often at the moment but I don’t know if that’s because of the settings I changed or because it still rebuilding the indexes. The process that builds the indexes seems to be fixed to use about 25% of one thread and produces only the tiniest barely visable flickers in the hard drive activety light. :(
-
I’m trying running with the Indexing Service disabled on both my PCs now because it’s useless and just sticks on certain files which there is no easy way to identify.
I don’t think I’m going to miss it because I already tend to use WHERE /r from the command line to find files since it usually gets results much quicker anyway.