Guides

Restore your browser after unwanted software

Restore wanted browser settings after cleanup, understand Chrome reset and Firefox Refresh, preserve useful data, and investigate changes that return.

After removing unwanted software, you may still need to put your browser back into a usable state. An unfamiliar search provider, notification permission, extension, or startup page can remain as a separate setting. Start by deciding what you want to recover and what was actually changed; restoring everything from an old profile can also restore the unwanted configuration.

This guide covers desktop Chrome and Firefox on Windows and Mac. Other browsers have their own reset and import controls. It assumes the immediate device problem has been addressed. For ongoing unauthorized access, repeated security detections, or files being encrypted, use the infection diagnostic first. On a managed device, ask IT before changing policies or profiles.

Choose a repair that matches the remaining problem

For a targeted correction, use the dedicated Chrome, Edge, Firefox or Safari guide. They distinguish website grants, extension removal, search/home choices and the consequences of deleting stored data. Safari instructions here apply to Mac.

For one unwanted website grant, use notification blocking; for an unwanted add-on, use extension removal. Mac users can connect associated-app and login-item checks through Mac cleanup guidance before a broader browser change.

A browser reset is a configuration change, not a malware-removal verdict. Identify the trigger: starting the browser, opening a new tab, searching from the address bar, visiting one site, or receiving a desktop notification. The Chrome guide and redirect investigation help locate the responsible control before you consider a broader reset.

Remaining problemFirst restoration choiceCheck afterward
One unwanted notification senderRemove that site’s permissionThe sender no longer produces unwanted alerts
An extension controls search or tabsRemove the unwanted extension through browser controlsThe relevant setting can be changed and stays changed
Several preferences are uncertainConsider the browser’s documented reset or refreshUseful data remains and unwanted settings are corrected
A setting returns after restartInvestigate the remaining controller or installed softwareThe recurrence has an explanation, not just another reset
Data is missing from an old profilePreserve the old data and recover wanted items selectivelyRecovery does not bring back the whole uncertain configuration

Record the original setting and each change. Testing one ordinary action after a small correction gives more useful evidence than making ten changes at once. Do not revisit a deceptive website just to reproduce its behavior.

Preserve useful information before a broad change

Make an inventory of bookmarks, local-only passwords, important tabs, and accessibility customizations. Establish whether each item exists only on this device or is also available through an account. Having signed into a browser previously does not establish that every wanted item was saved remotely.

Google’s bookmark instructions document exporting bookmarks as an HTML file from Bookmark Manager and importing a saved file separately. That offers a more selective recovery route than replacing an entire profile. Keep the file private: bookmark names and destinations may reveal personal or work activity. An old bookmark can still point to an unwanted destination, so review what you import.

Avoid making a plain-text password export merely for convenience. If credentials may have been exposed, recovering the old password list is different from securing the accounts. Follow account recovery on a trusted device; do not rely on a browser reset to revoke stolen access.

Do not delete the only old profile to tidy up before establishing what you need. Google warns that removing a Chrome profile erases its local data. Creating a separate profile and deleting the original are different actions.

Understand Chrome’s reset before confirming it

Google documents Settings → Reset settings → Restore settings to their original defaults. The reset explanation says saved bookmarks and passwords remain. Search, startup/home settings, content permissions, cookies/site data, and extension/theme configuration are affected; some other customizations remain. Google notes that reset settings can change across devices where you are signed into that profile. Read the confirmation shown by your installed version before proceeding.

Plan for websites needing sign-in again after site data changes. Save ongoing work and ensure you can recover access to important services. Retained passwords are not evidence that those passwords were never exposed.

After resetting, inspect the extension list and restore only the functions you actually need. Chrome’s extension controls provide supported removal and access settings. Re-enabling every old extension immediately would make it harder to tell which change resolved the problem. Use the extension selection guide when choosing replacements.

Know what Firefox Refresh keeps

Mozilla’s Refresh instructions describe a new profile that retains important personal data, including bookmarks, passwords, history, and cookies. Profile-installed extensions and many custom settings are removed. Accessibility adjustments may need to be recreated; add-ons stored outside the profile are not necessarily removed.

Reach More troubleshooting information through Firefox’s Help menu and read the Refresh confirmation. Mozilla notes availability differences with the newer profile-management system on versions earlier than Firefox 150. If your interface differs, use the documentation for the installed version rather than deleting files manually to imitate a refresh.

The retained cookies matter: do not treat Refresh as a way to revoke online sessions. Mozilla also describes an Old Firefox Data folder after refresh. Treat that folder as sensitive recovery material. Copying it wholesale back into the new profile can undo the separation you just created; keep only what you need after reviewing the supported recovery method.

Review account sharing before bringing everything back

Chrome account controls distinguish local information from information saved in the Google Account. Current desktop instructions put the choice of what to save under Settings → You and Google → your account name. Inspect the available categories and account identity before adding recovered settings or extensions to a rebuilt profile.

Reintroduce wanted information deliberately and note what changed after sign-in or import. If a problem returns then, that timing narrows your investigation; it does not by itself prove the account or synchronization caused an infection. Another installed component, a required policy, or an old setting may still explain it.

Avoid deleting all account-saved browser data as a speculative fix. That can affect recovery on other devices and deserves a specific reason. Preserve a useful record and seek supported help if you cannot separate the wanted data from the recurring configuration.

Verify restoration and investigate recurrence

Check a normal launch, a new tab, an address-bar search, the wanted notification permissions, and the extension list. Close and reopen the browser, then compare the same actions. Record remaining differences rather than declaring the whole device safe because one search works normally.

If an unwanted setting is locked or management is unexpected, Google’s management guide explains how to inspect browser management. A management message can be legitimate on a work device. Do not remove policies or certificates blindly to unlock a setting.

If the symptom returns, investigate device cleanup, software that changes settings, and account exposure through recovery verification. Keep the original data until wanted information is recovered, then retire sensitive redundant copies thoughtfully. This guide is based on official documentation, not a site-run browser infection or restoration experiment.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy