Forum Discussion
Windows 10 WVD pnplockdownfiles bloat
Hi, Windows 10 Multi-Session WVD machine and pnplockdownfiles bloating Dealing with an issue where the pnplockdownfiles seems to be bloating really badly with repeated printer driver installa...
Not seeing this behavior in our lab env if redirection is forced to use the RDS EasyPrint drivers (which I'm currently able to get away with in our environment ... you may not have that luxury).
Does pre-installing the HP/Ricoh/other vendor universal print drivers on the WVD host (instead of something from Windows Update) and / or changing the "Specify RD Session Host Server fallback printer driver behavior" GPO to "do nothing" make a difference? (not sure if either is an option in your environment ... but could potentially help prevent terminal services print driver installation bloat)
Hi,
Thanks for your reply. I'm just testing different drivers in the lab. The HP Universal Printer may be the answer as I've just tested using that with two printers and it doesn't add any entries to PnpLockdownFiles at all. I only have 40 users with 12 printers, the only difference is that all users have all 12 printers mapped as they move about.
I don't think I can recover the machines as its in Azure and won't be able to boot into PE to delete and compress the registry.
This issue has caught me by surprise.
Thanks for your reply. I'm just testing different drivers in the lab. The HP Universal Printer may be the answer as I've just tested using that with two printers and it doesn't add any entries to PnpLockdownFiles at all. I only have 40 users with 12 printers, the only difference is that all users have all 12 printers mapped as they move about.
I don't think I can recover the machines as its in Azure and won't be able to boot into PE to delete and compress the registry.
This issue has caught me by surprise.