Google Chrome commonly opens when you sign in to Windows 10 because its settings enable running at startup and the app is installed for all users, while Windows startup behavior can be set per user or system-wide through Task Manager, Settings, or Group Policy. This article explains how Chrome manages startup, why it launches automatically, what options you have to allow or block it, and how to change the behavior for a single account or across managed devices using built-in and administrative controls. You will find actionable steps, differences between user- and system-level effects, and practical guidance for maintaining the experience you want.
How Chrome starts automatically on Windows 10
On Windows 10, programs can start at different layers: per user at sign-in, per device for all new users, or via system services. Chrome typically opts into per-user startup through two common mechanisms: the Startup folder and Run keys in the registry. When you install Chrome and choose options to run in the background or to restore previous sessions, Chrome writes entries to one of these locations so that it launches when you sign in. These entries sit under your user profile rather than under a machine-wide key, so each user account can have its own startup behavior unless an administrator changes that scope.
Startup folder versus registry Run keys
The Startup folder is the simplest and most user-friendly way for an application to run at sign-in. On Windows 10, it is located at shell:startup for the current user and at the all-users Startup folder. The registry Run keys, such as HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run, achieve the same effect but can also be set by an administrator under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run to launch a program for every user on the device.
Chrome’s own settings for session and startup control
Within Chrome, you can choose to open the browser at Windows startup, continue where you left off, or open a specific page or set of pages. When you check “Open Chrome” on startup in Chrome settings, the browser ensures it is launched when you sign in, typically by adding or updating its entry in the Startup folder or a Run key. If you disable that setting or uninstall Chrome, those entries are usually removed, and Chrome will no longer start automatically unless other policies or scripts intervene.
Check and change Chrome startup behavior in Windows 10
Because many programs add themselves to startup, it helps to review the list and decide which apps should start and which should not. Windows 10 provides clear tools to audit and manage startup entries without installing third-party utilities.
Task Manager: quick audit and enable/disable
Task Manager consolidates startup information into one view, showing the app name, publisher, whether it is enabled, and an estimated impact on boot time. From there you can disable items you do not want at sign-in and enable them later if needed. This method affects only your user account and does not change system-wide settings.
Settings and advanced startup options
In Settings, you can manage which apps are allowed to run at startup for your account. For deeper control, Advanced Startup and Startup Apps pages let you review background activity and toggle apps individually. These settings are user-centric, meaning changes apply to the account you use to make them unless you adjust policies for all users.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Typical startup location for Chrome (user) | shell:startup folder or HKCU\…\Run | Observed behavior, documentation |
| Typical startup location for Chrome (all users) | All Users Startup folder or HKLM\…\Run | Observed behavior, documentation |
| Scope of change via Task Manager | User account only | Microsoft documentation |
| Scope of change via HKLM Run keys | All users on the device | Microsoft documentation |
| Recommended approach for managed organizations | Group Policy or Microsoft Intune policies | Enterprise documentation |
Using Group Policy to manage Chrome startup for all users
In domain or enterprise environments, administrators can control whether Chrome starts at logon for all users by configuring computer- or user-based policies. Group Policy can remove the ability for users to change the startup setting, enforce Chrome to start, or prevent it from starting, depending on the intended behavior. These policies write to the registry in a way that can override individual user choices, making them reliable for consistency across managed devices.
Chrome ADMX templates and recommended policy paths
Google distributes Chrome ADMX templates that add policy settings to Group Policy Management Editor and local policy editor on Windows. Relevant policies include startup configuration options that control whether Chrome is allowed to open at startup and whether users can override that behavior. When these templates are applied, administrators can set the behavior once and apply it to many devices without manually editing registries.
PowerShell, Registry, and Task Scheduler approaches
For targeted or scripted adjustments, you can use PowerShell to read, add, or remove startup entries, directly manage Registry keys, or create scheduled tasks that run at user sign-in. Because direct registry edits and scripts affect system configuration, they should be tested in a controlled environment and documented before deployment. Prefer built-in tools and policy settings when possible to reduce long-term maintenance overhead.
Common causes and what to do if Chrome still opens at startup
If you disabled Chrome in Task Manager but it still opens at sign-in, another mechanism may be responsible: a per-machine policy, a scheduled task, a third-party launcher, or another profile or browser setting. It is also possible that multiple user accounts on the PC have different startup settings, or that a previous session restore setting causes Chrome to reopen windows even when startup launch is turned off. Check each user account, review policies if on a domain, and audit scheduled tasks if the behavior persists.
Steps to isolate the cause
- Confirm the entry in Task Manager for your account and disable it.
- Check the all-users Startup folder and registry Run keys for machine-wide entries.
- Review local Group Policy or domain GPOs that might enforce startup behavior.
- Inspect other user profiles on the device for per-user settings.
- Check for scheduled tasks or third-party startup managers that might relaunch Chrome.
Differences between user accounts and device-wide behavior
Startup entries under HKCU or the user Startup folder apply only to the account that owns them, while entries under HKLM or the all-users Startup folder apply to every account that signs in to the device. Policies applied by administrators can affect both levels. Understanding whether a change is per user or per device helps you choose the right tool and anticipate how new user accounts will behave.
Frequently asked questions
- Does uninstalling Chrome remove its startup entries? Usually yes. Uninstallation typically removes per-user and per-device entries that Chrome created, but manually added entries or policies will remain and should be cleaned separately.
- Can I prevent other users on my PC from starting Chrome at startup? Yes. Use Task Manager or Settings for your account, or use HKLM startup keys or Group Policy to control behavior for all users.
- Will Chrome open at startup if I sign in to Windows with a local account versus a Microsoft account? The account type does not change how startup works; it depends on Chrome’s own settings and where its startup entries are located.
- Is it safe to disable Chrome from startup in Task Manager? Yes. Disabling prevents Chrome from launching automatically at sign-in, but you can re-enable it anytime.
Summary and best practices
Chrome opens on startup in Windows 10 because its startup setting is enabled and an entry exists in a startup location such as the Startup folder or a Run key under your profile or system-wide. You can manage this per user with Task Manager, Settings, or by editing registry keys, and you can enforce consistent behavior across devices with Group Policy or Intune policies. For reliable control, check both per-user and per-device locations, test changes in a standard user context before applying widely, and document administrative policies so teams understand how startup behavior is managed.