Some Chrome settings will not change no matter what you do - they are grey, locked, or they change back an hour later. On an office PC that is not a fault. It is your organisation managing its own browser, and this page explains how to work with it.
Office Chrome runs under policy: a layer of settings your IT team enforces on purpose. It explains the locked homepage, the blocked extension, the proxy you cannot switch off, and why resets seem to wear off. The honest approach is not to fight policy but to read it - Chrome shows you the whole list - then fix everything that lives in your own layer, and take the rest to IT with evidence. This page draws that line clearly.
Open chrome://policy. If the page lists policies, your browser is managed, and the note Managed by your organization in Chrome's menu is simply reporting the truth, not an error. Read the list with your own eyes: every line is a setting your IT admin has deliberately fixed - homepage, proxy, extension rules, update behaviour. This page is read-only, and that is correct. Knowing the exact policy names now saves you an hour of fixes that were never going to stick.
Typical office policies fix the homepage and search engine, block or allow specific extensions, force traffic through the company proxy, control Chrome updates and decide whether passwords may be saved. Settings enforced this way appear greyed out with a briefcase icon. Here is the part fix guides skip: resetting Chrome settings does not defeat policy. A reset returns user settings to defaults - then the policy layer reapplies itself, usually within the hour. The repair script from the video behaves the same honest way on a managed PC: it repairs what is yours, and the company settings return.
Plenty of real faults remain in your own layer. The cache clear, the cookie cleanup for one broken site, the halves hunt for an extension that policy allowed but that misbehaves, a damaged personal profile - all user-level, all fixable by you. Repairs also still work at the Windows layer within your rights: if pages fail for everyone in the office, that is the network, not your browser. Sort each fault into yours or theirs before spending effort - policy draws a clean line, and working with it is faster than fighting it.
Signing a work browser into your personal Google account does not unmanage it - policy follows the browser and the machine, not the account. The mirror image also surprises people: signing a home PC into work apps can bring work management with it. Neither is a trick or an error; it is how managed browsers are built to behave. Keep expectations aligned with that design and most office Chrome mysteries explain themselves.
When a policy genuinely blocks your work, admins grant exceptions to people who bring evidence. Bring three things: the policy name from chrome://policy, the exact error or greyed-out setting you hit, and what you already tested (works in Incognito, fails only on the office network, and so on). For a blocked extension, add its name and ID from chrome://extensions in developer mode. That message gets a decision in one round - while please fix my Chrome gets a questionnaire.
The custom Chrome repair script in action - 15 common Chrome problems fixed in about a minute, shown live, step-by-step.
Watch Full VideoSometimes security software or unwanted software sets a Chrome policy on a personal PC too. Open chrome://policy - if a policy exists that neither you nor any employer set, run a full malware scan first; on your own machine, a mystery policy is a symptom, not a setting.
No. It resets user-level settings, clears cache and temp files, flushes DNS and resets the network stack. Policies are applied from the organisation's configuration and return after refresh, exactly as designed.
Ask IT, and bring the extension's name and its ID from chrome://extensions. A blocked-by-policy extension can only be allowed by an admin changing the policy - no local setting can release it.