-
PA Queue does not compress file optimally with same parameters if used in Queue mode.
Being able to save advanced option, and set a default profile and archive type for compression so I can save clicks.
The above two are majorly affecting my efficiency with archiving stuff with PA 20.10.03.
Can someone confirm if they are resolved with the 2022 RC1?
-
Hi,
I thought, I’ll give it a try and upgrade my PA 2018 Toolbox on my production machine to PA 2021 (20.10.03)
Sending registration codes in your order recovery doesn’t seem to work at the moment (I also checked my junk folder), online activation works Using registry to disable modules (for example HKLM\SOFTWARE\PowerArchiverInt\General\DisableBurning) doesn’t work as expected with modern ui. The module is visible, but I’ll get the trial nag, if I try to open it. It’s almost fine in classic and ribbon mode.7989017c-3cd2-4a99-a1f6-06ce62329dec-image.png
“DisableClouds” and “DisableExplorer” seem not to be respected at all, while the classic UI seems to respect the setting to disable any other unused module:
In settings I won’t be able to access the SmartAI settings and the settings for the internal editor if the FTP module is disabled
89843f23-ad89-45bf-92bc-406b1a11dfc9-image.pngcc40877b-d8d0-404c-b7f8-d5ae0a1ee445-image.png
-
I’m running W10 Pro on an HP i-7 machine with now 32gb of RAM. The system drive is an SSD.
In the course of sorting out some inconsistencies in a couple of my .pbs jobs, I’ve been paying close attention to the system CPU resource and power consumption of PA Starter, as shown by the various resource management tools. I’ve also been trying to identify why my system seems rather sluggish despite some extensive tuning for speed etc.
When I have enabled Starter as a start-up programme, to use the PA Queue facility, I see that Starter consistently uses between 10-13% of CPU, with High Power consumption indicated. It runs, consuming this resource, irrespective of what may be happening with PA and any pbs script jobs.
I can understand a need to use a good chunk of CPU when Starter is actually handling PA jobs, but it shouldn’t sit and consume this amount when it really isn’t doing anything but wait for a job to start and for which it is needed.
Perhaps I’ve missed a way of lessening Starter’s impact, but in the meantime I’ve adjusted my set-up to running PA without it.
Suggestions, please.
-
Bug: When I use the right button on any folder to bring up the menu and click on e.g. compress or decompress, the program still requires registration even if it is correctly registered. When working with the folder, via the running Power Archiver, everything is fine. (Windows 10 - v. 20.10.03)
-
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
-
Hi,
The window size is suddenly “large” Resizing the window to normal size works for the current action, but isn’t remembered The next time I’m using the shell extension, the window is large again, so it seems the size change isn’t saved
I’ve got a strange behavior with the progress window in PowerArchiver 2021 shell extension:The progress window of PowerArchiver itself has its normal size.
Is there a possibility to reset the shell extension window size?
-
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.pdfCan 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.
-
Windows 10 extraction does a better extraction job than Power Archiver which chooses not to work much of the time. I’ve tried uninstalling/reinstalling it
Version 20.10.03
-
The support doesn’t answer my email about a license question for weeks, because despite a lifetime license Powerarchiver refuses some functions
-
Scusate non so a chi rivolgermi, ho regolarmente pagato tramite Poy Pol ma non mi è pervenuto il codice di attivazione, ho quello vecchio ma presumo che non sia più valido, a chi devo rivolgermi?
Spero che mi possiate aiutare indicandomi cosa devo fare.
Grazie -
I have a “USB2.0” DVD-RW drive with a blank 700MB CD-R inserted.
Windows 10 sees in just fine explorer and it’s usable, and works.
However it is not showing in any dropdown in PowerArchiver.Thanks for any help…
PowerArchiver 20.10.02 (05/2021) 64-bit
Windows 10 Pro
20H2 build: 19042.1348
Windows Feature Experience Pack 120.2212.3920.0 -
I’m using 20.10.02. When I try to drag files from an opened zip to a folder in Windows File Explorer, PA does nothing. It uses a CPU core and starts the clock, but no action is taken. I have to end task in task manager to get it to close.
-
6e4196e6-d59c-4870-b27e-80c5ae60e4d7-image.png
see image. the bottom of yes and no are cut off
-
Will PA 2022 still support windows 10 as majority of people can’t upgrade and won’t till 2025
-
Hello,
PowerArchiver Command Line 7 support file greater than 2 Go ?
Thanks
-
I’ve found a bug when trying to test an encrypted, 28-volume 7-zip archive of a 18.3 GB folder containing 41,751 files. The test fails, showing errors in all files.
Here’s the folder I compressed, and the 28 resulting files:Archives
Here’s the multi-volume compressed file opened in PA, showing the total file count and the full archive size:Opened in PowerArchiver
And here’s the test results screen after I click Actions -> Test…, showing an incorrect file count and archive size (this seems to be the file size of the first volume alone):Testing results
One important detail about the test screen above is that PA opens an UAC prompt asking for privileged execution before starting the test. Is this the expected behavior? It seems PA wouldn’t need higher execution privilege since everything it’s touching is owned by my own user.
In any case, granting or denying the UAC prompt results in the exact same screen.
Now, if instead of testing the archive I tell PA to extract the contents, the operation works fine (and with no UAC prompts):Extracting
With the Properties panel for both folders, the original and the extracted one, showing the exact same file count and total size:Extract results
I hope this helps. 🙂
-
Hi,
Currently on the 2021 20.00.55, updated, and licensed.
I have been facing this issue since 2019 version.
Queues don’t actually do anything
That I run powerarchiver starter as admin, or without admin.Then I queue some files, and most of the files take forever, to go from 1% to 2%
and let’s say if the 5th of total 10 files are stuck that should mean the other 4 should be completed, but no, the directories are just like that.
Using Queue feature makes the Powerarchiver to process and compress files, but the PA archives do no appear, neither the disk’s total used space changes.
However if I manually compress files without queuing, no matter if I run multiple compression or one by one, there’s always success.
sometimes compression is stuck at certain percentage for a 50 or 200 MB file, forever.
I want to speed up multiple compression, I find the batch compression feature useless, as I cannot configure any custom parameters or advanced option under PA archive format
So, Let me save parameters(Advanced Option) of Profiles
i) Either I should be able to customize PA Default profile, so I don’t have to select files and manually select profile, but not even single parameter can be saved
ii) Or I should be able to create a new profile and be able to set that as default.
It’s end of 2020 and I have been trying to reach Powerarchiver team to add this, but no one wants to listen or do anything.Refer case PA-FCW-TLNFM-096
I still cannot save parameters under advanced options like DDL/EXE filter to delta, or PNG PDF Filter, or set zlib to 9 or dictionary size or experimental stuff.
Soo many Revisions and versions released but I still cannot have a profile saved with whatever I want, be it existing or new profile.
Don’t you guys at Powerarchiver labs get frustrated everytime you have to configure these parameters manually?
When I stop an ongoing compression process, that is stuck or let’s say it’s not stuck but I click on cancel and then on No, it still continues compression for no reason.
If I start compression and pause, the progress bar shortly(progresses) reaches to completion, but no compression is done, and then archive is stuck forever
Just cancel itFor all my claims above I have sent ticket today with screenshots from my registered email.
if you can:
Batch archive is good idea, but if I have multiple directories inside directories, then I want first child directory to have all of it’s subdirectory compressed to that same first child directory
Example
I have a folder in D:\pics
that folder has following folder
Cats
Dogs
FishesEach of the above folder has sub folder:
Black
White
Fluffy
ColorfulI want those sub folders(black, white, colorful, fluffy) not to be compressed individually, but the cats, dogs and fishes folders to be compressed individually
-
Dear PowerArchiver Team!
As I unfortunately found out, there is a big bug in Powerarchiver, which causes the compression rate to drop really significantly! I wonder if no one has noticed this yet? Are you guys still actively developing?
The following error occurs! (This is already as I find a blatant error!).ERROR:
File extensions and formats are not recognized automatically! If a file name e.g. Mütze.jpg is simply “renamed” in Mütze.txt, or
Mütze.png, Mütze.mp3, Mütze.pdf etc. each time a DIFFERENT compression algorithm is performed on the SAME FILE! Remember! The file extension was only renamed, so the file extension e.g. from .jpg to .txt is only by Rename changed! Just take a .jpg or .txt or .pdf file and change the file extension, you will see see this error! No headers are read automatically! Is this really wanted?Then the perfect compression algorithm can never be found and optimized by PowerArchiver? You should investigate this dramatic error once absolutely!Greetings from your trusty Konglomat!
Please stay healthy and make PowerArchiver more powerful than ever! I am looking forward to future updates! You are still awesome! Please keep up the good work! I love PowerArchiver, really more than just about anything!And will probably buy and use it for eternity!
-
Configuration:
Powerarchiver 2021 20.00.73
Windows 10 Education 10.0.19042 Build 19042When 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 freeWhen 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.
-
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
SOLVED Windows 10 pro - Explorer crashing
-
I started having Windows explorer crash for no obvious reason, I even did a re-install of the OS. I could not replicate the exact action, that made explorer crash, it seems random. I have over time updated versions and today having check event logs I found “PASHLEXT64.DLL” to be at fault. I have uninstalled powarc170048 and are now trying powarc170050. below is copy of event log relating to crash.
Faulting application name: explorer.exe, version: 10.0.14393.479, time stamp: 0x58258a90
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.8.1, time stamp: 0x588786cc
Exception code: 0xc0000005
Fault offset: 0x00000000000f3970
Faulting process id: 0x2fac
Faulting application start time: 0x01d287e476cc7480
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: d1e246b4-12e2-4de3-8e78-b45b3c4035e2
Faulting package full name:
Faulting package-relative application ID:I hope this helps.
-
I’ve seen instances of Windows Explorer restarting lately, noticeable by icons disappearing from notification area.
I didn’t even think that PA may have been the cause of it, but yes looking in the events log I see the same report as you.
Good catch. -
Add more crashes, running windows 10 pro 1607 build 14939.693.
Faulting application name: explorer.exe, version: 10.0.14393.479, time stamp: 0x58258a90
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.8.1, time stamp: 0x588786cc
Exception code: 0xc000041d
Fault offset: 0x00000000000f3970
Faulting process id: 0x1624
Faulting application start time: 0x01d28928b6e20165
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: 6f828dcc-1190-4b7a-bf66-ae79ee30646c
Faulting package full name:
Faulting package-relative application ID:Faulting application name: explorer.exe, version: 10.0.14393.479, time stamp: 0x58258a90
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.8.1, time stamp: 0x588786cc
Exception code: 0xc0000005
Fault offset: 0x00000000000f3970
Faulting process id: 0x1624
Faulting application start time: 0x01d28928b6e20165
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: 95f19e94-9eab-4890-99ef-2698208f5070
Faulting package full name:
Faulting package-relative application ID: -
@Tyjen007 @Luxor We have been playing with this lately, it should be a focus for one of the future builds. Until then, please check Shell options, and uncheck Enable Archive Hints and Enable Archive Property Sheets. That seems to be causing it, but it is hard to catch for now.
Please uncheck those and lets see what happens. Thank you!
-
@spwolf said in Windows 10 pro - Explorer crashing:
We have been playing with this lately, it should be a focus for one of the future builds. Until then, please check Shell options, and uncheck Enable Archive Hints and Enable Archive Property Sheets. That seems to be causing it, but it is hard to catch for now.
Not helped by being so random I would imagine.
I think I’ve mostly noticed it happening after I have been using PA and my external usb drive at the same time. When I click on the usb icon in the notification area to remove the drive, that’s when it occurs.
@spwolf said in Windows 10 pro - Explorer crashing:
Please uncheck those and lets see what happens. Thank you!
Done!
Windows 10 Home 64-bit
Intel Core i7 6700HQ @ 2.60GHz
12.0GB Dual-Channel DDR3 @ 798MHz -
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
We have been playing with this lately, it should be a focus for one of the future builds. Until then, please check Shell options, and uncheck Enable Archive Hints and Enable Archive Property Sheets. That seems to be causing it, but it is hard to catch for now.
Not helped by being so random I would imagine.
I think I’ve mostly noticed it happening after I have been using PA and my external usb drive at the same time. When I click on the usb icon in the notification area to remove the drive, that’s when it occurs.
@spwolf said in Windows 10 pro - Explorer crashing:
Please uncheck those and lets see what happens. Thank you!
Done!
yeah, it happens only sometimes. Did you have any occurance since you changed those options?
-
@spwolf said in Windows 10 pro - Explorer crashing:
Did you have any occurance since you changed those options?
Not so far, will probably have a better idea if it helps after a few days of use.
Windows 10 Home 64-bit
Intel Core i7 6700HQ @ 2.60GHz
12.0GB Dual-Channel DDR3 @ 798MHz -
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
Did you have any occurance since you changed those options?
Not so far, will probably have a better idea if it helps after a few days of use.
thanks, we will likely have a special debug for dll by end of next week.
-
Three days of use with these changed options and no explorer crashes so far.
Windows 10 Home 64-bit
Intel Core i7 6700HQ @ 2.60GHz
12.0GB Dual-Channel DDR3 @ 798MHz -
@Luxor said in Windows 10 pro - Explorer crashing:
Three days of use with these changed options and no explorer crashes so far.
good to know… next update will have these disabled in the code + soon enough I expect us to have debug dlls that give us hopefully enough information. Thanks!
-
Just applied the directions will reboot and give it a few days testing before further comments. random crashing has been ongoing, hopefully this fix is the answer. Also of note in my case, “enable archive hints” was enabled so I disabled it. “enable archive property sheets” was already unchecked. So at present only “use explorer shell extensions” and enable explorer preview" are left enabled.
-
@Tyjen007 please check patchbeam, fast ring update and you will get latest release - .55. It has these disabled internally, and lets see what happens. Thank s a lot!
-
@spwolf said in Windows 10 pro - Explorer crashing:
It has these disabled internally
Does that mean if we selected them that they would do nothing, or does it mean that if you have them selected it will deselect them?
Windows 10 Home 64-bit
Intel Core i7 6700HQ @ 2.60GHz
12.0GB Dual-Channel DDR3 @ 798MHz -
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
It has these disabled internally
Does that mean if we selected them that they would do nothing, or does it mean that if you have them selected it will deselect them?
It won’t do anything… Sometimes when you uncheck it, parts of code are still working since it is part of same dll. So this is truer off.
-
@spwolf Thanks, it’s good to know these sort of things. :)
-
2-25-2017 11.44.47am crash…
Faulting application name: explorer.exe, version: 10.0.14393.479, time stamp: 0x58258a90
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.8.1, time stamp: 0x588786cc
Exception code: 0xc000041d
Fault offset: 0x00000000000f3970
Faulting process id: 0x2ac4
Faulting application start time: 0x01d28f8399fd117c
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: e8f0bc40-6357-4c3b-a096-daabe711d702
Faulting package full name:
Faulting package-relative application ID:Just checked shell extension options in PowerArchiver:
check = use explorer shell extensions
check = enable explorer preview
uncheck = enable archive hints
uncheck = enable archive property sheets.I don’t use the preview pane in windows explorer at, I only use the details pane.
I’m going to turn off the "enable explorer preview option in PowerArchiver and see if that stops the crashes. Will update. -
@Tyjen007 did you check latest .55 release via patchbeam?
-
17.09.0 is latest dll, lets see what happens with that one. Thanks!
-
Thank you I’ll try that version.
-
we had report from @keith via email that we could be reproduced and could be similar to this… hopefully it is. Spent whole day troubleshooting it, we are getting closer but still not fixed. Maybe new build with fix tomorrow? We will see. Thanks for reports.
-
Looking forward to new update.
Still running latest built powarc170055
Side note:
I now run windows explorer option “launch folder windows in a separate process”, this helps, since the fault is random. Now it does not crash all “windows explorer” windows that are open, just the process “window” that it does crash in.
Also I went for and are now using Windows 10 pro 15048.rs2_release. 170228-1522, mainly to see if PowerArchiver behaved with no issue in newer build. As it stands I have had few crashes but not as many as running the existing version in general use.I’ll post crash info if it starts being too regular again.
-
@Tyjen007 said in Windows 10 pro - Explorer crashing:
Looking forward to new update.
Still running latest built powarc170055
Side note:
I now run windows explorer option “launch folder windows in a separate process”, this helps, since the fault is random. Now it does not crash all “windows explorer” windows that are open, just the process “window” that it does crash in.
Also I went for and are now using Windows 10 pro 15048.rs2_release. 170228-1522, mainly to see if PowerArchiver behaved with no issue in newer build. As it stands I have had few crashes but not as many as running the existing version in general use.I’ll post crash info if it starts being too regular again.
we managed to reproduce one issue even with latest build. So we have made some changes and they will be available in next build. Lets see if it crashes ever again. We are waiting for few other things to come in and it will be published then. Thanks!
-
these crashes noted below are when doing a right click (copy and then paste) before competing operation, crash occured…
Faulting application name: explorer.exe, version: 10.0.15048.0, time stamp: 0xa6dd583e
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.9.0, time stamp: 0x58a6fb56
Exception code: 0xc0000005
Fault offset: 0x00000000000f38e0
Faulting process id: 0x3378
Faulting application start time: 0x01d296a3856ca7d2
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: 8328a8ee-76cc-4c9a-a960-2871661fff0b
Faulting package full name:
Faulting package-relative application ID:Faulting application name: explorer.exe, version: 10.0.15048.0, time stamp: 0xa6dd583e
Faulting module name: PASHLEXT64.DLL_unloaded, version: 17.0.9.0, time stamp: 0x58a6fb56
Exception code: 0xc0000005
Fault offset: 0x00000000000f38e0
Faulting process id: 0x3378
Faulting application start time: 0x01d296a3856ca7d2
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: PASHLEXT64.DLL
Report Id: 8328a8ee-76cc-4c9a-a960-2871661fff0b
Faulting package full name:
Faulting package-relative application ID:times are 2 seconds apart
-
@spwolf said in Windows 10 pro - Explorer crashing:
We are waiting for few other things to come in and it will be published then.
Shall we enable them now in build 17.00.57 or is it too soon?
Windows 10 Home 64-bit
Intel Core i7 6700HQ @ 2.60GHz
12.0GB Dual-Channel DDR3 @ 798MHz -
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
We are waiting for few other things to come in and it will be published then.
Shall we enable them now in build 17.00.57 or is it too soon?
there is .59, now it is really completely disabled by default. It seems like loading our dll into shell for display of files with latest Win10 causes crash… just loading the dll without actually using it. So MS changed something in past 3 months, maybe it is a bug or maybe it is a security feature, we dont know right now. But there should be no crashing anymore.
-
@spwolf said in Windows 10 pro - Explorer crashing:
there is .59
Didn’t notice that, just got it on patchbeam.
@spwolf said in Windows 10 pro - Explorer crashing:
now it is really completely disabled by default. It seems like loading our dll into shell for display of files with latest Win10 causes crash… just loading the dll without actually using it. So MS changed something in past 3 months, maybe it is a bug or maybe it is a security feature, we dont know right now. But there should be no crashing anymore.
I’ve not had a single crash in explorer since it was disabled that’s for sure.
Windows 10 Home 64-bit
Intel Core i7 6700HQ @ 2.60GHz
12.0GB Dual-Channel DDR3 @ 798MHz -
@Luxor said in Windows 10 pro - Explorer crashing:
@spwolf said in Windows 10 pro - Explorer crashing:
there is .59
Didn’t notice that, just got it on patchbeam.
@spwolf said in Windows 10 pro - Explorer crashing:
now it is really completely disabled by default. It seems like loading our dll into shell for display of files with latest Win10 causes crash… just loading the dll without actually using it. So MS changed something in past 3 months, maybe it is a bug or maybe it is a security feature, we dont know right now. But there should be no crashing anymore.
I’ve not had a single crash in explorer since it was disabled that’s for sure.
We found some way to reproduce it when just right clicking on .pa file which just loads the dll. And some other users reported it happening with zip and 7z files too. All this worked fine for years in Win7, 8 and 10. And on our main build computer, with final Win 10.1 build, it never crashes either. So it is one of the builds afterwards that changed something.
Since .59 release disabled it in .zip/.7z and all other formats, there are no more issues report by any of the users we sent it to. So definitely something on MS side.
Once PA 2017 is released in final form, we can spend some time investigating the issue. Thanks!
-
Looking forward to trying 59 version. I will say I have seen less crashes in the latest Insider preview Windows 10, that may also just be a side effect of using newer versions of the program. When I do get crashes I have verified that PASHLEXT64.DLL is the fault/reason. I wish it was it was as simple as saying while doing (insert action) that was the reason. And as spwolf states, this is a new bug that did not happen in prior versions of the app or OS. What is weird is you would expect the call for the DLL to be the issue when you right click on a file/ folder and the context menu would be calling the ddl for action to be offered. Yet windows explorer can crash with a open window and no active action taking taking place within the open window as your using an app. As noted above , I now run separate instances of explorer, so when one instance will crash, the other(s) will stay open. Which may mean, in the context cashing its’ is not always a system wide issue. Could that mean its how its called and held in memory for each instance? I have tried (completely disabled the context menu calls to the DLL), and had no crashes (as to be expected) but I want the functionality that is provided. rather than having to open the app and browse to the file/folder that I wish to complete a task. We’ll see what happens.
-
@Tyjen007 said in Windows 10 pro - Explorer crashing:
Looking forward to trying 59 version. I will say I have seen less crashes in the latest Insider preview Windows 10, that may also just be a side effect of using newer versions of the program. When I do get crashes I have verified that PASHLEXT64.DLL is the fault/reason. I wish it was it was as simple as saying while doing (insert action) that was the reason. And as spwolf states, this is a new bug that did not happen in prior versions of the app or OS. What is weird is you would expect the call for the DLL to be the issue when you right click on a file/ folder and the context menu would be calling the ddl for action to be offered. Yet windows explorer can crash with a open window and no active action taking taking place within the open window as your using an app. As noted above , I now run separate instances of explorer, so when one instance will crash, the other(s) will stay open. Which may mean, in the context cashing its’ is not always a system wide issue. Could that mean its how its called and held in memory for each instance? I have tried (completely disabled the context menu calls to the DLL), and had no crashes (as to be expected) but I want the functionality that is provided. rather than having to open the app and browse to the file/folder that I wish to complete a task. We’ll see what happens.
Yes, the compression dll is loaded for preview shell function only, but it is loaded first time you right click on shell. And new builds of Win10 dont like it. Same dll has been used for ever since we added that functionality.
.59 is on Patchbeam and you can try it to confirm thats it.
In one of the future builds, we will add preview functionality back in, but we will not use external dll anymore for these functions, but we will build it inside initial .dll, since even if Microsoft fixes the issue (which is possible), there will still be many preview builds out there with the issue.
However rest of shell functionality is unaffected. Thanks.
-
Since Creators update is coming out soon, I decided to keep going with newer versions of the Windows 10 Pro x64 OS, I’ve been running 15055.rs2_release.170307-1445 with PowerArchiver build 59. And I started to see fewer crashes. I have just updated to 15060.rs2_release.170314-1527 along with PowerArchiver version 61. I’ll clear my event logs and watch check for issues. and report back in a few days. Thanks spwolf for feedback and a great product.
-
I’ve been checking event viewer, and have seen no crashes related to PASHLEXT64.DLL for nearly a week. I’m running PowerArchiver version 17.00.63 (03/17) 64bit and have recently upgraded to windows 10 1703 (Build 15063.rs2_release.170317-1834). What ever work that was done by ConeXware, seems to have addressed the crashing issue. Unless anything changes I would say, we can assume the issue (as far as my situation) is resolved. Thank you spwolf for your prompt responses.
-
@Tyjen007 said in Windows 10 pro - Explorer crashing:
I’ve been checking event viewer, and have seen no crashes related to PASHLEXT64.DLL for nearly a week. I’m running PowerArchiver version 17.00.63 (03/17) 64bit and have recently upgraded to windows 10 1703 (Build 15063.rs2_release.170317-1834). What ever work that was done by ConeXware, seems to have addressed the crashing issue. Unless anything changes I would say, we can assume the issue (as far as my situation) is resolved. Thank you spwolf for your prompt responses.
thank you for the feedback.
