-
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.
-
Is the version Preview 2023 also considered to be tested by the testteam ? In the past we got messages in the forum for testing out version x.x, to be downloaded by fastring, or I missed the one for 2023. (I discovered 2023 on the official web…)
CU, Pirrbe.
-
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).
-
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. -
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.
Crash at Exit with PA 10.2 Beta 2
-
PA 10.20.02 on XP x64
Open PA with an empty archive, close PA, boom
First-chance exception at 0x0049890f in POWERARC.EXE: 0xC0000005: Access violation reading location 0x1a000008.
according to VS 2005 -
I run windows XP Pro SP2 with the latest updates as of 2 weeks ago and installed the same PA Version but did not experience this issue??
Did you do an upgrade or a clean install??
try uninstalling the program, then delete the PowerArchiver Folder in Program Files. Reboot and re-install then to be safe restart again!
If it still happens then send an error report to PowerArchiver Support.
-
Open PA with an empty archive, close PA, boom
What is an empty archive ?
What archive format? -
My mistake on the empty archive: it’s open PA without an archive loaded.
It was a clean install after a uninstallation of PA 10.2 Beta 1.
I already tried the reinstall/reboot Sir Richard suggested. Same problem.
-
How odd?
If not already try this then (only if you know the registry)
1. Uninstall PowerArchiver 2006/07
2. Delete “Program Files/PowerArchiver” Folder
3. Delete Registry LinkHKEY_CURRENT_USER\Software\PowerArchiver\
then… if you have any registry cleaning software such as CCleaner or tune-up etc… do a full registry clean!
Restart then re-install…
If it still continues then it must be a fault with the program or something on your system is causing a conflict.
-
Tried the procedure but that did not help
However, I have more information:
the crash occurs only with the classic skin, not with the ribbon interface.
The Default blue skin works nicely.
I though it may have been Windowblinds causing the problem. I unloaded Windowblinds and run PA: with the Windows classic style, PA does not crash, with the Windows XP style, PA crashes.That’s really odd.
-
Well, I have PowerArchiver :: Classic
Windows XP - Appearance XP Style / Color Silver
But no crash.
If you can reproduce it, provide/attach a DR Watson Log File (Zip). -
Did I read the original post correct that you are using the 64bit version of XP or is it the 32?
I’m not able to reproduce, but I’m using the 32 bit, so maybe it is a 64 bit problem.
-
I think I reproduced the error… it ocured when I did the following
1. Open PA With Silver Default Ribbon
2. Change to Blue Default Ribbon
3. Change to silver default Ribbon
4. Change to classic
5. Change to Silver default(I couldnt replicate it all the time only when I was clicking and changing skins like a mad man)
the errors are as follow’s (does it look familer?)
-
Yes, I am using XP x64. The errors reported by Sir Richard looks similar.
-
PA,
I will forward those results via your support page for you to look at!
Cheers crew, Vykranth Hopefully, this will support PA to amend the problem ready for the next release!
-
those are two different bugs - we are looking at 64bit one, already reported here while i will move sir richs to new thread…
p.s. devs on vacation until sunday, so expect new release in 6-7 days…thanks!
-
To be fair spywolf this is the 1st error I have personally experienced with PA in a long time!!
Looking forward to the next release, keep up the good work!
-
Please check with Beta 3 preview:
http://www.powerarchiver.com/test/release10/powarc1020b3.exeand let us know if it works properly now.
thanks!
-
Hiya,
I don’t have the crash at exit I experienced intially.
I did have one crash when changing from the classic skin to the modern silver sking but I cannot reproduce it anymore.I will try again later to see if I can reproduce it systematically.
Thank for the early preview. As Sir Richard said, it has been a very long time since I reported a problem in PA.
Keep up the good workVykranth
