Jump to content

Lucie

Honorary Members
  • Posts

    45
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Thank you for your help. its very much appreciated
  2. The june 13 kb was a malicous software removal tool that runs once on your comp when downloaded according to m.s. i guess thats why its not in the add/remove section as its not exactly an update??
  3. Ok thanks just seen your reply about the update agent
  4. also to add the june 4th update kb2718704 does show in the add/remove sections. read before with some updates that they over ride others so the updates that are over ridden dont show in add/remove section just abit concerened that even though the update agent update from june 19 and june 13 update kb 890830 show in my windows check whats been installed section they dont show in add/remove. personally i have no idea if every update should show in add/remove or only some do
  5. Thanks could you advise about my last question. as i never even knew till recently about some updates appearing in the add/remove section
  6. Thanks. i dont think im ibfected as ive done scans and had a look on google just was wanting some advice. should the update agent show in the add/remove section. it shows as installed in the update view installed update section. same with the kb890830 update from june 13
  7. Ive looked through m.s forums and it seems to be ok interms of when the two updates were installed and the time inbetween and also re the activex update. as others on m.s boards had this update message aswell.
  8. if the possible problem happened on my comp around 16th was i protected from the june 4th KB2718704 update? or was there still a problem with m.s security until the update agent was updated on the 19th?. trying to work out if there was a chance it could have been something bad on the 16th but because the update agent update didnt happen until the 19th did it leave me with a possible risk? or am i ok becasue of the update from the 4th june?. seems strange that M.S did an critical update on the 4th june but then left it till the 19th to update the agent if the problems were connected. thanks for your help
  9. ok ive checked my comp and i have the update KB2718704 installed on the 4th june . from googling that tells me that was the patch that was released on june 3rd to correct the security issue in regards to flame. can you advise as to what the update agent update was for.was it also inrelation to flame?
  10. Yes i have the update agent from the 19th. my concern is if i had the problem around the 16th then the update wasnt installed until the 19th. i will be able to chrck my comp in a few mins so will look for the update and come back
  11. Looking on google the update agent is diff from the one put out on the third june which was kb2718704 which was put out because of this security issue. I think the possible problem with the axtivex happened around the 16th. i clicked to check for updates and as normal it checks to make sure u have the right activex it said i didnt and the download came up.. is this how flame was causing issues?
  12. I see the update for this problem came out on june 3rd but as i cant get on my comp at the mo i cant see if the patch was installed then or in the the june 12th update as some articles say the update was sent then and there was only an advisory on the 3rd.
  13. Does mbytes free scanner detect the virus flame that was been installed by a fake microsoft certificate. as some reports say some antivirus dont detect it because the a.v thinks its come from microsoft when infact it hasnt. bit concerned as i had a activex update when checking for microsoft updates around the middle of june and after abit of googling its got me concerned. ive scanned several times with kaspersky and mbytes and nothing has come up and the comp is working fine
  14. Does a full scan scan more objects than if im just doing a quick scan
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.