-
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.
PowerArchiver 2010 and Windows 7
-
Well, the changelog says full Windows 7 support.
I’ve installed Win 7 x64 build 7057 yesterday. This came at PA installation. I’ve used the default installer settings.
-
and? I would guess it is temporary bug with temporary version of Win7.
It works fine with 7000 and 7022, you should report it to Microsoft if you can so they fix it, but I am assuming it is bug affecting many different programs.
Just like when your Notepad opens when desktop starts in 7057 :-).
-
I do hope it is just a temporary bug. When PA 2010 Beta 2 wouldn’t install on 7057 I figured no biggie I’d just drop back to beta 1.
It refused to install as well so I fell back to PA 2009. However, it wouldn’t install, either. Guess I’ll have to wait till the next Windows 7 build to (hopefully) get my PA functionality back.
-
I do hope it is just a temporary bug. When PA 2010 Beta 2 wouldn’t install on 7057 I figured no biggie I’d just drop back to beta 1.
It refused to install as well so I fell back to PA 2009. However, it wouldn’t install, either. Guess I’ll have to wait till the next Windows 7 build to (hopefully) get my PA functionality back.
we run PA 2010 on Win7 7000, 7022, 704x and 7057… all work fine.
What exactly happens? Generally speaking, there are so such bugs in Win7 that would make this happen. It is probaly Windows Installer acting up but you need to send us more info.
-
are you getting the same message as above or? I though original post was just Win7 thinking something went wrong with installation and trying to be helpfup, as that file is actually not crucial to installation.
-
After setting additional install options and my chosen install directory I’m directed to click the Install button to begin installation.
It is once I do this I get a dialog box titled “Installer information” which reads:
Error reading from file
C:\Users<username>\AppData\Local\Temp\7zSD52D.tmp\setup.msi. Verify the file exists and that you can access it.Of course the temp directory is always different, but every time I make the attempt with the different installers setup.msi is always present and seems accessible.</username>
-
seems as if Windows Installer is borked… do you have PA 2009 or PA 2010 listed when you go to Programs? If so, maybe you need to use Windows Installer Cleaner utility to clean Windows Installer if you do have PA 2009/2010 listed there.
-
No, I haven’t had PA installed on Windows 7 Build 7057 at all. Neither PA 2009 or PA 2010 get far enough to install.
I’ll try to dig up this cleaner and run it anyway just to be safe.
-
when you run setup, and go to the temp folder, all the files are properly there? what happens if you copy them to another folder and run them manually from there?
-
When I navigate to that directory there are three files:
setup.exe
setup.ini
setup.msiCopying those files to a different directory and running the setup.exe results in the same order of events above except that the error message dialog states:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package.The error code is 2203.
Running setup.msi instead gives me the same error code 2203 message.
-
Gawd, I fixed it! Seems user SYSTEM didn’t have full control access to the temp directory.
Sorry for the wild goose chase. How it “lost” its privileges is beyond me, though.
Thanks for all the help, SPWolf!
-
:-)
i was just reading what the error means and was about to post to check that :P.
thanks, np.
-
Consider this one fixed…although after it did install I did get the dialog above that the OP posted, but I run into quite a few programs that do that upon installation.
I’m so glad I don’t have to go without PA. I rely on it so much to be able to open everything I don’t know how I’d get along without it.
-
yeah, dialogue above is basically just due to win7 build and should be fixed by them, it is just an glitch that doesnt affect anything…
by the time Win7 is released, PA is actually going to be tested by Win7 Q&A team against final build to make sure all of their issues are fixed.
