Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 06/28/2010 in all areas

  1. 2 points
    I am running Windows 7 Pro on an older desk top and during the last few days have been getting a Virus detected and quarantined message on virtually every application that I use. I have been using some of these sights for 10 plus years and never had this issue previously. It persists even when I switch from Firefox to Chrome. I just ran a full scan of the entire computer and get reports of no virus found and have verified that the latest update is installed (as of 2/2/19). When I go to manually initialize Immunet, I see a note that the computer has never been scanned and is not secure even when I have just run a full scan. A typical warning is that f_0001f3 has been detected as Clam.Txt.Trojan.Generic-6840302-0. Quarantine was successful. I even got a message that Firefox Installer was a Trojan. This is very annoying and I would like some suggestions to resolve this issue. Nelson
  2. 2 points
    confirmed, is defiantly a Clam false positive. Thanks to everyone who reported this. we're reprod it internally and are working on a fix. In the mean time, if you turn off the clam AV engine in Immunet's settings that'll prevent the constant FP notifications and still keep your computer protected with the immunet cloud engine. We'll notify the thread to turn clam back on as soon as the fp is fixed.
  3. 2 points
    it might be an issue with a signature, I am looking into it.
  4. 2 points
    it looks like you are using clamav, not immunet. ClamAV gives you the ability to run commands- immunet does not. As far as multi-threaded scans in ClamAV, you could just do a clamd scan with multithreaded- should work
  5. 2 points
    Why not brother.. You can download Avast offline installer from here and Know how to uninstall avast step by step here.. The step by step guide also has a link to the avast removal tool
  6. 1 point
    Six months later and we're still on the Windows 7 era GUI
  7. 1 point
    We cannot force upgrade ANY Immunet version that is 5.x.x and below, so you need to manually upgrade to the latest version of Immunet 6.2.4. What happens if you do not upgrade before the decommission? You will need to uninstall and reinstall the software once the old infrastructure is decommissioned. We urge everyone on a version prior to 6.2.0 to upgrade Immediately. If you have any questions or concerns, please contact us via the support forums or posting below. Those that do not upgrade will cease to receive coverage from the product as we are doing a force cut over of the free antivirus system on the cloud side. March 4th is the OFFICIAL date when all coverage for ANY version of Immunet below 6.2.4 will stop receiving coverage. PLEASE upgrade ASAP so you do not have any interruption of service.
  8. 1 point
    Richie is correct - the internet connection icon is a standard windows thing. the Bing image search told your browser to show an image from neilrosenthl.com and your browser went to grab it from 104.27.175.64. According to https://dnslytics.com/ip/104.27.175.64 that ip is hosting 290 domains/websites. likely one of them at one point was hosting something malicious. Though currently neilrosental.com appears to be safe. Looks like a false positive to me. Sorry, our bad on that one. I do have one concern here though. It's common to first notice the internet connection icon after having a random router/modem reboot. I The internet stops working, so you go to your network connections to check your ip/network status and while your poking around the internet connection icon appears out of nowhere when the router/modem comes back online. There are lots of good reasons for a router to reboot itself, but it should be noted that not all vpn connections can survive a router reboot. Some can, some will notify you the vpn closed unexpectedly, and some will just fail silently and your internet activity will automatically re-route over non encrypted public internet. Thanks, RobT
  9. 1 point
    What is your Immunet version? It should look like this: The copy fail should be fixed in the later versions of Immunet. Though, sometimes it happens because it is not handling a odd character in the BIOs name such as a tilde key, or something similar. You could attempt to boot into safemode and try that, but if it is the bios name triggering the copyfail, then that wouldn't work without a bios change.
  10. 1 point
    Hello again. 64 bit protection in 6.2.4?? Thanks!
  11. 1 point
    Hello pufig, first of all it is very, very important to make sure that what you're attempting to restore is a False Positive and not actually genuine malware. One great way to do this is to check the file with VirusTotal.com's database first. https://www.virustotal.com/#/home/upload After you are "absolutely certain" that the file is not malicious you can click on the History tab -> to the right of View By click on the little downward pointing arrow -> this will open a little drop down menu and click on Quarantined File History -> find the file in question from the list, click on it and choose the "Restore" option. This automatically moves the file from Quarantine to the Exclusion list where it will no longer be scanned.
  12. 1 point
  13. 1 point
    Hi Rich, I'm sorry to say that Windows Server 2019 is not a supported platform at this time however Win 10 is supported. Immunet does have an "enterprise version" that I believe will work with Windows Server 2019 called AMP for Endpoints (AMP is an acronym for Advanced Malware Protection). It's not free but the price is reasonable and actually negotiable depending on the length of your license that you choose and the number of endpoints to be protected. Plus you get much better malware/intrusion protection compared to Immunet in a server environment. So take a look to see it AMP for Endpoints better meets your needs. https://www.cisco.com/c/en/us/products/security/amp-for-endpoints/index.html Cheers, Ritchie...
  14. 1 point
    Yes, it will have the same level of protection
  15. 1 point
    Hi all, I noticed a thread that's been moved to the FAQ section (therefore I can't reply on it) regarding someone wanting to use the CLI to restart the immunet service. The solution offered was to use good-old "net stop" / "net start". This requires you to know the exact name of the service (obviously). The problem is that over the years I've used Immunet, the service name has changed occasionally. It has been known as "ImmunetProtect", "Immunet", "Immunet[version.number]", etc. If you want a generic way of always reliably starting and stopping the service from a terminal, you need something that just needs to know that the service you're after is Immunet, but doesn't care about the exact name. The solution? The following "generic" commands: Stop any service that's got the word "Immunet" in its name: wmic service where "name like 'Immunet%'" call stopservice Start any service that's got the word "Immunet" in its name: wmic service where "name like 'Immunet%'" call startservice Please note that these work directly on the commandline. If you wish to execute these from within a batch file, you need to replace 'Immunet%' with 'Immunet%%' (add a second %), or it won't work. These two commands should allow you to always be able to restart the service, regardless of if the developers change its name slightly from version to version. I use these in a .bat file that adds the latest Sanesecurity and Securiteinfo ClamAV signatures to Immunet (amazing detection rate), but I will wait until the "ask me" bug in 6.2 is fixed before posting the source here, as these signatures cause many false positives.
  16. 1 point
    Thanks for some guidence Rekha,, Can you also provide me the links to these tools please ?
  17. 1 point
    It was never not safe. You can upgrade. Cloud issues that reported '0 people protected' is fixed.
  18. 1 point
    If you can obtain the files, I can do a comparison, but these would all be signature based. Signatures are what 'find' the malware / ransomware etc. The signatures aren't going to change version by version from 6.0.8 to 6.2, unless the malware itself is changed (or there was an issue with the signature in the first place, to which we push updated signatures out). I am not disbelieving you, But without knowing the exact file, the exact signature- this is a lot of 'he said', 'she said'. There was a few issues with some signatures about a week ago, in regards to detecting certain files, as malicious when they weren't, which were corrected. I would need the malware file(s), to conduct any test to see the following: 1) IF something has changed between versions (signature versions or software versions) 2) what signature(s) are being detected Though, nothing should of changed (other than the signatures possibly and I don't know that without the sample malware file(s)).
  19. 1 point
    We don't have anything to decrypt your data if a ransomware attack happens. We look for more malware and things like that. You might want to turn 'blocking' on if it isn't already in the immunet settings though. That could help. There should be ransomware specific softwares that could have key(s). The .krab file is a grancrab, which signatures DO exist for detecting but Immunet and clamav does NOT decrypt it. Below is a NON CISCO tool, use at your own risk. https://www.nomoreransom.org/uploads/GANDCRAB RANSOMWARE DECRYPTION TOOL.pdf
  20. 1 point
    We are aware of the issue and should be releasing a fix 'soon'
  21. 1 point
    Hi Art, what version of Win 10 are you using? In the mean time here's a few things you can look into. Make sure there isn't a program you use that may interfere with Immunet's installation such as your firewall of choice, another AV, sandboxing software, behavior blocker, etc... Since Immunet uses a bootstrapper installer an "uninterrupted internet connection" is also required when the files are being downloaded & during installation. You could also try a new installer package in case the one you downloaded got corrupted some how. Here's a link to download the newest installer. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe Best wishes, Ritchie...
  22. 1 point
    Good morning, This morning all the Windows Based Machines (Windows 10 and Windows Server 2012 and Windows 2008 R2) in our office running Immunet Anti Virus have this message: AppXDeploymentExtensions.onecore.dll has been detected as W32.45D0D4390-100.SBX.TG Quarantine failed. Any suggestions as I am not finding anything on the web about this other than AppXDeploymentExtensions.onecore.dll is a Windows Dymanic link library???? Any help appreciated! Thanks
  23. 1 point
  24. 1 point
    Hey everyone! Yes, more can be done with the overall design, and I can bring it up to the rest of the developers for a potential future release. @lucasLKs, you must know I am a sucker for anything dark themed because I dislike bright, bright colors in software. I actually really dig the design, though- I would probably tweak somethings. personally- interfaces are important for people to understand and use, and command-line only is more outdated than anything ( depending on who's actually using it, skill level, etc). I am simply saying, you all ARE being heard, and I will bring it up to the rest of the team.
  25. 1 point
    Hello everyone, I see a lot of future in this software, its interface is destined to "the end", compared to other interfaces today ... But instead of just talking, I made a new design for Immunet AntiVirus .. .I only did the basic part, in case I get you back, I can go back to work on the interface and finish for a new look to the software. Here are the images: I look forward to the feedback from the developers, and also from the community. Att: Lucas Lks
×
×
  • Create New...