# ConfigurationStatus folder filling up.

**URL:** <https://forums.powershell.org/t/configurationstatus-folder-filling-up/9746>\
**Category:** DSC\
**Created:** [November 21, 2017, 10:57am UTC](https://forums.powershell.org/t/configurationstatus-folder-filling-up/9746 "2017-11-21T10:57:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![matt-mcelreath](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@matt-mcelreath](https://forums.powershell.org/u/matt-mcelreath)\
**Post date:** [November 21, 2017, 10:57am UTC](https://forums.powershell.org/t/configurationstatus-folder-filling-up/9746/1 "2017-11-21T10:57:59Z")

</div>

We have a 2012R2 server running WMF 5.1 whose ConfigurationStatus folder under C:\Windows\System32\Configuration\ConfigurationStatus has over 69,000 files in it totaling about 25 GB. Is this folder supposed to be cleared out automatically by the DSC process or do we need to do that manually?

---

<div class="post-metadata">

**Author:** ![matt-mcelreath](https://avatars.discourse-cdn.com/v4/letter/m/a3d4f5/32.png) [@matt-mcelreath](https://forums.powershell.org/u/matt-mcelreath)\
**Post date:** [November 21, 2017, 11:03am UTC](https://forums.powershell.org/t/configurationstatus-folder-filling-up/9746/2 "2017-11-21T11:03:36Z")

</div>

I ended up coming across another topic about this same issue from WMF 5.0. The advice there was to set up a process to manually clear this folder out. Does anyone know of any updates to this? Doesn’t seem like it was fixed with the 5.1 update.

---

<div class="post-metadata">

**Author:** ![gaelcolas](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/gaelcolas/32/46_2.png) [@gaelcolas](https://forums.powershell.org/u/gaelcolas)\
**Post date:** [December 1, 2017, 5:18am UTC](https://forums.powershell.org/t/configurationstatus-folder-filling-up/9746/3 "2017-12-01T05:18:24Z")

</div>

I’m seeing similar behaviour on a Win7 Workstation with PS 5.1, and my Win 10 (I haven’t checked anywhere else yet).  
25k files ~ 2.2GB, oldest is months ago, which is probably when PC was last built.

I never changed the LCM StatusRetentionTimeInDays from the Default 10, so I’ll play with that see if it helps clearing it out.

Thanks for the heads up!

---

<div class="post-metadata">

**Author:** ![gaelcolas](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/gaelcolas/32/46_2.png) [@gaelcolas](https://forums.powershell.org/u/gaelcolas)\
**Post date:** [December 1, 2017, 7:58am UTC](https://forums.powershell.org/t/configurationstatus-folder-filling-up/9746/4 "2017-12-01T07:58:34Z")

</div>

Btw, I found the uservoice about it here (Saw your comment Matt): [https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/14343861-dsc-statusretentiontimeindays-is-not-deleting-file](https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/14343861-dsc-statusretentiontimeindays-is-not-deleting-file)  
(please everyone vote 🙂 )

And the other PoShOrg post here: [https://powershell.org/forums/topic/cwindowssystem32configurationconfigurationstatus-directory-growing/#post-40747](https://powershell.org/forums/topic/cwindowssystem32configurationconfigurationstatus-directory-growing/#post-40747)

Sounds like people using DSC via puppet came to the same conclusion: [https://tickets.puppetlabs.com/browse/MODULES-4412](https://tickets.puppetlabs.com/browse/MODULES-4412)

For now, setting to StatusRetentionTimeInDays = 5 does not seem to help on WMF5.1/Win7 (I tried changing the LCM, Running a Config, restarting machine, now letting for the next 24 hours to see if it makes any change).

---

<div class="post-metadata">

**Author:** ![dotnVo](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@dotnVo](https://forums.powershell.org/u/dotnVo)\
**Post date:** [May 16, 2024, 9:16pm UTC](https://forums.powershell.org/t/configurationstatus-folder-filling-up/9746/5 "2024-05-16T21:16:36Z")

</div>