Free tools Windows power users keep installed
One-click scans. No signup required.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
If Windows says microsoft.graph.dll is missing or was not found, restore the application or PowerShell dependency that needs it before changing Windows system files. Microsoft.Graph is distributed as a .NET package and as a PowerShell module, so downloading a loose DLL from an unofficial site is unsafe and often incompatible. If several unrelated Windows features are also failing, run Microsoft’s elevated DISM repair first and then sfc /scannow. The same general workflow applies to Windows 10 and Windows 11, although your build, edition and available repair source can affect the result.
What is microsoft.graph.dll and why is it missing?
microsoft.graph.dll is normally part of Microsoft Graph software used by an application or automation project. Microsoft’s official NuGet package describes Microsoft.Graph as the Microsoft Graph .NET Client Library targeting .NET Standard 2.0. Microsoft also distributes Microsoft.Graph as a PowerShell module. That distribution model makes this file more likely to be an application dependency than a Windows component that every PC should contain.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →The exact cause depends on the program that displayed the message. A program may have been incompletely installed, quarantined a file, lost a package during an update, or be looking for a different version, target framework or processor architecture. A PowerShell script may instead be missing the Microsoft.Graph module. The filename alone does not identify which of those situations applies.
Common messages
- “Microsoft.Graph.dll was not found.”
- “The application has failed to start because Microsoft.Graph.dll was not found.”
- “Microsoft.Graph.dll is missing from your computer.”
- A PowerShell command reports that Microsoft.Graph commands or the module cannot be loaded.
These messages do not prove that Windows itself is infected or that a system-wide repair is required. First determine whether one application is affected or whether unrelated Windows functions are failing too.
Popular on Amazon
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]
Which repair path should you use?
Use the narrowest official repair source that matches the scope of the problem. Restoring one package is safer and faster than servicing all protected Windows components.
| What you observe | Most likely scope | First action | Risk and trade-off |
|---|---|---|---|
| Only one installed program fails | That program’s files or dependency set | Use the program’s official repair or reinstall option, or its package manager | Usually limited to one application |
| Your .NET project fails after restore or deployment | NuGet dependency, lock file, target framework or architecture mismatch | Restore the Microsoft.Graph package at the project’s required version | Requires project files and package-manager access |
| PowerShell cannot import Microsoft.Graph | Missing or damaged PowerShell module, or an unsupported PowerShell version | Install the Microsoft.Graph module from PowerShell Gallery | Repository policy and permissions can block installation |
| Several Windows features or unrelated programs fail | Possible Windows component corruption | Run DISM, then SFC, in an elevated Command Prompt | Changes protected Windows components and can take time |
| DISM cannot obtain repair files | Windows Update is not a usable source | Provide an official Windows installation source with /Source |
The source must match the installed Windows edition and servicing context closely enough to repair it |
How do I check whether one app or all of Windows is affected?
- Write down the exact program, script or scheduled task that shows the error. Note whether it fails immediately at launch or only when a Microsoft Graph feature is used.
- Try another unrelated application. If only the same vendor’s program fails, stay on the application-dependency path.
- If the message appears in PowerShell, record the command and the PowerShell version. A module problem is handled differently from a graphical application’s missing file.
- Check whether Windows Update, Settings, File Explorer and other unrelated programs work normally. Multiple unrelated failures justify the DISM/SFC path.
- Do not delete a different copy of the DLL from another program’s folder. A copy can have the wrong version, target framework or architecture and create a new loading error.
How do I restore Microsoft.Graph for a .NET application?
Restore the package through the project’s normal package manager, using the version required by the project’s dependency file. The NuGet page displayed version 6.9.0 at the time of the documented check, but package metadata changes; do not replace a locked or tested version merely because a newer version is shown online.
Using the .NET CLI
- Open a terminal in the directory that contains the affected project file.
- Run
dotnet add package Microsoft.Graph --version 6.9.0only when that is the version your project expects. Otherwise specify the version recorded in the project, lock file or vendor instructions. - Run the project’s normal restore and build commands. Confirm that the package appears in the resolved dependency list and that the output directory contains the assemblies produced by the build.
- Start the application again. If it is a vendor-supplied program rather than your own project, use the vendor’s repair or reinstall process instead of editing its package files manually.
Using Visual Studio Package Manager Console
In Visual Studio, open Tools > NuGet Package Manager > Package Manager Console and use the documented form Install-Package Microsoft.Graph -Version 6.9.0 when that version matches the project. Select the correct default project in the console before running the command. A package installed into a different project will not repair the application that is failing.
Using PackageReference
Projects that manage dependencies in the project file can add a PackageReference for Microsoft.Graph at the required version, then restore and rebuild. Keep the project’s existing target framework and architecture settings. The package page identifies .NET Standard 2.0 as the library target; that does not by itself guarantee compatibility with every application runtime or native dependency around it.
Also popular on Amazon
- Large Data Storage Capacity: Flash Drive with 128GB capacity, meet your needs of daily use on work, school, home and travelling for photos, music, videos, files storage and transfer
- Easy to use: The thumb drive is plug and play without any software installation; Supports Windows 7/8/10 / Vista / XP / Unix / 2000 / ME / NT Linux and Mac OS, also compatible with USB 2.0 and 1.1 ports; Storage is fast, safe and stable
- Wide Compatibility: USB flash drive support TV, desktop, notebook computer, car, audio and other device; It is your great data storage and transfer companion with traveling and working
- Retractable Desgin: The usb drive's retractable design can effectively protect the USB interface; The capless design can avoid losing of cap; Weight: 7g, Size: 2.6 × 0.8 × 0.4 inch. Portable to take your digital world anywhere
- What You Get: 1 x 128GB USB Flash Drive Thumb Drive, All of usb drives have been rigorously tested and formatted before leaving the factory; The default format of the USB stick is exFAT
If the error appears after deployment
- Compare the deployed folder with the files produced by a clean local build.
- Check that the publish process did not omit managed dependencies.
- Verify that the application is loading the intended build and not an older copy from another directory.
- Recreate the deployment from the project’s package restore rather than copying a DLL from a different machine.
How do I restore Microsoft.Graph for PowerShell?
Microsoft Graph PowerShell is delivered as a module, not as a loose DLL that should be copied into a system folder. The PowerShell Gallery page displayed Microsoft.Graph version 2.41.2 and listed PowerShell 5.1 as the minimum at the time of the documented check. Confirm your environment and repository policy before installing.
- Open PowerShell using an account permitted to install modules. If your organization controls repositories or execution policy, follow that policy first.
- Run
Install-Module -Name Microsoft.Graph. If prompted about an untrusted repository, stop and verify that the configured repository is the official PowerShell Gallery endpoint approved for your environment. - Close and reopen PowerShell, then test the module import or the Graph command that previously failed.
- If multiple versions are installed, inspect the available module versions and select the one required by the script. Do not remove a working version until you know which scripts depend on it.
Installing the module does not repair a separate graphical application that bundled its own Microsoft.Graph assembly. For that situation, repair the application or restore its project package instead.
How do I repair an installed application that reports the DLL error?
- Use the application’s built-in Repair option if it has one. On Windows, the option may be available under Settings > Apps > Installed apps, the application’s installer, or the application’s own maintenance tool.
- If repair is unavailable, uninstall and reinstall the program from its official vendor channel. Back up settings, saved data and license information first.
- Temporarily check your security software’s quarantine history. If it removed a file, do not restore it blindly; verify the application’s installer and publisher, then reinstall from the official source.
- Restart Windows and launch the program before adding plug-ins or copying custom files back. This isolates the original dependency from an extension that may be loading an incompatible assembly.
Never solve the error by downloading a standalone Microsoft.Graph.dll from a DLL index or file-sharing site. Such a file can be tampered with or built for a different version, architecture, target framework or dependency set. It can also leave the application with a mixture of files that the vendor never tested together.
When should I run DISM and SFC?
Use Windows servicing commands when the problem is broader than one application or when Windows reports missing or corrupted protected files. Microsoft’s documented order is DISM first and SFC second. Running SFC before DISM can leave it without a healthy component source from which to repair files.
Also popular on Amazon
- What You Get - 2 pack 64GB genuine USB 2.0 flash drives, 12-month warranty and lifetime friendly customer service
- Great for All Ages and Purposes – the thumb drives are suitable for storing digital data for school, business or daily usage. Apply to data storage of music, photos, movies and other files
- Easy to Use - Plug and play USB memory stick, no need to install any software. Support Windows 7 / 8 / 10 / Vista / XP / Unix / 2000 / ME / NT Linux and Mac OS, compatible with USB 2.0 and 1.1 ports
- Convenient Design - 360°metal swivel cap with matt surface and ring designed zip drive can protect USB connector, avoid to leave your fingerprint and easily attach to your key chain to avoid from losing and for easy carrying
- Brand Yourself - Brand the flash drive with your company's name and provide company's overview, policies, etc. to the newly joined employees or your customers
Run DISM from an elevated Command Prompt
- Save your work and open Command Prompt with administrator rights. Search for “Command Prompt,” right-click it and choose Run as administrator.
- Run
DISM.exe /Online /Cleanup-image /Restorehealth. - Wait for the operation to finish. Do not close the window merely because progress appears to pause; servicing can take a substantial amount of time.
- Restart Windows if DISM requests it, then reopen an elevated Command Prompt.
DISM repairs the Windows component store that supplies protected system files. It is not a replacement for restoring an application’s NuGet package or PowerShell module, so a successful DISM run may not change a program-specific Microsoft.Graph error.
Run System File Checker after DISM
- In the same elevated Command Prompt, run
sfc /scannow. - Wait until verification reaches 100 percent. Interrupting the scan can prevent repairs from being committed.
- Read the final result. Microsoft documents outcomes including no integrity violations, successful repairs, and files that SFC could not repair.
- Restart Windows and retest the original program or feature.
Microsoft describes the command this way: “The sfc /scannow command will scan all protected system files and replace corrupted files with a cached copy.” That cached-copy mechanism applies to protected Windows files; it does not recreate every third-party application dependency.
What if DISM says the source files could not be found?
When Windows Update cannot provide repair files, Microsoft documents using an explicit alternate source with the DISM /Source option and, when appropriate, /LimitAccess. An official Windows installation running on the PC, an approved network share or removable installation media can provide that source.
- Obtain installation media that corresponds as closely as possible to the installed Windows version, edition and language. Use Microsoft’s official media-creation or installation process rather than an unofficial image.
- Connect the media and note its drive letter in File Explorer. A USB flash drive for Windows installation media can carry the official files; it does not contain or replace
Microsoft.Graph.dll. - Identify the correct Windows image file and edition index supplied by that media. If you are unsure which image applies, stop rather than guessing.
- Run DISM with an explicit source, for example
DISM.exe /Online /Cleanup-image /Restorehealth /Source:X:sourcesinstall.wim:1 /LimitAccess, replacingX:and the image index with the values that match your media and installed edition. - After DISM completes, run
sfc /scannowagain and review its result.
Source syntax and image contents vary between Windows media. If the command rejects the source, verify the drive letter, image type and edition instead of repeatedly running a mismatched command.
Also popular on Amazon
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9+; Software download required for Mac, visit the SanDisk SecureAccess support page]
What should I do if the error remains after package and Windows repair?
- Record the application name, version, Windows edition and the complete error text.
- Check the application vendor’s release notes for a known Microsoft Graph dependency change or a required runtime.
- Confirm that the application and its dependencies use the same processor architecture where required. A 32-bit process cannot load every 64-bit assembly arrangement, and a package built for a different runtime may fail even when the filename is correct.
- Create a clean test profile or use the vendor’s documented diagnostic mode to rule out a damaged user configuration.
- Back up personal files before using Windows recovery or installation options. Recovery operations can remove applications or settings.
- If command-line servicing or recovery media is outside your comfort level, use an authorized Windows repair professional and provide the records you collected.
Which mistakes make this error harder to fix?
- Copying a DLL from a download site: this bypasses version and integrity checks and can introduce unrelated malware or loader errors.
- Running SFC first: Microsoft’s sequence places DISM before SFC when component corruption is suspected.
- Installing the newest package automatically: the affected project may require an older, locked version.
- Installing the PowerShell module into the wrong scope: a module available to one account or host may not be visible to another.
- Ignoring architecture and target framework: a matching filename is not proof of binary compatibility.
- Using mismatched repair media: an image for another edition or build may not provide suitable component files.
- Repeating repairs without reading the result: DISM and SFC each report whether they repaired files or still found corruption; those messages determine the next step.
Does this procedure work on both Windows 10 and Windows 11?
Yes. Microsoft’s System File Checker guidance lists both Windows 10 and Windows 11 in its applicability information, and the DISM-then-SFC commands are relevant to both. Exact build, edition, servicing policy, administrator permissions and repair-source availability can change the prompts and outcome. The application and PowerShell package steps are independent of the Windows-wide repair commands and should still be matched to the affected software.
After trying the manual steps, Outbyte PC Repair is an optional shortcut for more than 100 common Windows issues, including broken system elements and app-crash troubleshooting. It offers a category-based free trial of at least two days before subscription; it complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
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 errorsFrequently Asked Questions
Can I download Microsoft.Graph.dll directly from Microsoft?
Microsoft distributes the library through the Microsoft.Graph NuGet package and the Graph PowerShell module, rather than as a general-purpose Windows download. Restore the package or module through the channel used by the affected software so its related dependencies and version constraints are preserved.
Why does the error appear only when a script runs?
A script can load the Microsoft.Graph PowerShell module only when the module is installed, discoverable in that session and compatible with the host’s PowerShell version. Check the module installation scope and start a new PowerShell session after installing it.
Will reinstalling Windows always fix this DLL message?
No. A reinstall can repair Windows components but will not automatically restore a project’s locked NuGet dependency or a vendor application’s private files. Reinstalling Windows is a last-resort recovery choice after backups and narrower repairs.
How can I tell whether a security program removed the file?
Review the security product’s quarantine and protection history for the affected application and timestamp. Do not whitelist or restore a file solely because its name matches; reinstall the application from its official source and verify the publisher first.
Recommended Free Tools
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.
