![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 5%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEB%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(284.8, 33%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDV%3C/text%3E%3C/svg%3E)
Hello Erik Bart,
The “Microsoft Print to PDF” feature is a built‑in Windows optional component, not a third‑party driver, so if it fails to install or activate after a cumulative update, it usually means the feature store is corrupted or the servicing stack is blocking the installation. Since you already tried PowerShell (Add-WindowsCapability) and DISM, the next step is to verify the integrity of the component store and repair it.
Run an elevated command prompt and execute:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
This ensures the servicing stack and system files are consistent. After that, try re‑adding the feature explicitly:
dism /Online /Add-Capability /CapabilityName:PrintToPDF~~~~0.0.1.0
If DISM still fails, check the CBS log at C:\Windows\Logs\CBS\CBS.log and the DISM log at C:\Windows\Logs\DISM\dism.log. These logs will show whether the capability package is missing, blocked, or mismatched with your build (25H2 26200.5).
If the capability package is not available locally, Windows should pull it from Windows Update. Since you are on WSUS, confirm that WSUS is configured to deliver Features on Demand. If WSUS does not have the FoD packages, the installation will fail. In that case, you need to temporarily bypass WSUS by enabling the Group Policy setting Specify settings for optional component installation and component repair under Computer Configuration > Administrative Templates > System. Point it to Windows Update or a FoD ISO.
If none of these steps succeed, the supported resolution is an in‑place upgrade repair using the latest Windows 11 ISO. This reinstalls all optional features, including Print to PDF, without affecting user data.
So the next step is to check CBS/DISM logs for the exact failure reason, confirm WSUS is serving Features on Demand, and if not, either bypass WSUS or perform a repair install. That is the only supported way to restore the Print to PDF feature when servicing commands fail.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
Domic Vo.