Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Config settings doesn't impact PA behaviour...

      pirrbe

      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

      Tech Support
    • Missing pdf markups in pdf preview

      L

      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?

      Tech Support
    • Question about PA Files...

      T

      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.

      Tech Support
    • Functions in Windows 11 context menu no longer work after last Windows Update

      T

      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.

      Tech Support
    • Multi Extract doesn't extract in parallel in Windows 11

      Z

      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.

      Tech Support
    • Functions in Windows 11 Context Menu don't work in some directories

      P

      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.

      Tech Support
    • PA 2023 Preview versus PA2022

      pirrbe

      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

      .

      Tech Support
    • Missing virtual driver in Patchbeam

      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

      Tech Support
    • How to get a registering code?

      N

      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 2023

      Can 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"

      Tech Support
    • File Explorer Shell Extension crash on Junction

      W

      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).

      Tech Support
    • PA 21.00.18 Action / Test behaves oddly for me on .PA files

      Brian Gregory

      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.

      Tech Support
    • PA 21.00.18 testing via context menu causes extraction of files

      D

      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.

      Tech Support

    TAR Archive Support Still Has Problems

    Tech Support
    4
    10
    11867
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      DaCypher last edited by

      I downloaded a TAR archive today and I immediately noticed some problems with the way PA handled it. First off, PowerArchiver seemed to be quite sluggish (used a high amount of CPU and RAM), this I could live with if it could handle the archive properly. However, the file listing showed me instantly that it was unable to properly be handled. Many of the filenames were cut off and there were @LongLink files listed. I decided to attempt to have PA extract the archive anyways. First I was given an error that said “Invalid argument to date encode.”, so I clicked Ok and was then asked if I wanted to overwrite the Read-Only @LongLink file. No matter my response to that, I only get 2 of the smaller files extracted from the archive. The archive is not corrupt as I have copied it to my linux machine and it extracted just fine with “tar -xf filename.tar”. I wouldn’t mind sharing this archive for testing purposes but it is about 120MB. Any help would be appreciated.

      1 Reply Last reply Reply Quote 0
      • D
        DaCypher last edited by

        Bump.

        TBGBe 1 Reply Last reply Reply Quote 0
        • TBGBe
          TBGBe @DaCypher last edited by

          Well, without the tar it is a bit difficult to identify the problem (I haven’t experienced this - but thatprobably means little).

          Could you perhaps provide a (complete) listing of the contents if not the tar itself (curious about the reference to @LongLink )?

          spwolf 1 Reply Last reply Reply Quote 0
          • spwolf
            spwolf conexware @TBGBe last edited by

            I was able to reproduce it - it seems that the issue is with filenames+path over 255 characters (Windows limit), which should not be the issue even if there is an Windows limitation there.

            We will have to report it engine developers, since it is definetly an engine issue.
            Thanks for finding it.

            regards,

            D 1 Reply Last reply Reply Quote 0
            • D
              DaCypher @spwolf last edited by

              Actually, the archive name itself was about 50 characters and contained filenames that were 50-60 characters each that were all in a directory which had a name of about 50 characters. Even if these were all added up I don’t think any of the files got near to the 255 limit.

              Unfortunately, it appears as though I allowed my carelessness to get the best of me and I am no longer in possession of this archive (neither is my recycling bin).

              At least one problem was found and should be fixed. :)

              TBGBe 1 Reply Last reply Reply Quote 0
              • TBGBe
                TBGBe @DaCypher last edited by

                Not sure if this is the same problem (or the same solution), but it appears that there is a filename length restriction for TAR format.

                name = 94 chars (98 with ext) OK
                name = 95 chars (99 with ext) fails - TAR is not created.

                Note: No Path is being stored. Other compression fromats work OK with name = 95 chars (99 with ext).

                (checked in 9.00.34 test - same) - see attachment.

                ivan 1 Reply Last reply Reply Quote 0
                • ivan
                  ivan conexware @TBGBe last edited by

                  Same problem.

                  We have recorded it and will check it for 9.1.

                  D 1 Reply Last reply Reply Quote 0
                  • D
                    DaCypher @ivan last edited by

                    I came across another archive with a very similar issue described in the first post, now that I have it I decided to take a screenshot of it to hopefully help with debugging (in case its not already been fully identified).

                    Feel free to ignore the what type of content is actually in the archive. :)

                    ivan 1 Reply Last reply Reply Quote 0
                    • ivan
                      ivan conexware @DaCypher last edited by

                      The issue has already been fully identified - we have addressed this problem for 9.1

                      D 1 Reply Last reply Reply Quote 0
                      • D
                        DaCypher @ivan last edited by

                        Ok, sorry for the redundancy, thanks for fixing the problem, looking forward to 9.1. :)

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post