CrossDeviceService.exe Bad Image and Parameter Is Incorrect Errors (Fix)

A pop-up reading CrossDeviceService.exe – Bad Image or CrossDeviceService.exe “The Parameter is incorrect” usually appears a few seconds after you log in to Windows 11. The message often points at a file such as MSVCP140.dll inside a Microsoft.VCLibs.140.00.UWPDesktop folder and may include a status like 0x0000020. It is tied to Windows’ cross-device features, which are driven by the Phone Link app and the Cross-Device Experience Host.

Quick answer: Open Task Manager, end every CrossDeviceService.exe process, then run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated Command Prompt and restart. If the error returns, disable Mobile Devices at startup or repair the Phone Link app.

What triggers the CrossDeviceService.exe error

CrossDeviceService.exe is a background service that handles cross-device syncing, such as sharing activity, photos, chats, and calls between your PC and phone. When it cannot load a shared runtime file, or when the Cross-Device Experience Host component is missing or out of date, Windows throws the Bad Image or Parameter is incorrect message on startup.

The most common cause is a corrupted or zero-byte Visual C++ runtime file. In several cases the DLLs inside the Microsoft.VCLibs.140.00.UWPDesktop folders were reported as 0 bytes, which stops the service from starting cleanly. The error can also follow a BIOS update, a Windows update, or a sync setting from an app that relies on cross-device functionality.

Stop the process and repair system files

Start here. Ending the process clears the immediate pop-up, and the repair scans fix the corrupted files that keep bringing it back.

Press Ctrl + Shift + Esc to open Task Manager. On the Processes tab, find CrossDeviceService.exe, right-click it, and choose End Task. End every instance you see.

Open the Start menu, type Command Prompt, right-click it, and pick Run as administrator.

Run the system health checks one line at a time, pressing Enter after each.

Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /RestoreHealth
SFC /SCANNOW

Restart the laptop. If the pop-up no longer appears after login and the scans reported no remaining issues, the corrupted files are repaired and you are done.

Fix corrupted or 0-byte VCLibs DLLs

If the message names a file inside a VCLibs folder, check those DLLs directly. When the runtime files show a size of 0 bytes, they cannot load, which is what produces the Bad Image warning.

Open File Explorer and browse to the folders that hold the UWP Desktop runtime. The exact version number in the folder name varies, so open the folder that matches the version shown in your error.

Runtime folder to check
`Microsoft.VCLibs.140.00.UWPDesktop_..._x64__8wekyb3d8bbwe`
`Microsoft.VCLibs.140.00.UWPDesktop_..._x86__8wekyb3d8bbwe`

Check the size of the DLLs, including MSVCP140.dll. If any file reads 0 bytes, it is corrupted.

Delete the affected files or the corrupted version folders, then reboot. Windows can revert the affected apps to an earlier working copy of these runtime files, which cleared the error for users who reported the 0-byte problem. Note that Photos, Notepad, and Paint may fall back to the older DLL version, which is expected behavior.

Find the startup app causing the error with a clean boot

If the pop-up keeps returning, a startup entry is likely triggering it. A clean boot starts Windows with a minimal set of drivers and startup items so you can isolate the culprit. In practice, the Mobile Devices startup entry was identified as the trigger through this process.

Perform a clean boot using Microsoft’s official steps at How to perform a clean boot in Windows.

Re-enable startup items in small groups, restarting between each round, until the error reappears. The item that brings it back is the cause.

Leave that item disabled and set the PC to start normally again. Disabling Mobile Devices at startup removes the message, though the related Phone Link photo-transfer feature will not work until it is enabled again.

Update the Cross-Device Experience Host

The Cross-Device Experience Host manages how devices connect to your PC for shared activities. If it is missing or outdated, the service can fail. Reinstalling it through winget refreshes the component.

Open Command Prompt as an administrator.

Run the install command and press Y to accept the terms when prompted.

winget install 9NTXGKQ8P7N0

Once the install finishes, restart and check whether the error still appears. To remove the component instead, run the following in an elevated PowerShell window.

Get-AppxPackage *Microsoft.CrossDeviceExperienceHost* | Remove-AppxPackage

Repair, reset, or reinstall the Phone Link app

Because the error is tied to Phone Link, fixing the app itself often clears it. Repairing tries to fix corrupted app files without touching your data, while resetting wipes stored data such as sign-in credentials, settings, and cache.

Open the Start menu, type Phone Link, right-click it, and choose App Settings.

Scroll down and click Repair. Test whether the error is gone. If it persists, return to the same screen and click Reset.

If repair and reset do not help, reinstall the app. Open Windows PowerShell as an administrator and run the re-register command.

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Extra checks if the error still appears

Check	What it does
Reinstall Visual C++ Redistributables	Uninstall them from Control Panel > Programs & Features, then reinstall from Microsoft’s official site to replace damaged runtime files.
Run `chkdsk /f /r`	Scans the disk for errors that could corrupt system or app files; runs on the next restart.
Create a new user account	If the error is gone in a fresh account, the original user profile or its settings are the cause.
Windows update	Install pending updates; in some cases the error cleared itself after a later Windows update.

You will know the fix worked when the Bad Image or Parameter is incorrect pop-up no longer appears in the first seconds after login, and the system health scans report no remaining corruption. If none of these steps resolve it, a system restore to a point before the error started, or a reset of Windows that keeps your files, will restore the affected service files.