Use case
Handle disk space issueswith safe cleanup and evidence.
Whether the issue starts as a user complaint or a device alert, GenticFlow investigates what is consuming space, applies approved cleanup actions, captures before-and-after free space, and only escalates the cases where storage growth is real and structural.
Free: 9.6 GB / 256 GB (3.8%)Top consumer: WinSxS 47.2 GBC:\Windows\SoftwareDistribution: 18.4 GBTemp folders: 6.8 GBUser Downloads: 24.1 GBGrowth rate: +2.1 GB/day (last 14d)
The problem
Low disk alerts are noise until they are crisis.
RMM fires a low-disk alert. A technician opens a session, deletes temp files, runs cleanmgr, watches the bar tick up, closes the ticket. Two weeks later the same machine alerts again. No record of what was deleted, no trend, no decision about whether the user actually needs more disk.
How GenticFlow investigates
Technicians start with context instead of a blank ticket.
GenticFlow pulls live context from the affected device, correlates against fleet baselines, and produces a root-cause hypothesis with the steps it recommends next.
Inventory the disk
Top consumers by directory and file type, system vs. user, temp vs. permanent, growth rate over the last 30 days, plus disk read and write throughput history charted alongside CPU and memory.
Classify what is safe
Match consumers against the safe-cleanup list: temp files, browser caches, Windows update cache, old restore points, crash dumps.
Detect runaway processes or logs
Identify log files growing unboundedly, application caches that never trim, dump files from repeated crashes.
Run the safe-listed cleanup
Clear temp directories, run component cleanup, clear update cache, remove orphaned crash dumps. Capture bytes reclaimed per category.
Verify free space recovered
Re-sample free space, confirm it crossed the recovery threshold, attach before-and-after with per-category breakdown.
Trend and decide
If growth rate suggests recurrence within 30 days, escalate with the trend so account management can act on it, not patch it again.
What gets resolved under policy.
The recoverable categories are cleared end-to-end with reclaimed bytes recorded per category.
What gets escalated and why.
When cleanup is not enough or when the growth is structural, the ticket arrives diagnosed with the right destination.
FAQ
Common questions.
Specific answers for service desk and operations teams evaluating this workflow.
What about user files? You wont delete the wrong thing?
Cleanups only target the safe-listed system and cache locations. User profile data, OneDrive sync directories, and project folders are never touched by automated cleanup.
Does it support shrinking the component store?
Yes, DISM component cleanup is part of the safe list with the standard /ResetBase guardrails and update-health verification afterward.
Can the policy be customized per client?
Yes. Cleanup categories, retention windows, and approval requirements are configurable per environment so a regulated client can require approval for any deletion class.
What happens on servers vs. workstations?
Server policies default to more conservative cleanup, with mandatory approval for any deletion class beyond temp and browser cache. The investigation logic is the same.
Stop running cleanmgr by hand.
See GenticFlow inventory a low-disk endpoint, run the safe cleanups, and either resolve the ticket or escalate with the growth trend attached.
Explore related
Other ways teams use GenticFlow.
Each page walks the live investigation path against a real ticket so you can compare patterns across categories and stacks.