Fix ERROR_NO_SITE_SETTINGS_OBJECT (0X000021AB)

This error means Windows can't find the site settings object for an IE or Edge site. The fix is usually a registry tweak or clearing cached site data.

You're staring at 0X000021AB and it's driving you nuts

This error pops up when you try to access a site in Internet Explorer or Edge (the old version), and Windows can't find the site settings object it expects. It's usually because of corrupted cached data or a registry entry that's gone sideways. Had a client last month whose entire print queue died because of this — the error hit after a failed Group Policy update. Let's get you fixed.

The fix: Clear cached site data and fix the registry

Skip the generic 'run SFC scan' advice — that won't help here. The real fix is two-step: clear the stale data, then repair the registry key.

Step 1: Clear IE/Edge cached site data

Press Win + R, type inetcpl.cpl, hit Enter.
Go to the General tab, under Browsing history, click Delete.
Check Temporary Internet files and website files, Cookies and website data, and History. Uncheck Passwords and Form data unless you want to lose those.
Click Delete.
Restart the browser and test.

Step 2: Fix the registry key for site settings

If clearing cache doesn't work (and it often doesn't for this specific error), the problem is in the registry. Specifically, the path HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SiteSettings might be missing or corrupted. Here's how to fix it:

Press Win + R, type regedit, hit Enter.
Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SiteSettings
If that key doesn't exist, you need to create it. Right-click Internet Explorer, select New > Key, name it SiteSettings.
Inside that key, right-click in the right pane, select New > DWORD (32-bit) Value. Name it SiteSettingsObject.
Double-click that new DWORD, set value to 1. Click OK.
Close Registry Editor, restart the browser.

Why this works

The error 0X000021AB translates to 'The site settings object for the specified site does not exist.' Windows expects a registry entry that tells it where to store per-site settings like zoom levels, cookie permissions, and compatibility view lists. When that key is missing — often after a Windows update or a botched Group Policy application — the browser throws this error. Clearing the cache removes stale references that might be pointing to a non-existent object. Creating the registry key manually gives Windows the placeholder it needs. I've seen this fix work on Windows 10 21H2 and Windows 11 22H2.

Less common variations of the same issue

Sometimes the error shows up with slightly different symptoms:

User profile corruption: If the registry fix doesn't stick, the user profile itself might be damaged. Test with a new local user account. If the error disappears, migrate data to a fresh profile.
Group Policy override: In enterprise environments, a GPO might be blocking registry writes to SiteSettings. Check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\SiteSettings. If that exists, the policy needs to be relaxed by IT.
Edge Chromium (new Edge): The new Edge doesn't use this registry path — it uses a SQLite database in %LOCALAPPDATA%\Microsoft\Edge\User Data\Default\Site Settings. If you get a similar error there, go to edge://settings/reset and click Restore settings to their default values.

Prevention: Stop this from coming back

This usually happens after a Windows update or a group policy change. To prevent it:

Always run Windows updates in batches — install them one at a time and reboot between them. That way if a key gets deleted, you know which update caused it.
Back up the SiteSettings registry key before any major update. Export it with regedit: right-click the key, select Export, save as a .reg file. If the error returns, double-click that .reg file to restore it.
For IT admins: verify your Group Policy objects don't accidentally delete HKCU\Software\Microsoft\Internet Explorer\SiteSettings. Use the Group Policy Management Console to check for settings under Administrative Templates > Windows Components > Internet Explorer.
If you're using the new Edge (Chromium-based), turn on sync for site settings in edge://settings/profiles/sync. That way if local data gets corrupted, the cloud restores it.

One more thing — don't bother with DISM or SFC for this particular error. They don't touch the site settings object. I've seen people waste hours running those commands for nothing. Stick to the registry and cache fix, and you'll be back in business in 10 minutes.