-
在当今的数字时代，通信变得更加快捷和高效，教育领域也不例外。 罗切斯特高中是学校采用技术来加强学生、教师和家长之间沟通的典型例子。 他们使用的最重要的工具之一是学校电子邮件系统，该系统在多个方面都大[有裨益。
首先，罗彻斯特高中的电子邮件系统允许学生和教师之间进行及时有效的沟通。 过去，学生必须依靠面对面的会议或电话与老师 沟通，这可能很耗时，而且常 工作职能邮件数据库 常导致错过消息或误解。 然而，通过学校的电子邮件系统，学生可以快速地向他们的老师发送电子邮件并得到及时的回复。 这不仅可以节省时间，还可以进行清晰简洁的交流，这对于学业成功至关重要。
a320f9d3-78c0-4c6a-b75f-8d0e1d4691cc-image.png
其次，电子邮件系统使教师能够向学生和家长发送重要更新。 罗切斯特高中每周向家长发送时事通讯，告知他们学校活动、学业进展和其他重要信息。 这有助于家长及时了解孩子的教育情况，并让他们更多地参与孩子的学业之旅。 此外，教师可以使用电子邮件系统向学生发送有关即将到来的作业、测试或活动的提醒。 这对于可能难以记住截止日期或在校外有多项承诺的学生特别有用。
-
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.
UNSOLVED PowerArchiver shell extensions possibly crashing windows explorer.exe
-
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 /scannowindicates 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.
-
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.
-
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!
-
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.
-
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.
-
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. -
@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!
-
Tried PowerArchiver 19.0 final release. This issue is still happening for me. Uninstalled for good.
-
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.
-
I have ESET Nod32 Anti-Virus installed. I have tried uninstalling this for a period of time but still experienced the same issue.
-
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.
-
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. -
@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!
-
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!
-
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”
-
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) -
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 :) -
Those dll’s should not be enabled anymore in PA 2020. Can you see location of those dlls through shellexview please?
thanks!
-
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:
-
“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” -
“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 -
-
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 -
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
-
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:
- I have disabled the Windows explorer preview option (the one that has a preview option on the right side of the window)
- 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.
- My only other entries in the context menu are Nero, Notepad++ and Avast.
- Firstly I tried with all non Microsoft entries disabled. Then enabling 1 at a time.
- 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.
- 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… -
Thanks @f16akias
Added this latest information to the logged in bug report, let’s try it with the next update, coming up soon -
Do we have any progress on that?
-
@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
-
@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… -
@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.
-
@davidsplash
Ok of course to give more information again.- 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…).
- 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
-
@f16akias said in PowerArchiver shell extensions possibly crashing windows explorer.exe:
@davidsplash
Ok of course to give more information again.- 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…).
- 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?
-
@spwolf Well I can confirm that I have never again encountered any Bex64 errors while using 20.00.73 and now 20.10.02 versions. No bex in logs nor explorer.exe restart-refresh.
@spwolf , @Mili , @ivan and the rest team thanks for solving this one, powerarchiver is again the best utility
-
@f16akias said in PowerArchiver shell extensions possibly crashing windows explorer.exe:
@spwolf Well I can confirm that I have never again encountered any Bex64 errors while using 20.00.73 and now 20.10.02 versions. No bex in logs nor explorer.exe restart-refresh.
@spwolf , @Mili , @ivan and the rest team thanks for solving this one, powerarchiver is again the best utility
Thank you so much for your great bug report and all the version checks!
