Jump to content

toliman

Members
  • Content Count

    2
  • Joined

  • Last visited

About toliman

  • Rank
    Candidate

Recent Profile Visitors

62 profile views
  1. it's detected as 2 different objects, hence the bouncing around in quarantine. add both exceptions for the same file Detected: UDS:DangerousObject.Multi.Generic ... \poclbm.exe KSN service Detected: not-a-virus:RiskTool.Win32.BitCoinMiner.r..\poclbm.exe/Py2Exe/poclbm.pyo Information i've tried to do this, but the UDS module doesn't respond to the exceptions list, and flags the file anyway. may have to see if there's a way to fix the problem elsewhere. as the KIS2011 GUI fails to anticipate multiple agents detecting the same file using multiple agents and allowing exceptions during the multiple conflicting detection chains. could be fixed with a better exclusion system that handles 'false flag' positives, i.e. files with multiple detections, ie packed, using DLLs, hardware access, etc. can be added to a 'safe list' and exceptions automatically added during the entire process list. this allows for process ID's to be created for a 'safe' execution, and behaviour added for a select few processes.
  2. .Net applications don't go quietly into the night, especially if they've been neutered by Kaspersky's Paranoid/proactive defense option or PDM first, you have to delete the system libraries for curse, and this should resolve properly without reinstalling constantly. i'll leave that till last. second, Roxio won't work until you remove the install folders for curse, if curse isn't installed properly, .NET won't work, and roxio won't work. so, if after removing curse, if roxio doesn't work, you should also remove roxio, and reinstall, following http://www.ehow.com/how_5958413_completely...io-creator.html that should resolve the problem entirely. if you want to run curse, you really have to add an exception in Kaspersky, or you will cause the .NET application/framework to crash spectacularly as kaspersky will delete files without telling .NET it's done so, or prompt for action. it's a badly designed system, but it's microsoft/kaspersky playing tug of war with your PC, both thinking they have your best interests in mind. once curse has been installed and logged in and running, open up the kaspersky config, under advanced, you have to add an exception for the curseclient.exe finding the correct CurseClient.exe to add as an exception can be tricky, a) there's several duplicates it will be nested in one of the many 32-digit folder names under the appdata/local/apps/2.0/ folders c) if there's later updates, the folder will change. so, to delete Curse , follow http://clientsupport.curse.com/guide.aspx?id=33 How to Fix a Corrupt Curse Client Install 1) From the Windows Start menu choose Run (Or Windows Key + R) 2) Enter the following, depending on your version of Windows, then click the OK button: On Windows XP: %userprofile%\Local Settings\Apps (e.g. C:\Documents & Settings\Username\Local Settings\Apps) On Windows VISTA / 7: %userprofile%\AppData\Local\Apps (e.g. C:\users\Username\AppData\Local\Apps) 3) Delete the 2.0 folder
×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.