-
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.
-
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. -
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 :)
-
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.Features implemented:
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.
thank you!
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
76e97ab9-8d75-4175-9ce8-446500031f38-image.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.
Slow startup
-
Could somebody let me know the minimum system specs for the latest RC1? I installed it on a laptop, whilst not the most stellar of machines, where it took 29 secs for the main window to appear. Machine is defagged, running clean and lean. OpenOffice Writer 3.1 is ready to use in 20 secs.
Celeron 2.6GB, Win XP, 496MB of ram just over half that used for cache, the rest free.
Cheers
DrT
-
use classic view, classic skin… hows that now?
-
Exactly the same.
Cheers
DrT
-
is PA registered? if so, clear registration info and check then (so it is unregistered). lets see what happens now.
-
I can clear the reg info, but not save the change. Clicking OK gives an error and the info returns. I can close the box by clicking the ‘X’ (top right) but PA remains registered.
Cheers
DrT
PS Issue still present in RC2
-
delete your HKCU\Software\PowerArchiver key…
-
delete your HKCU\Software\PowerArchiver key…
WOW :D:D! 7-8 secs until the screen telling me how many days left of trial to run, under which the PA program was seen! How do I get that 7-8 secs startup with PA being registered? 29 to 8 secs startup is not to be sneezed at.
Cheers
DrT
-
we start by giving me an headache and then we move on :)
-
we have tried on our Turion and it starts within 4 seconds.
Are you sure the difference isnt because of it being cached in memory 2nd time you try?
-
we have tried on our Turion and it starts within 4 seconds.
Are you sure the difference isnt because of it being cached in memory 2nd time you try?
Definitely. Just booting up the offending PC to check again…classic menu and unregistered flies.
Cheers
DrT
-
Nice to know it isn’t just me. I noticed that PA was not as quick as it was at loading when 2010 was first out in beta…and a fast(er) load was one of its plusses.
Cheers
DrT
-
Looks like setting “Startup location” to a fixed folder (my Documents folder for me) solved the issue (was set on “Last open Archive” before).
Double clicking on whatever Archive now makes PA instantly open it like it should. Setting the option back to Last open Archive, PA starts to hang again when opening Archives double clicking in Explorer.you have latest version right? Or older one? Check in Help> About, what version you have.
How many files/folders are there in folder where startup is slow?
-
No difference here at all with that change to a fixed folder.
Cheers
DrT
-
No difference here at all with that change to a fixed folder.
Cheers
DrT
yeah, as i said, it is two completly different problems.
-
Version 11.50.49
Just tested with a folder containing just 2 archives…still hangs if option is set to “last open archive”.
Not a great issue for me as I have no need to have it on…happy I found a way to get rid of it.how many files in that folder? (startup one?).
There has to be something in that startup folder thats causing it…
-
Can’t get what you’re meaning with “startup folder”, I’m sorry. I’m getting this with every archive, independently of the folder it’s stored in and of the number of files which are in that folder. Just having one folder with just 1 archive I get the hang when double clicking on it to open it with PA…
so when you open an archive it takes how long?
and if archive is in startup location (thats what i meant, location where PA Starts), same?
What Antivirus are you using? It seems to be scanning the file before letting PA use it?
-
When the problem is there, PA hangs 5-6secs before opening Archives. When it isn’t there, PA opens Archives almost instantly (depending on how big they are).
The hang is there if I start PA directly too…that means, not double clicking on an Archive but just starting the program. And just having one startup folder which doesn’t include more than 4 small zip Archives (max. 1.4mb). Like I said, forcing PA to a fixed startup folder looks to solve the problem, no idea on what it’s trying to do with the other option set.
My AV program is Avast…don’t think this could be it, as I never had this problem till maybe a pair of months ago (maybe even less)…if that would be the problem, then it would be there having one fixed startup folder, or?can you please disable Avast temporary and try again… PA scans files when it starts, AV could be blocking access until it scans them.
-
only difference in using last open archive as startup folder is that is starts in different folder than what you manually set, PA doesnt do anything else.
-
Disabled all Avast resident protection modules…no difference noticed.
hm, maybe send us your PA reg key to support at conexware . com
HKCU\Software\PowerArchiver and zip it before sending.
That will help us replicate this exactly.
thanks!
-
Got it… nothing special we could see from that.
Lets check this.
Create folder C:\1.
Copy those zip files that you have in folder thats slowing down PA startup to C:\1. Now set PA to start in C:\1.Is it slower now as well? If it is slower, remove file by file from C:\1 and see if you can pin point what exactly is slowing it down.
Doesnt that make sense?
thanks
-
Tried this…I get the hang if I set PA to startup on that folder and if I double click on Archives stored in that Folder (I put 2 very small Archives into it).
What I noticed is that I seem to get the very same hang while browsing to that Folder while setting it in PA options, at the exact moment when I click on the “Computer” icon (to make my drives show up). That doesn’t occur with any other application I have on my PC.
The funny thing is that if I move my Archives to the default folder “My Documents”, I don’t get the hang (keeping PA set to a fixed startup folder).hm, something like that happened to me - i had AVG installed on our test computer Vista 64 bit (disabled), I uninstalled it so i can install Avast and after i restarted everything worked fine, even with avast installed and working.
When was the last time you restarted that computer?
-
hm, something like that happened to me - i had AVG installed on our test computer Vista 64 bit (disabled), I uninstalled it so i can install Avast and after i restarted everything worked fine, even with avast installed and working.
When was the last time you restarted that computer?
I restart it on a daily basis…
-
yeah, as i said, it is two completly different problems.
Any news on this issue since I reported back on the test file?
Cheers
DrT
-
Any news on this issue since I reported back on the test file?
Cheers
DrT
nope, we will have to rewrite something once final is released. Annoying issue :)
-
nope, we will have to rewrite something once final is released. Annoying issue :)
Feel free to contact me to test any fixes.
Cheers
DrT
