lscshostpolicy.dll Won’t Start: Rebuild Windows RDS Safely

lscshostpolicy.dll is a genuine Microsoft Windows file used by Remote Desktop Services, not a normal game DLL or a standalone runtime. If Windows says it is missing, cannot load, or is damaged, repair the Windows component with Windows Update, DISM, and SFC rather than downloading a replacement copy.

The file is associated with Microsoft Remote Desktop Virtual Graphics Session Licensing Host Policy and normally belongs in a Windows system directory, especially C:WindowsSystem32. There is no verified official Microsoft standalone download named “LSCSHostPolicy Redistributable.”

As an Amazon Associate I earn from qualifying purchases.

What lscshostpolicy.dll does

lscshostpolicy.dll supports the licensing and virtual graphics policy layer used by Remote Desktop Services. It can be involved when starting or managing Remote Desktop sessions through mstsc.exe, Remote Desktop Services on Windows Server, or hosted desktop environments.

Microsoft documentation lists Remote Desktop Services licensing as a Windows Server feature, while Microsoft file-list evidence shows this DLL being delivered through Windows servicing. Public binary metadata also identifies Microsoft Corporation as the publisher and lists host-policy functions exported by the file. Those catalogue details are useful for corroboration, but they are not a current Microsoft download specification.

The file is therefore different from:

• Microsoft Visual C++ Redistributable files
• DirectX game libraries
• .NET assemblies
• A graphics-card driver DLL
• A DLL that a particular game normally bundles

Some third-party error databases describe it as being needed by applications or games, but there is not enough reliable evidence to identify a particular consumer program that normally ships this file. If the message appears while using Remote Desktop or Windows startup, treat it as a Windows component problem first.

Error messages this file can produce

Commonly indexed messages include:

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

These exact phrasings are commonly indexed by DLL reference pages rather than documented as Microsoft-specific diagnostics.

The important detail is “The specified module could not be found.” That can mean either the named DLL is absent or one of its dependencies failed to load. Do not assume that copying lscshostpolicy.dll will resolve every version of this error.

Fix 1: Install Windows updates and restart

Time needed: 10–30 minutes

A failed or incomplete Windows update is one of the most likely causes, particularly if the error began after an update, upgrade, disk cleanup, or unexpected shutdown.

1. Press Windows + I to open Settings.
2. Select Windows Update.
3. Choose Check for updates.
4. Install all available updates.
5. Restart the computer, even if Windows does not immediately require it.
6. Test Remote Desktop again.

On Windows 10, open Settings > Update & Security > Windows Update instead.

If updates fail, do not repeatedly retry the same installation while the component store may be damaged. Continue with DISM and SFC below, then retry Windows Update.

Fix 2: Repair Windows with DISM and SFC

Time needed: 15–45 minutes

DISM repairs the Windows component store, which provides trusted system files. SFC then checks protected Windows files and replaces damaged or missing copies.

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt and select Run as administrator.
4. Select Yes if User Account Control appears.
5. Run this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for it to finish. Do not close the window if progress appears to pause.
2. Run SFC after DISM completes:

sfc /scannow

1. Restart Windows.
2. Try the operation that produced the error.

Microsoft’s procedure is documented in Using System File Checker in Windows. If DISM reports that source files cannot be found, follow Microsoft’s Windows image repair guidance rather than downloading an isolated DLL.

SFC and DISM can take time and provide limited detail about which file changed. Outbyte PC Repair can scan for the underlying Windows repair issues and show what needs attention, while the repair action is handled by the full version. It is optional, and Windows servicing remains the correct primary repair path.

How to interpret SFC results

SFC normally reports one of these outcomes:

• Did not find any integrity violations: Windows protected files passed the check. Investigate dependencies, quarantine, or the affected RDS configuration.
• Found corrupt files and successfully repaired them: Restart and test again.
• Found corrupt files but was unable to fix some: Run DISM again, restart, and repeat SFC. If it still cannot repair Windows, use recovery options or an in-place repair.
• Windows Resource Protection could not start the repair service: Restart and try again from an elevated Command Prompt.

Fix 3: Check whether the file exists in the Windows directory

Time needed: 5 minutes

Do not begin by searching the entire internet for a DLL. First establish whether Windows already has a copy.

1. Open Command Prompt as administrator.
2. Run:

where /r "%windir%" lscshostpolicy.dll

A normal result may show a copy under a Windows system directory. C:WindowsSystem32 is the most relevant expected location, although the correct path can vary with Windows architecture and component layout.

If the command returns nothing:

1. Run DISM and SFC as described above.
2. Restart.
3. Run the search again.

If the file appears only in Downloads, a temporary folder, a user profile, or an unrelated application directory, do not automatically trust it. A random location does not prove that the file is malicious, but it does mean the copy needs verification.

Fix 4: Verify the Microsoft signature

Time needed: 5 minutes

A file can have the correct name and still be the wrong file. Check the copy that Windows is attempting to load.

Using File Explorer

1. Browse to the reported file.
2. Right-click LSCSHostPolicy.dll.
3. Select Properties.
4. Open the Digital Signatures tab.
5. Select the signature and choose Details.
6. Confirm that Windows reports the signature as valid and identifies Microsoft as the signer.

Using PowerShell

Open PowerShell as administrator and run:

Get-AuthenticodeSignature "$env:windirSystem32LSCSHostPolicy.dll"

A genuine system copy should normally have a valid Microsoft signature. If the file is missing, the command reports that it cannot find the path. If the signature is invalid or absent, do not replace the file with another downloaded copy. Run a Microsoft Defender scan and repair Windows from trusted installation sources.

Fix 5: Check Windows Security quarantine

Time needed: 5–20 minutes

Antivirus software may remove or quarantine a system file after a detection, malware cleanup, or false positive.

1. Open Windows Security from Start.
2. Select Virus & threat protection.
3. Select Protection history.
4. Review recent items.
5. Open any entry referring to LSCSHostPolicy.dll.
6. Check the original path, detection name, and action taken.
7. Verify the file’s Microsoft signature before considering restoration.

Do not blindly choose Allow on device. Microsoft warns that restoring a quarantined item can reactivate a genuine threat. If the device is clean and the removed file was a signed Windows copy, restore it only as part of a controlled repair, then run DISM and SFC so Windows can obtain the correct component from its trusted sources.

If you suspect malware:

1. Update Microsoft Defender security intelligence.
2. Run a Full scan.
3. Use Microsoft Defender Offline scan if the problem persists or suspicious files return.
4. Repair Windows after the scan completes.

Fix 6: Check for a dependency error

Time needed: 10–30 minutes

If where finds the DLL and its signature is valid, the error may concern a dependency rather than lscshostpolicy.dll itself.

Check:

• Event Viewer > Windows Logs > Application
• Event Viewer > Windows Logs > System
• The application log associated with mstsc.exe or Remote Desktop Services
• Any Windows error mentioning a second missing DLL or a failed service

Do not install Visual C++, DirectX, or .NET automatically just because a DLL error appears. lscshostpolicy.dll is not identified as one of those runtime components. Installing unrelated redistributables can leave the real Windows servicing problem untouched.

Similarly, a graphics-driver reinstall is relevant only when the event specifically identifies a graphics driver or virtual display failure.

Fix 7: Separate an RDS licensing problem from a missing DLL

Time needed: 10–30 minutes

A Remote Desktop host can have a healthy lscshostpolicy.dll and still reject sessions because licensing is misconfigured.

On a Windows Server RDS host, review:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing

Check the configured licensing mode and license-server settings against your organization’s deployment. Microsoft’s Remote Desktop session host licensing documentation covers these policies.

For Azure Virtual Desktop, also distinguish a Windows component failure from host registration, session-host health, identity, or licensing configuration issues. A missing system DLL requires Windows repair; a licensing or host-pool issue requires administrator-side configuration and service investigation.

Fix 8: Inspect Windows Features, but do not add random components

Time needed: 5–15 minutes

Windows Features is not a source for a standalone lscshostpolicy.dll, and enabling unrelated features will not repair it.

To inspect installed optional components:

1. Press Windows + R.
2. Enter:

optionalfeatures

1. Press Enter.
2. Review the feature list for a recent change.
3. Cancel without enabling arbitrary runtime or networking features.

On Windows Server, RDS roles are managed through Server Manager > Manage > Add Roles and Features, not by downloading this DLL separately. Only change server roles when you are following the deployment plan for that host.

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

Fix 9: Update a graphics driver only when logs identify it

Time needed: 10–30 minutes

Do this only if Event Viewer or the Remote Desktop failure specifically points to a display adapter or graphics-driver problem.

1. Right-click Start and select Device Manager.
2. Expand Display adapters.
3. Right-click the relevant adapter.
4. Select Properties > Driver.
5. Record the provider and current version.
6. Obtain the correct driver from the GPU or computer manufacturer.
7. Install it and restart.
8. Test Remote Desktop again.

Do not use Device Manager as a substitute for repairing a missing Windows component.

Outbyte Driver Updater can scan for outdated drivers when checking them manually across several devices is tedious; its free scan identifies issues, while driver installation is handled by the full version. A driver update is not the primary fix for lscshostpolicy.dll unless the recorded failure specifically involves graphics hardware.

Do not register this DLL with regsvr32

regsvr32 is intended for self-registering COM and ActiveX libraries that expose a registration entry point such as DllRegisterServer. The known public metadata for LSCSHostPolicy.dll identifies host-policy creation and release functions, not evidence of a registration interface.

Running this command is therefore unlikely to repair the problem:

regsvr32 lscshostpolicy.dll

It may simply produce an error stating that the entry point is missing. Use DISM and SFC for a Windows system DLL instead.

Why manual DLL downloads are unsafe

Do not download lscshostpolicy.dll from an unverified DLL catalogue or copy a file into both System32 and SysWOW64.

That approach can introduce:

• Malware disguised with a familiar filename
• A file from the wrong Windows build
• A 32-bit and 64-bit architecture mismatch
• An invalid or missing Microsoft signature
• A version mismatch that Windows servicing later overwrites
• A dependency failure that the copied file cannot solve

The safe sources are Windows Update, the Windows component store, a matching Microsoft installation image, or an official Windows recovery or repair installation. There is no verified current Microsoft standalone download page for this DLL.

Causes to consider after the main repairs

The usual causes, in practical order, are:

Likely cause	What to do
Corrupt Windows component or failed update	Run DISM, then SFC, restart, and retry Windows Update
Antivirus quarantine	Review Protection history, verify the signature, scan, then repair Windows
Incomplete Windows upgrade	Use System Restore or Windows recovery options
Malware or unauthorized modification	Run Defender scans and consider a repair installation
Disk corruption	Check storage health and back up important data
Wrong architecture or manually replaced file	Remove the untrusted replacement and restore Windows components
Dependency failure	Inspect Event Viewer and application logs
RDS licensing configuration	Review session-host licensing policies separately

Historical public catalogues list multiple Windows-era versions and both 32-bit and 64-bit builds, but they are not a complete current Windows 10 or Windows 11 inventory. Do not select a replacement based only on a version number or file size.

If the error survives DISM and SFC

Try these recovery paths in order:

1. Use System Restore if the problem began after a recent update or software change.
2. Install the latest cumulative update for the exact Windows edition and build.
3. Back up personal files and use Windows recovery options.
4. Perform an in-place repair installation using matching Windows installation media.
5. Use a clean reinstall only when repair options fail or the system cannot be trusted.

Microsoft explains the available choices in Recovery options in Windows.

FAQ

Should I install Visual C++ Redistributable?

No, not as a first response. This DLL is associated with Windows Remote Desktop Services, not identified as a Visual C++ runtime file.

Is lscshostpolicy.dll a virus?

The legitimate file is a Microsoft Windows component. Verify its path and digital signature. A copy in a temporary, download, or unrelated application directory deserves investigation.

Should I copy it from another PC?

Usually no. The Windows build, architecture, servicing state, and dependencies may differ. Use DISM, SFC, Windows Update, or matching Microsoft installation media.

Does System32 mean the file is 32-bit?

No. On 64-bit Windows, System32 commonly contains 64-bit system components, while SysWOW64 supports 32-bit compatibility. Do not move files between them based on their names.

Can regsvr32 fix it?

Generally no. This is not established as a self-registering COM or ActiveX DLL. Repair Windows components instead.

What if the file exists but Windows still says it is missing?

The message may refer to a dependency. Check Event Viewer and the failing executable’s logs for another missing module, then repair Windows and investigate the specific dependency.

Is this a Remote Desktop licensing error?

It can be related to the RDS licensing layer, but a missing or corrupt DLL and a licensing-policy configuration problem are different failures. Verify the file first, then inspect RDS licensing settings on the host.

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.