Microsoft TIME is a mess. There are many different formats used within many different systems and some which are the same definition return different or truncated values. There is no consistancy and no point of reference that we can find for an explanation.

Microsoft FILETIME#

Microsoft TIME is a 64-bit value that represents the number of 100-nanosecond intervals that have elapsed since 12:00 A.M. January 1, 1601 Coordinated Universal Time (UTC).[1]

Microsoft TIME is a NumericDate and a DateTime

Microsoft Active Directory#

Many attributes in Microsoft Active Directory have a data type (syntax) called LargeInteger which is defined in a similar manner.

But, MsSQL use the Unix Time format as I recall.

Microsoft Windows, the Client Operating System, counts the number of 100-nanosecond ticks since 12:00 A.M. January 1, 1601 Coordinated Universal Time (UTC) as reckoned in the proleptic Gregorian calendar, but only returns the current time to the nearest millisecond.

How to Convert Microsoft Time#

From the command-line, on Vista and Windows 7 this worked.
w32tm /ntte time-as-an-integer

We also have used the on-line site Active Directory / LDAP Date Converter

Microsoft Excel#

Microsoft Excel stores DateTime as NumericDate that represents the days since 1989-12-30. This is also the VB dateTime.

More Information#

There might be more information for this subject on one of the following:

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-4) was last changed on 08-Mar-2017 10:49 by jim