sharedlibrary.dll errors usually come from a Microsoft Store or UWP application whose .NET Native framework dependency is missing, damaged, or incorrectly registered. Repair or reinstall the affected app and its Store dependencies instead of downloading a loose copy of sharedlibrary.dll.
What this file actually does
SharedLibrary.dll is associated with the Microsoft .NET Native Shared Framework. Packaged Windows applications use this framework when their package manifest declares it as a dependency. Microsoft describes these dependencies as framework packages supplied separately from the application itself:
Microsoft.NET.Native.Framework.1.3Microsoft.NET.Native.Framework.2.1Microsoft.NET.Native.Framework.2.2
The file normally belongs inside a protected package directory similar to:
C:Program FilesWindowsAppsMicrosoft.NET.Native.Framework.<version>_<package-version>_<architecture>__8wekyb3d8bbwe
It is not normally a standalone System32 or SysWOW64 DLL. It is also not the ordinary .NET Framework, the modern .NET runtime, or the Visual C++ Redistributable.
#1 Best Overall
The application that triggers the message may be Microsoft Store, Photos, Phone Link, Xbox, Sticky Notes, Your Phone, or another packaged application. A desktop program can also display a similarly worded message, but you must identify that program before choosing a repair method.
Causes and symptoms
| What you observe | Most likely cause | Best next action |
|---|---|---|
One Store app reports that sharedlibrary.dll is missing |
The app or its framework dependency is incomplete | Repair, reset, update, or reinstall that app |
| Several Store apps fail | Windows component-store damage or broken package registration | Run DISM, then SFC, and update Windows |
Event Viewer lists SharedLibrary.dll as the faulting module |
A crash occurred in the DLL, but the file is not necessarily missing | Check the app, related dependencies, and package health |
The message also mentions mrt100_app.dll |
A damaged .NET Native or UWP dependency chain | Reinstall the app and update Store frameworks |
| The problem started after security software activity | The file or package may have been quarantined | Check Protection history, then reinstall if needed |
| A manually copied Store app fails | Package identity, registration, licensing, or dependencies were not recreated | Reinstall from Microsoft Store or the original publisher |
| Only a conventional desktop program fails | Its own installation is more likely responsible | Use that program’s official installer or repair option |
The known file information commonly associated with this name includes a reported 64-bit version 2.1.26424.0 with a size of about 12.18 MB. Do not use that information to force every system to install that version. Public evidence also shows other framework versions, and the architecture attribution for that reported version is not independently confirmed.
Fix 1: Identify the application that is failing
Do not begin by searching for the DLL. First determine which executable requested it.
Check the error window
Note the application name, shortcut, window title, and the action that caused the error. If the message appears immediately after launching a Store application, repair that application first.
If the message appears during startup, look at:
- Settings → Apps → Startup
- Task Manager → Startup apps
- The notification area near the clock
- Any shortcut or scheduled task that launches at sign-in
Disable an unfamiliar startup entry temporarily, then restart and check whether the error returns. Do not disable Windows security components or entries you cannot identify without first checking their file location.
Check Event Viewer
Event Viewer can show whether this is a missing dependency or merely a crash in SharedLibrary.dll.
- Press Windows key + X.
- Select Event Viewer.
- Expand Windows Logs.
- Select Application.
- Choose Filter Current Log in the right pane.
- Filter for Error and inspect entries recorded at the time of the failure.
- Look for Faulting application name, Faulting module name, and any package or application name.
If SharedLibrary.dll is listed as the faulting module, that does not prove the DLL is absent. The package may be corrupted, the application may be incompatible, or another dependency may be causing the crash.
Check the installed app list
- Open Settings.
- Select Apps → Installed apps.
- Sort by name or installation date.
- Look for the application that was open when the error appeared.
- Select its three-dot menu and choose Advanced options, if available.
For older Windows 10 layouts, open Settings → Apps → Apps & features, select the application, and choose Advanced options.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsFix 2: Repair or reset the affected Store app
Repair is the safest first change because it attempts to correct the installation without removing the app’s data.
- Open Settings → Apps → Installed apps.
- Find the affected application.
- Select the three-dot menu.
- Choose Advanced options.
- Select Terminate if the option is shown.
- Select Repair.
- Start the application again.
If the error remains:
- Return to the same Advanced options page.
- Select Reset.
- Confirm the reset.
- Restart Windows.
- Open the application again.
Resetting can remove the application’s locally stored settings or sign-in data. It does not install a loose DLL. If the app contains unsynchronized local data, check its own backup or sync options before resetting.
If the application starts after Repair, the framework dependency or package registration was probably corrected. If it starts only after Reset, recreate any required settings and sign in again.
Fix 3: Update Windows and Microsoft Store apps
Framework packages are normally provisioned through Windows and Store package servicing. Bring both up to date before attempting advanced repairs.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchInstall Windows updates
- Open Settings.
- Select Windows Update.
- Choose Check for updates.
- Install all available updates.
- Restart when requested.
- Return to Windows Update and check again until no further normal updates are offered.
Update Microsoft Store applications
- Open Microsoft Store.
- Select Library.
- Choose Get updates.
- Allow Store apps and framework packages to finish updating.
- Restart Windows.
- Test the affected app.
If the app still fails, open Microsoft Store → Library, find the application, and select Install or Update if that option is available. Reinstalling from the same Store account restores the package dependency graph more reliably than copying files from another computer.
Microsoft’s guidance for Store app failures is available in its Store troubleshooting instructions.
Fix 4: Reinstall the application from its official source
Use this step when Repair and Reset do not restore the app.
- Open Settings → Apps → Installed apps.
- Find the affected application.
- Select the three-dot menu.
- Choose Uninstall.
- Restart Windows.
- Open Microsoft Store → Library.
- Locate the application.
- Select Install.
If the app is not supplied through Microsoft Store, download its installer from the application developer’s official website and install it again. For a packaged desktop application, use its official MSIX or AppX package if the publisher supplies one.
Do not copy the application directory from another PC. That usually does not recreate package identity, dependencies, licenses, or registration.
Fix 5: Repair Windows components with DISM and SFC
Use system repair commands when multiple Store applications fail, Windows Update is damaged, or package installation repeatedly breaks. Open an elevated Command Prompt:
- Press the Windows key.
- Type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Approve the User Account Control prompt.
Run these commands separately:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Wait for DISM to finish. It may use Windows Update as its repair source. Then run:
sfc /scannow
Wait until SFC reaches 100 percent. Restart Windows after both commands complete, then retry Windows Update and Microsoft Store.
DISM repairs the Windows component store, while SFC checks protected system files. Neither command guarantees that a damaged Store package will be recreated, so reinstall the affected app afterward if the error continues. Microsoft documents DISM image repair and System File Checker.
Repeating SFC and DISM without knowing which component changed can make troubleshooting slow. Outbyte PC Repair can scan for system issues and show what it identifies; its repair functions require the full version, and it is not required when reinstalling the affected application is the definitive fix.
Fix 6: Check the framework package and architecture
The framework package should normally be under:
C:Program FilesWindowsApps
The folder is protected, so do not take ownership of it or replace files manually. Changing permissions can interfere with Store servicing.
To inspect installed package names without modifying them:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Open PowerShell as administrator.
- Run:
Get-AppxPackage -AllUsers | Where-Object {
$_.Name -like "*Microsoft.NET.Native.Framework*" -or
$_.Name -like "*Microsoft.NET.Native.Runtime*"
} | Select-Object Name, Version, Architecture, PackageFullName
Look for Microsoft.NET.Native.Framework and Microsoft.NET.Native.Runtime. The output may show x86, x64, ARM64, or neutral/package-specific architecture information.
The application and dependency must be compatible. An x86 app may need an x86 framework package, while an x64 app normally needs x64. ARM64 systems may use ARM64 packages or compatible x64 emulation support. The required version must come from the app manifest, installed package list, or Event Viewer. The filename alone does not identify the correct framework version.
Rank #4
Other missing files, including mrt100_app.dll, Microsoft.VCLibs, msvcp140_app.dll, and vcruntime140_app.dll, can indicate a broader packaged dependency problem. Reinstall the application and update Store packages instead of installing individual DLLs.
Fix 7: Check antivirus quarantine
Security software can remove or quarantine a package file after an update or application change.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- Open Windows Security.
- Select Virus & threat protection.
- Choose Protection history.
- Review entries recorded when the error began.
- Expand a relevant detection and inspect its path and publisher.
Restore a quarantined file only when the original application and package are trusted and the file is digitally signed by Microsoft. If there is any doubt, leave it quarantined, run a scan, and reinstall the application from Microsoft Store or its official publisher.
Fix 8: Check drivers only when the symptoms indicate a graphics or hardware problem
A driver is not the normal home of SharedLibrary.dll, and updating a graphics driver will not replace a missing .NET Native framework package. Consider this path only if Event Viewer also reports display-driver resets, graphics crashes, or the Store app fails during video playback or rendering.
- Press Windows key + X.
- Select Device Manager.
- Expand Display adapters.
- Right-click the graphics device.
- Select Update driver → Search automatically for drivers.
- Restart Windows and test the application.
For a clean reinstall, download the driver from the computer or graphics-device manufacturer, or uninstall the device from Device Manager and restart so Windows can redetect it. Outbyte Driver Updater can scan for stale drivers and identify the versions it finds; driver installation through its full version is optional and is not a substitute for restoring the Store dependency.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Commands and fixes that usually do not apply
Do not download a loose DLL
Random DLL download sites may provide malware, an altered file, the wrong architecture, or a version that does not match the app manifest. Even a genuine-looking replacement may fail because packaged applications depend on package identity and registration.
Recommended Free Tools
There is no verified official Microsoft standalone download page for SharedLibrary.dll. Restore it through Microsoft Store, the application’s official MSIX/AppX package, Windows Update, or the package vendor’s installer.
Do not copy it into System32 or the app folder
Copying SharedLibrary.dll into C:WindowsSystem32, C:WindowsSysWOW64, or an unrelated application directory can create version conflicts and bypass package servicing.
Do not use regsvr32
regsvr32 is designed to register DLLs that provide registration routines such as DllRegisterServer. It is not a universal repair command, and it is generally inappropriate for a .NET Native framework DLL. Microsoft explains its purpose in the regsvr32 documentation.
Do not install unrelated runtimes first
Ordinary .NET Framework 3.5 or 4.x, modern .NET, and Visual C++ Redistributable do not substitute for Microsoft.NET.Native.Framework. Install those only when the affected application’s official requirements specifically call for them.
Free tools Windows power users keep installed
One-click scans. No signup required.
If every normal repair fails
Test the application under another Windows user account:
- Open Settings → Accounts → Other users.
- Select Add account.
- Create or sign in to another account.
- Install or launch the Store application there.
If it works in the second account, the original profile or Store cache may be damaged. Repair and reinstall the app before attempting profile changes.
If the problem began immediately after a failed update or package change, retry Windows Update after DISM and SFC. If an appropriate restore point exists, use Control Panel → Recovery → Open System Restore and select a point from before the failure.
As a last resort, perform an in-place Windows repair installation that retains files and applications. Back up important data first. This is appropriate when several packaged applications and Windows Update remain broken after package repair and system-component repair.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →FAQ
Is sharedlibrary.dll a Windows system file?
It is a Microsoft .NET Native Shared Framework file used by packaged applications, but it is not normally a standalone DLL in System32. Its usual location is inside a protected Microsoft.NET.Native.Framework package.
Which application uses it?
The error can come from different Store or UWP applications. Event Viewer, the error window, and the time of failure are the best ways to identify the application. Do not assume that every occurrence belongs to the same program or framework version.
Does a faulting-module entry mean the file is missing?
No. It means Windows recorded the DLL as the module associated with the crash. The file may be present while another dependency, package registration, or application component is damaged.
Will Visual C++ Redistributable fix it?
Usually not. SharedLibrary.dll belongs to the .NET Native framework dependency chain, not the ordinary Visual C++ runtime. Repair or reinstall the affected Store application first.
Should I install version 2.1.26424.0?
Not automatically. Multiple .NET Native framework versions exist, and the correct architecture and version must match the application’s package manifest. Do not choose a version based only on the DLL filename.
Can I run System File Checker until it restores the DLL?
SFC checks protected Windows system files, but it does not guarantee restoration of a damaged Store package. Use it for broader Windows corruption, then repair or reinstall the affected application and its framework dependencies.
Quick Recap
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.
