riched20.dll Missing: Find the Correct Windows Repair Path

×Worth Installing

PC Slower Than It Used to Be?

Outbyte PC Repair · freeA free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Run a Free PC Scan →

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

This application failed to start because RICHED20.dll was not found. Re-installing the application may fix this problem.

The riched20.dll error usually means Windows or one application cannot load Microsoft’s Rich Edit text-editing control. The safest fix depends on whether the error appears everywhere, only in Office, during an MSI installation, or only when starting one older program.

#	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.

Which fix applies to you

Use the path that matches what you are seeing:

• Several unrelated programs fail: Repair Windows with Windows Update, DISM, and SFC.
• Only Office fails: Repair Microsoft 365 or Office using Online Repair.
• Only one game or application fails: Repair, update, or reinstall that application from its official source.
• An installer shows Error 2894: Treat it as a Windows Installer or system-component problem first, not as proof that you need a downloadable DLL.
• The error names System32 or SysWOW64: Check the application’s architecture before replacing anything.
• The problem began after antivirus activity: Check Windows Security Protection history.
• SFC and DISM finish successfully but the application still fails: Investigate the application’s private DLL, plug-ins, permissions, compatibility, or user profile.
• The message says “not designed to run on Windows” or “Bad Image”: Stop copying files and repair the correct Windows or application installation.

Do not download riched20.dll from a random DLL website. An altered file, wrong architecture, incompatible export set, or malware infection can create a more serious failure while leaving the original cause unresolved.

What is riched20.dll

riched20.dll is a Microsoft Windows component known as the Rich Text Edit Control, v2.0. It belongs to Microsoft RichEdit Control version 2.0 and provides text-editing functionality that applications can load as a Windows control.

#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

Microsoft documents that Rich Edit 2.0 and 3.0 use Riched20.dll, while Rich Edit 4.1 uses Msftedit.dll (About Rich Edit Controls). Older applications can load the control directly, and Microsoft Foundation Class applications may initialize it through AfxInitRichEdit2 (AfxInitRichEdit2).

This is normally a Windows component. It is not normally supplied by:

• Microsoft Visual C++ Redistributables
• DirectX
• The .NET runtime
• A graphics driver
• A sound driver

Some products, particularly Office, can also include private copies of riched20.dll inside their own installation folders. Those copies may have different versions from the Windows copy. Office update file information documents riched20.dll files within Office components (Office 2016 update file information).

That distinction matters. Replacing an application’s private copy with a file copied from Windows is not a general repair method.

Why System32 and SysWOW64 can both contain riched20.dll

On 64-bit Windows, the usual locations are:

• %windir%System32 for native 64-bit system files
• %windir%SysWOW64 for 32-bit system files

The names are historical and confusing. System32 does not mean that every file there is 32-bit. Microsoft’s documentation on the File System Redirector explains how 32-bit applications are redirected to the appropriate system locations.

The relevant copy depends on the application:

• A 64-bit application normally needs the 64-bit system component.
• A 32-bit application running on 64-bit Windows normally needs the 32-bit system component.
• A 32-bit application can fail even when the 64-bit copy is present and healthy.

Do not copy a file from System32 into SysWOW64, or the reverse, to make an error disappear. The file must match the application and Windows installation that loads it.

File versions and sizes also vary with Windows build, servicing level, architecture, language, and product packaging. Do not treat a particular file size or version as a universal test of whether riched20.dll is correct.

What the error message means

A crash report that names riched20.dll as the faulting module does not prove the DLL itself is defective. The application may have passed invalid data, loaded an outdated private copy, or used an incompatible plug-in.

Fix 1: Install Windows updates, then repair Windows

This is the correct first repair when multiple applications report the problem or when the message points to a Windows directory.

Install pending updates

1. Select Start.
2. Open Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install available updates.
6. Restart the computer, even if Windows does not immediately require it.
7. Test the affected application again.

Microsoft’s Windows Update installation guidance provides the current update path for Windows.

If the error remains, continue with DISM and SFC. Do not skip DISM when Windows component corruption is possible.

Run DISM, then SFC

1. Select Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Approve the User Account Control prompt.
6. Run this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish. Do not close the window while it is working.
2. Run:

sfc /scannow

1. Wait until the verification reaches 100 percent.
2. Restart Windows.
3. Test the program again.

DISM repairs the Windows component store that SFC uses as a repair source. SFC checks protected system files and replaces damaged copies where possible. Microsoft documents this DISM-then-SFC sequence in Using System File Checker in Windows.

If SFC reports that it found and repaired corrupted files, restart and test the application. If it reports that it could not repair some files, run DISM again, restart, and repeat SFC once. If the result does not change, move to the recovery options described later rather than downloading a replacement DLL.

Repeating SFC without understanding what changed can make troubleshooting needlessly circular. Outbyte PC Repair can show what its free scan identifies, while repair actions are handled by the full version; it is optional, and Microsoft’s DISM and SFC tools remain the normal Windows repair path.

Check only the system copy

For a targeted check, Microsoft documents the /scanfile option. In an elevated Command Prompt, run:

sfc /scanfile=C:WindowsSystem32riched20.dll

On 64-bit Windows, do not assume this checks the copy used by a 32-bit application. If the failing program is 32-bit, inspect the corresponding SysWOW64 path:

sfc /scanfile=C:WindowsSysWOW64riched20.dll

The Microsoft sfc command reference documents the command syntax. Use the path that corresponds to the copy being investigated, and do not confuse a 64-bit operating system with a requirement that every application use System32.

Fix 2: Repair the affected application

If only one application reports riched20.dll, the application is the leading suspect. It may have a damaged private copy, an incomplete update, an incompatible plug-in, or a broken installation path.

Repair Office or Microsoft 365

If Word, Excel, Outlook, Access, or another Office application is the only affected program:

1. Close all Office applications.
2. Select Start.
3. Open Settings.
4. Select Apps.
5. Select Installed apps.
6. Find Microsoft 365 or Microsoft Office.
7. Select the three-dot menu beside it.
8. Select Modify.
9. Choose Online Repair.
10. Follow the prompts.
11. Restart Windows and test Office.

Microsoft states that Online Repair replaces more components than Quick Repair. Use Repair an Office application if the menu names differ on your installation.

Do not copy the Windows riched20.dll into an Office directory. Office may intentionally ship its own private copy, and replacing it manually can create a version mismatch.

Repair another application

For a non-Office program:

1. Close the application.
2. Open Settings.
3. Select Apps.
4. Select Installed apps.
5. Select the application’s menu.
6. Choose Advanced options if available.
7. Select Repair.
8. Open the application and test it.

Not every desktop application exposes the Windows Repair button. If it does not:

1. Open the application’s official installer or launcher.
2. Look for Repair, Verify files, Scan and repair, or an equivalent option.
3. Run that operation.
4. Restart Windows.
5. Test the application.

If repair does not work, uninstall the affected application, restart, and reinstall it from the vendor’s official installer. This is especially important for older games, MSI-based software, and programs that keep a private DLL beside their executable.

Microsoft also provides guidance for fixing programs that cannot be installed or removed.

If the program is a game or specialist application, reinstalling that specific program remains the definitive fix when its private copy is damaged. Windows repair tools cannot reliably repair files owned and maintained by another product.

Fix 3: Check the architecture and DLL search path

A 32-bit application and a 64-bit application do not necessarily load the same copy of riched20.dll.

First identify the affected program:

• Check the vendor’s system requirements or documentation.
• Look at the application’s installation folder and launcher details.
• If it is an older program, assume it may be 32-bit until verified.
• Check whether the error names System32, SysWOW64, an Office folder, a temporary installer folder, or the application’s own directory.

A missing procedure entry point or “not designed to run” message is particularly consistent with loading an incompatible copy. Common locations to inspect are:

• The application’s installation directory
• An Office installation directory
• A temporary installer directory
• %windir%System32
• %windir%SysWOW64

Do not delete copies simply because more than one exists. Windows and applications can legitimately maintain separate copies. The safe response to an incorrect private copy is to repair or reinstall the owning application.

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 the application is an old 32-bit program, try its current vendor update or compatibility guidance. Do not force a 64-bit DLL into a 32-bit application folder.

Fix 4: Check Windows Security Protection history

Antivirus software can quarantine a file after a false positive, while malware can also damage or replace system files.

To inspect Microsoft Defender’s history:

1. Select Start.
2. Open Windows Security.
3. Select Virus & threat protection.
4. Select Protection history.
5. Review recent detections.
6. Expand any detection related to riched20.dll.
7. Confirm the file path and detection details before taking action.

Do not restore a quarantined file merely because its name is riched20.dll. Restore it only after confirming that it is a genuine Microsoft-signed system file and that the detection is a false positive. Microsoft warns that restoring a real threat can expose the device. See Protection history in Windows Security.

If malware is suspected:

1. Keep the device disconnected from untrusted networks where practical.
2. Run a full Microsoft Defender scan.
3. Follow the remediation instructions shown by Windows Security.
4. Run Windows Update.
5. Run DISM and SFC after the threat is removed.
6. Change important passwords from a known-clean device if compromise is possible.

Do not download a replacement DLL while malware is still a possibility.

Fix 5: Update drivers only when the evidence points there

Drivers are not the normal owner of riched20.dll, so driver updates are not a first-line fix for this error. Consider them only if the problem began with a broader display, input, storage, or system instability issue and Windows diagnostics point toward a device driver.

To check a driver through Device Manager:

1. Right-click Start.
2. Select Device Manager.
3. Expand the device category associated with the wider problem.
4. Right-click the device.
5. Select Properties.
6. Open the Driver tab.
7. Record the provider and version.
8. Use Update driver only when an appropriate update is available.
9. Restart Windows.
10. Test the affected application.

Do not remove an unrelated driver simply because the application mentions riched20.dll. If the error occurs only in one program, repair that program instead.

Hunting through multiple hardware vendors and guessing which driver is stale can be time-consuming. Outbyte Driver Updater can use its free scan to identify driver issues, while driver installation is handled by the full version; it is optional and does not replace repairing the affected application or Windows component.

Why regsvr32 is usually the wrong fix

regsvr32 registers DLLs that expose COM registration entry points such as DllRegisterServer. Microsoft documents it as a registry-registration utility (regsvr32).

Rich Edit is normally loaded as a Windows control, not repaired by registering it as a COM in-process server. Therefore, this is not a standard repair:

regsvr32 riched20.dll

Running it may produce an entry-point or registration error. That result does not show that the file is missing, and repeating the command will not repair Windows.

Use DISM and SFC for a damaged Windows copy. Use application repair or reinstallation for a private application copy.

If DISM and SFC report no corruption

When both tools report that Windows is healthy but the application still fails, narrow the problem:

1. Confirm scope: Test another application that uses rich text controls.
2. Identify ownership: Determine whether the failing executable is Office, an installer, an old game, or another third-party program.
3. Check the loaded path: Look for a private riched20.dll beside the application or inside its installation folders.
4. Repair the application: Use its launcher, installer, or Windows repair option.
5. Disable nonessential plug-ins: A plug-in can cause an application crash that names riched20.dll.
6. Test a new Windows user profile: If the program works there, the original profile or its permissions may be involved.
7. Check access: Confirm that the application can read its installation directory and temporary folders.
8. Update the application: An older build may expect exports or behavior from a different Rich Edit implementation.
9. Review the installer context: An MSI running under a different account or temporary directory may not see the same files as an interactive user.

For Windows Installer Error 2894, the official message is:

Error 2894. Loading RICHED20.DLL failed. GetLastError() returned: [number].

The trailing number can help an administrator investigate access, loading, or system-component conditions. It does not establish that a separate downloadable runtime is missing. Repair Windows first, then retry the installer from its original official media or package.

When to use System Restore or Windows recovery

If the problem started immediately after a Windows update, installer, cleanup utility, antivirus action, or other system change, System Restore may be appropriate.

To open System Restore:

1. Select Start.
2. Type Create a restore point.
3. Open the matching Control Panel result.
4. Select System Restore.
5. Choose a restore point from before the problem began.
6. Review the affected programs and drivers.
7. Confirm the restore.
8. Allow Windows to restart.

System Restore rolls back system files, registry settings, drivers, and installed programs while preserving personal files. Microsoft explains the process in System Restore.

Use recovery options progressively:

1. Windows Update and application repair
2. DISM and SFC
3. System Restore when a suitable restore point exists
4. Windows repair reinstall
5. Reset this PC as a more disruptive final option

Back up important files before major recovery work. Microsoft’s Recovery options in Windows explains the available choices.

Manual replacement is not a normal first step. Microsoft documents it as an advanced SFC recovery procedure using a known-good file from the same Windows version (repair missing or corrupted system files). Do not use a file downloaded from an unofficial DLL source.

Prevention

To reduce the chance of another riched20.dll failure:

• Keep Windows and the affected application updated.
• Use the application’s own repair or verify function before replacing files.
• Avoid cleanup utilities that delete unknown system or application files.
• Keep Microsoft Defender or another reputable security product active.
• Do not install DLL files from untrusted download pages.
• Keep installers and recovery media for important legacy applications.
• Record whether a program is 32-bit or 64-bit before troubleshooting its DLLs.
• Do not overwrite an application’s private DLL with a Windows system copy.
• Create restore points before major system changes when practical.

Frequently asked questions

Is riched20.dll part of Windows or Office?

It is normally a Microsoft Windows Rich Edit component. Office and other products may also ship private copies, so the file’s location determines which product should be repaired.

Should I reinstall Visual C++, DirectX, or .NET?

Usually no. Those runtimes are not the normal owner of the Windows Rich Edit 2.0 component. Repair Windows with DISM and SFC, or repair the application that reports the error.

Can I copy riched20.dll from another computer?

Not as a general fix. Windows build, architecture, servicing level, and ownership must match. Microsoft’s controlled manual replacement procedure uses a known-good file from the same Windows version and is an advanced recovery method, not ordinary troubleshooting.

Does a 64-bit Windows installation always use the System32 copy?

No. A 32-bit application generally uses the 32-bit system component in SysWOW64, while a 64-bit application generally uses the native component in System32.

Why does only one application fail?

That application may have a damaged private copy, an incompatible plug-in, incorrect permissions, or a defective installation. Repair or reinstall that application before changing Windows files.

What if the error says “not designed to run on Windows”?

Treat it as a compatibility, corruption, or wrong-copy problem. Run DISM and SFC if the path is a Windows directory. If the path belongs to an application, repair or reinstall that application.

Is regsvr32 riched20.dll required?

Usually no. Rich Edit is normally loaded as a control and is not repaired through COM registration. Use Windows servicing or application repair instead.

What is the safest source for riched20.dll?

For the Windows copy, use Windows Update, DISM, SFC, or Microsoft recovery procedures. For a private application copy, use the application’s official repair or installer. Do not use a random DLL download sites website.

When should I contact the application vendor?

Contact the vendor after Windows Update, DISM, and SFC report no unresolved corruption and the error remains limited to that product. Provide the exact message, executable name, file path, application version, architecture, and any installer or crash details.

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.