How to Fix ‘ERR_SSL_BAD_RECORD_MAC_ALERT’ in Google Chrome

Browsing websites in Google Chrome only to encounter the error screen displaying ‘This site can’t provide a secure connection’ alongside ‘ERR_SSL_BAD_RECORD_MAC_ALERT’ interrupts secure web traffic. The error indicates that the Message Authentication Code (MAC) verifying the integrity of encrypted Transport Layer Security (TLS) records failed validation between your client browser and the destination web server. This failure prevents Chrome from decrypting network packets, halting page rendering to protect against data tampering. While the alert suggests cryptographic tampering, the underlying cause is almost always network packet corruption, incorrect Maximum Transmission Unit (MTU) sizing, hardware-accelerated network card checksum offloading faults, or aggressive third-party antivirus TLS interception.

Why Does Google Chrome Display ERR_SSL_BAD_RECORD_MAC_ALERT?

The TLS handshake establishes a symmetric encryption key along with an integrity hash algorithm (HMAC or AEAD ciphers such as AES-GCM or ChaCha20-Poly1305). If even a single bit in the TLS record header or payload is corrupted during transit, the client fails the MAC verification check and immediately terminates the TCP connection. Common triggers include:

  • MTU Packet Fragmentation: Network routers fragmenting packets exceeding the network’s Maximum Transmission Unit, corrupting packet headers during reassembly.
  • Corrupted TCP/IP Checksum Offloading: Network interface card (NIC) drivers miscalculating hardware checksums before transmitting packets to the OS TCP stack.
  • Intrusive HTTPS Inspection: Antivirus software or corporate firewalls terminating and re-encrypting TLS connections with outdated cipher suites.
  • Corrupted Browser SSL State: Transient cryptographic session tickets cached in the Windows cryptographic subsystem becoming invalid.

Step 1: Clear the Windows Cryptographic SSL State

Stale TLS session tickets and cached cryptographic certificates can cause verification discrepancies with modernized web servers.

  1. Press Win + R, type inetcpl.cpl, and press Enter to open Internet Properties.
  2. Navigate to the Content tab.
  3. Under the Certificates section, click Clear SSL State.
  4. When the prompt confirms ‘The SSL cache was successfully cleared’, click OK.
  5. Restart Google Chrome and test accessing the destination website.

Step 2: Adjust Network Adapter MTU (Maximum Transmission Unit) Size

Large packet frames that get fragmented by intermediate network routers often arrive with corrupted MAC signatures. Reducing MTU to 1400 bytes eliminates packet fragmentation.

  1. Right-click the Start menu and select Terminal (Admin) or PowerShell (Admin).
  2. List your active network interface names and current MTU values by executing:
    netsh interface ipv4 show subinterfaces
  3. Identify your connected network interface name (such as Wi-Fi or Ethernet).
  4. Lower the MTU size to 1400 bytes by running the following command (substitute your exact interface name in quotation marks):
    netsh interface ipv4 set subinterface "Wi-Fi" mtu=1400 store=persistent
  5. Repeat the command for IPv6 if enabled on your local connection:
    netsh interface ipv6 set subinterface "Wi-Fi" mtu=1400 store=persistent
  6. Reload the affected page in Google Chrome to confirm whether the TLS record completes validation.

Step 3: Disable Large Send Offload and Checksum Offload

Network adapter hardware offloading features can introduce bit errors into TLS packets before they reach the Windows network stack.

  1. Press Win + X and choose Device Manager.
  2. Expand the Network adapters branch.
  3. Right-click your active Wi-Fi or Ethernet adapter and select Properties.
  4. Switch to the Advanced tab.
  5. In the Property list, locate and configure the following parameters:
    • Large Send Offload v2 (IPv4): Set to Disabled.
    • Large Send Offload v2 (IPv6): Set to Disabled.
    • IPv4 Checksum Offload: Set to Rx & Tx Enabled (or toggle to Disabled if experiencing persistent packet corruption).
  6. Click OK to apply the changes, allowing the network adapter to reinitialize.

Step 4: Disable HTTPS Scanning in Antivirus Software

Third-party security suites (such as Avast, Bitdefender, or Kaspersky) inspect encrypted traffic by acting as a local proxy, frequently failing modern ChaCha20-Poly1305 MAC checks.

  1. Open your installed third-party security software.
  2. Navigate to Protection Settings or Web Shield.
  3. Locate options named Enable HTTPS Scanning, Encrypted Connection Scanning, or Scan SSL/TLS Traffic.
  4. Toggle the setting to Off.
  5. If you manage enterprise group policies, ensure that proxy inspection rules support TLS 1.3 cryptographic suites without downgrading sessions to depreciated ciphers.

Step 5: Flush DNS and Reset the Windows Socket Stack

Resetting corrupted network routing tables ensures clean socket initialization for upcoming TLS connections.

  1. Open Terminal (Admin) in Windows 11.
  2. Execute the following commands sequentially, pressing Enter after each:
    ipconfig /flushdns
    netsh winsock reset
    netsh int ip reset
  3. Restart your workstation to finalize the network stack reinitialization.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.