-
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.
Regestration fails
-
The updater just installed version 12.00.41 (04/2011) of PowerArchiver (German version). As usual from time to time, it asked me to enter the registration code again. So I did. It is the one I received for PowerArchiver 2009. The registration code was confirmed – but after the restart of PowerArchiver, I was again asked to enter the registration code!
By now I have done that something like five different times, using the different ways of entering the registration code. None worked.
Maybe PowerArchiver fails to save my registration code. I am running it under Windows 7, which in turn runs under Parallels 6 on a MacBook Pro. I did encounter some problems already when I used Parallels 5: PowerArchiver could not save to my standard directory, because it was included in Windows by Parallels as some kind of network device. I had to extract files to a local directory and then copy it to my standard directory. That problem has gone with Parallels 6, but now I cannot enter the registration code …
Who can help?
-
You can always get your License Key for the latest version here:
https://www.conexware.com/shop -
You need latest key and you can find it at link NTFS posted above… thanks
-
on my machine I had a working installation of version 2010 (11.71)
I got my version 2011 registration key, but Powerarchiver remained unregistered.started up Sysinternals procmon to see what’s going on. Powerarc seems to write the registry information (RegnameW) to HKCU but wants to read it from HKLM, where the old Regname (without W) from one of the previous versions was already here.
After I copied the keys from HKCU to HKLM the program started as registered.
I tried with a fresh install in a virtual machine and there were no such problems.
OTOH, why do you write the registration to the user’s profile, even if I install with administrative rights?
Regards, Robert
-
@Robert:
on my machine I had a working installation of version 2010 (11.71)
I got my version 2011 registration key, but Powerarchiver remained unregistered.started up Sysinternals procmon to see what’s going on. Powerarc seems to write the registry information (RegnameW) to HKCU but wants to read it from HKLM, where the old Regname (without W) from one of the previous versions was already here.
After I copied the keys from HKCU to HKLM the program started as registered.
I tried with a fresh install in a virtual machine and there were no such problems.
OTOH, why do you write the registration to the user’s profile, even if I install with administrative rights?
Regards, Robert
PowerArchiver reads both, somehow it was previously written in HKLM, this is admin only feature for larger enterprise installations.
-
thanks, already got my key
-
:-)
-
Dear PA users,
i have the same problem entering the registration code.
I had a perfect running PA2010 installation. About a month ago i had updated to the PA2011 version. Received the new registration code, entered the registration code into the corresponding fields. I raceive the message “Code accepted, thanks ….”
But then PA restarts again with the registration window.
Now the 30 test days are over. I have deleted the 2011 version, reinstalled the 2010 version and have the same problem now with the 2010 version.
HELP - i have no running PA installation now.
I have read about the registry entry solution. Since i am not very familiar editing the registry i would like to ask you to give me some more detailled information how i can get my 2011 version to run.
Thaks in advanceMarco
-
you should contact support to help you with registration issues… you should have no issues with registering either PA 2010 or PA 2011 with their own registration codes that are specific to each version.