Category: Browsers

Google Chrome Keeps Crashing on Windows 11: 8 Ways to Stop It

Google Chrome keeps crashing on Windows 11? Fix it with 8 proven methods — update Chrome, disable hardware acceleration, clear cache, fix your profile. No reinstall required.

When Google Chrome keeps crashing on Windows 11 — suddenly closing, freezing mid-page, or showing an “Aw, Snap!” error — it can derail your whole day. The problem is especially frustrating because it often hits at the worst moment: during a video call, while filling out a form, or right in the middle of important research.

Chrome crashes on Windows 11 for a handful of common reasons: too many tabs eating up RAM, a conflicting extension, a corrupt browser profile, outdated graphics drivers, or a hardware acceleration glitch. The good news is that the fix is almost always free and takes less than 30 minutes.

This guide walks you through 8 proven fixes in order from quickest to most thorough.

Quick Answer

To fix Google Chrome crashing on Windows 11: open Chrome, go to Settings > Help > About Google Chrome and install any update, then turn off hardware acceleration under Settings > System. If crashes continue, clear your cache (Ctrl + Shift + Delete), disable all extensions, and run sfc /scannow in an elevated Command Prompt. One of these steps resolves most Chrome crashes.

Fix 1: Update Chrome to the Latest Version

Outdated Chrome builds can carry known crash bugs that a newer release already patched. This takes 60 seconds and should always be your first step.

  1. Click the three-dot menu (⋮) in Chrome’s top-right corner.
  2. Go to Help > About Google Chrome.
  3. Chrome checks for updates automatically. If one is available, click Relaunch.
  4. Once Chrome restarts, test whether crashes continue.

Pro tip: Chrome updates silently in the background, but you need to relaunch for them to apply. The About screen shows a colored dot next to the menu icon when a pending update is waiting for a relaunch.

Fix 2: Disable Hardware Acceleration

Hardware acceleration offloads browser rendering tasks to your GPU. When your GPU driver and Chrome version don’t agree, this setting becomes the most common hidden cause of random crashes.

  1. Open Chrome and go to Settings (three-dot menu).
  2. In the left sidebar, click System.
  3. Toggle off Use hardware acceleration when available.
  4. Click Relaunch.

Troubleshooting tip: If Chrome won’t stay open long enough to reach Settings, press Win + R, type chrome.exe --disable-gpu, and press Enter. This launches Chrome with GPU rendering disabled so you can access Settings normally.

Fix 3: Clear Chrome’s Cache and Cookies

A bloated or corrupted cache can cause Chrome to crash on specific sites — sometimes every time you load them.

  1. Press Ctrl + Shift + Delete inside Chrome.
  2. Set the time range to All time.
  3. Check Browsing history, Cookies and other site data, and Cached images and files.
  4. Click Clear data and wait for it to finish.
  5. Restart Chrome.

Real-world example: If Chrome crashes only on a specific site (like a banking portal or streaming service), the problem is almost always stale cached data for that site. Clearing the cache for “All time” resolves it in under a minute.

Fix 4: Disable or Remove Extensions

Every extension runs alongside every page you visit. One poorly coded or outdated extension can conflict with Chrome’s processes and trigger repeated crashes — and you’d never know which one without testing.

  1. Type chrome://extensions in the address bar and press Enter.
  2. Toggle off every extension.
  3. Restart Chrome and browse for a few minutes.
  4. If crashes stop, re-enable extensions one at a time to find the culprit.
  5. Remove the problem extension by clicking Remove.

Pro tip: Ad blockers, VPN extensions, and screen-recording tools are the most frequent crash offenders. Test those first before working through the rest.

Fix 5: Reset Chrome Settings

If Chrome’s internal settings have drifted — often from a bad extension or a site that changed a setting without asking — a reset restores everything to factory defaults. Your bookmarks and saved passwords are not affected.

  1. Go to Settings > Reset settings in Chrome’s left sidebar.
  2. Click Restore settings to their original defaults.
  3. Read the confirmation, then click Reset settings.

This clears your startup pages, default search engine, pinned tabs, and extension settings.

Fix 6: Create a New Chrome Profile

A corrupt user profile is a common cause of persistent crashes that no other fix solves. Creating a fresh profile is quick, and you can migrate your data later.

  1. Click your profile picture in Chrome’s top-right corner.
  2. Click Add (or the + icon) to create a new profile.
  3. Use Chrome under the new profile for a while. If it runs fine, your old profile was corrupted.

Troubleshooting tip: If Chrome won’t open at all, open File Explorer and navigate to C:\Users\YourName\AppData\Local\Google\Chrome\User Data. Rename the Default folder to Default.old, then relaunch Chrome. It creates a clean profile automatically.

Fix 7: Run an SFC Scan to Repair Windows System Files

Corrupt Windows system files can destabilize apps across the board, including Chrome. The built-in System File Checker (SFC) scans for and repairs them automatically. If your PC is also freezing in other apps, this fix is especially worth doing.

  1. Press Win + S, type cmd, right-click Command Prompt, and choose Run as administrator.
  2. Type sfc /scannow and press Enter.
  3. Wait for the scan to finish (10–15 minutes is normal).
  4. Restart your PC if files were repaired.

If SFC reports errors it can’t fix, run this command next:

DISM /Online /Cleanup-Image /RestoreHealth

Then run sfc /scannow again.

Fix 8: Update Your Graphics Driver

Chrome uses your GPU for page rendering. An outdated or corrupt graphics driver — especially combined with hardware acceleration — can cause repeated crashes during heavy browsing or video playback. If your CPU or GPU is already under strain, driver issues make things worse.

  1. Right-click the Start button and open Device Manager.
  2. Expand Display adapters.
  3. Right-click your GPU and choose Update driver.
  4. Select Search automatically for drivers and follow the prompts.
  5. Restart your PC after the update.

Pro tip: For the freshest driver, go directly to your GPU maker’s website — nvidia.com (NVIDIA), amd.com (AMD), or intel.com (Intel) — rather than relying on Windows to find the latest version.

Common Mistakes to Avoid

  • Reinstalling Chrome without fixing the profile first. A fresh install copies your profile data back over, so crashes caused by a corrupt profile return immediately. Use Fix 6 before you reinstall.
  • Skipping Windows Updates. Windows updates often include stability patches that affect how browsers interact with system components. Check Settings > Windows Update and install anything pending.
  • Ignoring too many open tabs. Chrome runs a separate process for each tab. On systems with 4–8 GB of RAM, 20+ tabs can trigger a crash. Enable Chrome’s Memory Saver mode to automatically suspend inactive tabs and reduce the load.
  • Testing with extensions still on. Diagnosing a crash with all extensions enabled makes it nearly impossible to isolate the cause. Always disable all extensions first — it takes 30 seconds and rules out a whole category of problems.
  • Not restarting after each fix. Driver updates, SFC scans, and Windows updates all require a full restart before they take effect. Skipping the restart makes the next fix look like it failed when it hasn’t been applied yet.
  • Confusing a crash with a freeze. If Chrome’s window stays open but stops responding (rather than closing entirely), the cause is usually high disk usage or RAM exhaustion rather than a corrupt install. Open Task Manager (Ctrl + Shift + Esc) and check Chrome’s resource usage before diving into profile or driver fixes.

Frequently Asked Questions

Why does Chrome keep crashing every time I open it?
The most likely causes are a corrupt Chrome profile or a conflicting extension. Start with Fix 4 (disable all extensions) and Fix 6 (create a new profile). These two steps solve the majority of “crashes on startup” problems.

Does reinstalling Chrome fix crashes?
Sometimes, but not if the crash is caused by a corrupt user profile — reinstalling leaves your profile data intact. Create a new profile first (Fix 6). If that fixes it, you can migrate your bookmarks and passwords to the new profile and delete the old one.

Can too many open tabs cause Chrome to crash?
Yes. Each tab runs as its own process and consumes RAM. When Chrome runs out of available memory, it can crash or forcibly close individual tabs. Enable Memory Saver mode in Chrome Settings to automatically free up RAM from tabs you haven’t used in a while.

Is Chrome crashing a sign of malware?
It can be. Some malware injects code into browsers and causes instability. After trying the fixes above, run a full scan with Windows Defender: open Windows Security > Virus & threat protection > Quick scan. For a deeper cleanup, follow our guide to removing malware from Windows 11.

Why does Chrome crash only when I watch videos?
Video playback is GPU-intensive. Disable hardware acceleration (Fix 2) and update your graphics driver (Fix 8) — these two fixes resolve most video-related Chrome crashes. If it’s only one platform (e.g., YouTube), also try clearing that site’s cookies and cache.

Why does Chrome crash on one specific website but not others?
Site-specific crashes usually point to corrupted cached data for that site. Clear your cache with the time range set to “All time” (Fix 3) and try again. If the site uses heavy JavaScript or video, disabling hardware acceleration (Fix 2) can also help.

How do I know which Chrome extension is causing crashes?
Disable all extensions at once (chrome://extensions), then re-enable them one at a time, restarting Chrome between each. The crash will return when you re-enable the problem extension. Ad blockers, VPN extensions, and screen-recorders are the most common culprits.

Conclusion

Chrome crashing on Windows 11 is almost always fixable without reinstalling Windows or replacing hardware. Work through the 8 fixes in order — update Chrome, disable hardware acceleration, clear your cache, and test without extensions — and you’ll solve the problem in under 30 minutes in most cases.

If all 8 fixes still haven’t solved it, test another browser (Edge or Firefox). If other browsers crash too, the issue is in Windows itself rather than Chrome — revisit the SFC/DISM commands in Fix 7 and make sure Windows is fully updated.

Found the fix that worked for you? Leave a comment below — it helps other readers skip straight to the right step.

Stop Google Chrome From Eating Your RAM: 7 Fixes That Actually Help

Chrome hogging your RAM? Fix it fast with 7 proven methods — Memory Saver mode, extension cleanup, cache clearing, and more. No paid software needed.

If your computer slows to a crawl the moment you open Chrome, you’re not imagining things. Chrome is notorious for consuming huge amounts of RAM — sometimes hundreds of megabytes per tab. When Chrome is using too much memory, everything suffers: other apps freeze, your PC’s fans spin up, and simple tasks start to drag.

The good news? You don’t need a new computer. A few quick settings changes can cut Chrome’s memory use significantly — using tools built right into the browser.

Quick Answer

Chrome uses too much memory because every tab, extension, and plugin runs as its own separate process for security and stability. To fix it: enable Chrome’s built-in Memory Saver mode, disable unused extensions, close idle tabs, and clear your browsing cache. Most users see immediate relief with just those four steps — no reinstall needed.

Why Does Chrome Use So Much RAM?

Chrome runs each tab as an isolated process. This design means a single crashed tab won’t bring down your whole browser — but it also means every tab reserves its own chunk of RAM, even when you’re not actively looking at it.

Extensions add to the problem: each one runs a background process whether you’re using it or not. Streaming video, complex web apps, and multiple sign-in sessions pile on top, and Chrome can easily consume 2–4 GB of RAM on a busy day.

If Chrome’s memory use is also causing your disk to spike, see How to Fix 100% Disk Usage on Windows 11 — the two problems often go hand in hand. And if your whole PC feels slow, our guide on How to Speed Up a Slow Windows 11 PC covers the full picture.

Fix 1: Enable Memory Saver Mode

Chrome’s Memory Saver mode automatically “sleeps” tabs you haven’t visited in a while, freeing RAM immediately. It’s the fastest, most impactful fix on this list.

  1. Click the three-dot menu (⋮) in Chrome’s top-right corner.
  2. Select Settings.
  3. Click Performance in the left sidebar.
  4. Toggle on Memory Saver.

A small leaf icon appears on sleeping tabs. Click any one to wake it up instantly — it reloads in about a second.

Pro tip: Add sites you always need live — like Gmail or your work dashboard — to the “Always keep these sites active” list in the same Performance panel so they’re never put to sleep.

Fix 2: Disable Unused Extensions

Extensions are one of the biggest hidden RAM drains in Chrome. Every installed extension runs in the background at all times, whether you’re actively using it or not.

  1. Type chrome://extensions in the address bar and press Enter.
  2. Toggle off any extension you don’t use regularly.
  3. Click Remove on extensions you no longer need at all.

Troubleshooting tip: Not sure which extension is the culprit? Disable them all, then re-enable one at a time while watching Chrome’s Task Manager (Fix 3 below) to track exactly where the memory spike comes from.

Fix 3: Use Chrome’s Built-In Task Manager

Chrome has its own Task Manager that shows exactly which tabs and extensions are consuming the most memory — the fastest way to pinpoint the real problem.

  1. Press Shift + Esc on Windows, or go to the three-dot menu → More tools → Task Manager.
  2. Click the Memory footprint column header to sort by RAM use.
  3. Select the heaviest process and click End process to kill it without closing your entire browser.

Fix 4: Clear Your Cache and Browsing Data

A bloated cache contributes to sluggish Chrome performance over time. Clearing it is safe — you won’t lose bookmarks or saved passwords, though you’ll need to log back into some sites.

  1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac).
  2. Set Time range to All time.
  3. Check Cached images and files and Cookies and other site data.
  4. Click Delete data.

Make it a habit to clear your cache every month or two — it only takes 30 seconds.

Fix 5: Limit the Number of Open Tabs

Every open tab — even a quiet one — holds a process in memory. The simplest fix is also one of the most effective: open fewer tabs at once.

  • Use Chrome’s built-in Reading List (click the bookmark icon → “Add to Reading List”) to save pages for later instead of keeping them open.
  • Right-click any tab and choose Add tab to new group to organize and collapse sets of related tabs.
  • Try the free OneTab extension, which collapses all your open tabs into a single list and can recover up to 95% of the RAM those tabs were using.

Fix 6: Keep Chrome Updated

Outdated Chrome versions can contain memory leaks — bugs that cause RAM use to climb without releasing it. Regular updates patch these automatically.

  1. Go to the three-dot menu → Help → About Google Chrome.
  2. Chrome checks for updates and installs them automatically on this screen.
  3. Click Relaunch when prompted to apply the update.

Fix 7: Use Separate Chrome Profiles

Running personal browsing, work tabs, and a stack of extensions all under one Chrome profile creates one very heavy combined process. Splitting into two lean profiles often reduces total RAM use.

  1. Click your profile picture in Chrome’s top-right corner.
  2. Select Add and create a new work profile.
  3. Install only work-related extensions in that profile and keep your personal one minimal.

Best Practices to Keep Chrome Running Light

  • Fully restart Chrome — close all windows, not just individual tabs — at least once a day to release accumulated memory.
  • Pause YouTube or any video tab before switching away; active video is one of Chrome’s heaviest ongoing memory consumers.
  • On a PC with 8 GB of RAM or less, Memory Saver mode (Fix 1) is practically mandatory.
  • Audit your extensions monthly and remove anything you haven’t actively used in the past 30 days.

Common Mistakes to Avoid

  1. Leaving dozens of tabs open “just in case” — Each tab costs RAM continuously. Save pages as bookmarks or to your Reading List instead of keeping them open.
  2. Installing too many extensions — Quality over quantity. Every installed extension runs in memory, whether you’re using it or not.
  3. Never clearing your cache — Cache bloat accumulates silently and slows Chrome over time. A quick monthly clear makes a real difference.
  4. Skipping Chrome updates — Updates fix memory leaks. An outdated browser stays buggy. Always run the latest version.
  5. Running Chrome alongside other memory-hungry apps — Video editors, virtual machines, and games all compete for the same RAM pool. Close what you’re not actively using.
  6. Overlooking malware as a cause — A rogue extension or browser hijacker can cause extreme RAM and CPU spikes. If Chrome’s usage is sky-high even with no tabs open, run a full malware scan before anything else.

Frequently Asked Questions

Why does Chrome use more memory than other browsers?
Chrome’s multi-process design — one isolated process per tab and per extension — makes it more stable and secure but more memory-hungry than single-process browsers. It’s a deliberate engineering trade-off.

Does Chrome Memory Saver actually work?
Yes. Memory Saver significantly reduces Chrome’s RAM use by putting inactive tabs to sleep. It’s one of the most impactful improvements Google has built into Chrome in recent years.

Will disabling extensions break my browsing?
Only for the features those extensions provide. Disable an ad blocker and ads return; disable a password manager and autofill stops. Only turn off extensions you don’t rely on daily.

Can malware cause Chrome to use too much memory?
Yes. Malicious extensions and browser hijackers can spike Chrome’s RAM and CPU use dramatically. Unusually high usage with almost no tabs open is a red flag — investigate immediately.

How much RAM should Chrome normally use?
Around 200–400 MB per active tab plus 50–150 MB per extension is a typical benchmark. Significantly more than that per tab usually points to a rogue extension, stale cache, or malware.

Should I switch to a different browser to save memory?
If your PC has 4 GB of RAM or less, Microsoft Edge or Firefox are worth trying — both use noticeably less memory on low-spec hardware. On 8 GB or more, the fixes in this guide are usually sufficient.

Will adding more RAM fix Chrome’s memory problem?
More RAM won’t make Chrome use less — but it gives your system enough headroom that Chrome’s appetite stops causing slowdowns. Upgrading from 4 GB to 8 GB makes a dramatic real-world difference.

Conclusion

Chrome’s memory appetite is by design — but a sluggish PC doesn’t have to be the price of using the world’s most popular browser. Enable Memory Saver, trim your extensions, close idle tabs, and keep Chrome updated. Those four steps fix the problem for most people.

Start with Fix 1 right now — turning on Memory Saver takes 30 seconds and delivers results immediately. Still seeing heavy usage after working through this guide? Drop a comment below and we’ll help you dig deeper.

How to Fix the “Your Connection Is Not Private” Error in Chrome

Seeing the “Your connection is not private” error in Chrome? Don’t panic — these 8 quick fixes clear the SSL error in minutes. Most users fix it in the first 3 steps.

You click a link and Chrome stops you cold: a big red warning reading “Your connection is not private.” Below it sits an error code like NET::ERR_CERT_DATE_INVALID. Your first thought might be: am I being hacked?

Almost certainly not. This error means Chrome couldn’t verify the security certificate for the website you’re trying to visit — and in the vast majority of cases, the fix lives on your own device and takes under two minutes. This guide walks you through eight proven fixes, starting with the most common cause.

Quick Answer

The “Your connection is not private” error in Chrome means Chrome can’t verify the site’s SSL certificate. The fastest fix: check that your device’s date and time are correct — a wrong clock is the most common trigger. If that doesn’t help, clear Chrome’s cache, update Chrome, or open an incognito window to pinpoint the cause.

What Does “Your Connection Is Not Private” Actually Mean?

SSL/TLS (the technology behind the padlock icon in your address bar) encrypts data between your browser and a website. Every secure site carries an SSL certificate — a digital ID proving the site is who it claims to be. Chrome checks this certificate on every connection. When something looks wrong, it blocks the page rather than quietly letting you through.

The error code beneath the main message tells you exactly what failed:

Error Code What It Means
NET::ERR_CERT_DATE_INVALID Certificate expired, or your device clock is wrong
NET::ERR_CERT_AUTHORITY_INVALID Certificate not trusted by Chrome
NET::ERR_CERT_COMMON_NAME_INVALID Certificate doesn’t match the website’s domain

8 Fixes for “Your Connection Is Not Private” in Chrome

Fix 1: Check Your Date and Time (Start Here)

A wrong device clock is the number one cause of this error. If your PC thinks it’s the wrong year, Chrome can’t check whether a certificate is still valid and blocks the connection immediately.

  1. Right-click the clock in your Windows taskbar and choose Adjust date and time.
  2. Turn on Set time automatically and Set time zone automatically.
  3. Click Sync now if that option appears.
  4. Reload the page in Chrome.

Pro tip: If your clock keeps resetting after syncing, the small CMOS battery on your motherboard may be dead. A local repair shop can replace it cheaply — usually just a few dollars.

Troubleshooting tip: If your date and time are already correct, skip straight to Fix 2 — the cause is something else.

Fix 2: Clear Chrome’s Cache and Cookies

Stale cached data can make Chrome check an outdated certificate snapshot instead of the live one. Clearing it forces Chrome to start fresh.

  1. Press Ctrl + Shift + Delete (Mac: Cmd + Shift + Delete) inside Chrome.
  2. Set the time range to All time.
  3. Check Cached images and files and Cookies and other site data.
  4. Click Clear data, then reload the page.

Fix 3: Update Google Chrome

An outdated Chrome build may not recognise newer certificate types or security protocols. Updating takes under a minute and often solves the problem immediately.

  1. Click the three-dot menu (⋮) in Chrome’s top-right corner.
  2. Go to Help > About Google Chrome.
  3. Chrome checks for and installs any available update automatically.
  4. Click Relaunch, then try the page again.

Fix 4: Try Incognito Mode

Incognito mode runs Chrome without any extensions. If the page loads fine in incognito but not in your normal window, a browser extension — often an antivirus add-on or ad blocker — is the culprit.

  1. Press Ctrl + Shift + N (Mac: Cmd + Shift + N) to open incognito.
  2. Visit the same website.
  3. If it loads without the error, go to chrome://extensions in your normal window and disable extensions one by one to find the problematic one.

Fix 5: Disable Your Antivirus HTTPS Scanning

Many antivirus programs scan encrypted HTTPS traffic by acting as a middleman between Chrome and the website. This well-meaning feature can interfere with certificate verification.

  1. Open your antivirus software’s settings.
  2. Look for an option called HTTPS scanning, SSL inspection, or Web Shield.
  3. Turn it off temporarily, then reload the page.
  4. If the error clears, add a trusted-site exception in your antivirus settings rather than leaving HTTPS scanning off permanently.

Troubleshooting tip: The feature name varies by antivirus brand. If you can’t find it, search your vendor’s support site for “HTTPS scanning” plus your product name.

Fix 6: Clear the SSL State in Windows

Windows keeps its own SSL certificate cache separate from Chrome. Clearing it forces a completely fresh certificate check the next time you visit the site.

  1. Open Control Panel (search for it in the Start menu).
  2. Click Internet Options.
  3. Select the Content tab.
  4. Click Clear SSL State, then click OK.
  5. Reload Chrome and try the page.

Fix 7: Disconnect Your VPN or Proxy

VPNs and proxies route your traffic through a different server, which can interfere with SSL certificate checks — especially on public Wi-Fi. Turn off your VPN, reload the page, and see if the error disappears. If it does, try updating your VPN app or contact your VPN provider’s support team. Public Wi-Fi can also cause connection problems more broadly — see our guide on fixing slow internet on Windows 11 for related troubleshooting.

Fix 8: Update Windows

Windows delivers root certificate updates through Windows Update. If your system hasn’t updated in months, it may no longer trust certificates from newer certificate authorities — causing this error on perfectly safe websites. Go to Settings > Windows Update, click Check for updates, install everything available, and restart your PC. For help if Windows Update itself isn’t working, see our guide: How to Fix Windows Update Not Working on Windows 11.

When the Error Is the Website’s Fault

Sometimes no fix on your end will work — because the problem is on the website itself. An expired or misconfigured SSL certificate on the server triggers the exact same warning, and it will show up on multiple devices and browsers.

If you can confirm the site loads fine on a completely different device and network, the site owner needs to renew their certificate. In the meantime, do not click “Proceed anyway” on any site where you enter a password, payment details, or personal information.

Common Mistakes to Avoid

  • Clicking “Proceed anyway” on sensitive sites. If this error appears on your bank, email, or any login page, stop — do not bypass the warning. The risk of real credential theft is highest here.
  • Assuming it’s always a hacker. The vast majority of cases are a clock problem, stale cache, or antivirus conflict — not an active attack. Diagnose first, panic later.
  • Ignoring it on a site you own. If this appears on your own website, your SSL certificate has likely expired. Log into your hosting control panel and renew it immediately — visitors are being turned away.
  • Leaving HTTPS scanning permanently disabled. It’s a real security layer. Switch it back on once you’ve confirmed it was the cause, and use a per-site exception instead.
  • Skipping the extension check. Browser extensions — especially security and privacy add-ons — are a surprisingly frequent trigger. The two-second incognito test rules them in or out instantly.
  • Falling behind on Windows Updates. Root certificate updates ship inside Windows Update. A long-unpatched system can start rejecting perfectly valid newer certificates without warning.

Frequently Asked Questions

Is “Your Connection Is Not Private” the same as being hacked?

Almost never. The error most often comes from a wrong system clock, stale cache, or an extension conflict. Genuine attacks that trigger this error are rare and mostly target users on unsecured public Wi-Fi networks.

Can I click “Proceed anyway” to get to the site?

Only on sites you fully trust and where you’re not entering any personal data. For anything involving login credentials, payments, or sensitive information, do not bypass the warning.

Why does this error only appear in Chrome and not Firefox or Edge?

Each browser maintains its own certificate cache and runs different extensions. If another browser loads the page without error, start by clearing Chrome’s cache and testing in incognito mode to rule out an extension.

Why does this happen on my laptop but not my phone?

Your laptop’s clock, antivirus settings, or installed Chrome extensions are the most likely culprits. Work through Fix 1 and Fix 5 specifically on the affected device.

What if none of the eight fixes work?

If the error persists across multiple sites after trying everything, scan your PC for malware — some malicious software intercepts SSL traffic and can cause this error. Run a free scan with Windows Security (built into Windows) or Malwarebytes. If you suspect an infection, our guide to removing malware from Windows 11 walks you through a full cleanup.

Conclusion

The “Your connection is not private” error looks alarming but is almost always fixable in minutes. Start with your date and time, clear Chrome’s cache, and test in incognito — those three steps alone clear the vast majority of cases. Work down the list from there and you’ll be back online fast.

Still having trouble with Chrome? Our guide on Google Chrome using too much memory covers more browser fixes worth bookmarking.