-
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
-
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.
UNSOLVED I found a solution to OneDrive problem
-
Re: PowerArchiver 2019 Cloud is one-stop application for multiple clouds
The problem with OneDrive, which I reported about, seems to be specific only to Windows XP. I found a solution to this problem by installing one VBS script. After running this script and rebooting the system, the PowerArchiver Cloud successfully logs in to OneDrive if it is running as an Admin.
AES256_for_WindowsXP.vbs
langFixUrl = "http://www.skaip.su/aes-256-dlya-windows-xp" langGetHelp = "Хотите посетить блог автора и обратиться за помощью?" langStartApp = "Вы уверены, что хотите заменить системные библиотеки?" langNoDownload = "Не удалось скачать библиотеку {name}.dll в папку %windir%\system32" langWrongVersion = "Библиотека {name}.dll не может быть заменена, поскольку не совпадают указанные версии." langRestartPc = "Скрипт закончил свою работу, но изменения вступят в силу только после перезагрузки системы. Перезагрузить компьютер сейчас?" Set App = CreateObject("Shell.Application") Set Shell = CreateObject("WScript.Shell") Set Fso = CreateObject("Scripting.FileSystemObject") Set TypeLib = CreateObject("Scriptlet.TypeLib") Function RunAsAdministrator() If WScript.Arguments.Length = 0 Then Set Systems = WmiQuery("Select Caption From Win32_OperatingSystem") For Each System In Systems If InStr(System.Caption, "Windows XP") Then Exit Function End If Next App.ShellExecute "wscript.exe", """" & WScript.ScriptFullName & """ RunAsAdministrator", , "runas", 1 WScript.Quit End if End Function Function WmiQuery(query) Set Wmi = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2") Set WmiQuery = Wmi.ExecQuery(query) End Function Function DownloadFile(url, file) Set Http = CreateObject("Microsoft.XMLHTTP") Http.Open "GET", url, False Http.Send Set Stream = CreateObject("Adodb.Stream") Stream.type = 1 Stream.open Stream.write Http.responseBody Stream.saveToFile file, 2 End Function Function RenameDll(sourcePath, dir, name) dirPath = Shell.ExpandEnvironmentStrings("%windir%\" & dir) If Fso.FolderExists(dirPath) Then targetPath = dirPath & "\" & name & ".dll" backupPath = targetPath & "." & UNIXTIME If Fso.FileExists(targetPath) Then Fso.MoveFile targetPath, backupPath End if Fso.CopyFile sourcePath, targetPath End if End Function Function ReplaceDll(name, version, url) tmpPath = Shell.ExpandEnvironmentStrings("%windir%\system32\" & name & ".dll.tmp." & UNIXTIME) DownloadFile url, tmpPath If Not Fso.FileExists(tmpPath) Then ShowError Replace(langNoDownload, "{name}", name) WScript.Quit End if If Fso.GetFileVersion(tmpPath) <> version Then ShowError Replace(langWrongVersion, "{name}", name) Fso.DeleteFile(tmpPath) WScript.Quit End if RenameDll tmpPath, "system32", name RenameDll tmpPath, "system32\dllcache", name RenameDll tmpPath, "ServicePackFiles\i386", name Fso.DeleteFile(tmpPath) End Function Function ShowError(msg) btn = MsgBox(msg + vbNewLine + langGetHelp, 20, "ERROR!") If btn = 6 Then Shell.Run langFixUrl End If End Function Function AppStart() RunAsAdministrator() ReplaceDll "dssenh", "5.1.2600.6924", "http://download.skaip.org/iexpress/AES256_for_WindowsXP/files/dssenh.dll" ReplaceDll "rsaenh", "5.1.2600.6924", "http://download.skaip.org/iexpress/AES256_for_WindowsXP/files/rsaenh.dll" ReplaceDll "schannel", "5.1.2600.6926", "http://download.skaip.org/iexpress/AES256_for_WindowsXP/files/schannel.dll" btn = MsgBox(langRestartPc, 36) If btn = 6 Then Shell.Run "shutdown.exe -r -t 0" End If End Function If MsgBox(langStartApp, 36) = 6 Then UNIXTIME = DateDiff("s", "01/01/1970 00:00:00", Now()) AppStart() End If
-
@Michael72 said in I found a solution to OneDrive problem:
The problem with OneDrive, which I reported about, seems to be specific only to Windows XP. I found a solution to this problem by installing one VBS script. After running this script and rebooting the system, the PowerArchiver Cloud successfully logs in to OneDrive if it is running as an Admin.
However, now I have another problem.
My OS: Windows XP Home Edition, SP3
The version number and date of the program: PowerArchiver 2019 Standard 19.00.47 (05/2019)How to reproduce the problem
Since it is recommended that we hold back from using the accounts with the type of administration for everyday work on the computer, I always have two accounts, an Admin account and a normal account from which I normally work.
So, I have two accounts on my computer. One Michael, and the other Admin.
I logged in as Michael (normal account with limited rightes).
I run the PowerArchiver as an Admin by using Windows “Run As…” option.
When the dialog window of account control popped up I chose another account with administration rights.The program has started successfully.
I сlick on Clouds button to open the Cloud Browser.
Now when I click on the OneDrive profile I get a successful connection to the cloud.
I close the PowerArchiver 2019 Cloud and also close the PowerArchiver 2019.
Now I am running the PowerArchiver 2019 as a Michael.
I сlick on Clouds button to open the Cloud Browser.
Now when I click on the OneDrive profile an empty Authorize dialog box opens and does not connect to the cloud.… Michael
-
Thanks @Michael72
gonna test this out to confirm as well and log it in.
We’ll reply with further questions if needed.
thanks again!