drvstore.dll Is Missing: Safe Repairs for Windows Driver Errors

Start with this diagnostic checklist

Before replacing anything, note:

• Which program fails: Device Manager, Windows Update, a game, launcher, or another application.
• The exact message: For example, “drvstore.dll is missing,” “could not be loaded,” or “not designed to run on Windows.”
• The path shown: %windir%System32drvstore.dll, %windir%SysWOW64drvstore.dll, or a file inside an application folder.
• When the problem began: After Windows Update, a failed driver installation, antivirus detection, disk cleanup, a crash, or reinstalling an application.
• Your Windows architecture: Most current Windows installations are 64-bit, but 32-bit applications can use 32-bit system components through WOW64.

drvstore.dll is a genuine Microsoft Windows system file. If it is missing or corrupt, repair Windows first rather than downloading a replacement DLL.

What is drvstore.dll?

drvstore.dll is the Driver Store API, a Windows component published by Microsoft Corporation. It belongs to Microsoft Windows Operating System, not to Visual C++, DirectX, .NET, or a particular game.

Windows uses the Driver Store as a protected repository for trusted driver packages. Those packages may support graphics cards, audio devices, chipsets, printers, network adapters, storage controllers, and other hardware. Windows and driver-installation services use the Driver Store when staging, validating, and installing device drivers.

That is why an error involving drvstore.dll can appear while installing a graphics or audio driver, running Windows Update, or starting software that relies on a recently changed device driver. The DLL is related to driver management, but it is not itself your graphics driver, sound driver, or printer driver.

The normal native location on 64-bit Windows is:

%windir%System32drvstore.dll

On 64-bit Windows, 32-bit system components are normally handled through:

%windir%SysWOW64

These names are counterintuitive: System32 normally contains native 64-bit system files on 64-bit Windows, while SysWOW64 contains 32-bit system files. Do not copy the file from one directory to the other simply because the filename matches.

Microsoft services this file as part of Windows. Historical inventories show different versions and sizes across Windows releases, architectures, and servicing levels. Examples include 32-bit version 10.0.19041.1 at about 0.96 MB and 64-bit version 10.0.18362.1 at about 1.19 MB. These are identification examples, not a current version table for every Windows installation.

Messages you may see

Windows or an affected program may display messages such as:

• C:WINDOWSSYSTEM32drvstore.dll is either not designed to run on Windows or it contains an error.
• Error status 0xc0000020
• The program can't start because drvstore.dll is missing from your computer. Try reinstalling the program to fix this problem.
• drvstore.dll file cannot be loaded. Module was not found
• Runtime Error - drvstore.dll
• drvstore.dll is corrupted
• Error loading drvstore.dll

The wording helps identify the repair path.

A message naming %windir%System32drvstore.dll, especially with status 0xc0000020, points toward Windows component corruption or a failed servicing operation. Reports involving DevInst.exe, Windows Update, and suddenly missing graphics or audio drivers also fit this pattern.

A message naming a game or application directory needs more care. The program may be loading a private copy, or the error may be a generic application failure. Reinstalling that program can help when the file genuinely belongs to its installation, but it will not repair the Windows copy in System32.

A crash report that lists drvstore.dll is not automatically proof that the DLL caused the crash. Crash reports often list every module loaded into the process. Treat the file as the cause only when Windows reports it as missing or damaged, the path is suspicious, or servicing and integrity checks identify a problem.

Fix 1: Install Windows updates and restart

A pending or incomplete update can leave Windows components and driver packages out of sync. Start with the least disruptive repair.

Windows 11

1. Open Start > Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install all available updates.
5. Restart the computer, even if Windows does not insist on a restart.
6. Try the affected program or device again.

If Windows Update itself is failing, restart once and check again. A restart can complete a pending component operation.

Windows 10

1. Open Start > Settings.
2. Select Update & Security.
3. Select Windows Update.
4. Select Check for updates.
5. Install available updates.
6. Restart Windows and retest.

If the error began immediately after a particular update and remains after restarting, note the update history before moving to the recovery steps below. Do not repeatedly install and remove drivers before repairing a damaged Windows component store.

Fix 2: Repair Windows with DISM, then SFC

This is the main repair for a missing, corrupt, or incorrectly loaded copy of drvstore.dll. Use an elevated Command Prompt and run the commands in this order.

Run DISM

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

DISM.exe /Online /Cleanup-image /Restorehealth

1. Press Enter and wait for the operation to finish.

DISM repairs the Windows component store, which provides the source that System File Checker uses for protected system files. The command may appear to pause for a while. Do not close the window simply because the percentage does not change immediately.

Run System File Checker

When DISM finishes, run:

sfc /scannow

Press Enter and wait until verification reaches 100 percent. Then restart Windows and test the original operation again.

A successful result may say that Windows Resource Protection found no integrity violations. It may also say that corrupted files were found and repaired. Either result should be followed by a restart and a retest.

If SFC says it found corrupt files but could not repair some of them, run DISM again, restart, and repeat sfc /scannow. If the same problem returns, continue to the repair-source and recovery options rather than copying a DLL from another computer.

Microsoft’s documented System File Checker and DISM instructions explain this order and the available results.

Repeating DISM and SFC by hand can make it difficult to know which component changed and which driver remains outdated. Outbyte PC Repair provides a scan that shows detected system issues, while repair actions are handled by the full version; it is optional, and Microsoft’s built-in servicing commands remain the appropriate first repair.

If DISM cannot find repair files

DISM may report that the source files could not be found, particularly when Windows Update is damaged or unavailable. Do not point it at an arbitrary downloaded DLL.

Use matching Windows installation media and Microsoft’s documented /Source and /LimitAccess procedure. The source must correspond appropriately to the installed Windows edition, language, architecture, and servicing state. Microsoft describes the advanced process in its guidance for repairing missing or corrupted system files.

If you cannot provide a matching source, use the Windows repair-reinstall option described later in this guide.

Fix 3: Reinstall the affected device driver

Repairing drvstore.dll does not automatically repair a damaged graphics, audio, chipset, printer, or network driver. If the error began during a driver installation, or a device disappeared at the same time, repair the device package after running DISM and SFC.

1. Right-click Start.
2. Select Device Manager.
3. Expand the category containing the affected device.
4. Right-click the device.
5. Select Uninstall device.
6. If Windows offers a checkbox to remove the driver package, use it only when you are deliberately replacing a damaged or incorrect package and have a compatible replacement available.
7. Select Uninstall.
8. Restart Windows.
9. Open Device Manager again.
10. Select Action > Scan for hardware changes, if the device does not return automatically.
11. Install the driver through Windows Update or from the hardware manufacturer’s official support page.

Start with Windows Update where possible. If Windows Update does not provide a working driver, use the manufacturer’s support page for the exact device and Windows version. Avoid generic driver packages that do not identify the hardware precisely.

If the problem began immediately after a driver update, open the device’s Properties, select the Driver tab, and use Roll Back Driver when that option is available. If rollback is unavailable, uninstall the device, restart, and install a known-compatible driver.

Finding the correct driver manually can mean comparing hardware identifiers and sorting through old packages. Outbyte Driver Updater can scan for outdated drivers and show what needs attention, while driver installation is performed by the full version; it is optional, and Device Manager, Windows Update, or the hardware manufacturer remain valid manual routes.

Clean up only when a driver package is clearly damaged

Do not delete random files from System32, SysWOW64, or the Driver Store. The Driver Store is managed by Windows, and manually removing packages can make a device harder to reinstall.

If Device Manager repeatedly reports a failed installation, first record the device name and driver provider. Then use the manufacturer’s uninstall instructions or Windows’ supported device-removal process. Run DISM and SFC again if the failure affects several devices or Windows Update itself.

Fix 4: Check whether antivirus quarantined the file

Security software can quarantine a system file after a false detection, but restoring it without checking the file is unsafe.

For Microsoft Defender:

1. Open Start > Settings.
2. Select Privacy & security.
3. Select Windows Security.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review the detection details.
7. Confirm that the detected file is the expected Windows component and that its path is the normal Windows location.
8. Restore it only when its authenticity and location are clear.

Do not restore a file merely because its name is drvstore.dll. A file with that name inside a temporary folder, download directory, game folder, or user profile may be unrelated or malicious. Do not exclude the entire Windows directory to suppress an alert.

After a verified restoration, restart Windows and run DISM followed by SFC. Microsoft explains the available actions in its Protection History instructions.

If the file is outside the expected Windows location, run a complete security scan and investigate the application that loaded it. DLL search-order problems can cause a program to load an impostor before Windows reaches its legitimate system component.

Fix 5: Remove a failed update

If drvstore.dll began failing directly after a Windows update and DISM/SFC do not resolve it, Windows provides supported ways to remove the update.

From Windows 11 or Windows 10

1. Open Start > Settings.
2. Open Windows Update on Windows 11, or Update & Security > Windows Update on Windows 10.
3. Select Update history.
4. Choose Uninstall updates.
5. Select the recent update associated with the failure.
6. Select Uninstall and restart.

Microsoft documents this process in its guide to uninstalling a Windows update.

If Windows cannot boot normally, enter Windows Recovery Environment and select Troubleshoot > Advanced options > Uninstall Updates. Remove the latest quality update first unless you have a specific reason to choose another recovery option.

After Windows starts, repair the affected driver and run Windows Update again when a corrected update is available.

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

Fix 6: Use Windows 11’s repair reinstall

Windows 11 includes a repair-reinstall feature that reinstalls the current Windows version while preserving applications, files, and settings.

1. Open Start > Settings.
2. Select System > Recovery.
3. Find Fix problems using Windows Update.
4. Select Reinstall now.
5. Follow the on-screen instructions.
6. Keep the computer connected to power and connected to the internet.
7. Restart when Windows requests it.

This is particularly useful when Windows Update and component servicing are damaged but Windows still starts normally. Microsoft describes the feature in its repair-reinstall instructions.

The option is not present on every Windows configuration. If it is unavailable, use matching Windows installation media for an in-place repair installation.

Fix 7: Try System Restore

System Restore is appropriate when the failure began after a recent driver, application, or system change and a restore point predates the problem.

1. Press Windows key + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the error began.
4. Select Scan for affected programs if available.
5. Review the changes.
6. Select Finish and allow Windows to restart.

System Restore rolls back system files, drivers, and settings without normally removing personal files. It does not replace a backup, and it does not guarantee that a damaged disk or malware infection will be corrected. Microsoft’s recovery options guide explains when to use it.

Fix 8: Perform an in-place repair reinstall from media

Use an in-place repair reinstall when:

• DISM cannot repair the component store.
• SFC repeatedly reports unrepaired files.
• Windows Update remains broken.
• drvstore.dll becomes corrupt again after repair.
• Several Windows components are failing.

Use Windows installation media that matches the installed edition and architecture. Start Windows normally, open the media, run setup.exe, and choose the option to keep personal files and applications when offered. Follow Microsoft’s reinstall Windows with installation media instructions carefully.

Back up important files before starting. A clean installation is more disruptive and should be reserved for severe corruption, an infection, or a system that cannot be repaired while preserving the existing installation.

Do not download drvstore.dll from a DLL website

Downloading a standalone DLL from a random site is a poor repair for this problem because:

• The file may contain malware or be modified.
• Its version may not match your Windows build.
• Its architecture may be wrong.
• Copying it into a game folder can create DLL search-order problems.
• It may hide corruption in the component store.
• It does not repair the driver package or failed Windows update that caused the error.

The safe sources are Windows servicing, Windows Update, matching Microsoft installation media, and an in-place repair reinstall. Microsoft does document manual replacement of a protected system file as an advanced last resort, but that requires a known-good file from a matching Windows installation and review of SFC results. It is not the normal first step.

Do not copy drvstore.dll into an application directory. Do not copy a 64-bit file into a 32-bit location or a 32-bit file into a 64-bit location.

Do not use regsvr32 for this file

regsvr32 is intended for DLLs that expose registration entry points such as DllRegisterServer. It is used to register certain COM components in the Windows Registry.

drvstore.dll is a Windows Driver Store API component, not a normal self-registering COM control. Running:

regsvr32 drvstore.dll

does not repair it and may produce an entry-point error. Use DISM, SFC, Windows servicing, or the appropriate driver-reinstallation procedure instead. Microsoft documents the purpose of regsvr32 separately from system-file repair.

Installing Visual C++ Redistributable, DirectX, or .NET is also not the normal fix for a missing Windows Driver Store DLL. Those packages repair their own runtimes, not Windows’ protected drvstore.dll.

What if the error appears in a game?

First inspect the path in the message or crash report.

• If it names %windir%System32drvstore.dll, repair Windows with DISM and SFC.
• If it names %windir%SysWOW64drvstore.dll, preserve the 32-bit architecture and still use Windows servicing.
• If it names the game’s installation folder, use the launcher’s file-verification feature and reinstall the game if necessary.
• If a crash dump merely lists drvstore.dll among loaded modules, do not assume it caused the crash.

A launcher’s verify feature can restore game files, but it cannot repair Windows system files. Reinstalling a game also cannot repair %windir%System32drvstore.dll.

FAQ

Is drvstore.dll safe?

The genuine file is a Microsoft Windows component. Verify its location and digital signature before trusting a copy restored from quarantine. A file with the same name outside the normal Windows paths requires separate investigation.

Is drvstore.dll part of a graphics driver?

No. It is the Windows Driver Store API. Graphics, audio, chipset, printer, and other device drivers use Windows driver-management services, but drvstore.dll is not the vendor driver itself.

Should I install Visual C++ to fix it?

No. Visual C++ Redistributable repairs Microsoft C and C++ runtime components. It does not normally restore a missing or corrupt Windows Driver Store DLL.

Should I register drvstore.dll?

No. regsvr32 is not a supported repair for this file. Run DISM followed by SFC instead.

Why does a game crash report mention drvstore.dll?

The module may have been loaded by the game, launcher, graphics stack, or Windows services. A loaded-module listing alone does not prove causation. Check the exact error path and repair Windows or the game according to that path.

What if SFC repairs the file but the error returns?

Investigate the event that preceded the failure: a bad update, repeated driver-installation failure, antivirus quarantine, filesystem damage, malware, or a failing disk. Capture the exact path, status code, Windows build, Event Viewer details, and signature status. If corruption continues, use System Restore or an in-place repair reinstall rather than repeatedly copying individual DLL files.

When should I reinstall the device driver?

Do so when the affected device disappeared, Device Manager shows an error, the problem began during a driver installation, or graphics, audio, printing, or chipset functions failed at the same time. Repair Windows first when several devices or Windows Update are affected.

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.