Hardware FixRecommendedDevice not working? Your driver may be the problemCheck updates for common hardware issues.Fix DriversOctober DealsAmazon USOctober deal check: compare before you payAmazon US: current deals, useful picks and tech finds.Check DealsPC HealthRecommendedCrashes, freezes, slowdowns? Check your PC nowSpot repairable issues before they interrupt work.Check PC×
Skip to content
VGSources
Blog

device.dll Missing: Repair PC Companion on Windows 11 and 10

Length11 min Posted Quest giverVGSources Team

Common device.dll error messages

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

You may see one of these messages when an older Sony PC Companion installation cannot start:

  • “The program can’t start because Device.dll is missing from your computer.”
  • “The code execution cannot proceed because Device.dll was not found.”
  • “Error loading Device.dll. The specified module could not be found.”
  • “Failed to load Device.dll.”
  • “Device.dll is either not designed to run on Windows or it contains an error.”

These are common reported messages for device.dll, but the wording can vary. “The specified module could not be found” may mean that device.dll is missing, or that another dependency required by it is missing.

As an Amazon Associate I earn from qualifying purchases.

The 60-second answer

device.dll is not normally a Windows system file. It is identified as Device Core Library, a component of Sony PC Companion, with indexed metadata attributing the DLL to Avanquest Software.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The safest fix is to repair PC Companion from Windows. If repair is unavailable, uninstall it, restart the computer, and reinstall PC Companion from the original Sony installation media or a trustworthy Sony support source.

#1 Best Overall
Sale
Microsoft Windows 11 (USB)
  • 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)

Do not download device.dll from a random DLL website or copy it into C:WindowsSystem32. The commonly indexed version is reported as a 32-bit file, so placing it in a Windows system folder is particularly likely to create an architecture or version mismatch. The DLL normally belongs beside the PC Companion executable that loads it.

What causes the device.dll error

The cause is usually one of these:

Likely cause What it means Best response
PC Companion was partially removed The program lost a private DLL or related file Repair or reinstall PC Companion
Antivirus quarantined the file Security software isolated the DLL Check Protection history, then reinstall if uncertain
A dependency is missing device.dll exists, but another library cannot load Identify the second filename and repair that dependency
Wrong or damaged installation The DLL is corrupt, incomplete, or incompatible Reinstall from original media
Windows components are damaged Broader Windows files are failing Run DISM and SFC
PC Companion is obsolete The old application may no longer work with the phone or Windows version Check current Sony support and consider Xperia Companion

The indexed build is reported as version 1.0.0.1, approximately 0.88 MB, and 32-bit. Those details come from public file records rather than an accessible official Avanquest installer, so use them for identification, not as proof that a downloaded copy is genuine.

Fix 1: Repair PC Companion from Windows

Start with Windows’ built-in repair option. This preserves the installation when the program installer supports repair.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Windows 11

  1. Right-click Start and select Installed apps.
  2. Find PC Companion in the list.
  3. Select the three-dot menu beside it.
  4. Choose Advanced options, if available.
  5. Select Repair.
  6. Restart Windows.
  7. Start PC Companion again.

If the repair completes successfully, device.dll should be restored to the program’s own installation directory. Do not expect it to appear in System32 or SysWOW64.

Windows 10

  1. Open Start.
  2. Select Settings.
  3. Choose Apps.
  4. Select Apps & features.
  5. Select PC Companion.
  6. Choose Advanced options, if shown.
  7. Select Repair.
  8. Restart the computer and test the program.

Some classic desktop installations do not provide an Advanced options page. Use Control Panel instead:

  1. Press Win + R.
  2. Type appwiz.cpl and press Enter.
  3. Select PC Companion.
  4. Choose Repair, Change, or a similarly named installer option.
  5. Follow the prompts.
  6. Restart Windows.

How to tell whether repair worked

Repair worked if PC Companion opens without the device.dll message and the DLL is present in the application’s installation folder. If the error remains, or PC Companion is not listed, continue with a clean reinstall.

Fix 2: Uninstall and reinstall PC Companion

A clean reinstall is the most reliable repair when the program was interrupted during an update, removed by cleanup software, or left with damaged files.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Before uninstalling, back up any data that PC Companion stores locally. Do not manually delete DLLs from Windows directories.

  1. Open Settings.
  2. Go to Apps > Installed apps in Windows 11, or Apps > Apps & features in Windows 10.
  3. Select PC Companion.
  4. Choose Uninstall.
  5. Complete the uninstall wizard.
  6. Restart Windows, even if the wizard does not request it.
  7. Remove only obvious PC Companion leftovers from its own installation directory if the uninstaller left them behind.
  8. Reinstall using the original Sony installer or a trustworthy Sony support archive.
  9. Right-click the installer and choose Run as administrator.
  10. Restart Windows after installation.
  11. Launch PC Companion before reconnecting the phone.

For older Control Panel installations:

  1. Press Win + R.
  2. Enter appwiz.cpl.
  3. Select PC Companion.
  4. Choose Uninstall or Change.
  5. Restart after removal.
  6. Run the original installer as administrator.

If PC Companion reinstalls but immediately produces a different missing-DLL message, record the new filename. Repair that newly named dependency instead of repeatedly replacing device.dll.

If the installer will not run

Try these checks:

  1. Copy the installer to a local folder such as C:Installers.
  2. Right-click it and select Properties.
  3. If an Unblock checkbox appears on the General tab, select it and choose Apply.
  4. Right-click the installer again and choose Run as administrator.
  5. If it still fails, temporarily test whether Windows compatibility settings help:
  6. Right-click the installer.
  7. Select Properties > Compatibility.
  8. Choose Run this program in compatibility mode for.
  9. Select the older Windows version that matches the software’s documentation.
  10. Select Apply, then run the installer again.

Compatibility mode does not supply a missing DLL. It only helps an older installer complete on a newer version of Windows.

Fix 3: Check Windows Security quarantine

Antivirus software may have removed or isolated a DLL after a scan. A filename alone does not prove that a file is safe, so do not immediately whitelist device.dll.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  1. Open Start.
  2. Search for Windows Security and open it.
  3. Select Virus & threat protection.
  4. Choose Protection history.
  5. Review recent detections for PC Companion or device.dll.
  6. Expand a detection to view its location and details.

Restore or allow the file only when all of these are true:

  • It came from the original PC Companion installer.
  • The installation source is trustworthy.
  • The detection is confirmed to be a false positive.
  • The installer and computer have been scanned.

If any part is uncertain, leave the file quarantined and reinstall PC Companion from trusted installation media. A clean reinstall is safer than restoring an isolated DLL by itself.

After reinstalling, run Scan options > Full scan in Windows Security. If Defender identifies the file as malware, do not add an exclusion merely because PC Companion expects a file with that name.

Fix 4: Check whether a dependency is missing

The message “The specified module could not be found” does not always identify the actual missing file. Windows may find device.dll but fail while loading a library that it depends on.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Look carefully at the complete error:

  • If it names device.dll, repair PC Companion first.
  • If it names MSVCR, MSVCP, or VCRUNTIME, investigate the Visual C++ runtime.
  • If it names another vendor DLL, repair the program or component that supplied that DLL.
  • If it says the file is “not designed to run on Windows,” suspect corruption, architecture mismatch, or a damaged dependency.

Do not download each named DLL separately. The correct repair is the original application installer or the official runtime package that owns the dependency.

Repair the Visual C++ runtime when the error supports it

PC Companion is commonly identified as a 32-bit application. On 64-bit Windows, a 32-bit program normally needs the x86 Visual C++ Redistributable, not only the x64 package.

Use Microsoft’s Latest supported Visual C++ Redistributable downloads page. Install the x86 package when the calling program is 32-bit. If the program specifically requires a different older runtime generation, retain compatible older versions rather than assuming the newest package replaces every older runtime.

You can also repair an installed package:

  1. Open Settings > Apps > Installed apps.
  2. Search for Microsoft Visual C++ Redistributable.
  3. Select the relevant x86 entry.
  4. Choose Modify if available.
  5. Select Repair.
  6. Restart Windows.

A Visual C++ repair is a secondary diagnostic step. There is no authoritative evidence that every device.dll failure is caused by Visual C++. If the error still names device.dll after reinstalling PC Companion, reinstall PC Companion again from original media rather than treating the runtime as the definitive fix.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Fix 5: Repair Windows components with DISM and SFC

DISM and System File Checker repair Windows components and protected Windows files. They generally do not restore a third-party DLL removed from the PC Companion directory, so use them when several unrelated programs are failing, Windows Update is damaged, or system corruption is suspected.

Run DISM

  1. Open Start.
  2. Type Command Prompt.
  3. Right-click Command Prompt.
  4. Select Run as administrator.
  5. Enter:
DISM.exe /Online /Cleanup-Image /RestoreHealth
  1. Wait for the operation to finish.
  2. Restart Windows.

Run SFC

After restarting:

  1. Open an elevated Command Prompt again.
  2. Enter:
sfc /scannow
  1. Wait until verification reaches 100 percent.
  2. Restart Windows.
  3. Test PC Companion.

If SFC reports that it repaired files, test the program again. If it reports that it could not repair everything, run Windows Update and restart before repeating the check.

Manually hunting through Windows components and repeating DISM or SFC without knowing what changed can be time-consuming. Outbyte PC Repair offers a free scan that shows reported issues, while repair is handled by the full version; it is optional, and reinstalling PC Companion remains the definitive fix for this application-specific DLL.

Fix 6: Update phone and Windows drivers

A driver problem usually does not recreate device.dll, but an obsolete PC Companion installation may also fail when its phone connection components cannot communicate with Windows.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

First check Windows Update:

  1. Open Settings.
  2. Select Windows Update.
  3. Choose Check for updates.
  4. Install available updates.
  5. Restart Windows.

Then inspect Device Manager:

  1. Right-click Start.
  2. Select Device Manager.
  3. Expand Portable Devices, Universal Serial Bus controllers, and Other devices.
  4. Look for a yellow warning icon or an unknown Sony device.
  5. Right-click the affected device.
  6. Select Update driver.
  7. Choose Search automatically for drivers.
  8. Restart Windows if a driver is installed.

If the phone driver remains broken, uninstall the affected device from Device Manager and restart. Windows may reinstall it automatically. Do not remove unrelated devices.

Finding the correct legacy driver manually can involve checking hardware IDs, Windows versions, and several old packages. Outbyte Driver Updater provides a free scan showing reported driver problems, while installation is handled by the full version; it is optional, and it cannot replace reinstalling PC Companion when the application itself is missing device.dll.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 7: Test a damaged user profile

If PC Companion works under another Windows account, the problem may be tied to permissions, per-user settings, or a damaged profile.

  1. Open Settings > Accounts > Other users.
  2. Select Add account.
  3. Create a local test account.
  4. Sign in to that account.
  5. Start PC Companion.

If the error disappears, repair or recreate the affected user profile after backing up its data. If the error appears for every account, the installation or its dependencies are more likely at fault.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Fix 8: Use System Restore for a recent failure

System Restore is appropriate when the error began after a driver installation, cleanup operation, update, or other recent system change and a suitable restore point exists.

  1. Press Win + R.
  2. Type rstrui.exe.
  3. Press Enter.
  4. Select Choose a different restore point if offered.
  5. Pick a restore point from before the failure.
  6. Select Scan for affected programs.
  7. Review the result.
  8. Select Finish.

System Restore rolls back system files, registry settings, and installed programs, but it does not remove personal files. It may not restore a third-party DLL if the original PC Companion installation was already incomplete, so reinstall the application if the error remains.

Do not register device.dll with regsvr32

Do not run:

regsvr32 device.dll

regsvr32 is intended for DLLs that provide registration entry points such as DllRegisterServer, commonly COM or ActiveX components. A normal application library may not support registration. Registering it will not recreate missing dependencies and can produce another error.

Use regsvr32 only when the software vendor explicitly instructs you to register that specific DLL and confirms that it is a registration-based component.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Do not copy device.dll into System32

The correct location is normally the application directory beside the executable that loads the file.

On 64-bit Windows:

  • C:WindowsSystem32 contains 64-bit system binaries.
  • C:WindowsSysWOW64 contains 32-bit system binaries.

Neither folder is the default destination for this PC Companion DLL. Copying a file into either folder can cause version conflicts, leave the real application installation broken, and expose Windows to an untrusted binary.

Random DLL download sites also create several risks:

  • The file may contain malware.
  • The version may not match PC Companion.
  • The architecture may be wrong.
  • The file may have been modified.
  • A dependency may still be missing.
  • The download may conceal an installer or unwanted software.

Use the original PC Companion installer, trustworthy Sony support media, Windows repair features, and Microsoft runtime packages instead. Do not treat a matching filename as proof of authenticity. Where possible, verify the original installer’s digital signature and scan it before running it.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Is PC Companion still supported

PC Companion is legacy Sony software. Sony’s newer Xperia support materials use the Xperia Companion branding, and compatibility with a current phone or Windows installation may differ from the old PC Companion software.

If reinstalling PC Companion restores device.dll but the program still cannot connect to the phone, check Sony’s current support guidance for the device. The DLL error may be a symptom of obsolete software rather than a standalone Windows problem.

If the error appears on every startup after PC Companion has been removed, inspect Task Manager > Startup apps for a leftover PC Companion entry. Disable only the entry clearly associated with the removed application. If you are unsure, reinstall PC Companion first and then remove it cleanly instead of deleting arbitrary files or registry entries.

FAQ

Is device.dll a Windows system file?

No evidence supports treating this PC Companion file as a standard Windows component. It is identified as Device Core Library and associated with PC Companion.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Which program installs device.dll?

Public file records associate it with Sony PC Companion and attribute the indexed component metadata to Avanquest Software.

Should I download device.dll separately?

No. A separate download can be malicious, the wrong architecture, or the wrong version. Repair or reinstall PC Companion from original trusted media.

Is device.dll 32-bit or 64-bit?

The commonly indexed version 1.0.0.1 is reported as 32-bit. Do not assume that an alleged 64-bit copy is a valid replacement.

Do I need the x86 Visual C++ Redistributable?

Only when the calling program or a related error indicates a Visual C++ runtime problem. A 32-bit PC Companion process on 64-bit Windows uses the x86 runtime, but Visual C++ is not proven to be the normal cause of every device.dll error.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Will SFC restore device.dll?

Usually not. SFC repairs protected Windows system files, while device.dll belongs to a third-party application. Run SFC when broader Windows corruption is suspected, then repair PC Companion separately.

Why does Windows say the specified module could not be found when device.dll is present?

The DLL may depend on another missing library, or it may be corrupt or the wrong architecture. Look for a second filename in the complete error and repair the owning application or runtime.

What if reinstalling PC Companion does not help?

Check Protection history, confirm that the correct 32-bit application is being launched, repair any specifically named Visual C++ dependency, and test a new Windows profile. If PC Companion remains incompatible with the phone or Windows version, use Sony’s current Xperia support software instead.

Quick Recap

SaleBestseller No. 1
Microsoft Windows 11 (USB)
Microsoft Windows 11 (USB)
Make the most of your screen space with snap layouts, desktops, and seamless redocking.; FPP is boxed product that ships with USB for installation
$124.97
Bestseller No. 2

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.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Leave a Reply

Your email address will not be published. Required fields are marked *

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

More quests from Patch Notes

  1. How to Set Up a RedM (RDR2) Server in 2026: License Key, txAdmin and server.cfg, Step by StepBlog11min
  2. Best RedM (RDR2) Server Hosting in 2026: Comparing Four Hosts on Slots, Memory and PriceBlog10min
  3. How to Host a Mindustry Server in 2026: server-release.jar, Port 6567 and the Commands That MatterBlog7min
Recommended PC Tool
Recommended PC Tool
Windows Errors? Fix Them Before They SpreadFree repair scan
Outdated Drivers Are Slowing You DownFree scan - exact matches

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.