Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Powerarchiver 2021 incorrectly extract tar.xz file

      E

      Configuration:
      Powerarchiver 2021 20.00.73
      Windows 10 Education 10.0.19042 Build 19042

      When extracting gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz , Powerarchiver wrongly thinks some .exe files have a length of zero:

      98773b3b-65c0-48fa-8cd4-d081b2e0adee-image.png

      Once extracted:

      D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin>dir *.exe Volume in drive D is DATA Volume Serial Number is 0E12-BCA2 Directory of D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin 2020-11-20 07:10 PM 1,391,599 arm-none-linux-gnueabihf-addr2line.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ar.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-as.exe 2020-11-20 07:41 PM 3,030,119 arm-none-linux-gnueabihf-c++.exe 2020-11-20 07:10 PM 1,389,293 arm-none-linux-gnueabihf-c++filt.exe 2020-11-20 07:41 PM 3,027,513 arm-none-linux-gnueabihf-cpp.exe 2020-11-20 07:10 PM 4,040,503 arm-none-linux-gnueabihf-dwp.exe 2020-11-20 07:10 PM 391,769 arm-none-linux-gnueabihf-elfedit.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-g++.exe 2020-11-20 07:41 PM 3,026,926 arm-none-linux-gnueabihf-gcc-10.2.1.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ar.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-nm.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ranlib.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-gcc.exe 2020-11-20 07:41 PM 2,165,533 arm-none-linux-gnueabihf-gcov-dump.exe 2020-11-20 07:41 PM 2,343,605 arm-none-linux-gnueabihf-gcov-tool.exe 2020-11-20 07:41 PM 2,450,233 arm-none-linux-gnueabihf-gcov.exe 2020-11-20 07:54 PM 9,605,899 arm-none-linux-gnueabihf-gdb.exe 2020-11-20 07:41 PM 3,028,997 arm-none-linux-gnueabihf-gfortran.exe 2020-11-20 07:10 PM 1,412,943 arm-none-linux-gnueabihf-gprof.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.bfd.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.gold.exe 2020-11-20 07:41 PM 25,546,567 arm-none-linux-gnueabihf-lto-dump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-nm.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objcopy.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objdump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ranlib.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-readelf.exe 2020-11-20 07:10 PM 1,393,083 arm-none-linux-gnueabihf-size.exe 2020-11-20 07:10 PM 1,392,464 arm-none-linux-gnueabihf-strings.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-strip.exe 32 File(s) 67,465,867 bytes 0 Dir(s) 1,002,422,431,744 bytes free

      When the same archive is being extracted from a git bash session (after having installed git 2.30.1 for Windows 64 bit version from git-scm.com), the .exe files are extracted as expected:

      xz -k -d gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz tar xf gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar cd gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf/bin ll *.exe -rwxr-xr-x 1 User 197121 1391599 Nov 20 19:10 arm-none-linux-gnueabihf-addr2line.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ar.exe* -rwxr-xr-x 2 User 197121 2028927 Nov 20 19:10 arm-none-linux-gnueabihf-as.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-c++.exe* -rwxr-xr-x 1 User 197121 1389293 Nov 20 19:10 arm-none-linux-gnueabihf-c++filt.exe* -rwxr-xr-x 1 User 197121 3027513 Nov 20 19:41 arm-none-linux-gnueabihf-cpp.exe* -rwxr-xr-x 1 User 197121 4040503 Nov 20 19:10 arm-none-linux-gnueabihf-dwp.exe* -rwxr-xr-x 1 User 197121 391769 Nov 20 19:10 arm-none-linux-gnueabihf-elfedit.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-g++.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-10.2.1.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ar.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-nm.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ranlib.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc.exe* -rwxr-xr-x 1 User 197121 2165533 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-dump.exe* -rwxr-xr-x 1 User 197121 2343605 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-tool.exe* -rwxr-xr-x 1 User 197121 2450233 Nov 20 19:41 arm-none-linux-gnueabihf-gcov.exe* -rwxr-xr-x 1 User 197121 9605899 Nov 20 19:54 arm-none-linux-gnueabihf-gdb.exe* -rwxr-xr-x 1 User 197121 3028997 Nov 20 19:41 arm-none-linux-gnueabihf-gfortran.exe* -rwxr-xr-x 1 User 197121 1412943 Nov 20 19:10 arm-none-linux-gnueabihf-gprof.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.bfd.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.exe* -rwxr-xr-x 2 User 197121 4550029 Nov 20 19:10 arm-none-linux-gnueabihf-ld.gold.exe* -rwxr-xr-x 1 User 197121 25546567 Nov 20 19:41 arm-none-linux-gnueabihf-lto-dump.exe* -rwxr-xr-x 2 User 197121 1404945 Nov 20 19:10 arm-none-linux-gnueabihf-nm.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-objcopy.exe* -rwxr-xr-x 2 User 197121 1991350 Nov 20 19:10 arm-none-linux-gnueabihf-objdump.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ranlib.exe* -rwxr-xr-x 2 User 197121 1163376 Nov 20 19:10 arm-none-linux-gnueabihf-readelf.exe* -rwxr-xr-x 1 User 197121 1393083 Nov 20 19:10 arm-none-linux-gnueabihf-size.exe* -rwxr-xr-x 1 User 197121 1392464 Nov 20 19:10 arm-none-linux-gnueabihf-strings.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-strip.exe*

      The same archive file does extract properly under a native Linux Ubuntu 20.04 system, or under Windows 10 using the WSL2 Linux subsystem using xz and tar.

      Tech Support
    • Bugs I found and wanted to share with the team.

      B

      Hi I recently bought PowerArchiver and found some bugs and issues that I hit testing some of the features out.

      If you are doing a backup and on the compression options screen its default is compression format is PA with no option to change disk spanning. If you change to 7-zip you can change disk spanning. If you change the disk spanning then move back to PA format the field for disk spanning disables but the option stays set to what you changed it to. When you do a backup it will use PA with files spanning but PowerArchiver says that its not a valid format when you open it. If PA can’t really do file spanning then this screen is allowing it.

      I have attached an image where the progress bar is in the middle of the CD/DVD/BD Tools screen.

      alt text

      I have a 7-Zip file I created using the backup tools doing an increment backup. It opens and extracts just fine but if you using the Test option PowerArchiver locks up. Link to file: Backup-2021-02-05-20-35-36 TEST LOCKUP.7z

      On any Zip/PA/7-Zip process the pause and cancel buttons do not work. You have to hard kill the entire application to get out.

      Tech Support
    • Does PA supports Intel's zlib?

      G

      There would be many of us with Intel Processors.

      and they have their own optimized zlib algorithm, which can result in more efficiency if used combined with their hardware processor.

      Reference:
      https://www.intel.com/content/dam/www/public/us/en/documents/white-papers/zlib-compression-whitepaper-copy.pdf

      Can we get the same Functionality Under Hardware Acceleration Feature?

      Zlib is not the only feature that intel has included with their processor, there’s many, which if combined can result in efficient and better compression ratios.

      Tech Support
    • PA Batch Archive post completion error

      G

      Hi,

      After the batch archiving is complete, and if I click on whitespace of the PA app, I get this error.

      PA Batch.png

      I did check for ongoing process and ensured no archives were corrupt, It seems like activity did complete successfully but the error is shown for no reason, and only after clicking the whitespace.

      Please see if this can be removed.

      Tech Support
    • PA and conflict with Antivirus

      G

      I’m using the Kaspersky Total Security.

      I have configured PA as exclusion as followed:

      PA Exclusion.png

      and also is set us trusted application

      PA Trusted Application.png

      Scenario:

      My Antivirus likes to scan for everything, and it’s safeguarding behavior is to prevent the access to the file until the file is properly scanned for.

      The issue:

      PA when losses the access to file, it is stuck, consumes Resources, and never completes the process or throws any error

      Recommendation:
      PAStarter should also work as PAMonitor:
      There should be a monitoring process, at least if I’m using queuing feature, that should check for never ending compression processes and terminate them so the queue can be little bit automated.

      Also,
      There should be multiple attempts at retrying if PA loses access to or is denied, instead of having to see process was stuck for longer duration.

      Or, better, save the parameters I used for keeping the files in compression, and automatically restart the whole compression process after termination the same, of same folders and files set, this should happen in case if compression was stuck.

      Tech Support
    • Using the Queue Feature affects Compression Ratio negatively

      G

      If you use Queue Feature, you are not saving on space, you are just squeezing less.

      Here’s explaination:

      https://youtu.be/XcxG2wxyink

      I did test the same on multiple files, and of different types.

      It does have large difference for each large file you are trying to squeeze.

      Folders with multiple files, just have no benefits if you use Queue Feature

      Tech Support
    • Problems with Color-scheme after upgrade to build 73

      A

      Hello!
      I am using the portable version of PA2021. After switching from build 58 to 73 I have problems with the color-scheme:
      While 58 behaves like expected and showed everything in light or dark colors according to the settings, 73 always shows the lower part of the window in dark colors, no matter whether I select automatic, light or dark.
      This happens on a clean installation of 73 as well as on an update from build 58. I have attached two images generated on the same machine at the same time with the same settings. The upper shows build 73, the lower 58. Is it a bug or some changed setting I miss?
      Thanks for help!
      A.Borque

      PA2021_73.png PA2021_58.png

      Tech Support
    • Command line

      L

      Hello,

      PowerArchiver Command Line 7 support file greater than 2 Go ?

      Thanks

      Tech Support
    • PA shows incorrect archive properties

      G

      If you have tabbed archive browsing(reuse same window for all archive opening)
      and if you open two archives, and right click on older one to view properties it will only show of the recent archive that was opened, on all tabs/archives

      upgraded to 20.0.73

      Tech Support
    • Can I activate PowerArchiver on 2 devices with 1 license?

      2

      Hi.

      I currently own the PowerArchiver Select - lifetime free upgrades and support for PowerArchiver Toolbox English license.

      This license is active on 1 device. Does the license allow me to activate PowerArchiver on a second device that I own? Or do I need a separate license for that?

      Thank you ! :)

      Tech Support
    • No updates for portable version?

      A

      Hello!
      While the installable version of PA 2021 has already received two updates and is at version 20.0.73 the portable version still remains at the initially released build 58. Are there plans to update that version, too?
      Thanks for a reply!

      Tech Support
    • PowerArchiver shell extensions possibly crashing windows explorer.exe

      U

      I’ve been dealing with an intermittent explorer.exe crash for 5-6 years now. It happens randomly and will usually occur multiple times within a single session of an hour or two on my machine when manipulating files through Windows Explorer. explorer.exe is the only thing that ever crashes, so it’s not hardware IMO. I’ve done all hardware diagnostics and RAM is good. I’ve even swapped out motherboards with different brand and even the exact same one and it still crashes. sfc /scannow indicates system files are fine. I’ve done multiple reinstalls of the OS with no positive results. This crashing has happened on Windows 7 64-bit and Windows 10 64-bit. It seemed to get more frequent with Windows 10 after upgrading last year. I’ve also been using PowerArchiver throughout that time period (upgrading over time with new releases). I recently disabled all non-Microsoft extensions via ShellExView and saw no crashes for about 10 days, which is really unusual. I turned back them all back on after 10 days and saw another explorer.exe crash within the hour. So I disabled all 32-bit extensions and saw another crash. Following that I disabled all the PowerArchiver shell extensions and haven’t seen a crash after a day of heavy usage manipulating files within Windows Explorer, which doesn’t happen for me. The crash dumps I’ve captured don’t seem to indicate PowerArchiver is involved but I have a hunch it has something do with PowerArchiver shell extensions. The system even feels smoother with the PA extensions disabled. Windows 10 reliability monitor always has the same type of problem:

      Description Faulting Application Path: C:\WINDOWS\explorer.exe Problem signature Problem Event Name: BEX64 Application Name: explorer.exe Application Version: 10.0.17134.165 Application Timestamp: 4031a9f8 Fault Module Name: StackHash_e78e Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: PCH_8D_FROM_ntdll+0x000000000009AA54 Exception Code: c0000005 Exception Data: 0000000000000008 OS Version: 10.0.17134.2.0.0.256.48 Locale ID: 1033 Additional Information 1: e78e Additional Information 2: e78e327659b46c9a0c6916396b253cbf Additional Information 3: cebf Additional Information 4: cebf952c5db535ae7880488aafce55d9 Extra information about the problem Bucket ID: 1a57e4e784fbc735c231c68bd88581a9 (1311047270476906921)

      I know this is a very nebulous explanation but is there any way to link this up to PA shell extensions as the cause? I can provide the crash dumps and additional information if necessary.

      Tech Support
    • Bug in Archive Converter

      T

      When you select “Deflate (.zip, compatible)” as the method, it still converts the archive to a ZIPX format.

      Tech Support
    • UHA support

      D

      Would like to see uha archives supported compression as well as extraction. I use this all the time and it is a very good compression format

      Tech Support
    • Right-Click Compression

      Z

      In windows 10 you can right-click and select send to and the compressed zipped folder and the zip folder will contain the name of the last selected file.

      Does PowerArchiver have a similar function?

      Tom

      Tech Support
    • Cannot convert archive to .zip, always creates .zipx

      C

      Converting an archive to .zip (using both the “Deflate (.zip, compatible)” and “Store” compression methods) always creates a .zipx file instead.

      pa-convert-zip-1.jpg
      pa-convert-zip-2.jpg

      Using the “Store” method sometimes creates a .zip file; I have seen it happen just now, but I cannot reproduce it.

      Tech Support
    • patch beam waste of time

      D

      patchbeam a waste of time never updated with latest version

      Tech Support
    • UI Issue moving between different monitors

      G

      I have just installed 2021, but seems to have similar issues to 2019. If you move the app between differen monitors (with different resolutions) the app does not automatically adjust accordingly, so on one monitor I have the app is too big for the screen, whereas on another monitor it only takes up a small fraction of the screen.
      This was worse with 2019, where the fonts were totally screwed up, making the app unusable. This seems better in 2021, but still not working properly.

      Tech Support
    • "The specified account already exists" error

      S

      Hi! I came across an issue when I tried to uninstall PowerArch 2013. I got an error “The specified account already exists” which broke the process. I got the same error when I tried to install the current version, without uninstalling the previous one.
      So I can’t uninstall and I can’t install PowerArchiver. Any suggestions? OS Windows 8.1 x64.

      Dariusz

      Tech Support
    • Self-extracting archive creation too messy!

      A

      Good morning,
      I have been using all compression programs for over 20 years, I have always found Winrar very easy to use when I create a self-extracting archive, even 7-zip is simple, “right click” and “create self-extracting archive”, because on powerarchiver it must be like this confused ?
      It doesn’t just create the archive, it opens a page where I have to select the file again, what kind of archive, which folder to create it, etc … you should learn from your competitors how to make life easier!

      Tech Support

    UNSOLVED PowerArchiver shell extensions possibly crashing windows explorer.exe

    Tech Support
    8
    29
    3060
    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.
    • U
      U1zy3o2ih5ebk2F last edited by U1zy3o2ih5ebk2F

      I’ve been dealing with an intermittent explorer.exe crash for 5-6 years now. It happens randomly and will usually occur multiple times within a single session of an hour or two on my machine when manipulating files through Windows Explorer. explorer.exe is the only thing that ever crashes, so it’s not hardware IMO. I’ve done all hardware diagnostics and RAM is good. I’ve even swapped out motherboards with different brand and even the exact same one and it still crashes. sfc /scannow indicates system files are fine. I’ve done multiple reinstalls of the OS with no positive results. This crashing has happened on Windows 7 64-bit and Windows 10 64-bit. It seemed to get more frequent with Windows 10 after upgrading last year. I’ve also been using PowerArchiver throughout that time period (upgrading over time with new releases). I recently disabled all non-Microsoft extensions via ShellExView and saw no crashes for about 10 days, which is really unusual. I turned back them all back on after 10 days and saw another explorer.exe crash within the hour. So I disabled all 32-bit extensions and saw another crash. Following that I disabled all the PowerArchiver shell extensions and haven’t seen a crash after a day of heavy usage manipulating files within Windows Explorer, which doesn’t happen for me. The crash dumps I’ve captured don’t seem to indicate PowerArchiver is involved but I have a hunch it has something do with PowerArchiver shell extensions. The system even feels smoother with the PA extensions disabled. Windows 10 reliability monitor always has the same type of problem:

      Description
      Faulting Application Path:  C:\WINDOWS\explorer.exe
      
      Problem signature
      Problem Event Name: BEX64
      Application Name:   explorer.exe
      Application Version:    10.0.17134.165
      Application Timestamp:  4031a9f8
      Fault Module Name:  StackHash_e78e
      Fault Module Version:   0.0.0.0
      Fault Module Timestamp: 00000000
      Exception Offset:   PCH_8D_FROM_ntdll+0x000000000009AA54
      Exception Code: c0000005
      Exception Data: 0000000000000008
      OS Version: 10.0.17134.2.0.0.256.48
      Locale ID:  1033
      Additional Information 1:   e78e
      Additional Information 2:   e78e327659b46c9a0c6916396b253cbf
      Additional Information 3:   cebf
      Additional Information 4:   cebf952c5db535ae7880488aafce55d9
      
      Extra information about the problem
      Bucket ID:  1a57e4e784fbc735c231c68bd88581a9 (1311047270476906921)
      

      I know this is a very nebulous explanation but is there any way to link this up to PA shell extensions as the cause? I can provide the crash dumps and additional information if necessary.

      D 1 Reply Last reply Reply Quote 0
      • Brian Gregory
        Brian Gregory Alpha Testers last edited by

        I’ve also come to the conclusion that PowerArchiver is one of the top suspects in the case of the occasional explorer.exe crash on 64 bit Windows 7.

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

          We have been investigating shell integration for a while now, it is really hard to catch via debugger when something happens. There will be some measures taken in upcoming PA 2019 so you can check if you can notice any crashes in the future. I will be updating this thread when we released the build with it. Thanks!

          1 Reply Last reply Reply Quote 0
          • J
            joakim_46 Alpha Testers last edited by

            My god, I have the same issue for ages, and I thought it might be related to PA, but saw no one reporting, I guessed it was my OS that was messed up. My Explorer crashes usually when right clicking, or when shutting down. It started in Windows 7 x64 and then migrated to Windows 10 as well.

            1 Reply Last reply Reply Quote 0
            • U
              U1zy3o2ih5ebk2F last edited by

              I have done additional testing and have confirmed my crashes are 100% caused by PowerArchiver. I did a fresh clean install of Windows 10 and this time did NOT install PowerArchiver along with all my other programs. I saw no crashes for a month. So I installed PowerArchiver again and got a crash within an hour. I have since uninstalled PA again and have seen no such explorer.exe crashes since. Unfortunately, this is annoying enough to me that I will not be re-installing PA. Enough is enough.

              spwolf 1 Reply Last reply Reply Quote 0
              • moles42
                moles42 Alpha Testers last edited by

                My system has had explorer crashes for quite some time so today I will start a lengthy test
                without PA’s shell integration to see what results arise.

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

                  @razor19 said in PowerArchiver shell extensions possibly crashing windows explorer.exe:

                  I have done additional testing and have confirmed my crashes are 100% caused by PowerArchiver. I did a fresh clean install of Windows 10 and this time did NOT install PowerArchiver along with all my other programs. I saw no crashes for a month. So I installed PowerArchiver again and got a crash within an hour. I have since uninstalled PA again and have seen no such explorer.exe crashes since. Unfortunately, this is annoying enough to me that I will not be re-installing PA. Enough is enough.

                  @razor19 As I mentioned above, we have taken some measures in PA 2019, so if you want to test and contribute, please let us know via support at conexware dot com and we will get you latest internal release… thank you!

                  M 1 Reply Last reply Reply Quote 0
                  • U
                    U1zy3o2ih5ebk2F last edited by

                    Tried PowerArchiver 19.0 final release. This issue is still happening for me. Uninstalled for good.

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

                      sorry to hear it’s still happening @razor19
                      We would love to figure out why, there are no active reports from PowerArchiver users about the issue occurring. Must be specific.
                      Do you have any Anti Virus or File Lock software installed?

                      Been reading up on BEX64 error and one of the culprits might be AV or file lock software that locks files which cannot be refreshed/updated.

                      U 1 Reply Last reply Reply Quote 0
                      • U
                        U1zy3o2ih5ebk2F @Mili last edited by

                        I have ESET Nod32 Anti-Virus installed. I have tried uninstalling this for a period of time but still experienced the same issue.

                        1 Reply Last reply Reply Quote 0
                        • F
                          f16akias last edited by f16akias

                          Hello there.

                          I know this post is quite old, but unfortunately I do CONFIRM this bug also. Windows 10 version 1903,1909,2004 and powerarchiver 2017.01.06 create BEX64 errors (exactly as the first post), explorer.exe crashes and refreshes automatically randomly after opening closing opening ‘this computer’. Disabling shell integration from PA options did not help. I managed to stop it by disabling all PA shell context menu entries via ‘ShellExView’. Thought it was Microsofts bug but started testing after seeing this post. Testing for over a month I am 100% sure it is happening due to the existence of these registry entries. I say again disabling shell extension from PA options did not helped but rather disabling them from ShellExView.

                          Moreover uninstalling pa still leaves 2 context menu registry entries one contains hint x64 on name and the other support x64 and I have to delete them manually.

                          This bug happens also with 2019.00.59 version.
                          Detected on 3 pcs all of them having PA. 1 of them after fresh installation of Windows 10 and installation of PA.

                          Please inform if this bug is fixed in 2021 version please since I cannot imagine working without powerarchiver. Using it since 2009.

                          F 1 Reply Last reply Reply Quote 0
                          • F
                            f16akias @f16akias last edited by f16akias

                            Will test if BEX64 errors are happening due to a single PA context shell menu entry or all of them.
                            Please help me understand the structure of pa dlls for context menu.

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

                              @f16akias said in PowerArchiver shell extensions possibly crashing windows explorer.exe:

                              Will test if BEX64 errors are happening due to a single PA context shell menu entry or all of them.
                              Please help me understand the structure of pa dlls for context menu.

                              Please test with PA 2021 20.00.58 which is latest release, there were many changes due to this issue in the past few months. Thanks!

                              1 Reply Last reply Reply Quote 0
                              • M
                                Mili conexware last edited by

                                I also remember this occurring in the 2019 version but have not experienced it yet in the 2021 version. Am keeping an eye on it though.
                                If you experience it, please try to remember the operation at the time so that we can try and reproduce it.

                                thanks for everyone’s help!

                                1 Reply Last reply Reply Quote 0
                                • F
                                  f16akias last edited by f16akias

                                  Yes PA 2017.01.06 and 2019.00.59 both result in BEX64 errors…
                                  I installed 2021.00.58 2 days ago and yet I have not experienced any BEX64 error or something similar. Will test until my trial expires now.
                                  One minor thing I noticed is that context menu icons are in red color and not yellow, though 2021.00.58 is declared as final release and not beta.

                                  As far as the operation that results in error for me is usually:
                                  plugin an external HDD os USB stick, copy-cut files from my internal hdd to the external, use back button till ‘this computer’, close window and reopen it from shortcut. Usually at reopening it “freezes for 2sec” and then explorer.exe crashes (no message for sending crash info or troubleshooting) and automatically restarting explorer.exe (it happens in a blink of eye).
                                  In summary copy-rename files to an external disk, browse in folders and then close and reopen ‘this computer’ shortcut. I do not remember experiencing it on user folder (where images,videos and download folders exist) though.

                                  Also keep in mind that after PA uninstall 2 context menu items are left in registry… “PowerArchiver Hint Handler64” and “PowerArchiver Preview Handler64”

                                  1 Reply Last reply Reply Quote 0
                                  • F
                                    f16akias last edited by f16akias

                                    Unfortunately I received again a BEX64 error with PA 20.00.58, just by cutting a folder, pasting it at desktop, then creating an empty folder at the initial origin and renaming with original name.

                                    Using Greek Windows 10 (English Translation)

                                    Περιγραφή (Description)
                                    Διαδρομή ελαττωματικής εφαρμογής (Faulting Application Path):	C:\Windows\explorer.exe
                                    
                                    Υπογραφή προβλήματος
                                    Όνομα συμβάντος προβλήματος (Problem Event Name):	BEX64
                                    Όνομα εφαρμογής (Application Name):	Explorer.EXE
                                    Έκδοση εφαρμογής (Application Version):	10.0.19041.610
                                    Χρονική σήμανση εφαρμογής (Application Timestamp):	ab30c679
                                    Όνομα ελαττωματικής λειτουργικής μονάδας (Fault Module Name):	StackHash_4fe4
                                    Έκδοση ελαττωματικής λειτουργικής μονάδας:	0.0.0.0
                                    Χρονική σήμανση ελαττωματικής λειτουργικής μονάδας:	00000000
                                    Μετατόπιση εξαίρεσης (Exception Offset):	PCH_E5_FROM_ntdll+0x000000000009C8F4
                                    Κωδικός εξαίρεσης (Exception Code):	c0000005
                                    Δεδομένα εξαίρεσης (Exception Data):	0000000000000008
                                    Έκδοση λειτουργικού συστήματος (OS Version):	10.0.19041.2.0.0.768.101
                                    Αναγνωριστικό τοπικών ρυθμίσεων (Locale ID):	1032
                                    Πρόσθετες πληροφορίες 1:	4fe4
                                    Πρόσθετες πληροφορίες 2:	4fe48443420d2e8d4afe531d780de425
                                    Πρόσθετες πληροφορίες 3:	c3ef
                                    Πρόσθετες πληροφορίες 4:	c3eff943408f9e455a715ed80d35b4ab
                                    
                                    Περισσότερες πληροφορίες σχετικά με το πρόβλημα
                                    Αναγνωριστικό κάδου:	dace8c8bdbc6cc651b643f81476063fc (1973772361175950332)
                                    
                                    F 1 Reply Last reply Reply Quote 0
                                    • F
                                      f16akias last edited by

                                      Will try now disabling the specific 2 registry options “PowerArchiver Hint Handler64” and “PowerArchiver Preview Handler64” via ‘ShellExView’ to keep testing.

                                      Please (if you cannot post it here send me a private message I am a programmer) regarding those 2 registry values. What are their purpose and how-where can i check-test them.
                                      Maybe you should consider troubleshooting with Microsoft also since they tend to make changes that break up programs. Missing the old Win XP times :)

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

                                        Those dll’s should not be enabled anymore in PA 2020. Can you see location of those dlls through shellexview please?

                                        thanks!

                                        1 Reply Last reply Reply Quote 0
                                        • F
                                          f16akias last edited by f16akias

                                          They are not leftovers from PA 2017 installation because as I said before
                                          @f16akias said in PowerArchiver shell extensions possibly crashing windows explorer.exe:

                                          Also keep in mind that after PA uninstall 2 context menu items are left in registry… “PowerArchiver Hint Handler64” and “PowerArchiver Preview Handler64”
                                          Moreover uninstalling pa still leaves 2 context menu registry entries one contains hint x64 on name and the other support x64 and I have to delete them manually.

                                          After manual deletion from Registry since PA 2017,2019 uninstallation, they are still imported to registry after PA 2021 installation. PA 2017,2019,2021 do create those 2 entries and after uninstall they do not delete them.

                                          Here are the paths:

                                          1. “PowerArchiver Hint Handler64”
                                            ~C:\Program Files\PowerArchiver*PASHLEXTh64.DLL* <–(This one cannot be found!!)
                                            ~\HKEY_CLASSES_ROOT\CLSID{d03d3e7B-0c44-3d45-b15f-bcfd8a8b4c7e}
                                            HKEY_CLASSES_ROOT\CLSID{d03d3e7B-0c44-3d45-b15f-bcfd8a8b4c7e}\InProcServer32]
                                            @=“C:\Program Files\PowerArchiver\PASHLEXTh64.DLL”
                                            “ThreadingModel”=“Apartment”

                                          2. “PowerArchiver Preview Handler64”
                                            ~C:\Program Files\PowerArchiver\PASHLEXTe64.DLL
                                            ~\HKEY_CLASSES_ROOT\CLSID{D03D3E7D-0C44-3D45-B15F-BCFD8A8B4C7E}
                                            [HKEY_CLASSES_ROOT\CLSID{D03D3E7D-0C44-3D45-B15F-BCFD8A8B4C7E}]
                                            @=“PowerArchiver Preview Handler64”
                                            “AppID”="{6d2b5079-2f0b-48dd-ab7f-97cec514d30b}"
                                            “DisableLowILProcessIsolation”=dword:00000001

                                          [HKEY_CLASSES_ROOT\CLSID{D03D3E7D-0C44-3D45-B15F-BCFD8A8B4C7E}\InprocServer32]
                                          @=“C:\Program Files\PowerArchiver\PASHLEXTe64.DLL”
                                          “ThreadingModel”=“Apartment”
                                          “ProgID”=“pashlexte64.zipfile”
                                          “VersionIndependentProgID”=“pashlexte64.zipfile”

                                          [HKEY_CLASSES_ROOT\CLSID{D03D3E7D-0C44-3D45-B15F-BCFD8A8B4C7E}\ProgID]
                                          @=“pashlexte64.zipfile”


                                          Fastest way for me to reproduce the bug:
                                          Browse folders-subfolders, go back,back.
                                          Cut some content and paste it somewhere else.
                                          Cut a folder and paste it to desktop.
                                          Ceate an empty folder there where you cutted and rename it with the same name as the cutted one.
                                          Close the folder view.
                                          If it does not crash reopen and close it.
                                          This gives me the best chances to reproduce the bug.
                                          If explorer restarts (BEX64) then to get it again faster reboot the computer

                                          1 Reply Last reply Reply Quote 1
                                          • M
                                            Mili conexware last edited by

                                            I think I have been able to reproduce it finally, by doing the step by step as you have mentioned.
                                            Will screen record it now and log it in for fixing

                                            1 Reply Last reply Reply Quote 1
                                            • M
                                              Mili conexware last edited by Mili

                                              After further testing, we have been able to reproduce the explorer crash even when PA shell is disabled in shellex as well as the two reg paths deleted.

                                              Initial tests did not reproduce the crash when PA shell was disabled but further testing today, while recording it on video, reproduced the crash when PA shell was disabled also.
                                              The crash does not mention PA Shell or BEX64.
                                              Are you still getting a PA Shell/BEX64 error when explorer crashes?

                                              Regardless, we are still logging this issue in for the dev team to check out

                                              1 Reply Last reply Reply Quote 0
                                              • F
                                                f16akias @f16akias last edited by f16akias

                                                With PA uninstalled plus those 2 leftover registry entries manually deleted I got no BEX64 error, explorer crash for over a week doing exactly the same actions.
                                                With it installed I got 7 BEX64 errors (no other crash) like the one below in 5 hours (after each bex64 I rebooted my pc)

                                                @f16akias said in PowerArchiver shell extensions possibly crashing windows explorer.exe:

                                                Unfortunately I received again a BEX64 error with PA 20.00.58, just by cutting a folder, pasting it at desktop, then creating an empty folder at the initial origin and renaming with original name.

                                                Using Greek Windows 10 (English Translation)

                                                Περιγραφή (Description)
                                                Διαδρομή ελαττωματικής εφαρμογής (Faulting Application Path):	C:\Windows\explorer.exe
                                                
                                                Υπογραφή προβλήματος
                                                Όνομα συμβάντος προβλήματος (Problem Event Name):	BEX64
                                                Όνομα εφαρμογής (Application Name):	Explorer.EXE
                                                Έκδοση εφαρμογής (Application Version):	10.0.19041.610
                                                Χρονική σήμανση εφαρμογής (Application Timestamp):	ab30c679
                                                Όνομα ελαττωματικής λειτουργικής μονάδας (Fault Module Name):	StackHash_4fe4
                                                Έκδοση ελαττωματικής λειτουργικής μονάδας:	0.0.0.0
                                                Χρονική σήμανση ελαττωματικής λειτουργικής μονάδας:	00000000
                                                Μετατόπιση εξαίρεσης (Exception Offset):	PCH_E5_FROM_ntdll+0x000000000009C8F4
                                                Κωδικός εξαίρεσης (Exception Code):	c0000005
                                                Δεδομένα εξαίρεσης (Exception Data):	0000000000000008
                                                Έκδοση λειτουργικού συστήματος (OS Version):	10.0.19041.2.0.0.768.101
                                                Αναγνωριστικό τοπικών ρυθμίσεων (Locale ID):	1032
                                                Πρόσθετες πληροφορίες 1:	4fe4
                                                Πρόσθετες πληροφορίες 2:	4fe48443420d2e8d4afe531d780de425
                                                Πρόσθετες πληροφορίες 3:	c3ef
                                                Πρόσθετες πληροφορίες 4:	c3eff943408f9e455a715ed80d35b4ab
                                                
                                                Περισσότερες πληροφορίες σχετικά με το πρόβλημα
                                                Αναγνωριστικό κάδου:	dace8c8bdbc6cc651b643f81476063fc (1973772361175950332)
                                                

                                                Again my notices:

                                                1. I have disabled the Windows explorer preview option (the one that has a preview option on the right side of the window)
                                                2. It does not matter if I select from PA options to enable-disable the shell extensions. BEX64 will continue. If I manually disable ALL PA extensions via ShellExView (right click all PA context entries plus those 2 mentioned above, disable) then I get no BEX64.
                                                3. My only other entries in the context menu are Nero, Notepad++ and Avast.
                                                4. Firstly I tried with all non Microsoft entries disabled. Then enabling 1 at a time.
                                                5. I spent a lot of time testing this, now I am enabling some PA entries and spend more time before I conclude if crash occurs-will occur or not, before I return here and write something.
                                                6. Funny thing is that PowerArchiver as an app works perfectly. The cause are the loaded dlls messing with explorer.exe

                                                Please keep testing and debugging as this error is not so informative but seems that something cause those dlls to crash explorer.
                                                One though and only guessing, nothing else is if something in those dlls looks for files-paths and when I cut them or create a folder that existed messes up things. Just a user experience thought…

                                                1 Reply Last reply Reply Quote 1
                                                • M
                                                  Mili conexware last edited by

                                                  Thanks @f16akias
                                                  Added this latest information to the logged in bug report, let’s try it with the next update, coming up soon

                                                  F 1 Reply Last reply Reply Quote 0
                                                  • F
                                                    f16akias @Mili last edited by

                                                    Do we have any progress on that?

                                                    1 Reply Last reply Reply Quote 0
                                                    • D
                                                      davidsplash @U1zy3o2ih5ebk2F last edited by

                                                      @u1zy3o2ih5ebk2f not to beat around the bus do you have specs of your computer like hardware chips and motherboard and bios. Then detailed list of programs on your computer and drivers.

                                                      use this program and send powerarchiver the files its generates and this should help them better

                                                      http://www.parmavex.co.uk/winaudit.html

                                                      F 1 Reply Last reply Reply Quote 0
                                                      • F
                                                        f16akias @davidsplash last edited by f16akias

                                                        @davidsplash as you imagine this user might has deleted his account.
                                                        Moreover I personally assisted one of PA’s programmer by testing and providing feedback. My support lasted 36 days and ended (with successful tracking of the bug from their side) at 6th December 2020.
                                                        I still wait and have NO feedback from them…

                                                        D 1 Reply Last reply Reply Quote 0
                                                        • D
                                                          davidsplash @f16akias last edited by

                                                          @f16akias The problem is they found the bug but do not know why it is doing it on your system and not others. That’s why I suggested using Winaudit program to give them what’s on your system, so they can see why you have. Finding bugs is one thing fixing them is another. I don’t have that crash and i’m on windows 10 but I have a HP computer. I know they have found the error but thats a start knowing what caused it is another.

                                                          F 1 Reply Last reply Reply Quote 0
                                                          • F
                                                            f16akias @davidsplash last edited by f16akias

                                                            @davidsplash
                                                            Ok of course to give more information again.

                                                            1. Just to make it clear, @U1zy3o2ih5ebk2F is someone else and you replied to him (last post from that user years ago. Most probably deleted account due to frustration…).
                                                            2. I 'll help again by providing what’s required. I just don’t get why I got NO feedback from them since December and why they don’t ask for help since they need it as you mentioned. I don’t charge for it neither I asked for a free license.

                                                            Will send required info later. Btw I am on HP Windows10. Seen it also on Asus win10 and my company desktops when they had it installed

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

                                                              @f16akias said in PowerArchiver shell extensions possibly crashing windows explorer.exe:

                                                              @davidsplash
                                                              Ok of course to give more information again.

                                                              1. Just to make it clear, @U1zy3o2ih5ebk2F is someone else and you replied to him (last post from that user years ago. Most probably deleted account due to frustration…).
                                                              2. I 'll help again by providing what’s required. I just don’t get why I got NO feedback from them since December and why they don’t ask for help since they need it as you mentioned. I don’t charge for it neither I asked for a free license.

                                                              Will send required info later. Btw I am on HP Windows10. Seen it also on Asus win10 and my company desktops when they had it installed

                                                              Hello @f16akias,

                                                              we closed several bugs regarding shell extensions in December. Did you have a chance to test it with latest build?

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