-
-
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).
-
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.
-
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 -
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.
-
In PowerArchiver 2023 22.00.06 configuration, the option labelled “Start PowerArchiver 2023 Starter when my computer starts” seems to be redundant.
I am only allowed to change this option when PA Starter is disabled, and then it seems to be ignored.
When I enable PA Starter this option is forced to the enabled state.
I think it’d be good to remove “Start PowerArchiver 2023 Starter when my computer starts” completely. I’ve always found it confusing having both options.
Added later: However i don’t particularly want to use queue but I do like having the PAStarter icon in my tray area.
-
W10 Pro 22H2 - 64 -bit
PA 22.00.06 (PA 2023)
It has been the case with previous versions of PowerArchiver, but I had hoped that the latest might behave differently. Not so, I’m afraid.
I have, for various obscure reasons, created a few .pa archives, mainly in the hope that they will save me some more space. From time to time, I use the “Test” option to check that important archives are OK and uncorrupted.
With every .pa archive I’ve tested, the process runs through OK but then reports that there are errors. This is always the number of files in the archive e.g. if 11 files, then 11 errors reported.
In the .pa, I can:-
preview the files (usually PDF) extract some or all files and look at or use them convert the .pa to a .zip or .zipx archive, which then works fine and tests without errorsIs it the case that the Test routine isn’t designed for .pa archives, or is there another reason? Although the .pa seems to function properly, despite the test reporting errors, I would like to be sure that every .pa is OK and not “broken”.
Some of the .pas are quite old and produced with earlier PA versions (they are truly “archives”). If I extract all the files in the old .pa, create a new, fresh .pa and add back the files to that, then test the new, no errors (at least in the .pa I’ve tried this on) are reported. This would suggest a mismatch between old .pas and newer versions of PA itself.
-
Clipboard02.jpg
See the, supposedly, blank space where the green box is? It’s like that in Modern Light theme too. I can toggle it, but it’s missing text or shouldn’t be there I guess?
Thanks :)
-
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
Cannot restore from a backup
-
I am running PA 16.00.56 (01/2016).
I have not had much need to restore from backups, but recently I did, I needed to restore a VM. Part way through, I got a message about a CRC error on a file., and if I continue the VM will not load. The original VM loads ok. Today, I made sure the VM was closed in case that caused a problem, ran the backups, and tried to restore, again got a CRC error, and attempts load generate a dictionary problem.
I have gone back and repeated this on 3 or 4 previous backups with the same result.
I checked the logs from today’s backup, could not see any errors.
So I have no backups???
Any ideas???
-
I have checked the host driver for errors, all ok.
-
I can copy the VM to another directory and it loads ok.
None of my VMs with Win 10 as the guest will reload from backup. Win 7 VMs work ok.
-
I can copy the VM to another directory and it loads ok.
None of my VMs with Win 10 as the guest will reload from backup. Win 7 VMs work ok.
what VM software? I know vmware asks when open up vm from backup if you moved it (from other computer) or copied it (from same computer).
-
VMWare Workstation 12 Player … but it is not getting to there, each time I use PA to backup a VM that is working, then try to restore it I get CRC errors.
-
VMWare Workstation 12 Player … but it is not getting to there, each time I use PA to backup a VM that is working, then try to restore it I get CRC errors.
its running during backup? You should try forcing VSS for those files. I am not sure what kind of exclusive access mode is VMP using when running, but it might doing some tricky stuff thats preventing proper access (however it should work with VSS option).
-
See my post above " Today, I made sure the VM was closed "
-
See my post above " Today, I made sure the VM was closed "
i saw both posts, so what does “that is running” refers to? I will have to test it on our lab computer, I dont have Win10 right now only older OSs like Win7, Xp… even 98SE (in VMware)
-
“That is running”? Sorry, I cannot see that.
-
“That is running”? Sorry, I cannot see that.
sorry, it says “that is working” not running, I figured out thats what you meant… did you mean simply a VM that works properly when run?
-
Yep, I can load from the original and it “works”.
I have taken the external drive out of it, I used PA to back up a Win 10 VM guest (VM not running) to my HDD, then restored to another directory, CRC error.
The file that gives the error varies from restore to restore.
-
I would offer to ftp the files … but is 50gigs
-
Yep, I can load from the original and it “works”.
I have taken the external drive out of it, I used PA to back up a Win 10 VM guest (VM not running) to my HDD, then restored to another directory, CRC error.
The file that gives the error varies from restore to restore.
but win7 VM works fine? What is the size of those? Also, what format did you use in backup?
-
Ok, a bit of progress. This time, to restore, I used File Explorer, ie Windows, rather tha PA … and it worked !!! I feel a bit happier, I have backups again!!!
Yep, restoring of Win 7 guest VMs work, I have restored them before, this was the first Win 10 - only been using Win VMs for a few months.
Win 10 VM (size on host) is 53.6G, Win 7 is 86.2G
Format? All defaults I think, it says Format ZIP (recommended) Backup Type Normal, Method Deflate, Compression Fast, Use current folder as temp is selected, Spanning No
-
Ok, a bit of progress. This time, to restore, I used File Explorer, ie Windows, rather tha PA … and it worked !!! I feel a bit happier, I have backups again!!!
Yep, restoring of Win 7 guest VMs work, I have restored them before, this was the first Win 10 - only been using Win VMs for a few months.
Win 10 VM (size on host) is 53.6G, Win 7 is 86.2G
Format? All defaults I think, it says Format ZIP (recommended) Backup Type Normal, Method Deflate, Compression Fast, Use current folder as temp is selected, Spanning No
interesting… everything works fine with the backup?
-
From memory, the dialog said backup completed ok, I looked through the logs, couldn’t see anything, searched for “error”, nothing.
If I can restore with Explorer, doesn’t that mean the backup is ok?
And the one that started it all, normal weekly backup to an external hard drive, that kept coming up with crc errors … just restored it ok with explorer, VM loads it ok.
-
From memory, the dialog said backup completed ok, I looked through the logs, couldn’t see anything, searched for “error”, nothing.
If I can restore with Explorer, doesn’t that mean the backup is ok?
And the one that started it all, normal weekly backup to an external hard drive, that kept coming up with crc errors … just restored it ok with explorer, VM loads it ok.
if VM loads it ok, then it is fine.
-
There is a file Development.vmsd (Development is the name of the VM). Using Explorer it shows in the zip as 0 bytes. It restores ok as zero bytes. Using PA, it shows zero in the ZIP. Attempting to restore generates a crc and a file with 467KB. If an attempt is made to restore that file and it already exists, the warning says it is 4,294,967,295 bytes … hhmmm where do I know that number from? :)
-
Win 7 VMs do not seem to have zero length files, at least none of mine seem to, but Win 10 VMs do … and that seems to be the problem in PA.
Also, try opening up a zip file in PA, drill down a few directories, then keep clicking the up arrow to go to the parent directory … one too many and PA hangs.
-
Win 7 VMs do not seem to have zero length files, at least none of mine seem to, but Win 10 VMs do … and that seems to be the problem in PA.
Also, try opening up a zip file in PA, drill down a few directories, then keep clicking the up arrow to go to the parent directory … one too many and PA hangs.
Please try latest update:
http://dl.powerarchiver.com/2016/powarc160063.exeThis should fix the fake CRC error bug. Thanks for reporting it in!
-
CRC problem is fixed … but VM will not load, the old dictionary problem. Good but no cigar!
The Development.vmsd file, shows in Ex in zip as zero bytes, PA restored it as 467K.
Trying a restore using Ex …
-
Restore using Explorer worked.
-
Copied vmsd from Explorer restore to PA restore, VM loads ok.
Your turn!
-
Please check with this latest release:
http://dl.powerarchiver.com/2016/powarc160064.exeWe didnt have much time to test it, seems fine so far in my testing.
-
Looks good … restores without a crc, destination file is zero, VM loads.
Thank you.
Ken
-
Let us know via email to extend your Select plan (if you dont have one, we will create it for you), this was definitely bug find of the month!
Pretty tricky, everything was compressed fine but extract did not work on 0 byte files if they were stored after 4 GB position in the zip archive (if they were saved before 4 GB in 100 GB archive it was fine). Thanks a lot once again!
-
I could not find an email, so I sent a PM a while ago.
-
I could not find an email, so I sent a PM a while ago.
we extended it as soon as you sent the PM…. thanks!
-
Why didn’t I think of this post earlier … :(
Yesterday I needed to restore a VM … restored would not load … dictionary error, so do research, nothing works … :(
Then I find a file Development.vmsd, which should be zero in size, is restored as 4,294,967,296 bytes … hhmm I remember that :(
Running PA 16.10.14.
Rest of info as per the top of this thread :)
-
can you quickly try with older release again?
http://dl.powerarchiver.com/2016/powarc160064.exethanks!
-
Installed old version, restored whole VM from backup, file is zero, VM loads perfectly.
-
Please try with this release:
http://www.powerarchiver.com/test/release16/powarc161018.exeAnd let us know. Thank you!
-
Been away, then a new server …
Should be trying thus tomorrow. -
there is later version (.21):
http://www.powerarchiver.com/forums/showthread.php?p=35188thanks!
-
Downloaded and installed new version, ran a backup of VM files, then did a restore … 0 file is zero! VM loads ok.
Thanks.