savrt32.dll Is Missing: Choose the Right Repair Path on Windows

“ The program can’t start because SAVRT32.dll is missing from your computer.” You may also see “Error loading SAVRT32.dll,” “The specified module could not be found,” or “Failed to load SAVRT32.dll.”

savrt32.dll is the Symantec Realtime DLL used by the Auto-Protect component of older Symantec and Norton antivirus products. It is not a Windows system file, Microsoft runtime, DirectX component, or .NET file.

#	Preview	Product	Price
1		Microsoft Windows 11 (USB)	$124.97	Buy on Amazon
2		Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |...	$119.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

The safest solution is to repair or reinstall the exact Symantec or Norton product that expects the file. If you no longer use that antivirus, remove the incomplete installation instead of downloading a replacement DLL.

Which fix applies to you

Choose the path that matches what happened:

• The old antivirus is still installed: repair or reinstall it using its original installer or trusted Symantec/Broadcom installation media.
• The error appears during Windows startup, but the antivirus was removed: remove the leftover service, scheduled task, or startup registration by reinstalling the product and uninstalling it properly.
• Your security software quarantined the file: inspect its quarantine history. Restore it only if it belongs to the installed Symantec product and the detection is clearly a false positive.
• The error started after malware removal: run a complete security scan, then repair or remove the damaged Symantec installation.
• The file is visible but will not load: the file may be damaged, incompatible, blocked, or missing a dependency. Replacing it with a random copy is not a reliable fix.
• Other Windows components are also failing: use Windows Update, DISM, and SFC as secondary diagnostics.
• You are unsure whether the product is still needed: uninstall the old antivirus and install a current, supported security product afterward.

What savrt32.dll does

The filename is associated with Symantec’s real-time antivirus protection. Historical products that used it include older Symantec AntiVirus, Norton AntiVirus, Symantec Client Security, and some Symantec Endpoint Protection releases.

#1 Best Overall

Sale

Microsoft Windows 11 (USB)

• Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
• Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
• Make the most of your screen space with snap layouts, desktops, and seamless redocking.
• Widgets makes staying up-to-date with the content you love and the news you care about, simple.
• Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)

$124.97

Buy on Amazon

Older installations placed the file in the product’s private directory, not normally in C:WindowsSystem32. You may find it under a Norton AntiVirus folder or inside a Symantec Endpoint Protection Bin folder.

The 32 in the filename suggests a 32-bit-oriented module, but it does not establish that every file with this name is interchangeable. A DLL from an older Norton release is not a safe substitute for a Symantec Endpoint Protection component. Current Endpoint Protection releases may use different Auto-Protect filenames altogether.

Fix 1: Repair or reinstall the owning antivirus

This is the most likely fix when Symantec or Norton is still present.

Identify the installed product

1. Press Windows + I.
2. Select Apps.
3. Select Installed apps on Windows 11, or Apps & features on Windows 10.
4. Search for Symantec, Norton, Endpoint Protection, Symantec Client Security, or Symantec AntiVirus.
5. Note the exact product name and whether it is still listed.

You can also check the older Control Panel list:

1. Press Windows + R.
2. Type appwiz.cpl.
3. Press Enter.
4. Look for the same product names under Programs and Features.

Do not use a different antivirus installer merely because its name contains Norton or Symantec. Match the installer to the product already installed.

Use the product’s repair option

If Windows displays Modify, Repair, or a similar option:

1. Open Installed apps or Programs and Features.
2. Select the Symantec or Norton product.
3. Choose Modify or Change.
4. Select Repair if the installer offers it.
5. Approve the administrator prompt.
6. Restart Windows when the repair finishes.

If no repair option appears, use the original installation media or the official Symantec/Broadcom package supplied for that product. Enterprise Endpoint Protection packages may be provided as a full installation executable, an all-clients archive, or separate Windows client installers. Use the package that matches your license, product release, and system architecture.

Reinstall from trusted media

If repair fails:

1. Back up any license or configuration information you still need.
2. Uninstall the existing Symantec or Norton product normally.
3. Restart Windows.
4. Run the matching official installer as an administrator.
5. Complete the installation.
6. Restart again.
7. Test the program or startup action that previously reported savrt32.dll.

To run an installer with administrator rights, right-click it and select Run as administrator. If the installer fails, do not copy a DLL into System32 or SysWOW64. Record the installer error and check whether an old Symantec service or previous installation remains.

A successful repair normally means the error no longer appears and the antivirus opens without reporting a missing component. If the same message returns immediately, the installer may be for the wrong product generation, the old installation may not have been removed completely, or another Symantec product may still be registered.

Fix 2: Remove an orphaned Symantec installation

If the antivirus was already removed but Windows still tries to load savrt32.dll, the error is probably caused by an incomplete uninstall.

Uninstall it normally first

1. Press Windows + I.
2. Select Apps.
3. Open Installed apps.
4. Find the Symantec or Norton entry.
5. Select the three-dot menu.
6. Choose Uninstall.
7. Follow the removal wizard.
8. Restart Windows.

On Windows 10, use Settings > Apps > Apps & features. You can also open Control Panel > Programs > Programs and Features, select the product, and choose Uninstall.

After restarting, check whether the error has disappeared. Do not manually delete random Symantec folders or registry keys before attempting the supported uninstall process.

Use CleanWipe only when normal removal fails

For Symantec Endpoint Protection, Broadcom provides a removal utility called CleanWipe. Broadcom describes it as a last-resort tool, not the first step for repairing a missing DLL.

Use the supported CleanWipe procedure when:

• the product will not uninstall normally;
• the installation is damaged;
• the uninstall process stops or rolls back;
• Endpoint Protection remains registered after removal.

CleanWipe may be included in the full Endpoint Protection installation under a Tools folder, or supplied through Broadcom’s support and download portal. Obtain it from the official vendor source for your product, then:

1. Close open applications.
2. Extract the CleanWipe package if it is compressed.
3. Right-click the CleanWipe executable and select Run as administrator.
4. Follow its prompts.
5. Restart Windows when requested.
6. Check whether the startup error is gone.

CleanWipe can remove security software components more deeply than a normal uninstall. Do not use it casually on a working installation unless you are prepared to reinstall or replace that product.

If the error disappears after removal, the remaining problem was an orphaned registration rather than a Windows DLL failure.

Fix 3: Check quarantine and recent security actions

A security product may quarantine or delete savrt32.dll after detecting a damaged or suspicious file. The correct response depends on whether the file belongs to a legitimate installed product.

1. Open the security software that performed the detection.
2. Open Protection history, Quarantine, or Detection history.
3. Find the event involving savrt32.dll.
4. Check the file path and the associated Symantec or Norton product.
5. Check the detection name and vendor recommendation.
6. Restore the file only when it is clearly part of your installed Symantec product and the detection is confirmed as a false positive.
7. Repair or reinstall the complete antivirus product afterward.

Do not restore a file simply because its name matches the missing filename. A copy found in an unexpected directory deserves additional scrutiny, although its location alone does not prove that it is malware.

If the security product cannot verify the file, leave it quarantined and reinstall the complete Symantec or Norton application from trusted media. Reinstalling the application restores the required files and their companion components together.

Fix 4: Scan for malware before repairing

If the message appeared after malware removal, a cleanup tool may have deleted or damaged part of the old antivirus installation. Malware may also have altered startup entries or services.

1. Open Windows Security from the Start menu.
2. Select Virus & threat protection.
3. Select Scan options.
4. Choose Full scan.
5. Select Scan now.
6. Follow the recommended action for every detection.
7. Restart Windows.
8. Repair or uninstall the Symantec product using the steps above.

If the system still behaves suspiciously, use Microsoft Defender Offline scan from the same Scan options page. Save your work first because Windows restarts to perform the scan.

Do not assume that every savrt32.dll error is caused by malware. A corrupted installation, failed uninstall, or incompatible product version is more directly connected to the file.

Fix 5: Repair Windows components with DISM and SFC

DISM and SFC repair protected Windows components. They do not normally restore an arbitrary third-party Symantec DLL, so use them when other Windows files are also failing or when Windows servicing appears damaged.

First install pending Windows updates:

1. Press Windows + I.
2. Select Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart if prompted.

Then open an elevated Command Prompt:

1. Open the Start menu.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Approve the User Account Control prompt.

Run DISM first:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for it to finish. Then run System File Checker:

sfc /scannow

Do not close the window until each command reaches completion. Restart Windows and test again.

Rank #2

Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC | Branded by Microsoft

• STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
• OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
• OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
• PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
• GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.

$119.99

Buy on Amazon

If SFC reports that it repaired files, test the system after restarting. If it reports that it could not repair everything, run Windows Update again and repeat the supported DISM-then-SFC sequence. If only savrt32.dll remains missing, return to the Symantec repair or removal path rather than repeating SFC indefinitely.

When manually checking DISM and SFC results becomes tedious, Outbyte PC Repair can perform a free scan to show what it finds; repairs are completed with the full version, and it is not required when reinstalling the owning Symantec program.

Fix 6: Check architecture, dependencies, and permissions

A visible DLL can still fail to load. Windows may report “specified module could not be found” when the named DLL exists but one of its required dependencies does not.

Possible causes include:

• a damaged savrt32.dll;
• a missing companion file;
• an incompatible release;
• a 32-bit and 64-bit mismatch;
• a blocked file;
• inadequate permissions;
• a remaining service pointing to an old installation directory.

Check the installation path:

1. Open the Symantec or Norton installation folder.
2. Confirm that savrt32.dll is inside the product directory rather than copied into a Windows system folder.
3. Right-click the file and select Properties.
4. Check the Digital Signatures tab if available.
5. Compare the path and product details with the installed application.

Do not treat the filename as a complete architecture guide. Install the Windows 32-bit or 64-bit client package that matches the product and operating system when the vendor provides separate packages. Do not combine files from different product releases.

If Windows says the file is blocked, right-click it, select Properties, and look for an Unblock option. Only unblock a file obtained from trusted installation media and verified as part of the installed product.

Fix 7: Check services and startup leftovers

A startup error often means Windows is launching a service or scheduled task from a partly removed antivirus installation.

Check services:

1. Press Windows + R.
2. Type services.msc.
3. Press Enter.
4. Look for Symantec or Norton services.
5. Do not disable a service blindly if the antivirus is still installed and working.
6. If the product is no longer wanted, use its supported uninstaller or CleanWipe instead of deleting the service manually.

Check startup applications:

1. Press Ctrl + Shift + Esc.
2. Select Startup apps.
3. Look for obsolete Symantec or Norton entries.
4. If the product has already been removed, disable only the clearly identified leftover entry.
5. Restart Windows.

You can also check Task Scheduler for an obsolete Symantec or Norton task, but avoid deleting entries merely because they contain a familiar vendor name. Reinstalling and then properly uninstalling the product is safer than manually editing registry entries.

Fix 8: Update drivers only when broader failures point there

A driver is not the normal source of a savrt32.dll missing error. Consider driver troubleshooting only if the failure began after a hardware, storage, security, or operating system change and other applications are also unstable.

To check drivers:

1. Right-click the Start button.
2. Select Device Manager.
3. Expand categories such as Storage controllers, System devices, Network adapters, and Display adapters.
4. Right-click the relevant device.
5. Select Properties.
6. Open the Driver tab.
7. Note the provider and driver date.
8. Use Update Driver only when Windows or the hardware manufacturer provides a matching package.
9. Restart Windows.

Do not use Device Manager to replace savrt32.dll; it cannot repair an application DLL.

When hunting through Device Manager for an outdated chipset, storage, or security-related driver is taking too long, Outbyte Driver Updater can provide a free scan showing detected driver issues; driver installation is completed with the full version, and it is not a substitute for reinstalling the Symantec application itself.

Do not download savrt32.dll separately

Avoid DLL download websites and unofficial file mirrors. A random copy may be:

• modified or malicious;
• from the wrong Norton or Symantec generation;
• built for the wrong architecture;
• missing required companion files;
• incompatible with the installed service;
• unable to repair the damaged product registration.

Copying the file to C:WindowsSystem32 or C:WindowsSysWOW64 is also unsafe. The owning antivirus normally loads its private DLL from its own installation directory. System-wide copying can create version conflicts and DLL search-order problems.

The safe sources are the original licensed Symantec or Norton installation media and official Broadcom support or download channels for Symantec Endpoint Protection. If the product is obsolete and no trusted installer is available, remove it and install a supported security product rather than reconstructing it from loose DLL files.

Why regsvr32 is normally not the fix

regsvr32 is intended for DLLs that provide a registration entry point such as DllRegisterServer. It is not a general-purpose command for repairing every missing or unloadable DLL.

There is no authoritative Symantec instruction directing users to register savrt32.dll with regsvr32. Running:

regsvr32 savrt32.dll

will usually produce another error or make no useful change. Use the product’s installer and uninstaller instead.

When to investigate the disk

If files repeatedly disappear, installers fail to write files, or Windows reports filesystem errors, back up important data and investigate the storage device.

You can check the drive from File Explorer:

1. Open This PC.
2. Right-click the Windows drive.
3. Select Properties.
4. Open the Tools tab.
5. Select Check under Error checking.
6. Follow the prompts.

Repeated corruption can cause an antivirus repair to fail again. Resolve the storage problem before repeatedly reinstalling the application.

Final checklist if the error remains

Work through these points before attempting another repair:

• Identify the exact Symantec, Norton, or Endpoint Protection product.
• Confirm whether it is still installed.
• Use the matching installer, not a loose DLL.
• Match the installer to the Windows architecture and product generation.
• Check quarantine history.
• Run a complete malware scan if the problem followed malware removal.
• Use DISM followed by SFC only for broader Windows integrity problems.
• Check for leftover services, scheduled tasks, and startup entries.
• Use CleanWipe only after normal uninstall fails.
• Check disk health if files or installations keep becoming damaged.
• Avoid copying the file into System32 or SysWOW64.
• Do not run regsvr32 unless the vendor specifically instructs you to do so.

FAQ

Is savrt32.dll part of Windows?

No. It is a third-party Symantec antivirus component associated with Auto-Protect and older Norton-branded products.

Can I restore it with System File Checker?

Usually not. SFC repairs protected Windows components, while savrt32.dll belongs to Symantec software. Repair or reinstall the owning antivirus instead.

Is the file always 32-bit?

The filename is 32-bit-oriented, but it does not provide a complete architecture or compatibility guarantee. Use the installer that matches the product release and operating system.

The file exists. Why does Windows still say it is missing?

The file may be damaged, blocked, incompatible, or missing a dependency. An obsolete service may also be loading it from a path that no longer exists.

Should I register it with regsvr32?

Normally no. regsvr32 is for DLLs designed for registration, and there is no authoritative Symantec instruction to register this file.

What should I do if I no longer use Norton or Symantec?

Uninstall it normally. If Endpoint Protection cannot be removed, follow Broadcom’s CleanWipe procedure as a last resort. Restart and install a supported security product if needed.

Is a copy from another computer safe?

Not necessarily. The other computer may have a different product generation, architecture, update level, or dependency set. Reinstall the complete application from trusted vendor media instead.

Quick Recap

SaleBestseller No. 1

Microsoft Windows 11 (USB)

Make the most of your screen space with snap layouts, desktops, and seamless redocking.; FPP is boxed product that ships with USB for installation

$124.97

Bestseller No. 2

Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC | Branded by Microsoft

GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.

$119.99

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.