Hi guys
I have configured my MSE to check for updates every 6 hours but have noticed the definition times are different to my pc and seem to follow no patern.For example my last update was at 11.48 this morning but mse reports definition 1.85.1695.0 was created at 02.46.My pc clock is correct.Anyone any ideas.
Thanx
Hi xxxdannyxxx, the answer here is very simple:
The Time and Date stamp on the updates is the time that the definitions were created. NOT the time that you installed them. There is nothing wrong with your setup there, it is simply telling you that MS created the definitions at 2.46AM (your time) These are the latest definitions available, and so thats what you got at 11.48.
Does that make sense?
Thanks severedsolo
Yer that makes sense now.I was getting 3 or 4 updates a day but none of them seemed to match but didnt read the CREATED bit.lol
Alls well then thankyou
I noticed this when I was trying to run MSE. The updates were to the minute x number of hours off, 6 or 8 can't remember now, meaning there was a time zone difference not a created on as opposed to when you installed it as you say. I never read any info as to why there was a difference in so many hours. Wait a minute, re-reading your post a couple of times, I see that we may be saying the same thing. Are we,lol?
hi !
no Greg S, you should read severedsoloīs post again.
forget about the timezones, MSE definitions are normally released 2-3 times daily, itīs the CREATION-time you see.
If you're interested, you can subscribe to the MMPC Definition Change Log: https://www.microsoft.com/security/p.../WhatsNew.aspx
hi !
donīt know what you mean Greg ?
severedsolo has already explained it very well.
of course there can be a time-difference between the CREATION-time and the DOWNLOAD-time into your computer.
unless you have used fx. my tip about taskscheduler or you download manually,
if the definitions are fx. downloaded before a scan, itīs NOT the same minute Microsoft release them.
take a look, start MSE and click on Update: "Definitions Created on:....."
What I'm saying is, they are creating the defs, holding them for said hours, then releasing them for installation which must be the difference of the several hours between the two. I was always under the impression the defs were created and ready for installation within minutes of creation which must not be the case because one wouldn't have the hours difference between the two. This is where I got the Time Zone thingy from. My udpates were always exactly x number of hours between the two. No big deal, just curious
From https://www.microsoft.com/security/p...efinition_date
Note also that the date/time are displayed as UTC: https://www.microsoft.com/security/p...sed&Package=AMWhat does definition available date/time mean?
The definition available date/time is the date and time that the definition is available to download. Your Microsoft product may display the created date/time, which is the date and time that the definition was created. There is often a time lag between the created date/time and the available date/time.
Edited to add:
Hi, Greg S
It isn't a matter of "holding" the definitions for a number of hours, but rather the time difference between when the final set of definitions were approved and uploaded to the download servers. I have no idea what the final process is for obtaining approval to release or how many people are involved in creating the definitions, at what stage testing or translations are completed. However, any of those aspects could account for a time delay between completion and availability.
Last edited by Corrine; 08 Jul 2010 at 20:39. Reason: update & typo :)
Quote