Announcement

Collapse
No announcement yet.

New Rollback v11.1.2704030551 corrupted my computer

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • carfal
    started a topic New Rollback v11.1.2704030551 corrupted my computer

    New Rollback v11.1.2704030551 corrupted my computer

    Well, I gave the latest RB a whirl for about a week and took about 10 snapshots as well as deleting countless others. I then realized that i hadn't done an actual rollback yet so proceeded to do my first rollback to the last snapshot I'd taken. What a f*****g disaster.. Corruption everywhere. All 10 snapshots (including Installation) were all f****d. Even more annoying was that right clicking on the snapshots and showing properties listed the Quality as "GOOD". Really??? Whats good about these f****d up snapshots. They're all corrupted. Why does RB still say "All good here?" Is that property window just for show? Is there any real code behind it that actually does a verification?. So many questions and absolutely no answers coming I'm sure.

    I havent had this issue for a very long while and while its true that RB is known to exhibit this random corruption, to do so so quickly only after the first rollback and a weeks use tells me that there is a problem with the code again. Especially since they must have done some major re-coding to get the baseline to delete and update to the next available snapshot (much like updating baseline only much more streamlined). This brings up (again) the question of how much or well they do their testing phase. HDS have been accused before of using their users as the testers which is extremely infuriating when you consider the loss of data that can occur to an unsuspecting (or unprepared) user. I mean come on. I say i've used the latest version for a week but over that week the reality is that I've used my PC for maybe 4hrs with RB installed and on the very first rollback it trashes my system???? Jesus, talk about sapping all confidence from a person.

    Why is RB so sensitive to any code change? Is it because RB works by hacking the system (eg MBR) therefore making it very difficult to track all the hacks that you guys are making and creating a massive scenario of unknown consequences?? Is this the real reason why no major feature has been added to RB since its inception?? Again so many questions and no answers will be forthcoming.

    You guys need to look at the new code changes you've made because something got over looked. Shame on you because this happens with great regularity and the nature of your software makes this a grave shortcoming. Dont bother asking for logs as over the years on using your software im over helping sort out your bugs. Thats your job...not mine.

    Luckily I'm a**l about having a current backup so i was able to recover without incident but others......

  • carfal
    replied
    Tested the latest version (...597) today for a hour or so and the corruption is fixed.........but

    There are still issues with the Space Saving Mode (SSM) and Fast Restore Mode (FRM) feature. Switching to FRM was easy enough (required a reboot) but i could not for the life of me get RB to retain the SSM when i tried to switch back to it. It changed to SSM when i clicked on it but upon any restore it reverted back to FRM (even though the 2 options remained ticked). Some more work please.

    Also something wrong with the resulting snapshot size once you delete the "Installation snapshot" while in SSM. I deleted the "Installation snapshot" as well as 4 other snapshots at once and the "installation snapshot" went from 70GB to 231GB. Me thinks a real problem there....No amount of defragging recovered the space.

    Cheers





    Leave a comment:


  • dbolotin
    replied
    That's good to hear.

    Leave a comment:


  • Ram Sarma
    replied
    The new version 11 build should fix some of the problems reported by users. If you're specifically referring to the checkdisk isue, then that would have been resolved as well.

    Thanks

    Leave a comment:


  • dbolotin
    replied
    Rollback Pro Rx Version 11.1, build #2704376957, is back again, since Feburary 8th, as the version available for download. If anyone here has been willing to risk it, has it gotten rid of the fatal defects in build #2704035511 from last December 12th?

    Leave a comment:


  • liamw
    replied
    I'm using version 11.0 with no problems.
    run 3 online

    Leave a comment:


  • Ram Sarma
    replied
    Hi Carfal,

    We actually have a beta build in the works that should resolve the issue you're dealing with.

    The Check for updates feature is really only available for enterprise/corporate customers that have an OEM licensing structure with us. Without getting into too many details, its an easier way for them to be able to mass deploy.

    Mr. Dutchie, I would really appreciate it if you would keep it civilized. The memory issue you're referring to happened a while ago when the build wouldn't be able to support high-performance machines (Already resolved) We really do care deeply about our users, hence the whole reason why we have a support portal and a forum community, to begin with. We take feedback seriously and we try and do our best to improve based on it.


    Leave a comment:


  • dbolotin
    replied
    You're right, mrdutchie. The downloadable build is again 2704035511, from December 2018. But on Monday it was 2704376597, with a shield.exe file dated 1/16/2019. Go figure. But like you, I'm using version 11.0 with no problems. And I hate to see what's happening to the company, since Rollback Rx has saved my bacon so many times I can't even count them. It has been by far the best recovery system I know of.
    Last edited by dbolotin; 01-30-2019, 06:55 AM.

    Leave a comment:


  • mrdutchie
    replied
    Originally posted by dbolotin View Post
    Carfal, As you may have noticed, Manolito on the other forum posted just this morning that the newest build of Rollback Rx Pro v. 11.1 is 2704376597, with the date for the shield.exe file being January 16th. Do you have any opinion about that build? I don't blame you, though, if you are unwilling to risk it.
    The latest is from December 2018.. Don't see a new one on the site. and no change log.... (like it matters since they never mention all the fixes)

    Leave a comment:


  • mrdutchie
    replied
    reported this a while ago, that the latest version f.cked up the system... went back to 11.0 and no problems, but no Support on my questions... They don't seem to give a ****..
    No wonder why nobody wants the software anymore. Even the basic "check for updates" tells you there is nothing, even though there is..
    original Admins are all gone..
    Seems like they have an overturn on people,
    All I get from Support a long time ago, is that Rollback will not work for your system, since I use 64gb of memory... What a Joke!!!

    Leave a comment:


  • dbolotin
    replied
    Carfal, As you may have noticed, Manolito on the other forum posted just this morning that the newest build of Rollback Rx Pro v. 11.1 is 2704376597, with the date for the shield.exe file being January 16th. Do you have any opinion about that build? I don't blame you, though, if you are unwilling to risk it.

    Leave a comment:


  • carfal
    replied
    Originally posted by Ram Sarma View Post
    Hi Carfal,

    Sorry about the situation you're in. Although you are resistant on providing log files, this is the only way the developers can analyze and see what happened.

    We do test our software extensively before pushing it out to the public, and we have not had any similar situations like this, we also have not had any reports of a similar case with other end users, so it's definitely odd that this happened and we do want to figure this out.

    Just provide the log files, and I'll take care of the rest, you can just PM it to me if you like.

    Thanks and let me know if you have any questions or concerns.
    Well I'm not sure where your looking or how you test your product but you only have to look here. These guys dont seem to have any issue with reproducing the problem (in particular look at manolito's post) and you've got to ask how many ticking time bombs are installed on peoples' PC's. As I've said, I'm not interested in providing or spending time sorting out your bugs. This is your job. If you cant reproduce this corruption issue then HDS need to take a serious look at their QC regiment because this small sample of testers has no issue reproducing the corruption,

    Leave a comment:


  • dbolotin
    replied
    Hello Ram Sarma,

    It's not just Carfal. Zoeff also reported the same kinds of problems (though with Rx Home 11.1) over the weekend.
    Last edited by dbolotin; 01-22-2019, 07:33 AM.

    Leave a comment:


  • Ram Sarma
    replied
    Hi Carfal,

    Sorry about the situation you're in. Although you are resistant on providing log files, this is the only way the developers can analyze and see what happened.

    We do test our software extensively before pushing it out to the public, and we have not had any similar situations like this, we also have not had any reports of a similar case with other end users, so it's definitely odd that this happened and we do want to figure this out.

    Just provide the log files, and I'll take care of the rest, you can just PM it to me if you like.

    Thanks and let me know if you have any questions or concerns.

    Leave a comment:


  • dbolotin
    replied
    It has now been a week and a half since carfal first posted this information about a FATAL FLAW in Rollback Rx Pro v. 11.1. But no one from Horizon DataSys has said a word about it. Does no one at the company care that they are pushing a product that trashes its users' computers? It is only by a combination of laziness and good luck that I hadn't installed it myself.

    Leave a comment:

Working...
X