Winrar was working fine for me on build 7048.
Suddenly, it doesnt work on build 7057?
Everything is fine except for the fact that everytime I try to make a new Winrar/Winzip Archive on the context menu it's always corrupted no matter what.
Other than that, it works(extracting, manually adding from application..etc)
Anyone else having this issue after upgrading to 7057?
Hi, I just checked and do not have this problem on 7057 using Winrar 3.80. Everything seems to work just fine.
this is probably due to 1 of 2 things... the horrendous upgrade beta over beta, or you have a corrupt hard drive
@Jacee, 7zip or any other program runs fine, it's just winrar.
Uninstalling/reinstalling
Deleting registry keys
Earlier versions of Winrar
I have tried the above and every solution out there and failed, and it suddenly only happens by making a new ZIP/RAR archive from the context menu;it comes out damaged by default, very annoying indeed.
That is weird - b/c I am having no issues at all with 7048 and WinRAR - I just used it to add a PW to one file, create a second file,a nd convert a third from ZIP to RAR format - all worked without any issues at all.
could it be a permissions problem ?
Uninstalling/reinstalling
Deleting registry keys
Earlier versions of Winrar
I have tried the above and every solution out there and failed, and it suddenly only happens by making a new ZIP/RAR archive from the context menu;it comes out damaged by default, very annoying indeed.
try runnin winrar as admin and or check the folders it's writing to/from for ownership ?
Hmmm - good point. Although I don't run WinRAR as an administrator, I do know that it fails when it does not have permission to write to a folder - but by fails I mean that it does not make the archive at all, terminating abruptly with an error message - not creating a file that is corrupted.
Of course, it could be corrupted because it is trying to create an archive of both public and restricted content, and thus only crashing when it gets to a file from a privileged location...
Or it could be running out of room in the temp folder....
Or, it could simply be a corrupted file to begin with....
Or it could be corrupted / failing hardware.....
Quote