Connection error in AdGuard

Discussion in 'Technical Support (AdGuard for Windows)' started by Venky, Nov 2, 2014.

  1. Venky

    Venky Beta Tester

    Joined:
    Jul 19, 2013
    Messages:
    151
    Hi, I am getting connection error in adguard. When I click on connect nothing happens and still get the same error.

    getting the error in Windows 8.1 setup.
     
  2. Venky

    Venky Beta Tester

    Joined:
    Jul 19, 2013
    Messages:
    151
    here is a screenshot of the error : [​IMG]
     
  3. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    12,891
  4. Venky

    Venky Beta Tester

    Joined:
    Jul 19, 2013
    Messages:
    151
    I re-imaged the pc to an earlier backup image. I am not sure what caused the error, but will keep an eye out if it occurs again.
     
  5. mysteriously

    mysteriously Beta Tester & Translator

    Joined:
    May 4, 2014
    Messages:
    508
    Last edited by a moderator: Nov 4, 2014
  6. Nameless

    Nameless Beta Tester

    Joined:
    Mar 19, 2014
    Messages:
    731
    Had this once or twice clicked connect it started to work.
    Can not remember what i did to cause this, might of disabled adguard for a second and tried to reconnect i forget.
     
  7. steve1209

    steve1209 Beta Tester

    Joined:
    Mar 31, 2014
    Messages:
    442
    I had this today as well, it was after a very quick power dip and my computer rebooted itself. I also clicked connect and it started to work just fine, not sure if it was the power dip, my cable modem, my router who knows on a power dip.
     
  8. Venky

    Venky Beta Tester

    Joined:
    Jul 19, 2013
    Messages:
    151
    Now that I come to think of it, my error was caused after a hard reboot. perhaps a bug in Adguard ? the only problem with my error was it did not work even after repeated click on connect or even after a shutdown.
     
    Last edited: Nov 5, 2014
  9. avatar

    avatar Administrator Staff Member Administrator

    Joined:
    Oct 26, 2010
    Messages:
    12,891
    Usually the cause of this issue is "damaged" .NET Framework on the computer (when some parts of the framework becomes unusable).
     
  10. mysteriously

    mysteriously Beta Tester & Translator

    Joined:
    May 4, 2014
    Messages:
    508
    Ok so I'll repair .NET Framework 4.5.2 and report if this error happen again
     
  11. steve1209

    steve1209 Beta Tester

    Joined:
    Mar 31, 2014
    Messages:
    442
    Hey buuuuuuu,

    I was using 4.5.1 .NET after seeing your post I upgraded to 4.5.2, thanks for the info...