Description of problem:

From a product perspective, any action to be taken for the below situation

While debugging an OCP issues on a unstable windows nodes(unstable due to multiple reasons), we noticed C:/var/log/wicd having 30000+ files. On some of the nodes, they noticed millions of files.
Unexpected node reboots + issues due to Antivirus + stability issues caused due to hybrd-overlay-node restarts can be attributed to this behavior.

WMCO/windows-instance-config-daemon should implement an internal log rotation policies in a way not to maintain more than 9 files (3 symlinks + 3 current logfiles and 3 older log files. Just an suggestion).

If the node is stable, then we wont hit this problem.

The issue can be reproduced by performing the following steps. Manual restart is just to show a corner case

1\. No files

PS C:\var\log\wicd> ls
PS C:\var\log\wicd> 

2. Start the service. Expected data in seem

PS C:\var\log\wicd> ls


    Directory: C:\var\log\wicd


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---l          2/3/2026  10:59 PM              0 windows-instance-config-daemon.exe.INFO
-a----          2/3/2026  10:59 PM              0 windows-instance-config-daemon.exe.WIN-ODPMD11LAOI.WORKGROUP_WIN-ODPMD11LAOI$.log.INFO.20260203-225914.6320

3. Restart the service

PS C:\var\log\wicd> Restart-service windows-instance-config-daemon

4. We ended up creating these many files

PS C:\var\log\wicd> (Get-ChildItem "C:\var\log\wicd" -File).Count
323

Another restart, almost double the number of files

PS C:\var\log\wicd> (Get-ChildItem "C:\var\log\wicd" -File).Count
648

    

Version-Release number of selected component (if applicable):
OCP 4.20/WMCO 10.20

How reproducible:
Always

Steps to Reproduce:

1. On a Windows 2022 Worker node, restart the service "Restart-service windows-instance-config-daemon" multiple times
2. check the number of files under C:\var\log\wicd

Actual results:
Wicd log folder(C:\var\log\wicd) has millions or thousands of files if the windows-instance-config-daemon service gets restarted due to multiple issues
Expected results:
There should be a control on number of files. Older files should be removed during start and a minimum number of files should be maintained
Additional info: