Print Server Role Won't Install on Server 2019/2022

1. Missing Source Files in Windows Image (Most Common)

I've seen this error hundreds of times. You click "Add Roles and Features," check Print Server, and boom — 0x800F081F with "The source files could not be found."

Windows Server 2019 and 2022 often don't ship with all printer drivers in the local image. Microsoft wants you to download them, but sometimes the server has no internet or WSUS is being weird.

The Fix: DISM with a Local Source

You'll need the Windows Server installation ISO or a network share with the sxs folder from that ISO. Mount the ISO to drive D: or wherever.

Open PowerShell as Administrator and run:

DISM /Online /Add-Capability /CapabilityName:Print.Server~~~~0.0.1.0 /Source:D:\sources\sxs /LimitAccess

Replace D: with your mounted drive letter. The /LimitAccess flag tells DISM to stop looking at Windows Update — it only checks your local source.

If that fails, try the full feature install with DISM:

DISM /Online /Enable-Feature /FeatureName:Print-Server /All /Source:D:\sources\sxs /LimitAccess

Wait about 3-5 minutes. It'll say "The operation completed successfully." Then go back to Server Manager and install the role normally — it should work this time.

Real-world trigger: This happens most often when you're building a server from an updated ISO (like one slipstreamed with updates) and the printer driver cab files got stripped out during the update process.

2. Group Policy Blocks the Feature Installation

Sometimes the error code is different — like 0x8007007e or just a generic "Installation failed." Look at your Windows Event Log under Applications and Services Logs > Microsoft > Windows > GroupPolicy > Operational.

I had a client once where their security team locked down feature installations via Group Policy. The Specify settings for optional component installation and component repair policy was set to "Never attempt to download payload."

The Fix: Check Local Group Policy

Run gpedit.msc and go to:

Computer Configuration > Administrative Templates > System

Find Specify settings for optional component installation and component repair. Set it to Enabled. Then choose Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS).

If you're in a domain, your admins may have set this via domain policy. Check gpresult /h gpresult.html and look for that setting. If it's set to Disabled or Not Configured, you're good — move on.

After changing the policy, restart the Group Policy engine:

gpupdate /force

Then try the DISM command from Fix #1 again.

Real-world trigger: This happens a lot in organizations that use WSUS to manage updates but forgot to sync the printer driver cab files. The policy blocks Windows from going to Microsoft directly.

3. Corrupted SxS Store or Missing Printer Drivers

Rarer, but when it happens, it's a headache. The c:\windows\winsxs folder gets corrupted, or the printer driver packages are missing entirely. You'll see 0x80073701 or 0x80070002.

Check if you have the printer driver files manually:

dir C:\Windows\WinSxS\ | findstr "print"

If you see nothing or only a couple of entries, the store is incomplete.

The Fix: Repair the System Image

Run the System Update Readiness tool (DISM with restore health):

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\sxs /LimitAccess

This takes 10-20 minutes. After it finishes, run an SFC scan to fix any remaining corrupted files:

sfc /scannow

Reboot the server, then try the Print Server role install again.

Real-world trigger: I've seen this after a failed Windows update or an improper shutdown during patching. The SxS store gets left in a bad state.

Quick-Reference Summary Table