Microsoft has addressed a notable issue affecting the ‘Print to PDF’ feature on Windows 11 24H2 systems, which emerged following the installation of the April 2025 preview update. Users had reported that the Microsoft Print to PDF printer was no longer visible under the Settings menu, specifically in the Bluetooth & devices section under Printers & scanners.
According to updates provided in the support documents, enabling the Printing-PrintToPDFServices-Feature resulted in the error code 0x800f0922, hindering the installation of the Microsoft Print to PDF printer driver located in C:WindowsSystem32DriverStoreFileRepository.
Resolution and Updates
The issue has been rectified in the KB5060829 preview cumulative update for Windows 11 24H2, which was released on Friday. This fix will be rolled out to all users with the upcoming July Patch Tuesday updates later this month.
For those who prefer not to install the June optional update to resolve this issue, there is an alternative method to manually enable the Printing-PrintToPDFServices-Feature. Users can do this by accessing the Windows Features dialog. Simply press the Windows + R keyboard shortcut and type in optional features.
Windows administrators also have the option to utilize PowerShell for enabling this feature. By opening Windows PowerShell as an Administrator, they can execute the following commands:
Disable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features
Enable-WindowsOptionalFeature -Online -FeatureName Printing-PrintToPDFServices-Features
However, Microsoft has cautioned that toggling the Printing-PrintToPDFServices-Feature through PowerShell may still result in the 0x800f0922 error.
This recent fix follows a series of updates from Microsoft addressing various printing issues, including a previous resolution in March for USB printers that were erroneously printing random text after updates released since late January. Additionally, last month, the company indicated potential delays in the June 2025 Windows security updates due to an incorrect metadata timestamp and implemented a configuration update to rectify a known issue causing Windows Update failures on certain Windows 11 systems.
