Google Chrome regularly checks Google's update servers to download security patches, bug fixes, and new features. During installation or manual update, users may encounter the following error:

Update check error: A connection with the server could not be established.

Advertisement

In many cases, users immediately suspect an internet issue, firewall problem, antivirus restriction, or proxy configuration. However, another often-overlooked cause is NetLimiter, which may have blocked Google Update.exe, preventing Chrome from communicating with Google's update servers.

In this case, Chrome installation and updates failed because Google Update.exe had been blocked inside NetLimiter. Once the block rule was removed, Chrome immediately resumed downloading updates and completed the installation successfully.

Symptoms

You may notice one or more of the following:

• Chrome installation does not complete.
• Chrome cannot update automatically.
• Manual update fails.

• Error:

  Update check error: A connection with the server could not be established.

• Chrome opens but remains on an outdated version.
• Enterprise deployment reports update failures.

Root Cause

Google Chrome uses a separate update component called:

GoogleUpdate.exe

or

Updater.exe

located under folders such as:

C:\Program Files (x86)\Google\Update\

or

C:\Program Files\Google\Update\

or

C:\Program Files (x86)\Google\GoogleUpdater\

If this executable is blocked by:

• NetLimiter
• Firewall
• Third-party security software
• Endpoint protection
• Network filtering software

Chrome cannot establish a secure connection with Google's update servers.

How NetLimiter Causes This Problem

NetLimiter allows administrators to:

• Block applications
• Limit bandwidth
• Denforce upload/download rules
• Restrict internet access per executable

If someone accidentally creates a rule like:

GoogleUpdate.exe → Block

or

Chrome Update Service → Deny Internet

Chrome displays the update connection error even though the computer has full internet connectivity.

How to Verify the Problem

Step 1

Open NetLimiter.

Step 2

Search for:

Google

or

Update

or

Chrome

Step 3

Look for blocked entries such as:

• GoogleUpdate.exe
• updater.exe
• Google Chrome Installer

Step 4

Check whether:

• Incoming traffic is blocked
• Outgoing traffic is blocked
• Connection is denied

The Fix

In this case, the solution was simple:

Remove the Block Rule

Delete or disable the blocking rule for:

GoogleUpdate.exe

or

Updater.exe

After removing the rule:

• Chrome installer immediately connected to Google.
• Update download started.
• Installation completed successfully.
• Chrome updates resumed normally.

Additional Things to Check

If the problem persists, also verify:

Windows Firewall

Allow:

• Google Chrome
• Google Update

through Windows Defender Firewall.

Proxy Settings

Run:

netsh winhttp show proxy

Reset if required:

netsh winhttp reset proxy

Internet Connectivity

Verify access to:

https://update.googleapis.com

and

https://dl.google.com

DNS Resolution

Test:

nslookup dl.google.com

Antivirus

Some antivirus solutions block updater components.

Temporarily disable protection for testing.

Services

Open:

services.msc

Ensure the Google Update services are enabled if present.

Common Network Software That May Cause Similar Issues

• NetLimiter
• GlassWire
• SimpleWall
• TinyWall
• Windows Firewall
• Sophos Endpoint
• CrowdStrike
• SentinelOne
• ESET
• Kaspersky
• Bitdefender
• Cisco Umbrella
• FortiClient

Best Practices

✔ Avoid blocking software update services.

✔ Allow Google Update to communicate over HTTPS.

✔ Review NetLimiter rules periodically.

✔ Keep Chrome updated for the latest security patches.

✔ Monitor endpoint security policies after deploying new firewall rules.

Troubleshooting Checklist

Conclusion

The error "Update check error: A connection with the server could not be established" is not always caused by internet connectivity issues. Application-level network control software such as NetLimiter can silently prevent Chrome's update engine from reaching Google's servers.

In this case, the issue was traced to a blocked Google Update.exe rule in NetLimiter. Removing the restriction immediately restored connectivity, allowing Chrome to install and update successfully. Administrators managing Windows environments should always inspect application-specific firewall or bandwidth management rules before troubleshooting more complex networking issues.

#GoogleChrome #ChromeUpdate #NetLimiter #Windows11 #Windows10 #ChromeError #GoogleUpdate #UpdateError #ChromeInstaller #BrowserUpdate #WindowsSupport #ITSupport #SysAdmin #TechSupport #Networking #Firewall #Proxy #DNS #Google #SoftwareUpdate #Troubleshooting #WindowsAdmin #ChromeFix #EnterpriseIT #CyberSecurity #EndpointSecurity #BandwidthLimiter #ApplicationControl #SystemAdministrator #ComputerRepair #WindowsTroubleshooting #ChromeInstallation #GoogleUpdater #InternetConnectivity #FirewallRules #SoftwareDeployment #DesktopSupport #ITInfrastructure #BrowserSecurity #WindowsServer #GoogleServices #NetworkSecurity #TechGuide #HowToFix #PCRepair #SoftwareMaintenance #WindowsTips #TechArticle #ChromeSupport #BisonInfosolutions