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.
WinRAR 5 has a rather useful option in some cases, which is to be able to create an archive by replacing identical files with a reference to the first occurrence (hardlink) within the archive.
In case you choose to convert the file with PowerArchiver to another format, however, the resulting archive does not have all the files. It does not consider those that were present as hardlinks.
If you do a normal extraction of the RAR archive instead, even with PowerArchivier, all the files are extracted correctly.
Unsolved File Browser: Operations don't trigger UAC
-
This happens in Archive and Explorer Mode:
- Navigate to a folder, which is UAC protected (for example C:\Program Files)
- Right click -> New -> Folder (or any other item)
=> Nothing happens
Expected behaviour: UAC prompt is triggered and a new folder (or file) will be created
PowerArchiver 19.00.57
-
Thanks @BigMike
Confirmed and logged in -
Just to report back: Still not working in 19.00.58
-
Hi @BigMike
I am getting UAC now when creating a folder in C:\Program Files. You’re still not getting UAC?
Anyone else? -
Seems to work for me with .59 on Windows 7 (64 bit). (Create “New Folder”, Rename folder and delete folder in “Program Files (x86)” each gave a UAC prompt and worked when I said Yes)
-
@Brian-Gregory nice, glad it worked. thanks for your help!
-
Seems still not working with .59 on Windows 10 1909 32bit.
I have no test machine on x64 - but glad to hear, it’s fixed there… -
I have still the problem with 20.00.53 (x64):
Being in explorer view, I try to create a new folder in “C:\Program Files” (right click -> New -> Folder: Nothing happens)
It’s working in folders, where I have write access with my restricted account.
-
Seems to have returned in the latest 2021 version, logged in for fixing.
thanks @BigMike -
While this seem to have been fixed in the x64 version 20.0.0.73, it seems to happen now with the x86 version
