Control Auto-Updates: Java, Browsers & Adobe

TL;DR

Auto-updates are vital for security but can cause disruption. This guide shows how to manage them effectively for Java, browsers (Chrome, Firefox, Edge), Flash Player and Adobe Reader/Acrobat, balancing security with stability.

Managing Auto-Updates: A Step-by-Step Guide

1. Understand the Risks & Benefits

• Benefits: Security patches protect against vulnerabilities. New features improve usability.
• Risks: Updates can break compatibility with existing software or websites. Unexpected changes can disrupt workflows.

Java Auto-Updates (End of Life – Focus on Removal)

• Java is largely end-of-life and a security risk. Uninstall it completely if possible.
• If you *must* keep Java (rare cases), use the latest version and configure updates carefully through the Java Control Panel. However, this is strongly discouraged.

Browser Auto-Updates

• Chrome: Chrome generally auto-updates in the background. You can check for updates manually by going to chrome://settings/help. There’s limited control over this process.
• Firefox: Configure auto-update settings via about:preferences#general under ‘Firefox Updates’. Options include:
  • Automatically install updates (recommended).
  • Check for updates but let you choose to install them.
  • Never check for updates (not recommended).
• Microsoft Edge: Edge auto-updates like Chrome, managed through Windows Update. You can control update frequency via Settings > About Microsoft Edge and then checking for updates.
  • To delay updates (advanced users): Use Group Policy or Registry settings (search online for ‘delay edge updates’).

Adobe Flash Player Auto-Updates (End of Life – Focus on Removal)

• Flash Player is end-of-life and a major security risk. Uninstall it completely. Adobe no longer supports or provides updates for Flash.
• If you find remnants, use the official Adobe uninstaller tool: https://helpx.adobe.com/flash-player/kb/uninstall-flash-player.html

Adobe Reader/Acrobat Auto-Updates

• Open Adobe Acrobat or Reader.
  Go to Edit > Preferences (or Acrobat > Preferences on macOS).
  Select ‘Updater’ from the left panel.
• Options:
  • Automatically install updates (recommended for most users).
  • Download updates but let you choose to install them.
  • Do not download or install updates (not recommended – significant security risk).
• Update Frequency: Set how often Acrobat checks for updates.

Centralised Management (For Businesses)

• Consider using a centralised patch management system (e.g., SCCM, Intune, PDQ Deploy). These tools allow you to control and schedule updates across your entire network.
• Group Policy (Windows environments): Use Group Policy Objects (GPOs) to configure update settings for browsers and Adobe products.

Testing Before Deployment

• Before deploying any major updates, test them on a small group of representative machines to identify potential compatibility issues.
• Create a rollback plan in case an update causes problems.