-
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.
How many times can I reactivate my install?
-
I’m dual booting Win7 and Vista 64. When I go into Win7 and use Power Archiver, it asks for registration so I register it and everything is good.
If I go to Vista and run PA, it asks to register it so I do and it’s all good. If I go back to Win7 and try and use Power Archiver it wants me to register again, and same thing if I register and go back to Vista.What I want to know is; how many times can I do this before my key is deactivated?
-
strange…I run a dual boot system also but once I register PA it all works fine.
Windows 10 Pro x64
Intel Core 2 Duo E6850 @ 3.00GHz
4.00GB Dual-Channel DDR2 @ 399MHz
NVIDIA GeForce GT 730 -
What I did was install PA in Vista64, when I first installed Win7 I made a shortcut to the Vista64 installs’ exe.
-
install PA on both systems and register it on both systems…you can’t use a shortcut to it on another OS…it will always give you registration prompts if you do it that way.
Windows 10 Pro x64
Intel Core 2 Duo E6850 @ 3.00GHz
4.00GB Dual-Channel DDR2 @ 399MHz
NVIDIA GeForce GT 730 -
I thought so, but didn’t want to lose the space, as I have to do that with only some programs.
Well how about my question though? How many times can I reactivate with my serial key before it gets black listed?
-
as far as I’m aware there is no limit…
but I’m sure the team here will verify that fact for you. -
I thought so, but didn’t want to lose the space, as I have to do that with only some programs.
Well how about my question though? How many times can I reactivate with my serial key before it gets black listed?
million times at minimum :-)
-
although you should be able to register it properly the way you are doing it… are you sure it gets registered once you do it? there is no PA reason for it to reset every time you boot into other windows.
-
although you should be able to register it properly the way you are doing it… are you sure it gets registered once you do it? there is no PA reason for it to reset every time you boot into other windows.
Yeah it gets registered. If I open PA back up it says it’s registered to me. If I go to Vista, it says it’s not registered. Which is weird as isn’t the registration stored in the registry?
-
Yeah it gets registered. If I open PA back up it says it’s registered to me. If I go to Vista, it says it’s not registered. Which is weird as isn’t the registration stored in the registry?
how do you mean if you go to Vista?
-
if you have registered it at Vista, then thats it, it should work… if it does not, something is deleting the registry key.
-
I thought so, but didn’t want to lose the space, as I have to do that with only some programs.
Well how about my question though? How many times can I reactivate with my serial key before it gets black listed?
install it on Vista64 in the same folder as it is on Win7.
I understand now - it will not work as registration is saved in Win7 registry and Vista64 is reading its own.
So if you want to save space, just install them both to the same folder and it will work fine.
What i dont understand is that it does not really need installation again - in Vista64 when nag screen pops up, you just had to enter registration code and it should have worked.
-
install it on Vista64 in the same folder as it is on Win7.
I understand now - it will not work as registration is saved in Win7 registry and Vista64 is reading its own.
So if you want to save space, just install them both to the same folder and it will work fine.
What i dont understand is that it does not really need installation again - in Vista64 when nag screen pops up, you just had to enter registration code and it should have worked.
That’s what I thought. I’ll check again just to be sure.
Step 1: Boot to Win7.
Step 2: Open PA. It’s registered
Step 3: Boot to Vista
Step 4: Check to see if registered, if not then register it.
Step 5: Boot to Win7
Step 6: Open PA. Check for registration.I’ll report back in a bit
