Recommended Free Tools
dui70.dll errors may appear as “The program can’t start because dui70.dll is missing from your computer” or “The code execution cannot proceed because dui70.dll was not found.” You may also see C:WindowsSystem32DUI70.dll is either not designed to run on Windows or it contains an error when Explorer, Task Manager, Settings, or another Windows interface fails.
dui70.dll is a genuine Microsoft Windows system component called the Windows DirectUI Engine. It normally belongs in a Windows system directory, not in a game folder or beside an unrelated application executable. The safest repair is to install pending Windows updates, then run DISM followed by System File Checker.
Which fix applies to you
Use the symptom that best matches what you see:
- A program or game reports that
dui70.dllis missing, but Windows itself works normally: repair Windows first, then reinstall the affected program if it is the only application showing the error. - Explorer, the Start menu, taskbar search, Settings, Task Manager, or Bluetooth controls crash: treat this as a Windows component or shell-extension problem. Run Windows Update, DISM, and SFC before replacing anything.
- The error started immediately after a Windows update, driver installation, customization tool, or system change: try System Restore or remove the recent change after checking for newer Windows updates.
- SFC and DISM complete successfully, but Explorer still crashes: test Safe Mode or a clean boot. A third-party shell extension, context-menu handler, graphics utility, or customization program may be the actual cause.
- You found
dui70.dllin a game, launcher, download, or application directory: do not automatically copy it intoSystem32. Check its signature and scan the file because a same-named DLL outside Windows directories can be a sideloading risk. - Windows Security quarantined the file: inspect Protection history before restoring it. Restore it only after verifying that it is a genuine Microsoft file and that the detection is demonstrably false.
What dui70.dll does
The file description is Windows DirectUI Engine, and its publisher is Microsoft Corporation. It is part of Microsoft Windows Operating System and supports native Windows user-interface components.
The correct copy depends on both the installed Windows build and the calling process:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches#1 Best Overall
- 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)
- A 64-bit Windows installation normally has a 64-bit system copy in
C:WindowsSystem32. - A 32-bit application on 64-bit Windows may use the 32-bit system environment, commonly represented by
C:WindowsSysWOW64. - A 32-bit Windows installation uses its own 32-bit system directory.
The names can be confusing: on 64-bit Windows, System32 contains 64-bit system files while SysWOW64 contains 32-bit system files. Do not copy a DLL between these locations based only on the filename.
Microsoft servicing file lists include dui70.dll in Windows 10 and Windows 11 update payloads. Historical file inventories also show versions from Windows 7, Windows 8, Windows 8.1, and older Windows 10 builds. Those versions are tied to particular Windows builds, architectures, and servicing states. A file that is newer, larger, or copied from another PC is not automatically the correct replacement.
Understand the error before repairing it
Different messages point to different situations.
“dui70.dll is missing” or “was not found”
This usually means that an application requested the DLL and Windows could not load a suitable copy. The file may genuinely be missing, damaged, quarantined, inaccessible, or incompatible with the application’s architecture.
If only one older application reports the message while Windows interfaces work normally, the application may have a damaged installation or an incorrect private DLL in its own directory. Repair or reinstall that application after repairing Windows.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →“The specified module could not be found”
This message does not always mean that dui70.dll itself is absent. Windows may have found the file but failed to load one of its dependencies. A damaged Windows component, incompatible architecture, blocked file, or bad application installation can produce the same result.
“Not designed to run on Windows” or “contains an error”
This generally indicates a corrupted, incompatible, unsigned, or wrong-architecture file. It can also appear when Windows loads a damaged copy from an unexpected location.
Do not solve this by downloading the newest-looking DLL. The replacement must match the installed Windows build and architecture, and Windows servicing should be allowed to restore it.
Explorer or another Windows process crashes in DUI70.dll
An Event Viewer entry might look like this:
Faulting application name: Explorer.EXE
Faulting module name: DUI70.dll
Exception code: 0xc0000005
Faulting module path: C:WindowsSYSTEM32DUI70.dll
The faulting module is the place where Windows detected the failure, not proof that the DLL is the original cause. Explorer can crash there because of corrupted Windows files, an incompatible shell extension, graphics software, a damaged update, or a bad dependency.
Fix 1: Install Windows updates first
Windows Update is the safest way to restore a missing or outdated Windows component because it obtains files intended for your edition, architecture, and build.
Windows 11
- Open Start and select Settings.
- Select Windows Update.
- Click Check for updates.
- Install every available update.
- Restart when Windows asks.
- Return to Windows Update and check again until no further updates are offered.
- Test the application or Windows interface that produced the error.
Windows 10
- Open Start and select Settings.
- Open Update & Security.
- Select Windows Update.
- Click Check for updates.
- Install the available updates and restart.
- Check again after restarting.
If the issue began immediately after an update, do not assume the update is permanently at fault. First install any newer pending updates. If the problem remains, use Settings > Windows Update > Update history to identify the recent change, then review Windows recovery options before uninstalling an update.
On supported Windows 11 installations, you may also see Settings > System > Recovery > Fix problems using Windows Update > Reinstall now. This reinstalls the current Windows version while preserving apps, files, and settings. Keep the computer connected to power and back up important files before beginning.
Fix 2: Repair Windows with DISM and SFC
Use an elevated Command Prompt. DISM repairs the Windows component store, which provides the source files that SFC uses to replace damaged protected files.
Rank #2
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
- Open Start.
- Type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Approve the User Account Control prompt.
- Run this command:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for DISM to finish. Do not close the window because the progress may pause for a while.
- When DISM completes, run:
sfc /scannow
- Wait until verification reaches 100 percent.
- Restart Windows.
- Test the affected application, Explorer, or Windows feature again.
Microsoft documents this DISM-before-SFC order because SFC needs a healthy repair source. The SFC result will usually say whether it found no integrity violations, repaired damaged files, or found corruption that it could not repair.
If SFC says it repaired files, restart and test again. If it says that some files could not be repaired, run DISM again, restart, and repeat SFC once. Do not keep running the same commands indefinitely if the result does not change.
If DISM cannot obtain repair files through Windows Update, Microsoft supports using a matching Windows installation source with /Source and /LimitAccess. The source must match the installed Windows edition, language, and architecture. Using an arbitrary ISO or a mismatched source can create another servicing problem.
When you are repeatedly hunting through repair commands and cannot tell what changed, Outbyte PC Repair can show detected system problems in a scan; its repair functions require the full version, while Microsoft DISM and SFC remain the appropriate built-in repair path.
Fix 3: Check whether the file is genuine and in the right location
Before copying or restoring anything, inspect the path.
- Press Ctrl + Shift + Esc to open Task Manager.
- Select Run new task from the Task Manager menu.
- Enter:
C:WindowsSystem32
- Press Enter.
- Search for
dui70.dll. - Right-click the file and select Properties.
- Open the Details tab and check for:
- File description: Windows DirectUI Engine
- Company: Microsoft Corporation
- Product: Microsoft Windows Operating System
- Open the Digital Signatures tab if it is present and inspect the signer.
A copy in C:WindowsSystem32 or the appropriate 32-bit Windows system environment is consistent with a Windows component. A copy in an application directory is not automatically malicious, but it deserves closer investigation.
Windows DLL search order can cause an application to load a same-named DLL from its own directory before the system directory. Microsoft documented a 2026 campaign that used a malicious unsigned DLL named dui70.dll beside a legitimate executable for DLL sideloading. If the file is in a download, game, launcher, temporary, or unfamiliar application folder, scan it and investigate its provenance before opening or copying it.
To scan a suspicious file or folder:
- Right-click the file or folder.
- Select Scan with Microsoft Defender if that option is available.
- Open Windows Security.
- Select Virus & threat protection.
- Choose Scan options.
- Run a Full scan.
Do not call every copy outside System32 malware solely because of its location. Check its path, publisher, digital signature, timestamp, hash, and the program that loaded it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Fix 4: Check Windows Security quarantine
Antivirus software can quarantine a legitimate file after a mistaken detection, or it can remove a malicious file that happened to use this name.
- Open Windows Security from the Start menu.
- Select Virus & threat protection.
- Select Protection history.
- Expand any event involving
dui70.dll. - Record the detected path and threat name.
- Compare the path with the expected Windows system location.
- Run a full Microsoft Defender scan.
Restore a quarantined file only when you have verified that it is a genuine Microsoft Windows file and the detection is clearly false. Restoring an unknown DLL can reintroduce malware, and Microsoft warns that a restored threat may be detected again.
If the file is genuinely missing from the Windows directory, use Windows Update, DISM, and SFC to restore it rather than downloading a replacement.
Fix 5: Test Safe Mode and third-party shell extensions
If Explorer crashes but DISM and SFC report a healthy system, a third-party component may be interacting with DirectUI.
Free tools Windows power users keep installed
One-click scans. No signup required.
Common suspects include:
- Context-menu handlers
- Explorer customization software
- Shell replacements
- System-tuning utilities
- Graphics overlays
- Window-management utilities
- Recently installed security or compression software
Test Safe Mode
- Open Settings.
- In Windows 11, select System > Recovery. In Windows 10, select Update & Security > Recovery.
- Under Advanced startup, select Restart now.
- Select Troubleshoot > Advanced options > Startup Settings.
- Select Restart.
- Press the key for Safe Mode.
If Explorer works in Safe Mode, the core Windows component may be intact and a startup service, driver, or shell extension is more likely to be involved. Remove or update recently installed customization and integration software, then restart normally.
Rank #3
- Does Not Fix Hardware Issues - Please Test Your PC hardware to be sure everything passes before buying this USB Windows 11 Software Recovery USB.
- Make sure your PC is set to the default UEFI Boot mode, in your BIOS Setup menu. Most all PC made after 2013 come with UEFI set up and enabled by Default
- Does Not Include A KEY CODE, LICENSE OR A COA. Use your Windows KEY to preform the REINSTALLATION option
- Free tech support
Perform a clean boot
- Press Windows + R.
- Type
msconfigand press Enter. - Open the Services tab.
- Select Hide all Microsoft services.
- Click Disable all.
- Open the Startup tab.
- Click Open Task Manager.
- Disable non-Microsoft startup items.
- Close Task Manager and click OK in System Configuration.
- Restart and test the failure.
If the problem disappears, re-enable services and startup items in groups until the failing component is identified. Restore normal startup after testing by opening msconfig, choosing Normal startup, and restarting.
Fix 6: Update graphics drivers when the crash is interface-related
A graphics driver is not a replacement for dui70.dll, but an Explorer or DirectUI crash can be triggered by graphics integration, overlays, or a damaged display driver.
Update through Device Manager
- Right-click Start.
- Select Device Manager.
- Expand Display adapters.
- Right-click the graphics adapter.
- Select Update driver.
- Choose Search automatically for drivers.
- Restart if Windows installs an update.
If the issue began immediately after a driver update:
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 match- Return to Device Manager > Display adapters.
- Right-click the adapter and choose Properties.
- Open the Driver tab.
- Select Roll Back Driver if available.
- Restart and test.
When manually checking a large hardware stack is the slow part, Outbyte Driver Updater can scan for outdated drivers; its driver installation requires the full version, and you should still review each proposed driver rather than treating it as necessary for every dui70.dll error.
Fix 7: Use System Restore or remove a recent change
System Restore is useful when the problem began after a driver, update, utility, or configuration change.
- Open Start and search for Create a restore point.
- Open the result.
- Select System Restore.
- Choose a restore point dated before the first
dui70.dllerror. - Select Next, review the affected programs, and choose Finish.
- Allow Windows to restart.
System Restore does not normally remove personal documents, but it can remove recently installed programs, drivers, and updates. Back up important data first.
If Windows cannot start normally, access Windows Recovery Environment through Troubleshoot > Advanced options and use System Restore or Safe Mode there.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Fix 8: Repair or reinstall the affected program
If only one application reports dui70.dll, and Windows interfaces work normally, the program’s installation may be damaged or it may contain an incompatible private dependency.
- Open Settings > Apps > Installed apps on Windows 11, or Settings > Apps > Apps & features on Windows 10.
- Select the affected application.
- Choose Advanced options if available.
- Try Repair, then Reset only if appropriate for that application.
- If no repair option exists, uninstall the program.
- Restart Windows.
- Install the program again from its official source.
Do not install a random copy of dui70.dll into the application folder. If the program specifically requires a private version, obtain it through that program’s official installer or vendor support.
Fix 9: Try a new Windows user profile
A damaged user profile or per-user shell integration can make Explorer fail for one account but work normally for another.
- Open Settings.
- Select Accounts > Other users.
- Choose Add account.
- Create a local test user or add another Microsoft account.
- Sign out of the current account.
- Sign in to the test account.
- Open Explorer and reproduce the problem.
If the error is limited to the original account, move personal files to a new profile after checking application settings and permissions. If every account has the same failure, continue with Windows repair rather than rebuilding only the profile.
Fix 10: Perform an in-place Windows repair
If Windows Update, DISM, SFC, Safe Mode, and recent-change recovery do not resolve the issue, perform an in-place repair using matching Windows installation media.
Use installation media that matches the installed Windows edition, language, and architecture.
Rank #4
- Video Link to instructions and Free support VIA Amazon
- Great Support fast responce
- 15 plus years of experiance
- Key is included
- Back up important files.
- Start Windows normally.
- Connect the installation media or mount the official Windows image.
- Run
setup.exefrom inside Windows. - Follow the setup prompts.
- Choose Keep personal files and apps when offered.
- Complete the repair and allow Windows to restart.
An in-place repair refreshes Windows system files while preserving supported applications, files, and settings. If Windows cannot boot, use Windows Recovery Environment first and back up files before considering a reset or clean installation.
Why downloading dui70.dll is usually the wrong fix
There is no legitimate standalone dui70.dll redistributable comparable to Visual C++, DirectX, or .NET. Random DLL download sites can provide:
- Malware or a malicious sideloading file
- The wrong 32-bit or 64-bit architecture
- A version from another Windows build
- A file with an invalid or missing signature
- A DLL that does not include the damaged dependency causing the error
Copying a DLL from another computer, an old Windows installation, or an application folder can also break servicing and create version mismatches. Let Windows Update, DISM, SFC, or an in-place repair restore the component.
regsvr32 is not a general DLL repair command. It invokes a DLL’s registration entry point, DllRegisterServer, and ordinary Windows runtime components are not repaired by registering them. Running commands such as the following against dui70.dll is therefore not an appropriate fix:
regsvr32 dui70.dll
What to record if the problem continues
Collect these details before asking for further help or examining crash logs:
- Windows edition, version, and build from
winver - The exact error text
- The full path shown for
dui70.dll - Whether the problem affects Explorer, Task Manager, Settings, or only one application
- Whether the issue started after an update, driver, utility, or antivirus event
- DISM and SFC results
- The Event Viewer faulting application and faulting module
- Whether Safe Mode or a clean boot changes the behavior
- Whether the file has a valid Microsoft digital signature
- Whether the affected process is 32-bit or 64-bit
To check Event Viewer:
- Press Windows + R.
- Type
eventvwr.mscand press Enter. - Open Windows Logs > Application.
- Find the error at the time of the crash.
- Record the faulting application, faulting module, exception code, and module path.
FAQ
Is dui70.dll a virus?
No. The legitimate file is a Microsoft Windows component named Windows DirectUI Engine. A file with the same name in an unfamiliar application directory may be legitimate, damaged, or malicious, so inspect its path and signature instead of judging by its name alone.
Free tools Windows power users keep installed
One-click scans. No signup required.
Should I copy dui70.dll into System32?
No. Copying a DLL manually can create architecture, version, signature, and servicing mismatches. Use Windows Update, DISM, SFC, or an in-place repair.
Is dui70.dll always the cause of an Explorer crash?
No. It may be the module where Windows detected the crash while a shell extension, graphics component, corrupted update, or dependency caused the underlying failure.
Do I need to install Visual C++, DirectX, or .NET?
The evidence identifies dui70.dll as a Windows component. Do not install a runtime package solely because this filename appears in an error. Repair Windows first, then repair the affected application if only that program fails.
Does regsvr32 fix this file?
Usually not. regsvr32 is for DLLs that provide a registration entry point. It is not a general-purpose repair method for Windows system components.
How do I know whether I have the 32-bit or 64-bit copy?
Check the Windows architecture and the process that is failing. A 32-bit application on 64-bit Windows may use the 32-bit system environment, while 64-bit applications use the 64-bit system environment. Let Windows servicing restore the correct copy instead of selecting one by file size.
When should I reinstall Windows?
Use an in-place repair when Windows Update, DISM, SFC, Safe Mode, clean boot testing, and recovery from a recent change have not fixed system-wide failures. Choose Keep personal files and apps, back up first, and use matching installation media.
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.
