The Initialization Blockade Vector
If Google Chrome is configured to launch immediately upon system boot, it forcefully intercepts critical CPU cycles and RAM allocation before the underlying operating system has finished stabilizing. This aggressive startup behavior severely delays your ability to interact with the desktop. You must instruct the operating system kernel to sever Chrome’s autostart privileges, preventing the browser engine from executing until you manually summon it.
How to Stop Chrome from Opening on Startup
Because Chrome utilizes different startup hooks depending on the host operating system, you must execute the termination command within the host’s native initialization matrix.
1. The Windows 11 Execution (Task Manager):
* The Windows operating system manages all boot-level software via the Task Manager.
* Press Ctrl + Shift + Esc to instantly summon the Task Manager.
* Look at the left-hand navigation sidebar and click on the Startup apps icon (it resembles a speedometer).
* You are now viewing the master list of all software authorized to boot with the system.
* Scroll down the list and locate Google Chrome.
* Right-click on Google Chrome and select Disable from the context menu.
* The “Status” column will instantly change from Enabled to Disabled. The execution is complete.
2. The macOS Execution (System Settings):
* Apple isolates boot-level applications within the specific User Profile matrix.
* Click the Apple Logo in the top-left corner and select System Settings.
* Navigate to General in the left sidebar, then click on Login Items in the main pane.
* Look at the top section titled “Open at Login.”
* If Google Chrome is in this list, click to highlight it.
* Click the small Minus (-) button located directly below the list to violently eradicate it from the boot sequence.
* Secondary macOS Check: Ensure Chrome isn’t accidentally pinned in the Dock. Right-click the Chrome icon in the Dock, hover over Options, and ensure “Open at Login” is unchecked.