Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6349769
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T21:40:48+00:00 2026-05-24T21:40:48+00:00

I have a PowerShell 2.0 script that I use to delete folders that have

  • 0

I have a PowerShell 2.0 script that I use to delete folders that have no files in them:

dir 'P:\path\to\wherever' -recurse | Where-Object { $_.PSIsContainer } | Where-Object { $_.GetFiles().Count -eq 0 } | foreach-object { remove-item $_.fullname -recurse}

However, I noticed that there were a ton of errors when running the script. Namely:

Remove-Item : Directory P:\path\to\wherever cannot be removed because it is not empty.

"WHAT?!" I panicked. They should all be empty! I filter for only empty folders! Apparently that’s not quite how the script is working. In this scenario a folder that has only folders as children, but files as grandchildren is considered empty of files:

Folder1 (no files - 1 folder) \ Folder 2 (one file)

In that case, PowerShell sees Folder1 as being empty and tries to delete it. The reason this puzzles me is because if I right-click on Folder1 in Windows Explorer It says that Folder1 has 1 folder and 1 file within it. Whatever is used to calculate the child objects underneath Folder1 from within Explorer allows it to see grandchild objects ad infinitum.

Question:

How can I make my script not consider a folder empty if it has files as grandchildren or beyond?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T21:40:49+00:00Added an answer on May 24, 2026 at 9:40 pm

    There were some issues in making this script, one of them being using this to check if a folder is empty:

    {!$_.PSIsContainer}).Length -eq 0
    

    However, I discovered that empty folders are not sized with 0 but rather NULL. The following is the PowerShell script that I will be using. It is not my own. Rather, it is from PowerShell MVP Richard Siddaway. You can see the thread that this function comes from over at this thread on PowerShell.com.

    function remove-emptyfolder {
     param ($folder)
    
     foreach ($subfolder in $folder.SubFolders){
    
     $notempty = $false
     if (($subfolder.Files | Measure-Object).Count -gt 0){$notempty = $true}
     if (($subFolders.SubFolders  | Measure-Object).Count -gt 0){$notempty = $true}
     if ($subfolder.Size -eq 0 -and !$notempty){
       Remove-Item -Path $($subfolder.Path) -Force -WhatIf
     }
     else {
      remove-emptyfolder $subfolder
     }
    
    }
    
    }
    
    $path = "c:\test"
    $fso = New-Object -ComObject "Scripting.FileSystemObject"
    
    $folder = $fso.GetFolder($path)
    remove-emptyfolder $folder
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a Powershell script that copies files from one location to another. Once
I have a powershell script ( setup.ps1 ), that we use as the entry
I have a simple PowerShell script that uses WMI to create a web site
I have a complex Powershell script that gets run as part of a SQL
I have a Powershell script that reads values off of the pipeline: PARAM (
I have a powershell script that is replacing patterns in a file with the
I have a PowerShell script that configures web site and web application settings in
I have a powershell script that needs to read from a config file with
We have a powershell script that creates a local html file and the owner
I have a nice powershell script that automates a particular website for my daughter.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.