HFS for Windows always BSOD!

Discussion in 'HFS for Windows' started by davidm71, May 23, 2011.

Thread Status:
Not open for further replies.
  1. davidm71
    Offline

    davidm71 Registered Member

    Few days ago I installed HFS+ for Windows, then the other day I noticed that my system blue screened upon shutting of siting error in fltmgr.sys. I thus rebooted and went into event viewer ( was hard as bsod were popping up) and saw that some file called uim something .sys was having errors. I googled it and found it to be a Paragon file. To make matters worse I couldn't uninstall it and had data corruption and had to revert back to my last april backup loosing data. This is not good...

    So I wasn't a hundred percent sure it was that utility so I copied my good partition to another drive on my system and installed the HFS Windows utility again and got an immediate BSOD upon boot! I mean who do these guys hire to do their programming? High school drop outs? Who is doing the beta testing? Is there any quality control here?! This is ridiculous!

    This is the second issue I had with a Paragon product in a month. The first being Paragon Partition Manager Pro crashing upon seeing an ntfs - HFS hybrid guid multi parition drive. Had to upgrade to the HDM Suite Pro with a newer engine to fix this problem. So I don't know why I installed this HFS utility considering what happened before, and I can tell you that I no longer trust Paragon with my data. As far as I'm concerned trashing someones drive is a serious offense!

    I advise any dual HFS NTFS booters to stay away from this product. It is very dangerous!

    Thank you.
  2. Mech_An
    Offline

    Mech_An Registered Member

    Did you try 9 version?
  3. davidm71
    Offline

    davidm71 Registered Member


    Unfortunately...
  4. Mech_An
    Offline

    Mech_An Registered Member

  5. davidm71
    Offline

    davidm71 Registered Member

    Got my money back.. not only that going to secure erase the files so they don't cause any trouble ever again!
Thread Status:
Not open for further replies.