Access Official Technical PDF

Share Summary:LinkedInEmail

Outdated software management is a practical concern wherever computers support daily operations. Avast’s 2019 PC Trends Report found that 55% of software on the consumer devices in its dataset was out of date, while the average PC was six years old. Those figures describe consumer PCs, not industrial control systems, but they highlight lifecycle challenges familiar to automation teams: software can remain installed long after support ends, and hardware may stay in service well beyond a typical replacement cycle.

For engineers, system integrators, and plant managers, the useful takeaway is not to apply consumer-device percentages to factory assets. It is to treat software versions, vendor support, and hardware age as information that needs active oversight. These factors can affect security exposure, compatibility, and maintenance planning across an organization’s broader computing environment.

Why outdated software management matters

The report found that 55% of installed programs across its dataset were outdated. It also noted that outdated applications can create bugs and compatibility problems, and may contain security vulnerabilities. Examples included older versions of VLC Media Player and Skype, as well as Java releases that were not current at the time of publication.

Industrial organizations face their own software lifecycle constraints. An update that is routine on an office PC may require additional evaluation when a computer supports an engineering workstation, production application, or connected operational workflow. The report does not assess those environments, but its findings reinforce the need to know what software is installed and whether its publisher still supports it.

A useful review process can distinguish among:

  • Current software that is receiving updates and is compatible with its intended use.
  • Outdated but supported software that needs a planned update.
  • Unsupported software that no longer receives vendor fixes and requires a risk-based replacement or mitigation plan.
  • Unneeded software that can be removed after confirming it is not a dependency for another application.

This last point matters because the report found that tools and frameworks were more numerous than some familiar end-user applications. Components such as Microsoft Visual C++ Redistributable, Java, and Adobe Flash Player could be installed to support other programs. Removing a framework without checking dependencies may disrupt an application; leaving unnecessary or unsupported components in place can also create avoidable maintenance concerns.

Operating system versions require lifecycle planning

In the report’s 2018 data, Windows 7 remained the most widely used Windows version at 43%, while Windows 10 had reached 40%. The report also identified users on Windows XP and Windows Vista, and described Windows 7 systems running the initial release without Service Pack 1 as outside support. For Windows 10, it reported that 9% of devices were using versions considered out of date at that time.

These are historical figures, not a description of current Windows usage or support status. Their broader lesson is that operating system adoption and update cycles do not automatically keep every device current. Teams need a reliable inventory of installed versions, plus a way to identify assets approaching or past the end of vendor support.

In operational settings, update decisions should account for application requirements and system dependencies. A managed process can document the version in use, the support status, the business or operational function, and the next review or upgrade action. That makes it easier to prioritize devices and avoid treating every computer as if it had the same role or update window.

Aging hardware affects refresh decisions

The report put the average age of consumer PCs at six years, up from five and a half years in 2017. It also found that 67% of the PCs in its dataset were laptops or tablets, that three-quarters had dual-core processors, and that nearly half had 4 GB of RAM. These observations describe the report’s consumer-device population; they should not be used as benchmarks for industrial computers.

For technical decision-makers, the relevant point is that hardware can remain in use for years, making lifecycle planning important. Age alone does not establish that a device must be replaced. However, recording age alongside operating system, application compatibility, and support information can help teams assess whether a machine remains suitable for its assigned role.

Storage technology was another indicator of the period’s hardware mix: about 85% of devices had a hard disk drive only, while approximately 15% had an SSD, either alone or alongside an HDD. The report connected this low SSD adoption with the slow replacement of older PCs. For organizations planning refreshes, storage type can be one element of an asset profile, but the report does not establish how any particular industrial system will perform.

Build a practical review around asset visibility

The report’s dataset came from anonymized information collected through an automatic software updater included with Avast and AVG security software, covering 163 million devices. Its analysis excluded Avast, AVG, and other third-party security products to reduce bias in that category. This methodology is useful context: the findings are based on a large consumer-device dataset, but they are not a survey of industrial automation assets.

Organizations can apply the lifecycle lessons without generalizing the report’s numbers. A structured review should:

  • Maintain an inventory of computers, operating systems, applications, and relevant software components.
  • Identify which installed software is supported, outdated, or no longer needed.
  • Track vendor support milestones and assign owners for review and remediation.
  • Assess updates against application dependencies and the operational role of each device.
  • Include hardware age and condition in refresh planning rather than relying on age alone.

Conclusion: turn lifecycle information into action

Avast’s 2019 report documented widespread outdated software and an aging consumer-PC population. It does not provide direct measurements of industrial control or plant-floor systems, but it underscores a broadly relevant management challenge: devices and software can persist beyond their original support windows unless lifecycle information is maintained.

For industrial organizations, the practical response is disciplined visibility and planning. Know what is installed, understand support status, evaluate updates in context, and use hardware and software records to guide maintenance and refresh decisions. These steps help technical teams make informed choices without assuming that consumer PC trends map directly to operational technology.

Access Official Technical PDF

About The Author