Auslogic Disk Defrag (Free and Pro) And Windows 10 Pro Install Issue

Discussion in 'other software & services' started by MADx, Oct 27, 2015.

  1. MADx

    MADx Registered Member

    Joined:
    Jul 18, 2012
    Posts:
    34
    Location:
    United States
    I have been having issues with trying to install Auslogic Disk Defrag Pro on Windows 10 Pro edition, I keep getting a "Runtime error 127 at 07835885. Auslogic refuse to give me technical help, because I bought my copy of Disk Defrag Pro from a third party site. I seen others who are having this same issue when installing Disk Defrag Pro on Windows 10 Pro but not on Windows 10 Home edition. Just thought I might give others a heads up on this issue.
     
  2. Rolo42

    Rolo42 Registered Member

    Joined:
    Jan 22, 2012
    Posts:
    571
    Location:
    USA
    That's pretty unacceptable. I can't say I care for that company.

    I did install that product on Win10 Pro (it was a giveaway) and it ran fine. However, launching it just now, it crashed. If I were you I would pursue a refund: the product doesn't work and they refuse to support it; take that refusal to the reseller and if they refuse, use BBB (or whatever equivalent in Australia), et. al. to get resolution. Don't stop until you either get a working product or a refund.

    My experience is that about the 3rd e-mail to support, I get resolution. In my last two experiences (Bethesda/ZeniMax and Kalypso), it took a year but I only spent about 20 minutes on it in total (patience). Meanwhile, the support metrics will show a very old unresolved support request that nobody wants to answer for. Basically, minimal effort on your part eventually leads to a headache on theirs--that's leverage.

    I had Disk Defrag Pro 4.6 installed; I just downloaded 4.7 Pro and I got Runtime Error 217. I get the same when trying to reinstall 4.6. If they refuse support, that means they have no idea how to fix their stuff.

    From Windows Event Log:
    Code:
    Faulting module name: KERNELBASE.dll, version: 10.0.10565.0, time stamp: 0x5614b4a7
    Are you running 10565 also?
     
  3. MADx

    MADx Registered Member

    Joined:
    Jul 18, 2012
    Posts:
    34
    Location:
    United States
    I don't think they know how to fix the problem. People been having the same issue as you also when upgrading to 4.7 getting the Runtime Error 127 then downgrading only to find that they no longer can use 4.6.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.