Google Chrome “Open a Specific Page or Set of Pages” Not Working – Complete Fix for Windows, Policies, Registry, Profiles & Startup Settings
Google Chrome includes an On startup setting that determines what Chrome displays when the browser is launched. Normally, you can configure Chrome to: Open t...
Google Chrome includes an On startup setting that determines what Chrome displays when the browser is launched.
Normally, you can configure Chrome to:
- Open the New Tab page
- Continue where you left off
- Open a specific page or set of pages
For example, a business user may want Chrome to automatically open:
- Gmail
- Google Workspace
- an ERP or CRM portal
- an attendance system
- a company intranet
- a support portal
- a frequently used web application
The normal configuration is straightforward:
Chrome → Settings → On startup → Open a specific page or set of pages
Then select Add a new page and enter the required URL.
However, sometimes Chrome refuses to retain this setting. It may revert to Continue where you left off, open a New Tab page, restore old tabs, open an unexpected website, or show that the setting is controlled by an administrator.
This problem can have several causes, and Windows file permissions are not normally the first place to look.
Common causes include:
- Chrome Enterprise policies
- Windows Group Policy
- Registry policies
- a managed work or school browser
- browser extensions
- corrupted Chrome profile data
- synchronization of unwanted settings
- browser hijackers or unwanted software
- an incorrect Chrome shortcut
- third-party security or management software
- multiple Chrome profiles
- damaged browser configuration
This guide explains how to diagnose each possibility systematically.
1. Understand Startup Page vs Homepage
Before troubleshooting, it is important to understand that Chrome's startup page and homepage are different.
Startup page
The startup page appears when Chrome is launched.
Configure it from:
Chrome → Settings → On startup
Homepage
The homepage is the page opened when you click Chrome's Home button.
Configure it from:
Chrome → Settings → Appearance → Show Home button
Changing the homepage does not necessarily change Chrome's startup behavior.
This distinction causes considerable confusion during troubleshooting.
2. Configure the Startup Page Normally
First, confirm that Chrome is configured correctly.
Open Chrome and enter:
chrome://settings/onStartup
Select:
Open a specific page or set of pages
Then click:
Add a new page
Enter the complete URL, preferably including HTTPS:
You can add multiple URLs if required.
Close all Chrome windows.
Wait a few seconds and launch Chrome again.
If the configured pages open correctly, no further troubleshooting is required.
3. Completely Exit Chrome Before Testing
Closing the visible Chrome window does not always mean that every Chrome process has stopped.
Press:
Ctrl + Shift + Esc
to open Task Manager.
Look for processes such as:
Close all Chrome windows first. If Chrome processes remain unexpectedly, investigate whether an extension or background component is keeping Chrome active.
Then launch Chrome again and test the startup configuration.
4. Check Whether Chrome Is “Managed by Your Organization”
This is one of the most important checks.
Enter:
chrome://management
If Chrome is managed, the page may indicate that the browser is managed by your organization.
Then open:
chrome://policy
This page displays policies currently detected by Chrome.
Look particularly for:
RestoreOnStartup
and:
RestoreOnStartupURLs
These policies can override what the user selects through Chrome Settings.
Therefore, if you repeatedly select Open a specific page or set of pages, but Chrome changes back after restart, checking chrome://policy should be one of the first troubleshooting steps.
5. Understand the RestoreOnStartup Policy
Google Chrome supports an enterprise policy called:
RestoreOnStartup
This controls Chrome's startup behavior.
Common policy values include:
| Value | Behaviour |
|---|---|
| 1 | Restore the last session |
| 4 | Open a list of URLs |
| 5 | Open the New Tab page |
| 6 | Open specified URLs and restore the previous session |
Therefore, if Chrome keeps reopening your previous tabs, a policy configured to restore the previous session may be responsible.
For an organization that wants specific URLs to open, administrators can configure the appropriate startup policy together with the URL list.
6. Check RestoreOnStartupURLs
Another important enterprise policy is:
RestoreOnStartupURLs
This policy specifies which websites Chrome should open when the startup behavior is configured to open a list of URLs.
Example URLs might be:
On managed computers, these settings may be deployed through:
- Active Directory Group Policy
- Chrome Enterprise management
- Microsoft Entra ID-managed environments
- endpoint-management software
- enterprise configuration systems
If the policy is enforced, an ordinary user may not be able to override it through Chrome Settings.
7. Check Chrome Policies from the Windows Registry
Advanced administrators can inspect Chrome policy locations in the Windows Registry.
Press:
Windows + R
Type:
regedit
and press Enter.
Check:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
and:
HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome
Look for entries related to:
RestoreOnStartup
or:
RestoreOnStartupURLs
Important
Do not delete registry entries simply because they exist.
On company-managed computers, they may have been intentionally deployed through Group Policy or another management system.
Deleting a locally visible registry policy may also be temporary because Group Policy can recreate it.
Always determine where the policy originates before modifying it.
8. Refresh Chrome Policies
After an authorized policy change, open:
chrome://policy
Click:
Reload policies
Then verify whether the unwanted policy has disappeared or changed.
On domain-managed Windows computers, you may also need to refresh Windows Group Policy.
An administrator can use:
gpupdate /force
Afterward, restart Chrome and check:
chrome://policy
again.
9. Check Group Policy on Business Computers
On Active Directory or centrally managed Windows systems, Chrome settings may originate from Group Policy.
An administrator should inspect the Chrome policies configured for the computer and user.
Chrome Enterprise policy templates can control areas such as:
- startup behavior
- startup URLs
- homepage
- extensions
- proxy configuration
- sign-in
- security
- browser restrictions
If a Chrome setting is intentionally enforced by company policy, changing it manually inside Chrome will either be impossible or ineffective.
10. Check Whether an Extension Is Changing the Startup Page
Browser extensions can modify browser behavior.
Open:
chrome://extensions/
Temporarily disable all non-essential extensions.
Close Chrome completely.
Launch it again.
Configure:
Settings → On startup → Open a specific page or set of pages
Test again.
If the setting now works, enable extensions one at a time until the problematic extension is identified.
Pay particular attention to:
- search extensions
- coupon extensions
- unknown toolbars
- download managers
- VPN extensions
- new-tab replacements
- browser customization extensions
- extensions installed outside normal business requirements
Remove suspicious or unnecessary extensions.
11. Check for Browser Hijacking or Unwanted Software
If your startup page changes to a website you never configured, treat this as a possible security problem rather than merely a Chrome preference problem.
Warning signs include:
- unknown search engine
- advertisements on the startup page
- unexpected redirects
- unknown extensions
- new tabs opening automatically
- homepage changing repeatedly
- startup page changing after reboot
- Chrome shortcut containing an unknown URL
- “Managed by your organization” appearing unexpectedly on a personal computer
Run a security scan using your trusted endpoint-security or antimalware solution.
Also review recently installed applications.
12. Inspect the Chrome Shortcut
A modified shortcut can cause Chrome to open an unwanted website regardless of the configured startup page.
Right-click the Chrome shortcut and select:
Properties
Check the Target field.
A normal installation may resemble:
"C:\Program Files\Google\Chrome\Application\chrome.exe"
or:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
There should normally not be an unknown website appended after chrome.exe.
For example, this should be investigated:
chrome.exe https://unknown-example-site.com
If a suspicious URL has been appended to the shortcut, remove the unwanted portion after confirming that it was not intentionally configured.
Also inspect Chrome shortcuts on:
- Desktop
- Taskbar
- Start Menu
A pinned taskbar shortcut may differ from a Desktop shortcut.
13. Test Using a New Chrome Profile
Profile corruption can prevent Chrome preferences from behaving normally.
Click the profile icon in Chrome.
Create a new Chrome profile.
Before installing extensions or enabling synchronization, configure:
Settings → On startup → Open a specific page or set of pages
Close Chrome and reopen it.
If the setting works correctly in the new profile, the problem is probably associated with the original Chrome profile rather than the Chrome installation itself.
14. Temporarily Test Without Chrome Sync
Chrome synchronization can restore browser settings associated with an account.
If the problem follows the same Google account across different computers, test a fresh Chrome profile without immediately enabling synchronization.
Configure the startup page.
Restart Chrome several times.
If the issue occurs only after synchronization is enabled, investigate synchronized settings or extensions.
Do not permanently remove synchronized information without confirming what data is stored in the Google account.
15. Reset Chrome Settings
If no policy is controlling Chrome, a settings reset can help.
Open:
chrome://settings/reset
Select:
Restore settings to their original defaults
Read Chrome's explanation carefully before proceeding.
After the reset:
- Restart Chrome.
- Configure the startup page again.
- Test before reinstalling extensions.
A reset should generally be attempted before a complete browser reinstall.
16. Why Clearing Cache Usually Does Not Fix This Problem
Many users immediately clear:
- browsing history
- cookies
- cached images
- temporary internet files
However, Chrome's startup configuration is not simply a web cache issue.
Therefore, clearing browsing data may have no effect if the real cause is:
- policy
- extension
- profile configuration
- shortcut modification
- unwanted software
- enterprise management
Repeatedly clearing the cache is therefore not an efficient troubleshooting strategy for this particular problem.
17. Should You Run Chrome as Administrator?
Running Chrome once as Administrator can sometimes be useful as a diagnostic test in an unusual permissions-related situation.
However, Chrome should not normally require permanent Administrator elevation merely to save an ordinary startup-page preference.
Therefore:
Do not make “Run this program as an administrator” the default permanent solution.
Instead, investigate why a normal user profile cannot retain its settings.
Potential underlying causes include:
- damaged user profile permissions
- security software
- unusual application-control configuration
- damaged Chrome profile
- incorrectly modified file permissions
- enterprise policy
Permanent administrative elevation also changes the security context in which the browser operates and should not be used unnecessarily.
18. Do Not Give “Everyone” Full Control to Chrome.exe
Some troubleshooting guides suggest:
chrome.exe → Properties → Security → Give Everyone Full Control
This is not recommended as a routine solution.
Chrome does not normally require all users to have Full Control over its executable.
Broadly weakening application permissions can create unnecessary security exposure.
If file permissions are genuinely damaged, repair the specific permissions or reinstall Chrome instead of granting unrestricted access.
19. Check Chrome Installation Location
Chrome is commonly installed in locations such as:
C:\Program Files\Google\Chrome\Application\
or:
C:\Program Files (x86)\Google\Chrome\Application\
Some per-user installations may exist within the user's profile.
Knowing the installation type can help when troubleshooting:
- multi-user PCs
- Windows Server
- Remote Desktop Services
- enterprise-managed computers
20. Windows Server and RDS Environments
Chrome startup problems require additional consideration on:
- Windows Server
- Remote Desktop Services
- Terminal Server
- multi-user systems
Each user normally has an independent Chrome profile.
Therefore, configuring a startup page for Administrator does not necessarily configure it for every RDS user.
Administrators who need the same startup configuration for multiple users should consider centralized browser management instead of manually configuring every profile.
Before implementing enterprise policy, test it with a small group of users.
This is particularly important on production RDS servers.
21. Personal Computer vs Managed Computer
The troubleshooting method differs significantly depending on the computer.
Personal computer
Check:
- Chrome Settings
- extensions
- Chrome profile
- shortcut
- malware/unwanted software
- sync
- browser reset
Business-managed computer
Check:
chrome://policychrome://management- Group Policy
- Chrome Enterprise policies
- registry policy keys
- endpoint-management configuration
On managed computers, policy should generally be investigated before resetting or reinstalling Chrome.
22. Recommended Troubleshooting Order
For the fastest diagnosis, use this order:
Step 1: Configure the startup page normally.
Step 2: Restart Chrome and reproduce the problem.
Step 3: Check:
chrome://policy
Step 4: Check:
chrome://management
Step 5: Disable suspicious or unnecessary extensions.
Step 6: Inspect the Chrome shortcut.
Step 7: Test a new Chrome profile.
Step 8: Test without synchronization if appropriate.
Step 9: Scan Windows for unwanted software or malware.
Step 10: Reset Chrome settings.
Step 11: On managed systems, investigate Group Policy and registry policies.
Step 12: Consider a clean Chrome reinstall only after the above checks.
This order avoids unnecessary administrative elevation and potentially unsafe permission changes.
23. Useful Chrome Diagnostic URLs
The following internal Chrome pages are particularly useful:
chrome://settings/onStartup
Opens startup configuration.
chrome://policy
Displays policies detected by Chrome.
chrome://management
Shows browser-management information.
chrome://extensions/
Displays installed extensions.
chrome://settings/reset
Provides Chrome's settings-reset option.
chrome://version/
Displays Chrome version, executable path, profile path, and other diagnostic information.
For technical support personnel, chrome://version/ is especially useful when determining which Chrome profile and executable are actually being used.
24. When Reinstalling Chrome May Help
Consider reinstalling Chrome when:
- Chrome installation files are damaged
- the browser repeatedly crashes
- a fresh Chrome profile also fails
- policies have been ruled out
- extensions have been ruled out
- security scans are clean
- Chrome reset does not resolve the issue
Before removing Chrome, ensure that important browser information is backed up or synchronized as appropriate.
Do not automatically delete Chrome user data unless you understand what information will be removed.
25. Enterprise Administrator Solution
For organizations that intentionally want Chrome to launch specific corporate websites, centralized management is preferable.
Google provides enterprise policies including:
RestoreOnStartup
and:
RestoreOnStartupURLs
For example, an administrator can configure Chrome to open a predefined list of URLs.
This is useful for:
- offices
- call centres
- schools
- computer labs
- Windows Server RDS deployments
- kiosk-like environments
- accounting offices
- support teams
- ERP/CRM users
Centralized policy provides more predictable configuration than manually changing Chrome settings for every user.
26. Important Security Recommendation
Avoid solving browser configuration problems by unnecessarily weakening Windows security.
Do not routinely:
- give Everyone Full Control to Chrome files
- disable antivirus
- disable User Account Control
- permanently run Chrome as Administrator
- delete unknown registry policies without investigation
- remove company Group Policies without authorization
The objective is to identify what is overriding Chrome's startup preference, not bypass Windows security.
FAQ
1. Why does Chrome keep changing from “Open a specific page” to “Continue where you left off”?
A browser policy, profile problem, extension, enterprise configuration, or unwanted software may be overriding the setting. Check chrome://policy first.
2. How do I make Chrome always open Google when it starts?
Open:
chrome://settings/onStartup
Select Open a specific page or set of pages, choose Add a new page, and enter:
3. Can Chrome open multiple websites automatically?
Yes. Add each required website under Open a specific page or set of pages.
4. Why does Chrome reopen my old tabs instead?
Chrome may be configured to Continue where you left off, or an administrator may have configured a policy that restores the previous session.
5. What is RestoreOnStartup?
It is a Chrome Enterprise policy used to control what Chrome does when it launches.
6. What is RestoreOnStartupURLs?
It is a Chrome policy that defines the list of URLs Chrome should open when startup behavior is configured for specified URLs.
7. How can I check Chrome policies?
Enter:
chrome://policy
in Chrome's address bar.
8. How do I know whether Chrome is managed?
Open:
chrome://management
You can also look for management information in Chrome's menu and policy page.
9. Why is the startup option greyed out?
The setting may be controlled by an administrator or enterprise browser policy.
10. Can an extension change Chrome's startup behavior?
Extensions can affect browser and new-tab behavior. Disable non-essential extensions temporarily to test.
11. Should I run Chrome as Administrator to fix the startup page?
Not as a routine permanent fix. Ordinary Chrome preferences should normally work without administrative elevation.
12. Is it safe to give Everyone Full Control over chrome.exe?
It is not recommended as standard troubleshooting. Broad application permissions unnecessarily weaken security.
13. Will clearing Chrome's cache fix the startup page?
Usually not if the problem is caused by policy, an extension, profile configuration, or browser management.
14. Will reinstalling Chrome fix it?
Sometimes, but reinstalling should generally come after checking policies, extensions, shortcuts, profiles, unwanted software, and Chrome's reset option.
15. Can Group Policy force a Chrome startup page?
Yes. Organizations can centrally configure Chrome startup behavior using supported enterprise policies.
16. Where are Chrome policies stored in Windows?
Administrators may find policy settings under locations including:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
and:
HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome
Do not modify them without understanding their source.
17. Why does a deleted Chrome policy return?
It may be reapplied by Active Directory Group Policy, Chrome Enterprise management, endpoint-management software, or another centralized management system.
18. Can every RDP user have a different Chrome startup page?
Yes. Chrome profiles and user preferences can be user-specific. Administrators can also use appropriate centralized policies when a common configuration is required.
19. Why does Chrome open a strange website every time it starts?
Check the startup settings, Chrome extensions, browser policies, Chrome shortcut Target field, and Windows for unwanted software.
20. What should I check first when Chrome refuses to save its startup setting?
After confirming the setting itself, check:
chrome://policy
This quickly reveals whether a browser policy is overriding the user's choice.
Conclusion
When Google Chrome's Open a specific page or set of pages option does not work, the problem should not automatically be treated as a Windows Administrator-permission issue.
Modern Chrome installations can be affected by browser policies, enterprise management, extensions, user profiles, synchronization, modified shortcuts, or unwanted software.
The most useful diagnostic pages are:
chrome://settings/onStartup
chrome://policy
chrome://management
chrome://extensions/
chrome://version/
For home users, extensions, profiles, unwanted software, and corrupted settings are important areas to investigate.
For businesses, Windows Server, RDS, Active Directory, and managed PCs, administrators should pay particular attention to RestoreOnStartup, RestoreOnStartupURLs, Group Policy, and Chrome Enterprise management.
Most importantly, avoid weakening Windows security merely to make a browser preference work. Permanent Administrator elevation or granting broad Full Control permissions should not be the standard solution when Chrome provides supported configuration and policy mechanisms for managing startup behavior.
#Tags
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.