HowToFixMe
Windows Pro Enterprise

How to configure WSUS cleanup script monthly on DHCP

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
BrandDHCP
FamilyWindows Pro Enterprise
CategoryMicrosoft
Guide typeHow To
Skill levelIntermediate

Why this matters

Configure wsus cleanup script monthly on a DHCP device is one of the highest-volume how-to searches for the Windows Pro Enterprise category. Most users find the menu path inconsistent across DHCP model revisions, so this guide gives a generalised path plus model-specific notes.

Pre-requisites

Step-by-step

  1. Locate the setting. Open settings on your DHCP device. For "configure WSUS cleanup script monthly", the option lives under one of: General, Advanced, Connectivity, Accessibility, or a DHCP-specific menu. Check the DHCP user manual for your exact model if you can't find it.
  2. Toggle the feature on. Confirm the on-screen prompt.
  3. Configure sub-options. Most features have 2-3 sub-options (mode, schedule, paired device). Pick values that match your real-world usage pattern.
  4. Save / apply. Some DHCP models auto-save, others require an explicit Done / Save tap.
  5. Test live. Trigger the feature in a real scenario to confirm the configuration is correct.

Tips that save time

Common gotchas

Region / variant notes

Some DHCP features are region-locked or only available on higher-tier SKUs. If your variant doesn't show "configure WSUS cleanup script monthly" at all, check the DHCP model spec sheet to confirm support.

Frequently asked questions

How long should the recovery / setup take?

For most DHCP Windows Pro Enterprise cases, allow 15-45 minutes the first time. Repeats are usually under 10 minutes once you know the menu path.

Will this exact procedure work on every DHCP model?

The procedure reflects current DHCP behaviour. Menu paths shift between service version generations; verify against the manual for your specific model + revision.

Is the procedure safe in production / live use?

Apply during a maintenance window where possible. Capture pre-change state. DHCP doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my DHCP support coverage?

Standard operation per the user manual + applying official service version updates does NOT void support coverage. Opening managed services, third-party repair, or unauthorised modifications can void support coverage. check before going further.

Related guides worth a look while you sort this one out:

References

Reference material, not professional advice. Validate with your vendor manual and follow local regulations.

Common patterns we see

When this symptom shows up on the affected device, three patterns repeat:

1. Recent service version update changed behavior, the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger: temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Safety + preconditions

Before any work on this hardware:

How to confirm it's actually fixed

On this unit, the test is rarely "reboot and see". Use this list:

Escalation guide

For the device in front of you, the right escalation depends on impact:

More frequently asked questions

How long does this fix usually take?

Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a tenant reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major service version generations sometimes shift the menu path; the option is usually under a similarly-named section.

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

Can I roll this back if something breaks?

Yes for software-level changes (service version rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Field notes from real Windows Pro Enterprise incidents

When I work on configure WSUS cleanup script monthly on DHCP the rhythm I lean on is the one I have built over years of these tickets. Reliability Monitor is the most underused tool in Windows, open it once and you have the last 30 days of crash history without writing a single query. DISM and sfc in that order; doing it the other way wastes a reboot when the component store is the actual problem. Whenever a Pro/Enterprise box behaves weirdly after a feature update, I check gpresult before I touch anything else: group policy is usually the culprit, not the OS.

Tools I actually reach for

For configure WSUS cleanup script monthly on DHCP on DHCP the cheapest signal I can land usually comes from rsop.msc, then Reliability Monitor (perfmon /rel), DISM when rsop.msc cannot see the layer the fault sits in, and Windows Update Troubleshooter for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.

Verification I run before I close the ticket

Before I mark configure WSUS cleanup script monthly on DHCP resolved on a DHCP unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.

sfc /scannow

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Get-HotFix | Sort-Object -Property InstalledOn -Descending | Select-Object -First 10

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Get-WinEvent -FilterHashtable @{LogName='System'; Level=2; StartTime=(Get-Date).AddHours(-24)}

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

gpresult /scope:computer /v

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

DISM /Online /Cleanup-Image /CheckHealth

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Windows Pro Enterprise detail, the disambiguation order I lean on is stable. I usually start at techcommunity.microsoft.com/category/windows for the ground-truth view on Windows Pro Enterprise. I usually start at docs.microsoft.com/windows-server for the ground-truth view on Windows Pro Enterprise. I usually start at learn.microsoft.com/windows for the ground-truth view on Windows Pro Enterprise. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on configure WSUS cleanup script monthly on DHCP have a habit of biting back. The pitfalls below are the ones I have personally walked into on a DHCP unit, not things I read about. Reliability Monitor is the most underused tool in Windows, open it once and you have the last 30 days of crash history without writing a single query. DISM and sfc in that order; doing it the other way wastes a reboot when the component store is the actual problem. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand configure WSUS cleanup script monthly on DHCP off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for DHCP on the Windows Pro Enterprise family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For configure WSUS cleanup script monthly on DHCP on a DHCP unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.