Closed H3X1C closed 1 month ago
Hi man, thanks for the bug report. I will investigate this ASAP!
Interesting, I cannot reproduce this issue, @H3X1C what's your WinRAR version?
WinRAR 5.71, I know an older version. Checking I don't think this version supports the optemp arg. I see you recently refactored the process spawning logic: https://github.com/ElPumpo/TinyNvidiaUpdateChecker/blob/ce6e311466d36c4632170b356d1db77ef8b55467/TinyNvidiaUpdateChecker/MainConsole.cs#L902 This would explain why it previously worked and now doesn't for my version.
Guessing the aim is extraction to a folder called temp overriding existing files. If so the following works on my version:
"c:\Program Files\WinRAR\WinRAR.exe" x HardwareManagerSvc.zip -o+temp
Was the p in -optemp a typo?
@H3X1C be wary of versions before 6.23 https://nvd.nist.gov/vuln/detail/CVE-2023-38831
Yea update WinRAR, that will fix the problem, seems like that old version doesn't have this CLI argument. I agree with you it looks very weird, but apparently that's how they developed it. If I were them I would have something like a =
char to sepeate arg and its value.
This is new code because we now extract the full driver file and then query all components, display to user which chooses which ones he wants.
Also like Mr Tech is advising you.. update! It has a CVE
Just wanted to say thanks for the resolve, I was having the same issue and have thus resolved it after reading this!
Perhaps if this secondary argument works on both version I might change it
EDIT Yea i dont think i am going to address this issue. Just update winrar
Thanks guys, I've swapped over to 7zip so problem solved
Hi,
I have WinRAR set as my default archive program. It seems recently the command line parameters have been changed and now get this error when it attempts to unpack:![image](https://github.com/user-attachments/assets/be0433e9-0556-4b0f-b3bc-9ad4c3f88355)
Command line arguments:![image](https://github.com/user-attachments/assets/b683db5f-8ea8-4be9-b9a3-f7c0ff32da9e)