-
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. -
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).
-
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.
-
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
Crash of PA Starter
-
When I start a Backup script (copy folder on a HD to a network folder), the PA Starter crash (see attachment). :eek:
PA 11.60.08
Vista 64Bit
Non-Admin
-
Im running Win7 RC1
have just installed (and paid for) laster version of PA 2010 (eng version),
i get the same error as above on ALL starts of the OS - as soon as i start windows , and the PAstarter starts up - i get the same error …im not sure is this is due to Win7 , and/or the firewall , or something else
this means i cannot schedule any backups currently - only run as manually
i have made sure all EXEs are running as administrator , and in XP (SP3) , compatibility mode - always the same error appears …
I have a dual boot pc , and in XPpro - the problem does not exist
- forgot to add - im runing the 11.60 beta version !
-
please check the date inside your PowerArchiver folder. Is PA Starter same date as powerarc.exe?
If so, please zip your HKCU\Software\PowerArchiver key and send it to support @ conexware . com.
p.s. backups are not scheduled by Starter but via Windows Scheduler.
-
Uninstalled 11.6 Beta 1 - and ensured the physical directory had been removed , before reinstalling the “official” 11.5 release
and problem with PA starter appears to have gonei can only assume - that when the 11.6 beta version was installed, some of the EXE/DLL were not updated correctly over 11.5 , and hence had a mix of versions
-
you had old PA Starter, which had the issue
-
I had the same problem with 11.6 RC2, which went away when I fell back to 11.50.
Is it correct to assume that 11.6 RC2 was bundled with an old version of PA starter or did the 11.6 install not replace the old version?
-
I had the same problem with 11.6 RC2, which went away when I fell back to 11.50.
Is it correct to assume that 11.6 RC2 was bundled with an old version of PA starter or did the 11.6 install not replace the old version?
Nope, rather 11.6 RC2 has new starter that does not get overwriten sometimes until you restart your computer (depending on OS).
Can you send us your HKCU\Software\PowerArchiver regostry key, zipped, at support @ conexware . com.
thanks
-
(if you use german version, key is HKCU\Software\PowerArchiverInt)
thanks!
-
I sent.
But, realize the registry I sent is for version 11.50 (where PA starter works) I fell back to.
Good luck.
-
thats ok too :)
what version of RC2 did you use, german or english?
-
Hopefully English. I received it through the program update to latest version notification (powarc1160rc2.exe).
-
it seems that you just need to close PA Starter and then upgrade to RC2… that should work fine (so you wont need to restart after upgrading).
-
I thought I did have it stopped but maybe not.
I did the reinstall this time specifying that PA starter not be running. I then started it after install and its now working.
-
Cool :)
-
There were some additional improvements for this issue/starter.
You can re-download Preview version (11.60.12) from our website. Please check it out and see if this solved your issue.
Thanks!
-
POWERARC.EXE is two days older than the starter.
I try to reinstall.