Has anyone had MS Print to PDF get totally messed up after NTLite session?
- Thread starter Sonicmojo
- Start date
nt4print is the Core Printer Driver
; NTPRINT.INF - Microsoft Windows Core Printer Driver Package
for Microsoft PDF printing you need prnms009.inf
; File Name:
; prnms009.inf
; Abstract:
; The Microsoft Print To PDF install file
WinSxS is crucial for maintaining system stability and compatibility in Windows environments
Key Features of WinSxS: Versioning, Storage, Component Store, File Integrity, Cleanup
these are not the location of your "working" drivers.
The installed drivers you can find in:
Start Windows Terminal and use command printerdriver
Check folders:
"C:\Windows\System32\spool\drivers\x64\PCC"
"C:\Windows\System32\spool\tools\Microsoft Print To PDF"
"C:\Windows\System32\DriverStore\FileRepository\prnms009.inf_amd64_.........xxxxxx"
In Audit Mode you can not find these drivers, you have to check after finish Audit Mode
that is why I atm "inject" the PDF driver in the image, works good for the moment.
I have now finished testing included features:
More testing with added driver to "audit" image and custom components and features
No Microsoft update integration and tweaks & custom components
NTLite with finishing Microsoft Audit mode: Yes PDF
NTLite with finishing Anarethos Audit mode: Yes PDF
Next step will be integrated Microsoft Updates and see what happens
I finally figured out why the printer isn't configured, some versions of prnms009.cat are corrupt.
If you try adding the driver, using the INF file from amd64_microsoft-windows-printing-printtopdf_31bf3856ad364e35_10.0.26100.3912_none_1dbc9b66f6ba8895, both "pnputil /add-driver prnms009.inf /install" and Device Manager report:
Running "pnputil /add-driver prnms009.inf /install" from a .1882 folder works the first time. The INF files are identical, so something's definitely wrong with the catalog file.
Workaround:
1. Download .1882 component folder from:
2. Run "pnputil /add-driver prnms009.inf /install".
3. DISM /Online /Enable-Feature /FeatureName:"Printing-PrintToPDFServices-Features"
4. Print a test page.
If you try adding the driver, using the INF file from amd64_microsoft-windows-printing-printtopdf_31bf3856ad364e35_10.0.26100.3912_none_1dbc9b66f6ba8895, both "pnputil /add-driver prnms009.inf /install" and Device Manager report:
Code:
prnms009.inf: Failed to add driver to the system. Error 0xE000024B: The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
prnms009.inf: Failed to add driver to the system. Error 0xE0000100: The style of the INF is different than what was requested.Running "pnputil /add-driver prnms009.inf /install" from a .1882 folder works the first time. The INF files are identical, so something's definitely wrong with the catalog file.
Workaround:
1. Download .1882 component folder from:
2. Run "pnputil /add-driver prnms009.inf /install".
3. DISM /Online /Enable-Feature /FeatureName:"Printing-PrintToPDFServices-Features"
4. Print a test page.
I also had this error message: The hash for the file is not present in the specified catalog file
That moment I thought this was my mistake because I manually created a CAB file from prnms009 drivers
Because I tested 3 different driver packages I did not know Microsoft created different build versions for same package
prnms009.inf.......7e2
prnms009.inf.......a5a
prnms009.inf.......1fd
I have been created new images without MS Updates and added prnms009 driver manually, that is working for me.
Some builds I have not fixed yet and are with non working PDF so will try your solution, for know the first build is working with your solution.
Thank you garlin !
- Messages
- 1,230
- Reaction score
- 246
There was already a fix to apply here (but no link to download the driver 
)
And it seems that MS has fixed this issue with the latest LCU
But I didn't check
)And it seems that MS has fixed this issue with the latest LCU
But I didn't check
I wrote a short PS script to repair Print To PDF on any W11 24H2 release. This can be added to Post-Setup (Before logon) with no command-line arguments.
The script makes a temp copy of the first PrintToPDF component folder it finds (doesn't matter if there's multiple versions), and replaces the prnms009 files. Because those two files are not executable code, I don't run into DMCA issues by redistributing Windows software.
If the script fails to enable the PDF printer, restart Windows and re-run the script.
The script makes a temp copy of the first PrintToPDF component folder it finds (doesn't matter if there's multiple versions), and replaces the prnms009 files. Because those two files are not executable code, I don't run into DMCA issues by redistributing Windows software.
If the script fails to enable the PDF printer, restart Windows and re-run the script.
francis11
Well-Known Member
- Messages
- 1,169
- Reaction score
- 235
Funny u say - without an even one preset in this post?
You don't need a preset, this problem is documented all over the web. Look at Reddit.
Once you know the workaround of manually installing the PDF printer from a known good driver folder, the question becomes why did it break in the first place? The mismatched catalog confirms it was caused by poor release management.
francis11
Well-Known Member
- Messages
- 1,169
- Reaction score
- 235
Without a Hardware printer or PDF software installed it open fine in EDGE.
How did you assume that the driver prnms009 is missing - it's not even present in 24H2 - 4351 drivers opening with NTL?
009 is refefering to modems or network cards!
How did you assume that the driver prnms009 is missing - it's not even present in 24H2 - 4351 drivers opening with NTL?
009 is refefering to modems or network cards!
