Jump to content

jeremyl

Members
  • Content Count

    7
  • Joined

  • Last visited

  • Days Won

    1

jeremyl last won the day on January 19 2017

jeremyl had the most liked content!

Community Reputation

1 Neutral

About jeremyl

  • Rank
    Newbie
  1. Thanks Rithie58 & daphneg fixed now I have worked it out that the issue was actually caused by having Immunet 3.0 (v3.0.13.9411) which is out of date (August 2013) as my other servers had no issue installing the update but they were running a later version of immunet 3.0 (v3.1.13.9666). The solution was to download/upgrade Immunet from your website + reboot then attempt to install KB3072633. Normally I am use to seeing a notification in the system tray about a new Immunet version update possibly this version did not have that feature/notification in it. My plan is to either using spiceworks to check all my servers for out-dated Immunet 3.0. Just another question any idea how to auto-update the client rather than manually telling it to upgrade (Talking about the Scanner not the definitions)?
  2. Hi Daphneg No luck I declined/removed the update from WSUS & re-imported it into WSUS. On the server:- 1. Ran all other windows updates 2. Rebooted (Only listed update is KB3072633) 3. Stopped WSUS service 4. Deleted "Software Distribution" folder 5. Started WSUS Service 6. Ran "Windows6.1-KB3072633-x64.msu" (hash was previously checked & correct) During the end of the installation Immunet detected the same virus & on reboot it reverts the windows updates. Is there anything I can send you to help me debug this issue? Thanks Jeremy
  3. Thanks for testing it daphneg :-) I will try to decline/purge "Windows 2008 R2 x64" update & re-import it into my WSUS. I do find it weird how none of our other 20 servers did not have an issue installing it so guessing it either became corrupted or it's windows updates order which is screwy. Leave it will me :-) (Will attempt this & let you know :-) )
  4. Hi Daphne Yes that is correct I am using "Windows6.1-KB3072633-x64.msu" & checking both the SHA1 & SHA256 hashes they both match the file I downloaded. There are currently two possibles:- 1. When I run "Windows6.1-KB3072633-x64.msu" it uses the cache instead from "C:\Windows\SoftwareDistribution" (Collected from my WSUS Server) 2. "Windows6.1-KB3072633-x64.msu" is getting detected as a false positive I did run a scan with "KB890830", "Stinger" & "Immunet" on both our WSUS Server + the server with the warning message without any viruses found. (I managed to install the other 12 updates by excluding "KB3072633" on that server) I am going to setup a virtual machine shortly to test both situations & will update this post :-) ==========Update 1======================= 1. Install Windows 2008 R2 Enterprise + SP1 2. Saved Snapshot 3. Downloaded/Installed "Windows6.1-KB3072633-x64.msu" from Microsoft Website Everything Worked Fine (No Virus warning message) This leads me to believe that our WSUS Server is infected or some sort of bad caching is occurring on our server :-( I will now attempt to install the updates via our WSUS Server which could take a while as there are lots of updates
  5. Hi Immunet I have Windows 2008 R2 installed & every time I try to run windows updates from my WSUS it gives this message attached message. I have now found out it is caused by "KB3072633" even downloading via my WSUS Server or downloading the update from the official website. Is this normal & should I disable Immunet 3.0 to install "KB3072633" ? (It is very weird as have all the other non-exchange Windows 2008 R2 servers have installed it successfully & all have Immunet installed)
  6. Hi Ritchie58 From the 1st post by "Davros30" it works just by switching off "Monitor Program Install" but it does mean that I am crippling the anti-virus a bit. (I have temporarily done that on Windows 2008 R2 so that my staff don't complain about 30s-60s saving time for MS Office files over samba sharing) Thanks Jeremy
  7. Nope this issue is still happening on Immunet 3 (v3.1.13.9671) but even using the IP address causes the issue :-( Any plans or ETA on solving this issue?
×
×
  • Create New...