Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • 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
    • 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
    • Start PowerArchiver 2023 Starter when my computer starts

      Brian Gregory

      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.

      Tech Support
    • Testing .pa archives

      PA_Fan

      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 errors

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

      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
    • Small UI / Theme bug in 2023

      Z

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

      Tech Support
    • PowerArchiver and PACL for macOS

      spwolf

      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

      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

    [BUG] PA 11.60.22 triggers "Windows - No Disk" error on startup

    Tech Support
    3
    19
    11562
    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.
    • W
      welhaux last edited by

      PA 11.60.22 on Windows XP SP3

      I have a floppy drive in my system. There is no disk in it and I have not used it in about a year.

      When I launch PA via Windows Start menu (i.e. as opposed to double-clicking an archive), I get a “Windows - No Disk” message, because PA tries to access my floppy (A:) drive, when it should not be.

      This bug did not exist in 11.60 RC4.
      attachment_t_4221_0_pa_11_60_bug.png

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

        try using reset to defaults… does that help?
        Do you have explorer view on?

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

          Haven’t used PA for a week or so (on a course). But started PA (60.20) today and I got same error (identical - even parameter string). Also after web update (60.23)
          @spwolf:

          try using reset to defaults… does that help?
          Do you have explorer view on?

          Default - PA restarts in Classic ?? But no error message.
          Change to Modern View

          • Explorer with folders
          • Start folder system default

          Close PA
          Start PA
          Error appears again - the access LED on floppy Drive A: is activating
          Note:
          “Try again” just “loops” with error
          “Continue” and PA works.
          .

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

            probably change the startup location to documents/desktop and see what happens then.

            then go into explorer view, click on my computer or C:\ and see when does the error show again (when is PA querying the A: drive).

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

              @spwolf:

              probably change the startup location to documents/desktop and see what happens then.

              Yes, choosing specific folder seems to avoid problem.
              @spwolf:

              then go into explorer view, click on my computer or C:\ and see when does the error show again (when is PA querying the A: drive).

              [Folder View]
              Select “My Computer” - error message
              … Continue
              Select any folder on C:
              Select “My Computer” - error message

              repeatable loop :p

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

                @TBGBe:

                Yes, choosing specific folder seems to avoid problem.

                [Folder View]
                Select “My Computer” - error message
                … Continue
                Select any folder on C:
                Select “My Computer” - error message

                repeatable loop :p

                so basically it is when clicking on my computer?

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

                  Yes - but don’t forget initial start as well as “my computer” in folder view.

                  1 Reply Last reply Reply Quote 0
                  • W
                    welhaux last edited by

                    I am using Explorer view

                    For me, the startup location is set to “Last open archive.”

                    But when I startup, “Desktop” is the folder that initially appears in the Explorer view folder drop-down, followed shortly by PA trying to access my A: drive and failing. Then I get the error message and when I click on “Continue,” it then finally goes to my D: drive, which is the actual “last open archive” folder.

                    So it’s the “Last open archive” folder option that’s not working as it should and instead appears to be needlessly scanning drives on it’s way to selecting the correct folder.

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

                      @welhaux:

                      I am using Explorer view

                      For me, the startup location is set to “Last open archive.”

                      But when I startup, “Desktop” is the folder that initially appears in the Explorer view folder drop-down, followed shortly by PA trying to access my A: drive and failing. Then I get the error message and when I click on “Continue,” it then finally goes to my D: drive, which is the actual “last open archive” folder.

                      So it’s the “Last open archive” folder option that’s not working as it should and instead appears to be needlessly scanning drives on it’s way to selecting the correct folder.

                      it does not matter what is the option (last open archive, default, etc), but what folder it ends up opening… if that folder sees A:\ directly, it will try to read it to see if it has any files on it.

                      W 1 Reply Last reply Reply Quote 0
                      • W
                        welhaux @spwolf last edited by

                        @spwolf:

                        it does not matter what is the option (last open archive, default, etc), but what folder it ends up opening… if that folder sees A:\ directly, it will try to read it to see if it has any files on it.

                        I believe you’ve misunderstood my explanation.

                        POINT #1: The last open archive folder is D:. That is the last folder where I opened an archive. That is the folder explorer view should default to when I launch PA from the Start menu, given that the “Last open archive” option is set.

                        POINT #2: Even though, as stated in POINT #1, D:\ was the last open archive folder, when I launch PA, it initially opens the Desktop folder before going to D:, and it is in that process of starting with Desktop then going to D:\ that it scans A:\ drive. This should not happen. Go directly to D:\ drive and don’t try and access any other drive. This is what SHOULD happen but is NOT happening, and that is why I get this error.

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

                          can someone send us their PA registry, to support at conexware . com? HKCU\Software\PowerArchiver.

                          thanks

                          W 1 Reply Last reply Reply Quote 0
                          • W
                            welhaux @spwolf last edited by

                            Registry file sent.

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

                              do you mind testing several versions to see which ones has it working properly? and we can go back to that… as we currently can not find any computer that we can reproduce it on…

                              1 Reply Last reply Reply Quote 0
                              • W
                                welhaux last edited by

                                Sure. Give me the links and I’ll give it a go.

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

                                  @welhaux:

                                  Sure. Give me the links and I’ll give it a go.

                                  we got it - well, reproduced it… sent bug reports to perspective companies… hopefully it will be fixed within a week or.

                                  It has been like that for a while though, at least a month…

                                  W 1 Reply Last reply Reply Quote 0
                                  • W
                                    welhaux @spwolf last edited by

                                    @spwolf:

                                    we got it - well, reproduced it… sent bug reports to perspective companies… hopefully it will be fixed within a week or.

                                    Great. Thanks.

                                    @spwolf:

                                    It has been like that for a while though, at least a month…

                                    Seems about right. I know I skipped some builds, and I assumed the last PA release I installed, prior to the final, was RC4, because I have the setup file on my system, but I could be wrong considering that I did not encounter the bug until I installed the final build.

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

                                      Should be fixed in 11.60.25 build:
                                      http://bit.ly/4snT7H

                                      check it out and let us know… thanks!

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

                                        @TBGBe:

                                        Start folder system default

                                        Reset to this setting with 11.60.23 - error appears.
                                        Upgrade to 11.60.25 - no more error message(s).

                                        So fixed (for me).

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

                                          Partially fixed by 11.60.25:

                                          1. PowerArchiver still accesses the A: drive. This slows down population of the explorer view, as the A: drive is waited unnecessarily waited on.

                                          2. The error message is now gone.

                                          Why not just go directly to the last open archive folder? Why start from Desktop and drill down, drive by drive?

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