Jump to content

Wookiee

Administrators
  • Content Count

    204
  • Joined

  • Last visited

  • Days Won

    18

Wookiee last won the day on January 13

Wookiee had the most liked content!

Community Reputation

26 Excellent

About Wookiee

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

675 profile views
  1. Wookiee

    OFFLINE INSTALLER

    It requires an active internet connection
  2. Wookiee

    I am back to project!

    if you have a second anti-virus, just exclude them from eachother so it doesn't cause any issues and you should be fine.
  3. Wookiee

    support forum in https

    Cisco did take over this project and we are working on improving everything (the software, the forums etc). Glad you like it !
  4. Wookiee

    Feb 4th Infrastructure date is approaching.

    Windows XP isn't even supported by Windows...
  5. Immunet is undergoing major changes. For a long time, the AMP infrastructure and Immunet infrastructure have been the same. But, we are changing that now to separate the customers of AMP and Immunet into their own cloud infrastructures. As of right now, any Immunet user who is not on version 6.2.0 is on the old infrastructure and will need to upgrade to the latest version as soon as possible. We plan on decommissioning the old infrastructure (that means any versions prior to 6.2.0) on Feb. 4, 2019. What does this mean? This means that all users who aren’t already, need to be on version 6.2.0. If you are on 6.2.0 now, you will not see any changes and do not need to worry. If you are on the older version, you need to upgrade immediately. If you do not upgrade before Feb. 4, you may experience service interruptions and may not be able to upgrade Immunet or receive protection. 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.
  6. what is the bios name? or what is the character that is in the bios name?
  7. Also, you saved the bios once you removed the character in the name? safe mode with networking would be best to try and install it with, (with full admin rights) IF you did make the name change, are you getting the same error ?
  8. 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.
  9. Wookiee

    Network Share exclusion

    i will put a feature request in then.
  10. Wookiee

    Network Share exclusion

    Not at the moment, I can put a feature request in to the developers to see if they can't have a whitelist with anything that starts with "UTW" or whatever you want (wildcard characters) , and such. Is there anyway in the software to have the local/TEMP files be created in another location? If so, point it to a generic folder that you create, and then whitelist that folder so it wouldn't matter the name changes
  11. Wookiee

    Network Share exclusion

    If you just exclude the exe file or application path on the share, it should work without crashing while being able to access the other files. unless it is creating temp files, that it needs each time the application is launched - where knowing the exact file name could be difficult.
  12. Wookiee

    64 bit Protection??

    Any version 6.2.0 and greater should have 64 bit support
  13. Yeah, Rich is correct- Immunet doesn't out-source or do anything like that.
  14. Wookiee

    Happy Holidays Everyone!

    happy holiday's
×