Finding Old Files

When it comes to finding old files in PowerShell we have several options, all in which involve subtracting DateTime objects or using comparison operators. For example, if we want to remove all files older than 14 days, we can test if the LastWriteTime property of each FileInfo object is greater than a DateTime objects which has been subtracted 14 days:

In the above example we initialize $date to a date in the past and test against it inside Where-Object.  When the older file is found, based on its LastWriteTime property, it is passed through to the Remove-Item cmdlet.

However, this doesn’t tell as the age of the file. We can produce a list of old files and create a new calculated property that will calculate the age:

Now we get a 3-column output with an age of each file system object (including directories).
The expression we are using subtracts the LastWriteTime value of each file from the current date, which produces a TimeSpan object, and then we call its Days property to get the result.

But, did you know that you can also pipe file system objects to the New-TimeSpan cmdlet and it will give you the same result?


As you can see, system.ini is 137 days old. So, how does this work? Let’s take a close look of the Start parameter of New-TimeSpan:


The Aliases member has the LastWriteTime alias defined, meaning that if an incoming object has a property of that name it will be automatically bind to the Start parameter. Pretty neat. So, based on the above we can also write a shorter expression:

Filed in: Did you Know? Tags: ,
© 2018 PowerShell Magazine. All rights reserved. XHTML / CSS Valid.
Proudly designed by Theme Junkie.
%d bloggers like this: