Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 05/31/2019 in Posts

  1. 3 points
    Hello all, We are happy to announce a new release of Immunet: Version 7.0.0! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes Credo and AMSI. Credo is a ML engine that allows endpoint connector to extract feature print of a PE file and send to the cloud to see whether the file is malware or not. ScriptID engine allows AMP connector to analyze scripts prior to execution. It is based on the Windows Antimalware Scan Interface (AMSI). In 7.0.0 version of connector only PowerShell scripts are analyzed. You can get the new installer here. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe If you are running an older version of Immunet, you should be able to upgrade via the 'Update Now' button in the UI. If you don't see the update in your UI we recommend uninstalling Immunet and reinstalling the version downloaded from http://www.immunet.com/index Changes in 7.0.0 Improvements and updates: New Credo engine New ScriptID engine for AMSI Query improvements in Immunet Protect driver Improvement in preforming Immunet registration Improvements in Connectivity test tool Curl version update ImmunetSCMS service now handle crash reporting Driver updates to support No Reboot upgrades New certificate for the ELAM driver Improvements on the Malicious Activity Protection (MAP) to reduce false positive Fixes: Stability Improvements in the Immunet Protect driver Stability Improvements in the SPP Stability Improvement on Immunet Protect shutdown Stability Improvements in the Exploit prevention
  2. 2 points
    Hi 4tygrit i've the same update problem with the main.cvd file in a other post. To update immunet i've download ClamAV Portable (doant forget to get Updates in ClamAV). Stop the Immunet Service Delete in "C:\Program Files\Immunet\clamav\0.1......" the file main.cvd and daily.cvd copy the main.cld and daily.cvd files from "...\PortableApps\ClamWinPortable\Data\db" to "C:\Program Files\Immunet\clamav\0.1......" Start the Immunet Service again
  3. 2 points
    I'd like to report that the 7.2.8 upgrade through the UI took place with no problems. No reboot necessary! Great job on that guys! I did have to create a new allow rule with my firewall for sfc.exe but that's not uncommon behavior when a new build is installed. Some impressive changes have been made! A personal thanks to nirmeshptl for including a detailed change log with this announcement! Something I've been suggesting in the past when a new build is publicly rolled out. Best wishes, Ritchie...
  4. 2 points
    Interesting video you uploaded Valnat! Thanks for sharing. As the video demonstrates Immunet has some suburb efficacy! Much better than Microsoft's Defender AV! As you mentioned Immunet can be used as a stand-alone AV solution but it is recommended you use the ClamAV module if used in that manner. If Immunet is used as a companion AV to another compatible "paid product" it's best if the ClamAV module and updates for it remain disabled. This will reduce the amount of system resources being used. Also, don't forget to create exclusion rules for the Program Files folders for both AV's. This can go a long way in avoiding possible conflicts between the two AV's. Regards, Ritchie... P.S. I moved this topic to the General forum section since that's a better place for it.
  5. 2 points
    Hello Damokles and thank you for your interest in Immunet, Not sure what you mean by making a complete list. Immunet originally was strictly just a cloud based AV when it was first introduced. The draw back to that was Immunet had to have a constant internet connection for cloud based lookups during normal operation & during a scan. Also there was no off-line scanning capabilities. After the introduction of the open-sourced signature based ClamAV into the program that not only added an additional layer of off-line protection but also added the ability to run scans even if no internet connection is present as it works as a traditional downloaded malware definition signature based AV. You can use just the scalable multi-threaded ClamAV scripting code http://www.clamav.net/ as an automatic or on-demand AV scanner & a email gateway scanner for instance. ClamAV does not have a UI in the traditional sense since everything is handled through Command Line scripts. Of course Immunet provides a traditional UI to users without the need for advanced technical skills to configure or use since ClamAV's scripts are integrated into Immunet's program code via the ClamAV module. Immunet can be used as a "stand-alone" AV solution. If used in this manner it is recommended that the ClamAV module & updates for it be enabled. If Immunet is used as a companion AV to a compatible paid product it is recommended that the ClamAV module remain disabled. This improves the amount of system resources being used. Immunet will work with Defender. Using them both should provide good malware protection for the average user. In fact Immunet has, by default, an exclusion for Defender for improved compatibility. If using Immunet with Defender I would consider "not disabling" the ClamAV module for the reasons described below. Adding an exclusion/exception rule to Defender for Immunet's Program Files folder is also very highly recommended. That way they recognize each other as safe programs and goes a long way in avoiding possible future conflicts. If I "had to choose" one or the other I would definitely go with Immunet over Defender. Microsoft even admits that Defender is meant for users that don't have or don't want to use a different AV solution. Although some improvements have been made with newer builds Defender still is not a stellar anti-malware program as it provides basic protection. The Plus version of Immunet is no longer available. Immunet Protect Free is just like the name implies, it's totally free for individual/home or private network use and for "non-profit" charitable or educational organizations! Immunet is not licensed for any "for profit" business, service, organization or product. If it's found that Immunet is being used in such a manner no support will be offered. This information is included in the End User License Agreement (EULA) when first installing Immunet. We recommend that any for-profit entities use Immunet's paid Enterprise version called AMP for Endpoints. https://www.cisco.com/c/en/us/products/collateral/security/fireamp-endpoints/datasheet-c78-733181.html I hope this answers your questions. Regards, Ritchie...
  6. 2 points
    Hello all, We are happy to announce a new release of Immunet: Version 7.0.2! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes NoReboot upgrade beta. The Immunet Windows Connector often requires a reboot to complete the upgrade. This can be problematic for end users who have to time reboots, if they are in middle of critical updates or working on some important project, in order to upgrade the Connector, raising barriers to upgrading more regularly. This feature is to remove the requirement for reboots when upgrading the Windows Connector for good. Expected upgrade behaviour for Immunet users: * Upgrades from Connector versions < 7.0.0 to 7.0.0+ require a reboot to complete * Upgrades from Connector versions 7.0.0+ to any higher version do not require a reboot to complete Looking forward for your participation and help in cases of upgrade reboot failures issues, if encountered any. We would appreciate if you can reach out to us via support forum with Support logs as soon as you see upgrade failing or upgrade asking for reboot on upgrade. You can get the new installer here. https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe If you are running an older version of Immunet, you should be able to upgrade via the 'Update Now' button in the UI. If you don't see the update in your UI we recommend uninstalling Immunet and reinstalling the version downloaded from http://www.immunet.com/index Changes in 7.0.2 Improvements and updates: No Reboot upgrades No Reboot uninstalls New kernel logs for Connector upgrades and uninstalls Installer improvements to handle NoReboot upgrades and uninstall Fixes: Stability Improvements in the Immunet SelfProtect driver Fixed reference leak in asynchronous kernel exclusions Stability Improvements on Immunet Protect driver
  7. 2 points
    Yup, this is the right place for your questions. Sorry, Immunet doesn't offer spam or phishing protection, Interestingly , older versions of Immunet could scan local Outlook.pst email databases for malicious email attachments, but we shelved this feature for a couple reasons: 1) the average user moved to cloud email services (gmail, Hotmail, outlook.com / etc), most of which provide absolutely minimal span and phishing protection, making local emal scanning redundant 2) Microsoft changed their outlook.pst format and libraries a couple times resulting in Immunet failing to quarantine just the attachment from within the outlook.pst database file; and instead quarantined the entire email database.
  8. 2 points
    Ritchie, As soon and you mentioned AMP I fully remembered that I selected YES on both of those systems. I uninstalled Immunet and selected NO, rebooted and all is good now!! I agree that I will stay with AMP, but this is a GREAT free product for home users. Grant
  9. 2 points
    I've sent it to Clam so guess we'll see what they say. Thanks for your help!
  10. 2 points
    I would venture to guess that the ClamAV module is scanning files at the same time as they're being created by Visual Studio. Try creating a custom Immunet Exclusion rule for Visual Studio's entire Program Files folder in Settings. Then turn ClamAV back on, restart your computer and see if the same behavior persists. You can also directly contact the ClamAV developers to inform them of this issue if you wish. https://www.clamav.net/contact Best wishes, Ritchie...
  11. 1 point
    Hello all, We are happy to announce a new release of Immunet: Version 7.2.8! This latest version of Immunet provides the same great protection against malware and viruses as before but also includes some new features, enchantments and bug fixes as below. Changes in 7.2.8 New & Enhancements: Added support for the Windows 10 November 2019 Update (version 1909) Added support for Windows 10 20H1 (Version 2004) (RTM Preview build: 19041) Improved visibility and enhanced protection against script-based attacks System Process Protection Improvements Improved Malicious Activity Protection engine to no longer detect on Google Chrome Stability Improvements in the Exploit Prevention engine Installer improvements to handle NoReboot upgrades and uninstall Stability Improvements in the Immunet SelfProtect driver Bug Fixes: Resolved Windows Connector service freeze issue on startup, under certain circumstances Improved the Windows connector process of gathering BIOS serial number, when needed, to properly detect hardware changes for registration with AMP Cloud Fixed a crash that could be encountered on shutdown Addressed issue where Windows Connector would fail to upgrade when installed alongside BitDefender AV Made stability improvements in the Connector installer Fixed an issue where ClamAV was taking a long time in scanning PDF files resulting into longer high CPU usage Updated ClamAV to 0.102.1, including changes related to the vulnerability described in CVE-2019-15961 Fixed an Exploit Prevention engine issue that could cause Google Chrome v78 and later to crash or display a renderer code integrity error This version also addresses the following vulnerabilities: CVE-2019-1010305 CVE-2019-12625 CVE-2019-12900 You can get the new installer from here https://download.immunet.com/binaries/immunet/bin/ImmunetSetup.exe Expected upgrade behaviour for Immunet users: * Upgrades from Connector versions < 7.0.0 to 7.0.0+ require a reboot to complete * Upgrades from Connector versions 7.0.0+ to any higher version do not require a reboot to complete Looking forward to your participation and help in cases of upgrade reboot failures issues, if encountered any. We would appreciate it if you can reach out to us via support forum with Support logs as soon as you see upgrade failing or upgrade asking for a reboot on upgrade. If you are running an older version of Immunet, you should be able to upgrade via the 'Update Now' button in the UI. If you don't see the update in your UI we recommend uninstalling Immunet and reinstalling the version downloaded from http://www.immunet.com/index
  12. 1 point
    Hi 4tygrit, You're not the only one experiencing update problems with Immunet presently. After folks upgraded to version 7.2.8 the UI cloud stats no longer displayed correctly and also there's reports of Immunet not letting updates to be installed. Your guess is as good as mine as to why these issues are not being looked into in a timely manner! The admin. Rob T. was helping out on the forum but he's been M.I.A. for more than a month now. There's only so much I can do being the moderator for this site. These issues need to be looked into on the server side of things. Something I can't do. "It's really starting to bum me out that support for Immunet is seemingly being completely neglected at this time to be perfectly honest with you!" Regards, Ritchie...
  13. 1 point
    works fine ran few tests of crap detectionS went OK
  14. 1 point
    Personally, I've never seen the cloud stat issue go unresolved this long after a new build is released. Now users are reporting update issues too. Are these related or what? "Hello, is there anybody out there!!!"
  15. 1 point
    I used Immunet alongside Sophos Home for maybe a year on a Windows 10 rig. It was probably the most stable and quick combination I've ever used - and that was with the ClamAV engine enabled as well! They never clashed once, even on files they could both detect. For ages I never bothered adding each to the other's exclusion list, and they played fine together. I eventually added each one's "program files" folders to the other's exclusion-list, when Sophos eventually got a false positive on one of Immunet's temporary files (I had ClamAV enabled). I think I also had to add another Sophos folder (somewhere inside "c:\programdata") to Immunet's exclusions. The combo was great and never gave me an issue once. Speed was similar to running just Windows Defender. The only way I could get quicker performance was to turn off ClamAV or switch to running just Kaspersky or F-Secure on its own.
  16. 1 point
    Thanks Ritchie! I should have been a bit more specific with "low power" like HTPCs and basic builds I have been a fan of Immunets cloud ability's for a while. Yeah my personal build is a bit overkill Donavyn, I set up a VM to test Sophos with immunet and my results are pretty good like yours. I did run in to a bit of slow down with opening larger programs, but turning off monitor program start seemed have fixed it. Have you run in to that? Could have just been me as I only allocated 4 gigs ram to it. I usually keep that setting on though. Other then that it seems to work very well with both AVs running. I'll keep testing it for a bit to see if anything under different scenarios else come up.
  17. 1 point
    Thanks Richie, as you know Immunet uses the 'Cisco AMP for Endpoints' scanning and detection engine, which is how it appears as the process on a windows system. This is indeed an immunet issue.
  18. 1 point
    Hi FoxFerox, It could be that the servers were really busy at that time. Try updating tomorrow to see if the same thing happens. Also make sure that any other security software you may be using is not blocking or interfering with any of Immunet's processes. These are sfc.exe, iptray.exe, cscm.exe and freshclam.exe. The ETHOS & SPERO engines don't use downloaded malware definitions in the traditional sense since everything is handled in the cloud. Don't have a clue as to why you couldn't upload that image to your post. If you continue to see this issue would you be willing to do some troubleshooting? This would entail using the Verbose Tray Notifications feature for a few days and uploading a Support Diagnostic Tool report for the Admin. Rob. T to take a look at. Cheers, Ritchie...
  19. 1 point
    op, Can you tell us what version of immunet & operating system your seeing this on and share a link to where you got your copy of privazar that's fp'ing? I tried privzar v3.0.96.1 Released : 06 April 2020 (both the Pe and installer versions) on win 10_X86&X64 and I can't reproduce your FP. Cheers, RobT
  20. 1 point
    Did you make sure you got the correct file path for the executable as a custom Exclusion rule with Immunet? If the installer created it, did you try an Exclusion rule for the "entire Program Files folder" for the software? If you are sure you created an Exclusion with the correct file path(s) and it's still being blocked then I would suggest you submit a False Positive report at this URL for the devs to take a look at. https://www.immunet.com/false_positive You will need the correct SHA256 checksum to complete the FP report. If you're not sure what the correct hash is you can contact the software developers for this info. Another option to obtain the correct SHA256 checksum would be to use a third-party software program like HashCalc. I've personally used this software myself on occasion. https://download.cnet.com/HashCalc/3000-2250_4-10130770.html Best wishes & stay healthy, Ritchie...
  21. 1 point
    Has anyone else been getting a certificate error/warning when attempting to visit these forums? I've checked my computer's clock and tried visiting with GNU Icecat (Firefox ESR), regular Firefox, and Vivaldi (based on Chromium). Warning message every time. I haven't tried regular Google Chrome but suspect users of that browser won't have any issue connecting, because last time I paid any attention to anything G, Chrome still wasn't checking the validity of HTTPS certificates (this might seem convenient because all websites "just work", but in reality is a very bad thing for your security). This situation might have changed, but as I have not used anything G for a very long time, I cannot check. If it helps webmasters with any diagnostics, I use "HTTPS everywhere" from EFF.
  22. 1 point
    Thanks for calling it out Zom, our forum cert is defiantly expired. A new one is on the way but I don't have an ETA fr it yet. Cheers, RobT
  23. 1 point
    That's kinda what I want. And I agree 100%
  24. 1 point
    If the UI ever supposedly comes to a change where the old theme will be replaced with a newer one then before that happens you should know why it's not a good idea. Modern UI is almost everywhere, some people have brought up the idea to replace the "dated" older UI. My question is, do you REALLY want to do what everybody else's doing with THEIR website? I mean, you can do whatever you want to YOUR website but consider this: why am I doing this? Are you doing it because of the new modern UI trend popularized by Microsoft? (Microsoft really popularized modern UI, look it up if you don't believe what I'm saying). What I think is; you should do what YOU want to do, not what everybody else's doing. And if that IS what you want to do then go ahead. I must say though, a flat UI makes a 2D screen boring. A 3D UI (like the one Immunet is using for their program rn.) establishes what's boring to new, futuristic, and special. My idea is this: You can change whatever you want, but don't make it modern UI. This's just a constructive opinion, you don't have to do what I tell you to do, but when you have almost every single website you look at SHARE ONE ENTIRE UI, I start to lose sanity. What I will like is if you change the UI to something less "dated" but keep the 3D effect. You can even make a whole new UI yourself.
  25. 1 point
    I wholeheartedly agree. The standard Immunet UI actually looks pretty good and has aged rather well. It's also very easy to understand and use, right from the moment you first ever use the program. The only real area where it starts to show its age is on high resolution screens, where it either appears very small or scales poorly. It was better suited to the days of 800x600 or 1024x768. Maybe all it needs is a very slight cosmetic revamp, and the addition of scaling/HiDPI capability, with the general layout left largely untouched. Like others here, I really don't like the trend for "modern" UI. It's flat, boring, looks dated to begin with, and has no visual appeal whatsoever. It's like the whole metaphor of a "button" that you "press" has gone out of the window, and designers got lazy and just drew harsh-edged rectangles in Paintbrush. I remember DosShell and the MS Windows 1.x-2.x series being more ornate than W10. Even the standard X11 TWM is, and that's older than me! I still think the prettiest and nicest looking user interface for desktop PCs was KDE3 with the Keramik widgets and window-decorations, and Crystal icon theme. That was extremely 3D! The nearest Windows equivalent would probably be Windows XP Luna. Both still look good today even in a VM on modern hardware - although I think the best looking Windows interface by far (and easiest to use) is the 9x/ME/NT/2000 interface. Again, those buttons etc. still look good for some programs, even at high res.
  26. 1 point
    Ritchie I went and loaded Firefox on another drive so the warning would come up. I'll just uninstall it. I couldn't find it once I went past it on other drive with Firefox. If I'm getting it so are others. My clock is correct.
  27. 1 point
    Sorry all, I haven't been able to reproduce the 503 error on any version of windows 10 so all I have to offer is some troubleshooting steps for it's most likly causes. By any chance Is anyone on this thread seeing this error from somewhere outside north America? If you are seeing the 503 error please verify you can at least: 1) ping clamav.net should output something similar to: Pinging clamav.net [198.148.79.54] with 32 bytes of data: Reply from 198.148.79.54: bytes=32 time=80ms TTL=128 2) browse to update.immunet.com --> It's just a blank page with nothing to see. The important thing is you don't get any "page not found"/403/503/unreachable error messages. 3) browse to http://database.clamav.net --> this should open a page saying "You reached one of ClamAV virus database mirrors:" 4) if steps 2 or 3 fail, please double check from a different browser. If your getting errors with any of the above, you there are 3 common causes: A) there is a local a firewall preventing you from accessing Immunet's servers. Temporarily disable it and see if your 503 errors stop. Also note that sometimes windows 10 updates will turn the default windows firewall back on. So if you thought you left it disabled it's worth double checking it's still disabled. Immunet's IP addresses change all the time and a common problem we see is users allowing access to Immunet server IP's during the initial install and everything works great, but a few months later our server IP's change but your local machine's firewall rules have to be manually get updated to allow connecting to Immunet's new IP's. C) You might be using a DNS server that can't resolve Immunet's hostnames to the correct IP addresses. Try setting a different DNS server in your network connection settings : Google hosts one at 8.8.8.8 (it's also the only static IP I know). I won't guarantee anything about it's privacy, but I will guarantee its at least providing accurate hostname-to-IP resolution to reach Immunets servers. i) Immunet uses the default system level default DNS server, which is usually found in your local area connections settings, and is usually assigned automatically by your internet provider. ii) Note that a computer can be configured to use an multiple alternate DNS servers than the one provided by your internet provider. Individual web browsers can be set to use different DNS' from each other, which can in turn also be different from the local area connection level dns. iii) Some programs that can lead to the confusion of dealing with multiple DNS servers are: -Comodo Firewall products that install their own local DNS Server. -browser plugins & add-ons that claim to to increase security or privacy by re-routing DNS queries that originate from the browser through their secure/alternate DNS server. -Private vpn's usually provide their own DNS servers while you're connected to them and sometimes offer free private DNS servers for use when disconnected from the vpn. -malware that will maliciously redirect your DNS settings "aka the DNShijack" attack. iv) The user Amydala reported above that Immunet's installer didn't work with the Firefox browser but did work with IE. This is a telltale sign of having multiple different DNS servers across different browsers.
  28. 1 point
    I receive "Error creating scheduled scan. An unknown error has occurred." when I try to scheduled a scan. This happens no matted what type of scan day/week/month or full/flash/custom. I have tried to Run as Administrator, reboot, check for and update. Scan now works fine. Immunet version 7.0.2.11454.
  29. 1 point
    Well this morning it decided to work. The last scan button was yellow (for not doing a scan within 24 hours?) so I did a flash scan.After that was complete I tried to schedule a scan again and it let me.
  30. 1 point
    JUICE JACK payload loaded through using public charging stations in airports ,malls phones and tablets and maybe few laptops that allow USB charging once connected payload steals information via USB connection (usually USB ports have cables already provided) STAY SAFE CAREFUL USING public USB stations use your own charger connected to power plugs thieves dont stop
  31. 1 point
    Thank You Ritchie!
  32. 1 point
    Thanks for the additional feedback qwerty123! I'm not unfamiliar with building a rig from scratch. Letting me know that the D:\ drive is a HDD & not a SSD was very helpful! That would have been my next question. I think I have a good extrapolation what may be causing this behavior as I was able to reproduce it after some experimentation. I have a couple of HDD drives connected via SATA to the MoBo besides the C:\ drive on my current rig. I also use the Windows energy saver settings. If, after boot-up, a drive is not accessed within the specified time Windows will automatically turn off that drive to save power & needless wear & tear. Some MoBos have similar hardware based BIOS settings too. If you attempt to conduct a Context Menu Scan with Immunet and that particular HD disk is not already spinning at normal speed then it is possible that Immunet cannot access that drive before the disk has a chance to spin up to speed. If the drive is already spinning at normal speed then a CM scan will take place regardless of the drive letter has been my observation. P.S. - With your 10th post you are our newest official forum "member" and no longer a newbie! Congrats on that bro! Regards, Ritchie...
  33. 1 point
    Happy New Year! And a pray for the fires all over the world, especially Australia, to stop! Finally, I did it again! To remove this error 503 you need to make a clean uninstall of Immunet first and then reinstall it! Uninstall, clear all data. After restarting, delete folders of immunet on program files and data. After, running regedit.exe, search for "immunet" delete these keys and subkeys... (I deleted some root keys also (where I see that it is only for immunet). Then reinstall! I didn't try it without registry cleaning (only reinstall after uninstalling) but you can try it first (just to not mess up with registry) Happy new 2020
  34. 1 point
    RanSim is a tool that simulates the behavior of ransomware. The purpose of RanSim is to check if a workstation is well-protected with endpoint security software which would be able to detect and prevent real ransomware attacks. It also allows you to see if this software is incorrectly blocking files by running "false positive" scenarios. You can optionally select specific files you'd like to test to see how they would be affected by the ransomware simulations. ............................................maybe similar to cisco/talos amp,network protection
  35. 1 point
    +1 for Richie's answer.
  36. 1 point
    Thank you, let me make one more example.
  37. 1 point
    Will be nice can protect the program with password so cannot be edited or deactivated by other PC users.
  38. 1 point
    Hi all, The newest 6.3.0.10988 build of Immunet has a new running process called cscm. Microsoft made some improvements as to how antivirus solutions can better protect their software from unauthorized intrusion. It's a fact that some malware has the capacity to disable the installed AV, usually through unauthorized code-injection methods. This added security protocol will make it much harder for malware to disable Immunet. For anyone that wants to read this Windows Dev Center article (thanks Wookiee) regarding this added security protocol click on this link. https://docs.microsoft.com/en-us/windows/desktop/services/protecting-anti-malware-services- Regards, Ritchie...
  39. 1 point
    Successfully reproduced with Chrome on Win7x64 & Win10x64 today - Thanks again Deathinition, you rock! Hopefully we'll have the FP fixed by Monday. On another note, that's for introducing me to listenonrepeat . Am learning to play a guitar and it' s going to be really handy.
  40. 1 point
    Hi Ritchie, I will look into providing a list of important fixes that are included in the release. To answer some of your other questions: The Credo engine is a new engine that is integrated within the product. The ScriptID engine will monitor PowerShell activity and doesn't require a new process to function. Cheers, Andrew
  41. 1 point
    You may be interested to know that Windows Defender is detecting some immunet temp files as Trojan: JS/Foretype.A!ml This started happening 2 days ago, and has happened daily to me since. Their "more info" link, if useful: https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-description?name=Trojan%3aJS%2fForetype.A!ml&threatid=2147724342&enterprise=0 Edit: Uh, pasting images to your forum is terrible, they lose a ton of quality in the process, practically unreadable. Here: https://imgur.com/15VhZ3Y
  42. 1 point
    @Rob.Turner I can confirm that I can either see text or get a download prompt for every one of those links supplied. @ritchie58 Don't worry, I of course still allow Windows updates on my internet-connected machine. I have Pro so am fortunately able to defer any non-security updates for up to a year, which I recommend everyone should do before their PC gets bricked. It gives Microsoft a good chance at fixing the worst of their problems before their "improvements" reach your machine - unless the next broken update they release without testing just happens to be a security one... As a side note, When your Windows 7 reaches end-of-life, one option would be to just have a dual-boot scenario: Switch to GNU/Linux for anything that requires the internet, and keep your unsupported Win7 installation as-is, unpatched, for any obscure software you might still need to run occasionally, but can't get on GNU/Linux. You'd just need to keep the Windows 7 installation offline, for instance by disabling your network interfaces in the device-manager, or unplugging your network cables. I'm aware there's a learning-curve, it's a matter of personal taste, and It's not possible for everyone, but I'm about 90% of the way there. I used to dual-boot and value both OSs for their respective qualities, but I'm rapidly getting to the point where I just need to get the work done and Windows now gets in the way of that for me.
  43. 1 point
    Two days ago my Windows 10 got a serious update (took about 3 hours). Since that time I've been getting that 503 error. Coincidence?
  44. 1 point
    Sorry for the delay in responding & thanks for the added info. What it sounds like to me is that your copy of Immunet has some corrupted .db files if it's not remembering the previous settings configuration. I would suggest you try and do a clean uninstall. First uninstall Immunet, when asked by the uninstaller if you plan to reinstall Immunet again choose the "NO" option, this will delete all .db history files. Then reinstall Immunet but you will have to reconfigure the Settings and add any custom Exclusions you were using again. Let us know if this corrects the issue. I was given a free one year license for AMP a while back just to check it out myself so I am familiar with the software. It can be configured for home/personal use too. Having to use an on-line console to effect changes instead of a traditional UI did take a bit of getting use to I remember. This is a security feature since no unauthorized personal can make any changes to the software without the proper log in credentials to the console. Although not free like Immunet, AMP for Endpoints really is the better choice if you're using a multiple endpoint server environment for the simple fact that you can customize this software to your specific needs. Also with AMP you have the option of using the TETRA detection engine (which was part of the no longer available Immunet Plus). Originally based on Bitdefender's detection engine this now highly customized engine can sniff out usually hard to detect malware like root-kits, keyloggers, encrypted Trojan downloaders, etc... One more nice thing with AMP (compared to Immunet) is that you can configure it to automatically scan all in-coming email data packets for malware. A still prevalent attack vector. Compared to AMP, Immunet doesn't have no way near the customization options. I would suggest you stick with using AMP for Endpoints at least with your server! Something else I should mention is that Immunet is not licensed to be used in any "for profit" business, service, product or organization. If it's discovered Immunet is being used in this manner no further support will be offered. This info is included in the End User License Agreement (EULA) when you first install Immunet. Best wishes, Ritchie...
  45. 1 point
    Hi Bitsomper, I'm sure you've read the previous threads to this topic so the devs are definitely aware of the situation. Unfortunately the newest 6.3.0.10988 build did not address this known issue. Thanks for adding this thread! Maybe the devs will see this issue is still causing problems for users and "eventually" do something about it. Immunet really needs to incorporate a way to upscale the UI for 4k screens! That is a obviously needed upgrade, that seems to be continually overlooked, that should be implemented with some new code in some future build. The sooner the better in my opinion.
  46. 1 point
    Instead of downloading an online installer, try the same with the offline installer. You can download it here. Also, ClamAV detects a lot of false positives, so no need to worry.
  47. 1 point
    Problem solved. I used Immunet installer (found in the \Temp folder) in a Windows 10 virtual machine, then I monitored the uninstaller process handlers while I used Revo Uninstaller. Then I erased (on my real, affected PC) all of the files the Uninstaller modified/erased (Cleanup agent included) and that Revo had to erase too (I used a Linux LiveCD as some files/registry entries were blocked). It looks like Immunet uses Cisco's AMP, (Self Protect, Policy files...) and all of those files are kind of hidden and well protected. After all that was done, Immunet installed correctly. If someone's having this problem, please don't do as I did, as this process is very, very risky and Windows will most certainly get damaged. Just disable your antivirus before installing KB4503293 update. It seems like this problem could happen with any antivirus, but Immunet has no Removal Tool and so the only fix is to reinstall (a system restore point won't do the trick) Windows. Anyway, this is a really unique problem so I don't think someone will ever run into this issue where Windows removes Immunet files (and uninstallers). Still, Cisco should offer a Removal Tool to avoid these situations. Thanks for all the help you've given to me, ritchie58.
  48. 1 point
    It's a hell wonderful idea! I promise I will share this great news when new Immunet will be in use with all my friends and tell them what to do to be secure and safe. You are really cool, guys! Are you going to create several VPN servers or only one?
  49. 1 point
    Initially, my Immunet had the auto quarantine option activated and it quarantined a lot of my executables from program files folder including IDMan.exe and some others like the vipsocks executable. I have no complaints against that - ClamAV's security features might be too good. What bugged me though is the quarantine's UI design. Some of the executables, detected from the "Appdata/Roaming" folders were leftovers from installations and I wanted to batch delete them. Alas, I couldn't do it. Also, there wasn't any option to add an exclusion as well for a particular file in quarantine itself while restoring a false positive. Same goes for deletion - I couldn't use my keyboard to multi - delete files. And its a pain to select 10 files by clicking on each of them and deleting them one by one. Workaround - Its true that the Immunet folder C:\Program Files\Immunet\Quarantine contains the quarantined files, but at least the GUI should prompt to open that folder so that one can batch delete at least if not batch restore.
  50. 1 point
    Hello all, We are happy to announce a new release of Immunet: Version 6.3.0! This latest version of Immunet provides the same great protection against malware and viruses as before, but also includes Improved detection coverage Windows 10 RedStone 6 support Update ClamAV to version 0.101.2 Improved status in Windows Security Center Bug fix to exploit prevention engine Immunet installer now handles all legal windows characters that can be in a Windows file path for default install Fixes to mitigate high CPU/Memory issue some users are seeing on Windows 10 during Windows updates. As always, you can get the new installer at https://www.immunet.com. We strongly recommend existing Immunet user to upgrade to v6.3.0 and start taking advantage of new improvements. If you are running an older version of Immunet, you should be able to upgrade via the 'Update Now' button in the UI. If you don't see the update in your UI we recommend uninstalling Immunet and reinstalling the version downloaded from https://www.immunet.com If you do encounter problems with the new version of Immunet Protect, please let us know via forums at http://support.immunet.com Thank you for your continued support! The Immunet Protect Team
×
×
  • Create New...