{"id":8701,"date":"2012-07-16T00:01:00","date_gmt":"2012-07-16T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2012\/07\/16\/use-powershell-to-detect-and-fix-files-with-leading-spaces\/"},"modified":"2012-07-16T00:01:00","modified_gmt":"2012-07-16T00:01:00","slug":"use-powershell-to-detect-and-fix-files-with-leading-spaces","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/use-powershell-to-detect-and-fix-files-with-leading-spaces\/","title":{"rendered":"Use PowerShell to Detect and Fix Files with Leading Spaces"},"content":{"rendered":"

Summary<\/b>: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell to detect and to fix files that have leading spaces in the file name.<\/p>\n

\"Hey, Hey, Scripting Guy! I am hoping that you can help me. We have a rather strange problem at work, and if I do not get to the end of it, I am afraid I might be looking for a new job. The reason is that for some reason we are getting files that have a leading space in the file name on one of our storage servers. This is only part of the problem because our backup program is rather old. It works—except that it fails when it finds a file with a leading space in the file name. You might say we should upgrade our backup program, and that would be fine, except that our tape array is no longer supported and new backup programs do not have the correct driver. I know, I know, I know. But, for now, I need to figure out a way to detect files that are getting this leading space in the file name. As luck would have it, the way we found out that the files were not getting backed up is that our CEO corrupted one of the files that had the leading space in it, and when we attempted to restore the file, we discovered the problem. Of course, we did not replace the guy who was in charge of backups and who must have been the last planet to know about the software and the old tape array, but no one wants to hear about that. Well anyway, now I am “on notice” and I am really hoping you can help me.<\/p>\n

—KS<\/p>\n

\"Hey, Hello KS,<\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. Wow! KS, I am sorry things have not been going so well for you recently. I am really saddened to hear about your problems at work. To be honest, I do not think I have ever created a file with a leading space in the name—don’t know why I would want to do so. As a matter of a fact, I am not certain that until I read your email to scripter@microsoft.com<\/a>, I even knew that one could create a file with a leading space in it.<\/p>\n

The first thing I decided to do was to create a file with a leading space in it. I opened Windows File Explorer, and created a new text file with 10 leading spaces. This is shown in the image that follows.<\/p>\n

\"Image<\/a><\/p>\n

But when I pressed ENTER, it seems that Windows Explorer stripped out the leading spaces. This is shown in the image that follows.<\/p>\n

\"Image<\/a><\/p>\n

Of course, the best way to check this is to use Windows PowerShell. To do this, I run the following Windows PowerShell code, which gets the length of the file name, and uses the Trim<\/b> <\/i>string method to remove excess spaces. Nothing returns, which lends credence to my suspicion.<\/p>\n

PS C:\\a> gci -Recurse | % { if($_.name.length -ne $_.name.trim().length) { “file with space”}}<\/p>\n

KS, based on this easy test, it would seem that Windows File Explorer, at least, does not permit creating files with spaces at the beginning of the name. So someone is using some other method to create the files. If I am going to test my code, I need a quick easy way to create files with leading spaces. To do that, I need to use Windows PowerShell. I create a function called New-FilesWithLeadingSpaces<\/b>. This function accepts three parameters. The first is the path to create the files, and the second is a base file name parameter. I set the default value to myfile.txt<\/b>, but you could use any string you choose to do this. The final parameter is Count<\/b>, which tells the function how many files to create. Inside the function, I have a for<\/b> <\/i>loop that counts up to the Count<\/b> property. Inside the loop I create a space padding string that I prepend to each FileBaseName<\/b>. Of course the ItemType<\/b> is file. Here is the new New-FilesWithLeadingSpaces<\/b> function:<\/p>\n

Function New-FilesWithLeadingSpaces<\/b><\/p>\n

{<\/p>\n

 Param([string]$path = “c:\\test”,<\/p>\n

       [string]$FileBaseName = “myfile.txt”,<\/p>\n

       [int]$count)<\/p>\n

  For($i = 0; $i -le $count ;$i ++)<\/p>\n

    { $pad = ” ” * $i<\/p>\n

     New-item -Path $path -Name “$pad$FileBasename” -ItemType file}<\/p>\n

} #end function new-FileWithLeadingSpaces<\/p>\n

When I run the script, I bounce over to the Windows File Explorer, and it is obvious that Windows does, in fact, permit files with a leading space—KS, a fact unfortunately of which you are painfully aware. The Windows File Explorer results are shown here:<\/p>\n

\"Image<\/a><\/p>\n

So, I created a new function called Get-FilesWithLeadingSpaces<\/b>. This function accepts a single parameter, Path<\/b>, which specifies from whence the search begins. Next, the Get-ChildItem<\/b> cmdlet with the –recurse<\/b> switch is used to return the FileInfo<\/b> objects that are piped to the Foreach-Object<\/b> cmdlet. Inside the loop, the length of a file name is compared with the length of the file name after using the Trim<\/b> <\/i>method to remove any trailing spaces. Using the Trim<\/b> <\/i>string method is perfect for this application. The following illustrates using Trim<\/b>. <\/i>First, a variable that holds five spaces and the word fiveSpaces<\/b> is created. That value displays and shows that there are five spaces preceding the value. Now, the Trim<\/b> method is called to remove the spaces. This is shown here:<\/p>\n

PS C:\\a> $name = ”     fiveSpaces”<\/p>\n

PS C:\\a> $name<\/p>\n

     fiveSpaces<\/p>\n

PS C:\\a> $name.Trim()<\/p>\n

fiveSpaces<\/p>\n

If the length of the trimmed file name is not equal to the file name, it means that it contains either leading or trailing spaces. Therefore, the file name displays to the console. The complete function is shown here:<\/p>\n

Function Get-FilesWithLeadingSpaces<\/b><\/p>\n

{<\/p>\n

 Param([string]$path = “c:\\a”)<\/p>\n

 Get-ChildItem -Path $path -Recurse |<\/p>\n

 foreach-object {<\/p>\n

   if($_.name.length -ne $_.name.trim().length)<\/p>\n

    { “$($_.basename) contains a leading space”} }<\/p>\n

} #end function Get-FilesWithLeadingSpaces<\/p>\n

When the function loads and is run, the output in the Windows PowerShell ISE appears as shown here:<\/p>\n

\"Image<\/a><\/p>\n

If there was only one file, renaming it might not be too bad. But in the case of my example, if I renamed each file after removing the leading spaces, I would end up with a bunch of duplicate files. Therefore, I decided to add a counter number to the file name after renaming it. Renaming a file in Windows PowerShell is trivial because there is a Rename-Item<\/b> cmdlet that takes a Path<\/b> <\/i>and a new Name<\/b> parameter. Rather than creating a new function with much of the same capabilities of the Get-FilesWithLeadingSpaces<\/b> function (such as detecting files that have a leading space in the name, I decided instead to add a Rename<\/b> <\/i>switch to rename the files with leading spaces in the name. Adding a switched parameter is super easy in Windows PowerShell—all you do is use the [switch]<\/b> type constraint in front of the variable name as shown here:<\/p>\n

[switch]$rename<\/p>\n

Because I wanted an easy way to create a unique file name, I added a counter variable at the Begin<\/b> <\/i>portion of the Foreach-Object<\/b> command. In the Begin<\/b> <\/i>portion, I set the value of the $count<\/b> variable to 0. This appears here.<\/p>\n

-Begin {$count = 0}<\/p>\n

When I detect that I have a file name with spaces either before or after the file name, I check to see if the $rename<\/b> switch appears. If it does, the Rename-Item<\/b> cmdlet renames the file. The path is the FullName<\/b> <\/i>property from the FileInfo<\/b> object. The FullName<\/b> <\/i>property contains the complete path to the file, and it should always be used when working with files that are discovered via the Get-Item<\/b> cmdlet (this is one good property name to remember). Next, the new name needs to be created. First I take the BaseName<\/b> property—that is the file name without the path or the file extension. I trim that BaseName<\/b>, and then I use the count number from the $count<\/b> variable. Lastly, I add back in the file extension. The file extension is always available from the Extension<\/b> <\/i>property. If at any time you are not certain of what properties you have available to you, use the Get-Member<\/b> cmdlet to display the properties of your file. This technique is shown here:<\/p>\n

PS C:\\a> Get-Item .\\myfile.txt | Get-Member -MemberType property<\/p>\n

 <\/p>\n

   TypeName: System.IO.FileInfo<\/p>\n

 <\/p>\n

Name              MemberType Definition<\/p>\n

—-              ———- ———-<\/p>\n

Attributes        Property   System.IO.FileAttributes Attributes {get;set;}<\/p>\n

CreationTime      Property   System.DateTime CreationTime {get;set;}<\/p>\n

CreationTimeUtc   Property   System.DateTime CreationTimeUtc {get;set;}<\/p>\n

Directory         Property   System.IO.DirectoryInfo Directory {get;}<\/p>\n

DirectoryName     Property   System.String DirectoryName {get;}<\/p>\n

Exists            Property   System.Boolean Exists {get;}<\/p>\n

Extension         Property   System.String Extension {get;}<\/p>\n

FullName          Property   System.String FullName {get;}<\/p>\n

IsReadOnly        Property   System.Boolean IsReadOnly {get;set;}<\/p>\n

LastAccessTime    Property   System.DateTime LastAccessTime {get;set;}<\/p>\n

LastAccessTimeUtc Property   System.DateTime LastAccessTimeUtc {get;set;}<\/p>\n

LastWriteTime     Property   System.DateTime LastWriteTime {get;set;}<\/p>\n

LastWriteTimeUtc  Property   System.DateTime LastWriteTimeUtc {get;set;}<\/p>\n

Length            Property   System.Int64 Length {get;}<\/p>\n

Name              Property   System.String Name {get;}<\/p>\n

The newly added rename <\/i>clause appears here.<\/p>\n

if($rename)<\/p>\n

      {<\/p>\n

        Rename-Item -Path $_.fullname -NewName (“{0}{1}{2}” -f `<\/p>\n

         $_.basename.trim(),$count,$_.extension)<\/p>\n

        $count++<\/p>\n

        }<\/p>\n

The complete function is shown here:<\/p>\n

Function Get-FilesWithLeadingSpaces<\/strong><\/p>\n

{<\/p>\n

 Param(<\/p>\n

       [string]$path = “c:\\a”,<\/p>\n

       [switch]$rename<\/p>\n

       )<\/p>\n

 Get-ChildItem -Path $path -Recurse |<\/p>\n

 foreach-object -Begin {$count = 0} -process {<\/p>\n

   if($_.name.length -ne $_.name.trim().length)<\/p>\n

    {<\/p>\n

     if($rename)<\/p>\n

      {<\/p>\n

        Rename-Item -Path $_.fullname -NewName (“{0}{1}{2}” -f `<\/p>\n

         $_.basename.trim(),$count,$_.extension)<\/p>\n

        $count++<\/p>\n

        }<\/p>\n

     else<\/p>\n

      {“$($_.basename) contains a leading space”}} }<\/p>\n

} #end function Get-FilesWithLeadingSpaces<\/p>\n

After I run the function, I go back into the Windows File Explorer to see if it worked. As shown here, it worked perfectly.<\/p>\n

\"Image<\/a><\/p>\n

KS, that is all there is to using Windows PowerShell to detect files that have leading spaces. Join me tomorrow for more good Windows PowerShell stuff.<\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b> <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell to detect and to fix files that have leading spaces in the file name. Hey, Scripting Guy! I am hoping that you can help me. We have a rather strange problem at work, and if I do not get to the end of […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[38,3,4,12,45],"class_list":["post-8701","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-files","tag-scripting-guy","tag-scripting-techniques","tag-storage","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, shows how to use Windows PowerShell to detect and to fix files that have leading spaces in the file name. Hey, Scripting Guy! I am hoping that you can help me. We have a rather strange problem at work, and if I do not get to the end of […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/8701","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=8701"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/8701\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=8701"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=8701"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=8701"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}