Delete contents of a folder every night


Recommended Posts

there are several ways.

the way I would do it is set a task in task scheduler and either set the delete command right in the task or point the task to a batch file

  • Like 2

Off the top of my head, I'd probably create a batch script and put it into the task scheduler to run each night, maybe at 0300 or something.

I think the command would be:

cd C:\Users\James\AppData\Local\Plex Media Server\Cache\
rmdir /s /q PhotoTranscoder

 

On 08/02/2024 at 10:03, Nick H. said:

Off the top of my head, I'd probably create a batch script and put it into the task scheduler to run each night, maybe at 0300 or something.

I think the command would be:

cd C:\Users\James\AppData\Local\Plex Media Server\Cache\
rmdir /s /q PhotoTranscoder

 

technically don't even need the cd command; can just be a one line command. also would need "" around the directory path due to the spaces in the Plex Media Server folder.

rmdir /s /q "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder"

 

On 08/02/2024 at 08:07, Brandon H said:

technically don't even need the cd command; can just be a one line command. also would need "" around the directory path due to the spaces in the Plex Media Server folder.

rmdir /s /q "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder"

 

Thank you, what would be the command to just delete the contents of the folder instead of the folder itself ?

On 08/02/2024 at 11:09, jamester64 said:

Thank you, what would be the command to just delete the contents of the folder instead of the folder itself ?

I think a standard del command with a * wildcard should work

del /S /Q /F "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*"

 

On 08/02/2024 at 12:18, Brandon H said:

I think a standard del command with a * wildcard should work

del /S /Q /F "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*"

 

Please note, these "del" and "rmdir" commands will not work with powershell and will only work in the context of cmd.exe

 

If you are going to create a scheduled task for this and wish to use these CMD commands, you will need to create the "Action" as follows:

In the "Program/script" portion of adding a new "Start a program" action, you would put cmd.exe with the arguments /C "del /S /Q /F 'C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*"'

 

A functional scheduled task would look like this:

image.png.cca282ba8e80f86fac5d05c704697108.png

On 08/02/2024 at 09:18, Brandon H said:

I think a standard del command with a * wildcard should work

del /S /Q /F "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*"

 

That deleted the contents of the folders inside the directory but left the folders

Looking to delete the entire contents of this folder  C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder

On 08/02/2024 at 12:28, jamester64 said:

That deleted the contents of the folders inside the directory but left the folders

Looking to delete the entire contents of this folder  C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder

You can do this with Powershell and the "Remove-Item" command: 

remove-item c:\utils\test\* -recurse -force

If you wanted to bake it into a scheduled task, you can run powershell.exe with the -command argument like follows:

powershell.exe -command "remove-item c:\utils\test\* -recurse -force"

 

  • Like 2
  • Love 1
On 08/02/2024 at 11:28, jamester64 said:

That deleted the contents of the folders inside the directory but left the folders

Looking to delete the entire contents of this folder  C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder

yeah, bad limitation of the two commands. alternate option would be go back to previous command and just have a 2nd command to recreate the folder after I think

rmdir /s /q "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder"
mkdir "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder"

 

On 08/02/2024 at 11:32, satukoro said:

You can do this with Powershell and the "Remove-Item" command: 

remove-item c:\utils\test\* -recurse -force

 

also a good option. I'm still familiarizing myself with the PowerShell version of commands like that so didn't think of it.

On 08/02/2024 at 12:33, Brandon H said:

yeah, bad limitation of the two commands. alternate option would be go back to previous command and just have a 2nd command to recreate the folder after I think

rmdir /s /q "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder"
mkdir "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder"

also a good option. I'm still familiarizing myself with the PowerShell version of commands like that so didn't think of it.

I nearly posted the same solution of "make the directory after deleting it" but realized I had just done this in a .ps1 script I wrote for something random at my job.

On 08/02/2024 at 09:32, satukoro said:

You can do this with Powershell and the "Remove-Item" command: 

remove-item c:\utils\test\* -recurse -force

If you wanted to bake it into a scheduled task, you can run powershell.exe with the -command argument like follows:

powershell.exe -command "remove-item c:\utils\test\* -recurse -force"

 

Running this in PS doesn't seem to do anything,

remove-item C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\* -recurse -force 

On 08/02/2024 at 13:02, jamester64 said:

Running this in PS doesn't seem to do anything,

remove-item C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\* -recurse -force 

don't forget your quotes around the directory path due to the spaces

remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force

and this would be run from powershell.exe instead of cmd.exe | or as a .ps1 file instead of .cmd

On 08/02/2024 at 11:08, Brandon H said:

don't forget your quotes around the directory path due to the spaces

remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force

and this would be run from powershell.exe instead of cmd.exe | or as a .ps1 file instead of .cmd

Got it :-)

remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force

Thank you

  • Like 3
On 08/02/2024 at 11:08, Brandon H said:

don't forget your quotes around the directory path due to the spaces

remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force

and this would be run from powershell.exe instead of cmd.exe | or as a .ps1 file instead of .cmd

I'm having trouble running this in task schedule 

this is what I have in scheduler and I see PS quickly open then close but files remain, not sure what I am missing

-command remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force

Annotation 2024-02-08 132328.png

On 08/02/2024 at 15:25, jamester64 said:

I'm having trouble running this in task schedule 

this is what I have in scheduler and I see PS quickly open then close but files remain, not sure what I am missing

-command remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force

Annotation 2024-02-08 132328.png

if you're setting the 'program' to powershell.exe then you don't need '-command' at the beginning of your argument

On 08/02/2024 at 13:30, Brandon H said:

if you're setting the 'program' to powershell.exe then you don't need '-command' at the beginning of your argument

Program is set to Powershell.exe and added just this to argument and still not working in scheduler,        remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force

not sure what I'm doing wrong

Edit- I just found a way to make it work by adding this  -ExecutionPolicy Bypass C:\Users\James\PlexClean.ps1

Edited by jamester64
On 08/02/2024 at 18:30, jamester64 said:

Program is set to Powershell.exe and added just this to argument and still not working in scheduler,        remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force

not sure what I'm doing wrong

Edit- I just found a way to make it work by adding this  -ExecutionPolicy Bypass C:\Users\James\PlexClean.ps1

I apologize for the late reply. If you wanted to avoid including -executionpolicy bypass and/or using a .ps1, the argument field should look like the following:

-command 'remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force'
# or alternatively this:
-command "remove-item 'C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*' -recurse -force"

The issue with what you had in there before was the missing single quote. By placing the entire command within a set of quotes (either single or double, but not the same ones you use for your folder path), you pass the entire quoted string into powershell.

If you want to continue using your powershell script file (.ps1), the argument field could look like this:

-executionpolicy bypass -file "c:\path\to\script.ps1"

It looks like you figured it out on your own, but I wanted to add this information for clarity.

--

On 08/02/2024 at 16:30, Brandon H said:

if you're setting the 'program' to powershell.exe then you don't need '-command' at the beginning of your argument

In regards to this, I think you only need the -command argument if you are not going to reference a script. I have not tested this however to see if -command is an implied argument for powershell. Another thing to note (according to the following link) is that the -command argument must be the final argument, otherwise the rest of the arguments are run as part of the -command arg. More information can be found here: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1

On 09/02/2024 at 08:24, satukoro said:

I apologize for the late reply. If you wanted to avoid including -executionpolicy bypass and/or using a .ps1, the argument field should look like the following:

-command 'remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force'
# or alternatively this:
-command "remove-item 'C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*' -recurse -force"

The issue with what you had in there before was the missing single quote. By placing the entire command within a set of quotes (either single or double, but not the same ones you use for your folder path), you pass the entire quoted string into powershell.

If you want to continue using your powershell script file (.ps1), the argument field could look like this:

-executionpolicy bypass -file "c:\path\to\script.ps1"

It looks like you figured it out on your own, but I wanted to add this information for clarity.

--

In regards to this, I think you only need the -command argument if you are not going to reference a script. I have not tested this however to see if -command is an implied argument for powershell. Another thing to note (according to the following link) is that the -command argument must be the final argument, otherwise the rest of the arguments are run as part of the -command arg. More information can be found here: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1

Thank you for the explanation of what i was doing wrong and the fix ;-) 

Did some testing and this line worked 

-command "remove-item 'C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*' -recurse -force"

This line did not 

-command 'remove-item "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\*" -recurse -force'

 

# Specify directory to clear
$Path = "C:\Users\James\AppData\Local\Plex Media Server\Cache\PhotoTranscoder"

# Remove items
Remove-Item "$Path\*" -Recurse -Force

Save as Clear-PlexCache.ps1

Task scheduler:

Run: powershell.exe
Command arguments: -ExecutionPolicy Bypass -File "Clear-PlexCache.ps1"
Folder to start in: <path to script folder>

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • FxSound 1.2.9.0 / 1.2.10.0 Beta by Razvan Serea FxSound (formerly DFX Audio Enhancer / FxSound Enhancer) is now free, making high-quality audio enhancement accessible to everyone. Designed for all PC sound systems, from average setups to audiophile-grade equipment, it offers automatic or fully customizable processing. As automatic or customizable as you want, it utilizes the highest-grade processing to deliver more volume, better equalization, and a wider, deeper sound. For the serious audiophiles, FxSound gives you the tools to adjust the FxSound Effects and EQ to your exact preferences. Turn FxSound on and immediately hear the difference in sound quality. FxSound is ideal for budget audiophiles, music lovers, gamers, transcriptionists, Netflix enthusiasts, and more. It’s particularly beneficial for those relying on quiet laptop speakers or low-quality audio hardware. As a free tool, FxSound excels in boosting volume, enhancing bass, and improving sound quality. No other free EQ for Windows matches its ease of use. FxSound Is Now Completely Free and Unrestricted FxSound Pro is now free for everyone, not just those who can afford it. Get free and unrestricted access to better sound today. FxSound is now entirely supported by users. Click here to donate to help fund continued development and improvements to FxSound. FxSound 1.2.9.0 changelog: Auto save preset when Equalizer or Effects settings are changed Reset to factory defaults can reset the unsaved preset changes Settings dialog UI improvements for Audio and Equalizer sections Output device list is now displayed in the device preference order Preset is selected immediately when the preset for an active output device changes from settings Fixes and improvements in preferred output device selection Fixed crash issue #487 Fixed preset not getting applied and EQ flat after update (#403 and #472) Fixed system audio device not being restored on reboot (#483) Fixed preset export and import dialogs not shown when always on top is enabled Fixed audio not being restored on exit after the preset save dialog Fixed FxSound on/off handling on Windows session changes FxSound 1.2.10.0 Beta changelog: Command line options can now be applied to an already running instance of FxSound Command line option added to launch FxSound minimized to the system tray Fixed output device not being changed through hotkeys when FxSound is off (#524) Individual hotkeys can now be disabled with Delete key (#515) Fixed the but to prevent invalid hotkeys from being registered (#523) Bluetooth devices removed from device settings are removed from device preference list Fixed device detection failures Fixed application hang when retrieving the audio mix format fails Fixed presets import dialog file name combo box text alignment Fixed output device not being applied through command line Fixed a delay blocking application load when minimizing to the system tray Fixed EQ band sliders not refreshing when switching number of bands (#521) Fixed user-set mute being overridden by FxSound Fixed icon visibility in ARM64 version Finnish language support added Corrected Persian translations Download: FxSound 1.2.9.0 | ARM64 | ~70.0 MB (Open Source) Download: FxSound 1.2.10.0 Beta | ARM64 View: FxSound Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • mIRC 7.84 Final by Razvan Serea mIRC is a full featured Internet Relay Chat client for Windows that can be used to communicate, share, play or work with others on IRC networks around the world, either in multi-user group conferences or in one-to-one private discussions. It has a clean, practical interface that is highly configurable and supports features such as buddy lists, file transfers, multi-server connections, SSL encryption, proxy support, UTF-8 display, customizable sounds, spoken messages, tray notifications, message logging, and more. mIRC also has a powerful scripting language that can be used both to automate mIRC and to create applications that perform a wide range of functions from network communications to playing games. mIRC has been in development for over a decade and is constantly being improved and updated with new technologies. mIRC 7.84 changelog: Added custom dialog editbox option 'optional' for grayed out optional text. Fixed DirectShow temporary wave file not being deleted on exit. Changed $urlget() to retry a connection without compression in the event of an error. Updated code signing certificate to use Azure Artifact Signing. Fixed menubar display bug when in dark mode. Fixed /server -a not preserving existing entry's codepage. Fixed Address Book nick colors "idle time" display bug. Changed installer to no longer require administrator access on startup. Added support for displaying an MDI window's System menu when right-clicking its titlebar. Updated libararies to OpenSSL v3.5.7, TagLib v2.2.1, Zlib v1.3.2, and ADA v0.5.5. Updated CA root certificates cacert.pem file. For a full list of recent changes, please see the versions.txt file. Download: mIRC 7.84 | 4.3 MB (Shareware) View: mIRC Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You might be right... Look at his name, hiding in plain sight: hAmId.
    • ExplorerPatcher 26100.8457.70.3 by Razvan Serea ExplorerPatcher is a versatile and free tool that allows you to tweak and enhance the Windows Explorer. It comes with a range of useful features, including the ability to add new context menu items, change file name colors, and enable hidden features. Feature summary Choose between Windows 11 or Windows 10 taskbar (with labels support, small icons and lots of customization). Disable Windows 11 context menu and command bar in File Explorer and more. Open Start to All apps by default, choose number of frequent apps to show, display on active monitor and more. Choose between the Windows 11, Windows 10 and Windows NT Alt-Tab window switcher with customization. Lots of quality of life improvements for the shell, like: Skin tray menus to match Windows style, make them behave like flyouts and center them relative to the icon. Choose action when left and/or right clicking the network icon. Revert to the Windows 7 search box in File Explorer, or disable Windows Search altogether. Disable immersive menus and use mitigations that help you run the real classic theme without glitches. Discover the program's full range of features by reading this wiki article. ExplorerPatcher 26100.8457.70.3 changelog: Tested on OS builds 22621.4317, 22631.7079, 26100.6899, 26100.8037, 26200.8246, 26200.8457, 26300.8493, and 28000.2113. TIP: Windows Defender no longer flags ExplorerPatcher. It is no longer needed to configure Defender exclusions. Enjoy! Important Update for Windows Insider Users If you're running Windows 11 Beta build 26220.8474 or Experimental build 26300.8493, updating ExplorerPatcher is highly recommended. Microsoft has removed parts of the old Windows 10 Start menu from these builds, which caused ExplorerPatcher's Windows 10-style taskbar and Start menu to crash. This update fixes those issues and ensures Explorer starts correctly after future Windows updates. Because the required components are no longer included in Windows, the Windows 10 Start menu option has been disabled on these builds and future builds that lack the necessary files. A temporary workaround is to replace StartTileData.dll with a version from build 26xxx.8457, but this solution may stop working in future releases. The good news: development on the Windows 10 Start menu isn't over yet. More updates are planned. Highlights Fixed crashes affecting the Windows 10 battery flyout on Windows builds 25951 and newer. As part of that fix, network flyout buttons now behave like they did before Windows 11 version 24H2. Changes to the Primary taskbar location on screen setting now apply instantly without requiring a restart. ExplorerPatcher no longer modifies Windows 11 taskbar auto-hide settings when Explorer starts. The Open Start in All apps by default option is now hidden when the new Windows 11 Start menu is enabled. Fixed Windows 10 Start menu crashes on very early Windows 11 builds (21996–22000.51). Fixed a crash in Registry Editor when switching to thumbnail view during registry import/export operations. Improved compatibility with recent Windows builds, especially ARM64 and upcoming 26H1 releases. Improved overall ARM64 performance. Added Greek language translations. Thanks to @KonVetsos! ep_taskbar Improvements ep_taskbar now supports all 43 Windows 11 display languages. Fixed several issues in the system tray and other taskbar components. For mod developers: DLL naming has been simplified and made easier to understand. For mod developers: internal TrayUI changes provide better stability across Windows builds that use different taskbar implementations. Windows 10 Start Menu Improvements To help preserve compatibility, ExplorerPatcher now includes a newly recreated version of the tile layout engine that Microsoft removed in build 26xxx.8474. Current limitations: Tiles may occasionally overlap when pinned in certain ways. Restarting StartMenuExperienceHost.exe or Explorer usually corrects the layout. Further improvements are planned. Additional Fixes Added a blacklist that prevents ExplorerPatcher's shell extension from loading inside specific applications where it may cause problems. Updated Windows 10 Start menu animation support for newer ARM64 Insider builds. Fixed a rare taskbar initialization deadlock that could occur during startup. Start10 Updates Addressed a new compatibility issue caused by Microsoft's ongoing removal of tablet mode code in Windows 11 25H2 Experimental builds. Pinned tiles are no longer reset after repeated crashes. Various wording and interface text improvements throughout the application. Translation and UI Several interface strings have been cleaned up and clarified. Thanks to @sefinek for wording improvements. Please consult the README for more details. Download: ExplorerPatcher 26100.8457.70.3 | ARM64 | ~11.0 MB (Open Source) View: ExplorerPatcher Home Page | Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This author may be AI..... we just...... don't know.... lol AI is taking over.....run for the hills!
  • Recent Achievements

    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      +Edouard
      165
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Michael Scrip
      87
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!