-
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.
-
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. -
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
-
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.
SOLVED SharpShell errors in Win 7 Event Viewer
-
Over the last few days I’ve suddenly started getting a slew of SharpShell “0” errors in the Event Viewer. These all relate to creating icons, mostly creating overlay icons. There is very little information to help with identifying what process is causing this, but by turning on some extra process creation logging, it seems that the errors all occur at the same time as PABACKUP.EXE, SearchProtocolHost.exe and SearchFilterHost.exe.
Are these in some way related?
I can upload more information, if required. -
@PA_Fan said in SharpShell errors in Win 7 Event Viewer:
Over the last few days I’ve suddenly started getting a slew of SharpShell “0” errors in the Event Viewer. These all relate to creating icons, mostly creating overlay icons. There is very little information to help with identifying what process is causing this, but by turning on some extra process creation logging, it seems that the errors all occur at the same time as PABACKUP.EXE, SearchProtocolHost.exe and SearchFilterHost.exe.
Are these in some way related?
I can upload more information, if required.is something uploading those backups you create? Like dropbox folder for instance? For instance backup could create an zip file, search engine would try to catalogue it and some upload service could create overlay icons for uploading state.
-
@PA_Fan do you know what is using sharpshell? Apparently it is SDK for building shell extensions via .NET framework.
-
@spwolf Nothing is running to upload anything, as I have all cloud applications set to run on my command only.
I’ve tried to isolate this exactly to a particular program, but it’s not easy. The Event Viewer (EV) doesn’t give any clues, and although I have turned on the Security audit process creation/termination via Group Policies, that throws up some information which is ambiguous in determining the culprit.
Process Monitor logging isn’t helpful until I can work out what to filter for, otherwise the logs are just too enormous.
I have just cleared all the logs on EV, so that Errors is zero. I then ran PA, looked at an archive, and then ran a pbs script, which ran to end.
However, the end screen for the script run was as per shot #1, with icons all over the place. This is the “flickering” and distortion I have reported before.
The EV, previously empty, now shows 15 Sharpshell errors and 1 .NET error, and all time to the running of PABACKUP.EXE.This may be coincidence, or not directly connected with PA, but I’m at a loss to see how running PA would provoke the Sharpshell errors, or what else could be running at the same time to do so.
I also have a problem where the opening screen on PA shows multiple panels, as per shot #2. If I then select an archive to open, it will appear in one of the panes - shot #3. PA is also slow to close, presumably because of the number of panes now in the screen.
I should add that I haven’t had these Sharpshell errors before on this system (i.e. years), and they seem to have arisen since 2017 was installed. I have certainly not had the icon/screen problems with PA 2016.
PS #3 is top shot, #2 middle, #1 bottom.
-
@PA_Fan sharpshell is .net library for shell… so what programs are running shell, it does not have to be a .net program though? If you look and download shellexview, you can disable individual shell extensions and figure it out that way. That should help with troubleshooting:
http://www.nirsoft.net/utils/shexview.htmlCan you please post the issue with screens into separate threads, pretty please? That way we can track it separately and fix it next week. Thats very much on us, so we would like to fix it asap. Thank you very much!
-
@spwolf
Certainly I will post into separate thread. I included them here because the Sharpshell errors seem connected with icon management and creation, and, given that the screen problem seems to be icon-connected (at least in some way), I wasn’t sure if there might be a connection. -
@PA_Fan said in SharpShell errors in Win 7 Event Viewer:
@spwolf
Certainly I will post into separate thread. I included them here because the Sharpshell errors seem connected with icon management and creation, and, given that the screen problem seems to be icon-connected (at least in some way), I wasn’t sure if there might be a connection.with link to shellexview, you will be able to manually disable various different shell extensions, and you will certainly find the issue since you wont have that many non-microsoft ones.
as to the screen issue, it is a backup bug, it doesnt have anything to do with icons in any way, it is just that backup writes wrong values in PA registry once completed and causes issues…