shfolder.dll: Trace the Broken App or Windows Component

The exact shfolder.dll errors

You may see one of these messages when starting an older application, game, installer, or Wine prefix:

The program can’t start because SHFOLDER.DLL is missing from your computer. Try reinstalling the program to fix the problem.

#	Preview	Product	Price
1		CORRSQ 30-in-1 Bootable USB Drive	$20.99	Buy on Amazon
2		5-in-1 Win Repair & Reinstall Bootable USB Flash Drive – Fix, Recover, or Reinstall Windows 11...	$24.99	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

Fatal Error — Failed to load library ‘SHFolder.dll’.

×

Quick wins for a faster PC:

Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →

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

C:WindowsSystem32SHFOLDER.DLL is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.

#1 Best Overall

CORRSQ 30-in-1 Bootable USB Drive

• 1. COMPATIBLE WITH WINDOWS 11, 10, 8.1 & 7 Designed for compatible 64-bit PCs and laptops that support USB booting. Works with Windows 11, Windows 10, Windows 8.1 and Windows 7 installation and recovery options.
• 2. INSTALL, REINSTALL & REPAIR Provides access to installation and recovery options for startup failures, boot errors, system crashes, failed updates, system repair and reinstallation. Results depend on the condition of the computer and the cause of the problem.
• 3. READY-TO-USE BOOTABLE USB Reusable installation and recovery media that helps eliminate the need to download large system files or create bootable media yourself. Insert the USB drive, open the computer’s boot menu and select the appropriate installation or recovery option.
• 4. HELP KEEP OLDER PCS USEFUL Refresh, reinstall or maintain a compatible older computer before deciding whether replacement is necessary. Suitable for home computers, office workstations, PC enthusiasts and technicians who regularly work with supported systems.
• 5. IMPORTANT COMPATIBILITY & LICENSE INFORMATION Supports compatible 64-bit computers with UEFI or Legacy BIOS USB booting. No Windows license, activation key or product key is included. Activation may require an existing digital license or a separately purchased valid product key. Back up important files before installation or repair.

$20.99

Buy on Amazon

The wording matters. “Missing” usually points to a missing, quarantined, or damaged file. “Not designed to run on Windows” or error 0xc000012f more often indicates corruption, a wrong-architecture file, an invalid replacement, or a damaged application package.

The 60-second answer

shfolder.dll is a genuine Microsoft Windows component called Shell Folder Service. It supports older programs that use the SHGetFolderPathA or SHGetFolderPathW functions to locate special folders such as the Desktop and My Documents. Microsoft describes it as a compatibility DLL associated historically with Windows 2000, Windows XP, and later Windows releases. On Windows XP and later, related functionality was also incorporated into Shell32.dll. See Microsoft’s SHFolder background and compatibility documentation.

Do not download a replacement from a random DLL website and do not begin with regsvr32. First determine whether every program fails or only one old program. If several applications fail, install pending Windows updates, then run DISM followed by SFC from an elevated Command Prompt:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

If only one application fails, repair or reinstall that application, or verify its files through the game launcher. That is often the correct fix rather than replacing a protected Windows file.

What causes a shfolder.dll failure

The likely cause depends on the scope and timing of the problem.

What you observe	Most likely direction
Several unrelated programs fail	Windows component corruption or malware
Only one old game or application fails	Damaged installation or compatibility problem
The error names System32shfolder.dll	Windows component, architecture, or signature issue
The error started after antivirus detection	Quarantine or false positive
The file exists but gives a bad-image error	Corruption, wrong architecture, or invalid replacement
A same-named file exists beside the application	DLL search-order or hijacking concern
The issue began after a system change	Update rollback, System Restore, or application repair

Before changing anything, record the exact error, the full path shown in it, and the name of the program that fails. Also note whether the issue began after a Windows update, antivirus action, disk cleanup, application removal, failed installation, or malware incident.

First check: Windows file or application file

Check the normal Windows locations

Open File Explorer and enter each path in the address bar:

%WINDIR%System32

Then search for:

shfolder.dll

On 64-bit Windows, also check:

%WINDIR%SysWOW64

Do not assume that SysWOW64 contains 64-bit files. Windows uses System32 for 64-bit system files and SysWOW64 for 32-bit system files on a 64-bit installation. WOW64 redirection normally presents the correct system environment to each application. Microsoft’s File System Redirector documentation explains this behavior.

The file being present does not prove that it is healthy. Right-click it, select Properties, open Digital Signatures, and inspect the signer. A normal protected Windows component should have a valid Microsoft signature. If the tab is absent, the signature is invalid, or the file is located in a temporary folder or an unexpected application directory, treat it cautiously.

Do not overwrite both System32 and SysWOW64. File versions and metadata vary by Windows release, servicing level, architecture, language, and service pack, so there is no universal version or file size that applies to every PC.

Check whether the program is 32-bit or 64-bit

The error may be caused by a mismatch between an old 32-bit application and an incorrect DLL replacement. The folder name alone is not enough to identify the required architecture.

Useful clues include:

• A program installed under C:Program Files (x86) is commonly 32-bit, though the folder is not absolute proof.
• A program installed under C:Program Files may be 64-bit, but some 32-bit installers use that location.
• The application’s documentation or vendor support page may state its architecture.
• A launcher may identify whether it is running a 32-bit or 64-bit executable.

If the application is old, assume its own installation may be the problem until Windows component repair shows otherwise.

Fix 1: Install updates, then repair Windows

Use this path when multiple programs fail, the message names a Windows directory, or the problem appeared after system damage.

Install pending updates

1. Open Start and select Settings.
2. On Windows 11, select Windows Update. On Windows 10, select Update & Security, then Windows Update.
3. Select Check for updates.
4. Install all available updates.
5. Restart the computer, even if Windows does not immediately require it.
6. Try the affected program again.

If the error remains, continue with DISM and SFC.

Run DISM as administrator

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for the operation to finish.
2. Leave the Command Prompt window open and run:

sfc /scannow

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

Microsoft recommends DISM before SFC because DISM repairs the Windows component source that SFC uses. The official procedure is documented in Microsoft’s System File Checker guidance.

Possible SFC results include:

• Windows Resource Protection did not find any integrity violations: Windows did not find protected-file corruption. Focus on the application, architecture, antivirus history, and compatibility.
• Windows Resource Protection found corrupt files and successfully repaired them: Restart and test the application.
• Windows Resource Protection found corrupt files but was unable to fix some of them: Run DISM again if necessary, restart, and repeat SFC. If it still cannot repair the component store, use a matching Windows installation source.
• The repair source could not be found: Windows Update may not be supplying the required files, or the component store may be too damaged for the default source.

For a matching installation source, Microsoft documents this form:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:RepairSourceWindows /LimitAccess

Replace C:RepairSourceWindows with a source that matches the installed Windows edition, release, language, and architecture. Do not use an arbitrary folder or another PC’s Windows directory.

Repeating DISM and SFC without knowing what changed can make troubleshooting slow and confusing. Outbyte PC Repair can scan for problems and show what needs attention, while repair actions are performed by the full version; it is optional, and Windows’ built-in repair remains the first choice for a protected system file.

How to confirm this fix worked

The repair succeeded if:

• The original application starts normally.
• The error no longer appears for multiple affected applications.
• SFC reports that it repaired corrupted files.
• The file is present in the expected Windows location and has a valid Microsoft signature.

If only one old program still fails after SFC reports a clean system, stop treating this as a Windows-wide DLL problem and repair that program.

Fix 2: Repair or reinstall the affected application

Use this path when one application or game fails while other programs work.

For a conventional desktop application

1. Open Settings.
2. Select Apps, then Installed apps on Windows 11. On Windows 10, select Apps, then Apps & features.
3. Select the affected application.
4. Choose Advanced options, if available.
5. Select Repair.
6. Start the application again.

If no repair option exists:

1. Open Control Panel.
2. Select Programs, then Programs and Features.
3. Select the application.
4. Choose Change, Repair, or Modify, if offered.
5. Complete the vendor’s repair process.
6. Restart Windows and test again.

If repair does not help, uninstall the program, restart, and reinstall it from the original vendor installer or the service where you legitimately obtained it. Back up saved games, settings, licenses, and custom data first. Do not assume that removing the application also removes every private DLL it placed in its installation folder.

For a game

Use the launcher’s built-in file repair function before changing Windows files. The label varies by launcher, but it is generally named Verify integrity, Verify files, Scan and repair, or Repair.

1. Open the game launcher.
2. Open your library.
3. Select the affected game.
4. Open its settings or manage menu.
5. Start the verification or repair process.
6. Wait for it to complete.
7. Restart the launcher.
8. Start the game again.

If verification reports missing or damaged files, let the launcher reacquire them. If the problem persists, reinstall the game from its original service. An unofficial repack or modified installer may contain an incompatible private copy of shfolder.dll; replacing a Windows file will not repair that package.

What success looks like

Application repair is the right result when:

• Other programs launch normally.
• SFC reports no protected-file corruption.
• The failing program starts after verification or reinstall.
• The error path points inside the program’s own folder rather than the Windows directory.

If SFC repairs Windows but the same application still fails, the application may be loading a private or wrong-version copy. Compare the path in the error with the files beside the program executable.

Fix 3: Check antivirus quarantine and scan for malware

An antivirus product may quarantine a file after a detection or false positive. Do not restore it automatically just because the application needs it.

Check Microsoft Defender Protection History

1. Open Start and select Windows Security.
2. Select Virus & threat protection.
3. Select Protection history.
4. Review recent detections.
5. Expand any item that identifies shfolder.dll.
6. Check the file path and detection details.
7. Restore it only when the file is confirmed to be a genuine Microsoft-signed Windows component and the detection has been established as a false positive.
8. If its location, signature, or origin is unclear, leave it quarantined.

Afterward, update security intelligence and run a scan:

1. Return to Virus & threat protection.
2. Select Protection updates, then Check for updates.
3. Select Scan options.
4. Run a Full scan.
5. If malware is suspected or the file keeps returning, use Microsoft Defender Offline as described in Microsoft’s Defender scanning guidance.

A same-named DLL in an application directory, download folder, or temporary folder may be an unauthorized replacement or DLL hijacking attempt. Do not repeatedly restore a file that antivirus removes. Investigate the detection and scan the system instead.

Fix 4: Resolve architecture and compatibility problems

A 32-bit program should use the 32-bit Windows system environment, while a 64-bit program should use the 64-bit environment. WOW64 normally handles this automatically, so manually copying files is more likely to make the situation worse.

Try these compatibility steps:

1. Right-click the program’s shortcut.
2. Select Properties.
3. Open the Compatibility tab.
4. Select Run this program in compatibility mode for.
5. Choose the oldest Windows version appropriate for the software’s documentation.
6. Select Apply, then OK.
7. Start the program.

If that does not help:

1. Return to the Compatibility tab.
2. Select Run compatibility troubleshooter.
3. Follow the prompts.
4. Test the recommended setting.
5. Keep it only if the program launches correctly.

Do not use compatibility mode as a substitute for Windows repair. If the error states that SHFOLDER.DLL is not designed to run on Windows, verify the file signature and application source before trying additional settings.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 5: Update a driver only when the timing points to one

A graphics, storage, or chipset driver is not a normal source of shfolder.dll, and updating a driver will not replace this Windows component. Consider this path only if the error began immediately after a driver or system software change, or if Device Manager shows a related device problem.

Check Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Look for a device with a yellow warning icon.
4. Expand the relevant category.
5. Right-click the device.
6. Select Properties and open the General tab.
7. Read the device status.
8. If a driver update is appropriate, right-click the device and select Update driver.
9. Choose Search automatically for drivers.
10. Restart Windows and test the application.

For a recently updated driver:

1. Right-click the device in Device Manager.
2. Select Properties.
3. Open the Driver tab.
4. Select Roll Back Driver, if available.
5. Restart and test again.

Driver packages should come from Windows Update or the hardware vendor. Guessing among old driver versions can take longer than diagnosing the actual change. Outbyte Driver Updater can scan and identify outdated drivers, while driver installation is handled by the full version; it is optional and is not a targeted replacement for shfolder.dll.

Fix 6: Use System Restore after a recent system change

System Restore is appropriate when the error began after an update, driver installation, cleanup utility, security change, or other software installation and a restore point exists from before the failure.

1. Open Start.
2. Type Create a restore point.
3. Open the matching result.
4. Select System Restore.
5. Choose Next.
6. Select a restore point dated before the error began.
7. Select Scan for affected programs to review likely changes.
8. Select Next, then Finish.
9. Allow Windows to restart.
10. Test the affected program.

System Restore rolls back system files, settings, and installed programs associated with the restore point. It does not remove personal files. Microsoft’s System Restore instructions explain the process.

If no suitable restore point exists, back up important data before considering Windows repair or reinstallation.

Why regsvr32 normally does not apply

regsvr32 is not a general DLL repair command. It calls exported registration entry points such as DllRegisterServer or DllInstall, which are used by DLLs designed for registration.

Known shfolder.dll builds expose the shell-folder APIs rather than the COM registration entry points required by regsvr32. Commands such as these are therefore inappropriate:

regsvr32 /u shfolder.dll
regsvr32 /i shfolder.dll

They may produce an entry-point error and do not restore a missing or corrupt Windows component. Microsoft’s regsvr32 command documentation describes what the command actually does.

Do not register shfolder.dll, unregister it, or run it from an unknown folder. Repair Windows with DISM and SFC, or repair the application that owns the failing copy.

Why Visual C++, DirectX, and .NET are not targeted fixes

shfolder.dll is a Microsoft Windows shell compatibility component, not a Visual C++ runtime, DirectX runtime, or .NET runtime file. Installing those packages may be correct for a separate error, but there is no current Microsoft Visual C++ Redistributable, DirectX, or .NET package specifically intended to restore this file.

The same applies to the historical Platform SDK ShFolder redistributable. It was intended for older Windows compatibility scenarios, not as a general repair package for Windows 10 or Windows 11.

Why downloading shfolder.dll is unsafe

Random DLL download sites can supply:

• A file modified to contain malware.
• A file for the wrong Windows release.
• A 32-bit file where a 64-bit file is required, or the reverse.
• A file with the wrong language, servicing level, or dependencies.
• A private application DLL that does not belong in a protected Windows directory.

Even a genuine file from the wrong source can hide the root cause, break Windows servicing, or create a DLL search-order security problem. Safe sources are Windows Update, DISM’s matching repair source, SFC’s protected component store, the original application vendor, or the legitimate game launcher. Manual copying is appropriate only in an exceptional controlled case, such as restoring a verified file from matching original installation media on an obsolete system.

When Windows repair or reinstallation is justified

Consider Windows repair when:

• DISM cannot repair the component store.
• SFC repeatedly reports unrepairable corruption.
• Multiple protected Windows components are failing.
• Malware has altered system files.
• There is no usable restore point.
• Windows Update and a matching repair source cannot restore system health.

Back up personal data first. Use Microsoft’s supported Windows repair or reinstallation options for the installed edition and architecture. Do not copy DLLs from another computer as a substitute for repairing Windows.

Frequently asked questions

Is shfolder.dll a Windows system file

Yes. It is a Microsoft component named Shell Folder Service, historically associated with Microsoft Windows 2000 and later Windows compatibility support. It is not a third-party runtime.

Should I copy shfolder.dll into System32

Normally, no. Let Windows repair its protected component files. On 64-bit Windows, System32 contains 64-bit system files and SysWOW64 contains 32-bit system files, so copying without confirming architecture can worsen the error.

Does shfolder.dll need to be registered

Normally, no. regsvr32 applies to DLLs that expose registration entry points. It is not a repair utility for this shell compatibility DLL.

What if the file exists but Windows says it is bad

Check its full path, Microsoft digital signature, and architecture. Then run DISM followed by SFC. If only one application fails, verify or reinstall that application because it may be loading a damaged private copy.

Should I restore the file from antivirus quarantine

Only after confirming that it is a genuine Microsoft-signed system file and the detection is a false positive. Otherwise leave it quarantined, update security intelligence, and run a full or offline scan.

Will reinstalling Visual C++, DirectX, or .NET fix it

There is no current package in those families specifically intended to restore shfolder.dll. Repair Windows or repair the application based on whether the failure is system-wide or limited to one program.

Why does only an old game fail

The game may have damaged files, an obsolete installer, a private DLL, or compatibility issues with the current Windows release. Verify the game files first, then reinstall it from its legitimate launcher or original media.

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.