How to fix cdp.dll error in Windows?
Prefer to fix it yourself? The manual steps follow.
- 7methods
- 20 minutes to 2 hours
- Easy to medium
Applies to Windows 11 and Windows 10: the Bad Image window naming C:\Windows\System32\cdp.dll, from Win32Bridge.Server.exe, ArmouryCrate.AppServiceBridge.exe or another program
7 methods in this guide
Hi, I was wondering if you could help me with an issue I'm having. I keep getting a pop-up that says, "C:\Windows\System32\cdp.dll is either not designed to run on Windows or it contains an error" and it is rather frustrating. Could you give any tips on removing this? Thanks.
cdp.dll is a Windows file in C:\Windows\System32, not part of any app. When a Bad Image window says it "is either not designed to run on Windows or it contains an error" with Error status 0xc000012f, Windows found the file but could not load it. Most often the copy is damaged, often after an interrupted update: repair Windows files with DISM and SFC first.
cdp.dll belongs to Windows, so the fix is to repair Windows, not the app in the window title. Run DISM and then SFC as administrator (Fix 1) and restart. If the window appeared the morning after an update, let Windows Update finish and restart twice (Fix 2), or remove the newest update (Fix 3). Never download cdp.dll from a DLL site.
| Error | "C:\Windows\System32\cdp.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. Error status 0xc000012f." |
|---|---|
| Where it appears | In a window titled <program>.exe - Bad Image, usually at sign-in. Reported titles: Win32Bridge.Server.exe (a Windows process) and ArmouryCrate.AppServiceBridge.exe (ASUS Armoury Crate). |
| Main cause | The Windows copy of cdp.dll is damaged or does not match the rest of the system, often after an update that was cut short. Less often one program loads it badly. |
| Fastest fix | Run DISM and SFC as administrator and restart (Fix 1). Then finish all pending Windows updates (Fix 2). |
| Also written as | cdp.dll error, cdp.dll bad image, cdp.dll 0xc000012f, cdp.dll is either not designed to run on Windows, and with typos such as cpd.dll or "Sysyem32". |
| What the file is | A Windows system file in C:\Windows\System32. Its name and the programs that load it point to the Connected Devices Platform, which Microsoft runs as the CDPSvc and CDPUserSvc services. |
| Status code | 0xc000012f: the file Windows tried to load is not a valid program file. Our general Bad Image guide lists the other codes. |
| Affects | Windows 11 and Windows 10. Windows 10 left support on 14 October 2025. |
| Vendor status | Not a documented Microsoft issue with one patch. Users reported it after Windows updates (Microsoft Q&A, 2023) and in ASUS's Armoury Crate 3.3.7 thread (2021). |
| Time to fix | 20 to 30 minutes for DISM and SFC. Up to an hour for updates. 1 to 2 hours for a repair install. |
Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.
What cdp.dll is and why a program needs it
cdp.dll ships with Windows and lives in C:\Windows\System32. CDP stands for Connected Devices Platform, the part of Windows that Microsoft describes as "used for Connected Devices" scenarios, run by the CDPSvc service and the per-user CDPUserSvc service. We could not find a Microsoft page that documents cdp.dll by name, so read the facts below as what the file and its errors show.
- File
cdp.dll- Location
C:\Windows\System32(the path in every reported window)- Belongs to
- Windows itself. Programs that use connected device features load it, Windows processes and third-party apps alike.
- Related services
- Connected Devices Platform Service (
CDPSvc) and Connected Devices Platform User Service (CDPUserSvc), both set to start automatically - Who reported the window
- Win32Bridge.Server.exe after a Windows update, with a Razer Synapse error at the same time; ArmouryCrate.AppServiceBridge.exe from ASUS Armoury Crate
- Open File Explorer and go to
C:\Windows\System32. - Find cdp.dll, right-click it and select Properties.
- On the General tab, check Size. A file of 0 bytes is empty and certainly damaged.
- On the Details tab, check that Copyright names Microsoft Corporation and Product name reads Microsoft Windows Operating System.
The only right copy is the one Windows installs and repairs for your exact build. A single file from a download site can be the wrong version, unsigned or infected, and a mismatched copy is one way to get the same Bad Image window again. Let DISM and SFC put back the original (Fix 1).
What the cdp.dll Bad Image error means
The window is a standard Windows Bad Image message. The program in the title tried to load cdp.dll, Windows opened the file, and the content was not a valid program file. The text tells you to reinstall the program, but here that rarely helps: the broken file belongs to Windows.
The message, as users quoted it on Microsoft Q&A and the ASUS forum
Win32Bridge.Server.exe - Bad Image
C:\Windows\System32\cdp.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.
Error status 0xc000012f.
| Part of the window | What it tells you |
|---|---|
| Title: Win32Bridge.Server.exe - Bad Image | A Windows process tripped on the file. Expect other problems too: the asker on Microsoft Q&A could not use Start, Search or Settings. |
| Title: ArmouryCrate.AppServiceBridge.exe - Bad Image | An ASUS app tripped on the file at startup. The Windows copy is still the suspect, but the app can be updated too. |
Path: C:\Windows\System32\cdp.dll | The file is in the Windows folder, so Windows tools repair it. A cdp.dll anywhere else deserves a malware scan. |
| Error status 0xc000012f | The loaded file is not a valid program image: damaged, cut short or the wrong file. |

What causes the cdp.dll error, from most to least common
Most often the Windows copy of cdp.dll is damaged or out of step with the rest of Windows, typically after an update that did not finish. Less often one program fails while loading it. Rarely Windows is damaged beyond what SFC can repair, or the disk itself is failing.
| Cause | How often | How to tell | Fix |
|---|---|---|---|
| Damaged Windows system files, cdp.dll among them | Most often | Bad Image at sign-in, sometimes several windows at once | Fix 1 |
| A Windows update that was cut short or only half installed | Often | Started the morning after "Update and shut down"; Start, Search or Settings fail | Fix 2, Fix 3 |
| A third-party startup app that loads cdp.dll | Sometimes | Only one app in the title, such as ArmouryCrate.AppServiceBridge.exe | Fix 4, Fix 5 |
| A driver or app change shortly before | Sometimes | You know the day it started | Fix 6 |
| Windows damaged beyond SFC, or a failing disk | Rarely | SFC says it could not repair some files, or errors return after a repair | Fix 7, then hardware checks below |
- Why a Windows process can break apps too. In the Microsoft Q&A case, Razer Synapse failed first, then the Win32Bridge.Server.exe window appeared, and Start, Search and Settings stopped working. One damaged system file can break many things at once.
- Why the message's advice misleads. "Try installing the program again" refers to the program in the title. Reinstalling Armoury Crate or Razer Synapse does not replace a Windows file in System32.
How to fix the cdp.dll error in Windows
Start with Fix 1: it repairs the file itself and helps most readers. Fix 2 and Fix 3 are for a window that started right after an update. Fix 4 is for a single third-party app in the title. Fix 5 to Fix 7 are for a window that survives all of that.
| What you see or what your PC has | Start with |
|---|---|
Bad Image naming C:\Windows\System32\cdp.dll, any title | Fix 1 |
| It started the morning after "Update and shut down"; Start, Search or Settings do not open | Fix 1, then Fix 2 |
| Fix 2 found nothing to install, and the window began with the last update | Fix 3 |
| Only one app in the title, such as ArmouryCrate.AppServiceBridge.exe | Fix 4 |
| Unclear title, or several apps at sign-in | Fix 5 |
| A restore point exists from before the window started | Fix 6 |
| SFC says it could not repair some files | Fix 7 |
Fix 1. Repair cdp.dll and other Windows files with DISM and SFC
20 to 30 minutesNo riskAnyone with the Bad Image window naming C:\Windows\System32\cdp.dll. Start here.
cdp.dll is a protected Windows file. DISM first repairs the store that Windows keeps clean copies in, then SFC replaces a damaged cdp.dll from that store with the right version for your build.
If Start or Search does not open, start Command Prompt another way: press Ctrl + Shift + Esc, select Run new task, type cmd, tick Create this task with administrative privileges and select OK.
- Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

Search for cmd and choose Run as administrator. Screenshot: Windows 11 26H2. - Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.
DISM.exe /Online /Cleanup-Image /RestoreHealth
DISM /RestoreHealth running. Screenshot: Windows 11 26H2. - Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.
sfc /scannow
sfc /scannow at 100%. Screenshot: Windows 11 26H2. - Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

The result line tells you what SFC did. Screenshot: Windows 11 26H2.
These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files
Run DISM first, then SFC, then restart. SFC alone can fail if the component store is damaged too. Restart even if SFC found nothing, because a file in use is replaced at the next start.
It worked if: SFC reports no integrity violations or that it repaired files, and the next sign-in shows no Bad Image window.
If not: If the window stays and an update is waiting, go to Fix 2. If SFC could not repair some files, go to Fix 7.
Fix 2. Finish pending Windows updates and restart twice
20 to 60 minutesLow riskThe window started after an update, especially after "Update and shut down", or Windows Update shows a restart or a download waiting.
An update replaces many system files over more than one restart. If it stopped halfway, cdp.dll can be from one build and the files that load it from another. Finishing the update brings them back in step.
- Press Win + I to open Settings. If Settings does not open, run Fix 1 first.
- Open Windows Update (Windows 11) or Update & Security > Windows Update (Windows 10).
- Select Check for updates and let everything download and install, optional updates included.
- Select Restart now, sign in, and restart once more.
- Check that Windows Update shows You're up to date.

If updates fail with an error, reset the update components: Reset Windows Update components
It worked if: Windows Update says you are up to date, and two restarts later no Bad Image window shows.
If not: If there was nothing to install and the window began with the last update, remove that update with Fix 3.
Fix 3. Uninstall the newest Windows update
15 to 20 minutesLow riskThe window started right after an update, and Fix 1 and Fix 2 did not help.
If the update itself left a bad cdp.dll or a mismatched caller, removing it puts back the previous files. Users have reported the error right after an update; we found no Microsoft notice naming one update as the cause.
- Open Windows Update. Select Start > Settings > Windows Update.
- Open the update history. Under More options, select Update history. Note the KB number and the date of the update you suspect.
- Open the list of removable updates. Scroll down to Related settings and select Uninstall updates.

Uninstall updates is under Related settings. Screenshot: Windows 11 26H2. - Uninstall the update. Find the update in the list and select Uninstall next to it. If the update is not in the list, Windows does not allow it to be removed this way.

Each removable update has its own Uninstall link. Screenshot: Windows 11 26H2. - Pause updates. Go back to Settings > Windows Update and select Pick a date on the Pause updates control. If your PC shows a list there instead, select the pause length you prefer. Without a pause Windows downloads the same update again.
These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to uninstall a Windows update

Windows Update will offer the update again. If the window returns after it reinstalls, Fix 1 and Fix 7 are the way forward, not removing it again.
It worked if: After the restart the Bad Image window is gone, and Start, Search and Settings work.
If not: If the window stays, the update was not the cause: go to Fix 4 or Fix 5.
Fix 4. Update or reinstall the app named in the window title
15 to 30 minutesLow riskOnly one third-party app ever appears in the title, such as ArmouryCrate.AppServiceBridge.exe (ASUS Armoury Crate) or a Razer Synapse process, and Fix 1 is done.
The window comes from the program that tried to load cdp.dll at startup. A newer version of that program may load it correctly, and removing it at least stops the window while you repair Windows.
- Note the name before - Bad Image in the window title, then select OK.
- Check the maker's site or app for an update. For Armoury Crate, ASUS publishes updates in the app and on the ROG forum.
- If no update helps, uninstall the program, restart and check whether the window still appears.
- Install the current version from the maker's own website.
Step by step for removing a program: Uninstall a program or app in Windows
Win32Bridge.Server.exe is part of Windows, not an app you can reinstall. For that title stay with Fix 1, Fix 2 and Fix 7.
It worked if: The next sign-in shows no Bad Image window, and the app works after its reinstall.
If not: If the window returns with another title, the Windows file is still damaged: repeat Fix 1, then try Fix 5.
Fix 5. Find the startup program that triggers the window with a clean boot
15 to 40 minutesLow riskThe window appears at every sign-in but the title is unclear, or several apps fail.
A window at sign-in means something that starts with Windows loads cdp.dll. A clean boot starts Windows with Microsoft services only, so if the window is gone, one of the turned-off items caused it.
- Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
- Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.

With Hide all Microsoft services ticked, only third-party services stay in the list. Screenshot: Windows 11 26H2. - Disable the remaining services. Select Disable all, then select Apply.
- Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.

The Startup tab only links to Task Manager. Screenshot: Windows 11 26H2. - Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.

Select an app, then Disable. Screenshot: Windows 11 26H2. - Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
- Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).
These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows
- If the window is gone in the clean boot, turn on half of the disabled items and restart.
- Keep halving until one item brings the window back.
- Update or uninstall that program (Fix 4), then turn the rest back on.
A clean boot does not tick Safe boot on the Boot tab. Leave it off, or Windows starts in Safe Mode every time until you untick it.
It worked if: No Bad Image window in the clean boot, and you find the one item that brings it back.
If not: If the window shows even in a clean boot, a Windows process loads the damaged file: try Fix 6 or Fix 7.
Fix 6. Undo a recent change with System Restore
20 to 40 minutesLow riskThe window started on a known day, and a restore point from before that day exists.
System Restore puts back system files, drivers and settings from the restore point, so a cdp.dll from before the damage comes back with them.
- Open System Restore. Press Windows+R, type the command below and press Enter. You can also open Control Panel > Recovery > Open System Restore. If a first page opens, select Next.
rstrui.exe - Choose a restore point. Select a restore point from a time before the problem started. The Description often names the event, such as a driver or app install. If the one you need is missing, select Show more restore points (shown only when there are more).

Pick a restore point from before the problem started. Screenshot: Windows 11 26H2. - See what will change. Select Scan for affected programs. The upper list shows programs and drivers that will be removed; the lower list shows those that might come back and may need to be reinstalled. Select Close.

The scan lists programs and drivers the restore removes or brings back. Screenshot: Windows 11 26H2. - Start the restore. Select Next, check the summary and select Finish. Windows restarts and applies the restore point. Do not turn the PC off.
- Check the result. After sign-in Windows reports whether the restore succeeded. Check whether the problem is gone.
These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Undo recent changes with System Restore
Your documents and photos stay. Programs and drivers installed after the restore point are removed, so check the list with Scan for affected programs first.
It worked if: Windows reports that the restore completed, and the next sign-in has no Bad Image window.
If not: If there is no restore point, or the window returns, repair Windows in place with Fix 7.
Fix 7. Reinstall Windows and keep your files and apps
1 to 2 hoursRead the warningSFC cannot repair files, or the window survives every fix above.
A repair install replaces every Windows file, cdp.dll included, with a fresh copy of your version, while it keeps your files, apps and settings.
A repair install keeps files and apps when you choose to keep them, but a power cut or a wrong choice can cost data. Copy your documents to an external drive or the cloud first: Back up your files (Windows Backup, File History, Time Machine)
- Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.

Fix problems using Windows Update reinstalls the current version and keeps apps, files and settings. Screenshot: Windows 11 26H2. - Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
- Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.
- If that did not help: Reset PC. Back in Settings > System > Recovery, next to Reset this PC, select Reset PC. This keeps your personal files but removes installed apps and settings.
- Choose Keep my files. Select Keep my files. Do not select Remove everything.

Keep my files removes apps and settings but keeps personal files. Screenshot: Windows 11 26H2. - Choose where Windows comes from. Select Cloud download to download a fresh copy of Windows, or Local reinstall to use the files already on the PC (faster, but may not include the latest updates).
- Reset. Review the summary and select Reset. The PC restarts several times.
These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files
It worked if: Windows starts after several restarts, your files and apps are still there, and no Bad Image window shows.
If not: If the window comes back even after a repair install, collect the details in the next section and check the hardware.
If the cdp.dll error is still there: how to diagnose it
Stop changing things and collect what support needs. Three facts decide the next step: the exact window title, whether SFC repaired cdp.dll, and when the problem started.
- Photograph the window with the title, the path and the Error status code visible.
- Open Command Prompt as administrator and run
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt". - Open sfcdetails.txt on the desktop and search for
cdp.dll: the lines say whether SFC repaired it or could not. - Press Win + R, type
perfmon /reland press Enter. Reliability Monitor shows, day by day, which programs failed and which updates were installed just before. - Ask on Microsoft Q&A with the photo, the CBS lines and your Windows version from
winver.
- Nothing on the screen works. Start in Start Windows or a Mac in Safe Mode, which loads no third-party startup programs, and run Fix 1 or Fix 6 from there.
- When it is hardware. If system files break again after a repair, or other files also show Bad Image, check the disk with Check a disk for errors (chkdsk) and the memory with How to test your RAM with Windows Memory Diagnostic.
How to keep the cdp.dll error from coming back
- Let updates finish. "Update and shut down" is fine, but do not cut the power while Windows says it is working on updates.
- Never replace system files by hand. A cdp.dll from a download site is the shortest road to the next Bad Image window.
- Keep restore points on. They make Fix 6 possible after a bad update or driver.
- Keep startup apps current. Update vendor tools such as Armoury Crate when their makers release fixes, or remove the ones you do not use: Stop apps from opening at startup
If you run Windows 10, plan the move to Windows 11 or an extended security option: Windows 10 left support on 14 October 2025 and no longer gets regular fixes.
Frequently asked questions
What is cdp.dll?
cdp.dll is a Windows system file in C:\Windows\System32. Its name stands for Connected Devices Platform, the part of Windows that Microsoft runs as the CDPSvc and CDPUserSvc services for features that connect your PC with other devices. It is not part of Armoury Crate, Razer Synapse or any other app, even when their windows name it. We could not find a Microsoft page that documents the file itself, so check its Properties: the Details tab should name Microsoft Windows Operating System.
Is there a DLL repair tool for Windows 11?
Yes, and it is built in. DISM repairs the store of clean Windows files, and SFC then replaces damaged system DLLs such as cdp.dll from that store. Run them as administrator (Fix 1). For a file that SFC cannot repair, the repair install in Fix 7 replaces every Windows file and keeps your apps. Third-party DLL fixers and DLL download sites cannot know your exact Windows build and can install the wrong or an infected copy.
Can I download cdp.dll and copy it to System32?
Please do not. The correct cdp.dll depends on your exact Windows build, and Windows Resource Protection expects its own copy. A file from a DLL site can be the wrong version, unsigned or carry malware, and a mismatched copy can cause the very same Bad Image window. DISM and SFC (Fix 1) restore the right file from Windows itself, and a repair install (Fix 7) does it when SFC cannot.
What does Error status 0xc000012f mean?
0xc000012f means the file Windows tried to load is not a valid program image. The file exists, but its content is damaged, cut short or not what Windows expects. With cdp.dll it points to a damaged Windows copy, so repair Windows files with DISM and SFC (Fix 1). The same code shows up with other DLLs, such as MSVCP140.dll; our general Bad Image guide covers those.
Why did the cdp.dll error appear after a Windows update?
An update replaces many system files across more than one restart. If it stops halfway, for example after a power cut, cdp.dll and the Windows processes that load it can come from different builds, or the file can be cut short. A user on Microsoft Q&A saw it the morning after "Update and shut down", together with a broken Start menu and Settings. Run Fix 1, then let Windows Update finish (Fix 2).
Why does Armoury Crate show the cdp.dll Bad Image window?
ArmouryCrate.AppServiceBridge.exe, a part of ASUS Armoury Crate, loads cdp.dll at startup. When the Windows copy is damaged, the window carries Armoury Crate's name, as users reported in ASUS's forum thread for Armoury Crate 3.3.7. Repair Windows first (Fix 1), then update Armoury Crate or reinstall it from ASUS (Fix 4). Reinstalling the app alone does not replace a Windows file.
Can I just disable the Connected Devices Platform service?
It is not a fix. Microsoft's guidance for Windows Server 2016 says CDPUserSvc is OK to disable there and gives no guidance for CDPSvc. On a home PC, turning them off can break features that connect to phones and other devices, while the damaged file stays damaged and other programs can still load it. Repair the file with Fix 1 instead and leave both services on their default automatic start.
Is the cdp.dll error a virus?
The message itself is not a sign of infection: it appears when a file cannot be loaded. Malware can damage system files, though. If the window names a cdp.dll outside C:\Windows\System32, or other files break too, scan the PC with Microsoft Defender: How to scan for malware with Microsoft Defender. A cdp.dll in Downloads, Temp or an app folder that you did not put there is worth a full scan.
How do you diagnose a failing CDP program?
Start with the window title: it names the program that failed to load cdp.dll. Then check the file's size and Details tab in its Properties, run SFC and read the CBS.log lines for cdp.dll, and open Reliability Monitor with perfmon /rel to see what failed on which day and which update came just before. The steps are in the section "If the cdp.dll error is still there" above.
What does this page cover?
This page covers the cdp.dll Bad Image error in Windows 11 and Windows 10: what the message and its code mean, which programs show it, and how to fix it, from DISM and SFC to a repair install. Searches such as "how to fix" or "pictures" that land here are answered by the short answer at the top and the screenshots in each fix. The picture of the message itself is in "What the cdp.dll Bad Image error means".
Sources
- Microsoft Learn: Security guidelines for system services in Windows Server 2016 (CDPSvc and CDPUserSvc entries) (learn.microsoft.com)
- Microsoft Q&A: Why is my computer broken after an update? (Win32Bridge.Server.exe Bad Image naming cdp.dll, Error status 0xc000012f, user report) (learn.microsoft.com)
- ROG Forum: Armoury Crate v3.3.7.0 issues thread (ArmouryCrate.AppServiceBridge.exe Bad Image naming cdp.dll, user report) (rog-forum.asus.com)
Did this fix work?
One click, no account. It tells the next reader which guides are worth their time.
Questions and experiences: fix cdp.dll error in Windows
Still broken, or found a fix we did not cover? Ask here: members and our editors answer. Reading is open; writing needs a free account.
…