Back to the blog
PRACTICAL BUSINESS GUIDES

Windows Preventive Maintenance for Small Businesses: What Should Be Checked Monthly?

Monthly maintenance should leave a useful record: what was checked, what changed and what still needs attention. Update status, storage and backup evidence each answer different questions.

A monthly Windows maintenance check should review the named computer's update status, available storage, accessible health information and agreed backup evidence. It should also capture reported problems and leave a concise record of changes, incomplete checks and follow-up decisions.

A scheduled review is a snapshot. It is not continuous monitoring, a promise to prevent faults or permission to carry out every repair discovered during the session.

For a small Suffolk County office, the useful outcome is a record the owner can act on: what needs approval, what can wait for a planned window and what requires a separate diagnosis.

Which computer and working conditions are being checked?

Start with the device identity, Windows edition and version, and the work the computer supports. A report about “the office PC” is ambiguous when several machines have similar names or different users.

Record recent symptoms before changing anything. Ask whether the person using the computer has noticed failed updates, storage warnings, unexpected shutdowns or trouble opening important files. Include approximate dates and the task affected.

Confirm that the installed Windows release is supported or has an applicable support arrangement. Support status depends on the edition and release. For example, Windows 10 Home and Pro version 22H2 reached end of support on October 14, 2025, but some devices may have Extended Security Updates or a long-term servicing edition with a different date. Do not treat a working desktop as proof of update eligibility.

Agree on access, permitted routine changes and a suitable maintenance window. An office taking payments or running appointments may need to postpone a restart even when the technician is ready to proceed.

Have updates actually completed?

Check the update status and any unresolved errors or pending restart. A downloaded update and a completed installation are different states, so record what is still required.

Microsoft explains that some updates need a restart to finish and that active hours help reduce inconvenient restarts. Active hours are a scheduling aid, not a substitute for an agreed plan.

If a restart is approved, save work first and verify that the agreed everyday applications still open afterward. If it is deferred, record who will complete it and when the status will be checked again.

Treat repeated update failures as a finding requiring investigation. Do not describe a maintenance visit as complete simply because the same failed update was attempted again. Check separately scoped application updates against the software vendor's requirements.

Is there enough storage for work and updates?

Record free space and investigate unexpected growth before deleting anything. The relevant question is whether the computer has room for its actual workload and necessary updates, not whether it meets an arbitrary universal percentage.

Microsoft's update-storage guidance explains that updates need space for downloading, installation and temporary recovery-related files. Requirements vary with the update and installed features.

Review cleanup choices with the owner. Storage Sense can remove selected temporary or Recycle Bin contents. It affects Downloads or the local availability of cloud files only if those options are turned on. Cloud files may be made online-only rather than deleted. On a computer with more than one volume, this automatic cleanup applies to the system drive. A cleanup label does not establish that every affected item is expendable.

Do not use broad deletion as a routine shortcut. Record the categories approved for cleanup and any larger storage problem that needs a separate plan.

What can reported drive health tell you?

Drive-health information can reveal warnings reported through a supported device and tool. It does not certify that a drive is fault-free or predict exactly when it might fail. A named-tool observation is not a comprehensive hardware or filesystem certification.

There is an important visibility limit: Microsoft's Windows storage-health guidance says the drive-health monitoring described in Windows Settings covers NVMe solid-state drives only. It does not monitor SATA solid-state drives or traditional hard disks through that view. This is a limit of that specific Windows check, not a claim that other tools cannot assess those drives.

If that view does not provide health data, report “not available through this check,” rather than marking the drive healthy. Record the device, tool and warning observed when information is available.

A critical warning or serious access problem should prompt an appropriate follow-up, with data preservation considered before repair attempts. Repeatedly running demanding tests on a suspect drive is not a substitute for a diagnosis and recovery plan.

What does backup verification prove?

Distinguish what was actually checked: the backup configuration, job status, destination, a sample restore, a recovery point and whether the restored files opened. Checking the destination, selected folders and latest recorded job provides useful evidence about the setup. It does not demonstrate that the files can be restored and opened.

For an agreed sample restore, use a separate destination and inspect the restored files. Microsoft's File History guidance explicitly provides a different-location restore option to avoid replacing the current version. Other backup tools require their own supported procedure.

Record exactly which files and recovery date were tested. A sample establishes evidence for those selected files, not every folder or a complete computer recovery.

Ross Core IT's Backup and Restore Check has its own selected-folder and recovery-check scope. A new backup project or a larger restore exercise should not be assumed to fit inside routine maintenance.

What should the monthly report contain?

A useful report distinguishes observations, authorized changes, verification and unfinished work. It should be understandable without requiring the owner to interpret a collection of unexplained screenshots.

Hypothetical report entry: “PC-FrontDesk: update awaiting restart; restart deferred at owner's request. Backup log reviewed; sample restore not included in this session. Free space recorded; no personal files removed. Follow-up: agree restart window and discuss restore-check scope.”

That entry is more informative than “maintenance successful” because it explains the limits of the visit.

Monthly review checklist

  • Record the named device, Windows version and support status.
  • Capture user-reported problems before changes.
  • Document update errors and restart requirements.
  • Review storage and obtain specific approval for any cleanup.
  • Record available drive-health evidence and visibility limits.
  • Describe backup checks separately from restore tests.
  • Follow approved changes with agreed functional checks.
  • Assign unfinished work a next step and decision owner.

How is scheduled maintenance different from repair or monitoring?

Scheduled maintenance checks agreed items at an agreed time. Continuous monitoring involves ongoing observation, while repair investigates or resolves a particular fault. Those services have different responsibilities and should be scoped separately.

Ross Core IT's Windows preventive maintenance service provides scheduled remote checks and agreed routine work for named PCs, with verification and reporting within the selected allowance. It does not include continuous monitoring, unlimited repairs or assumed permission for disruptive changes.

A monthly cadence also does not mean a serious new warning should wait until next month. Record and raise significant problems when they occur.

Frequently asked questions

Have updates actually completed?

Check the update status and any unresolved errors or pending restart. A downloaded update and a completed installation are different states, so record what is still required.

What does backup verification prove?

Distinguish what was actually checked: the backup configuration, job status, destination, a sample restore, a recovery point and whether the restored files opened. Checking the destination, selected folders and latest recorded job provides useful evidence about the setup. It does not demonstrate that the files can be restored and opened.

How is scheduled maintenance different from repair or monitoring?

Scheduled maintenance checks agreed items at an agreed time. Continuous monitoring involves ongoing observation, while repair investigates or resolves a particular fault. Those services have different responsibilities and should be scoped separately.

For a broader discussion of interruptions and recovery planning, read the guide to business IT downtime.

To discuss scheduled checks, send Ross Core IT the number of PCs, their Windows versions and your main concerns. Suitability, scope, availability and pricing are confirmed before booking.

Based in Holbrook, NY, serving Holbrook, Ronkonkoma, Bohemia and Suffolk County. Nassau County, Queens and Brooklyn by arrangement, confirmed per job. Suitable services are also available remotely.