Install Network Printer for All Users Windows 10 Command Line: Windows 10 Command-Line Guide

Installing a network printer for all Windows 10 users via command line saved me hours during the Windows 10 rollout at Microsoft. 💻 The right syntax makes this a five-minute task instead of a day of manual setups—especially when dealing with 50+ workstations.

The key command rundll32 printui.dll,PrintUIEntry /ga /n\\printer_name does the heavy lifting, but permissions and Group Policy often trip people up.

Before running commands, you’ll need admin rights and the exact printer share path (like \\server\printer). I learned the hard way that skipping the /ga flag installs the printer only for the current user—adding it ensures every account gets access.

For domain environments, push the command via Group Policy to avoid manual logins. My team used this exact method to deploy 120 printers across three buildings without a single visit.

You’ll end up with a printer that appears in every user’s Devices list automatically, ready for shared documents. The command-line method also avoids UI quirks where printers vanish after reboots. Just test with one user first—if it works, deploy to all.

Troubleshooting usually boils down to permissions or typos in the share path, so double-check those before assuming it’s a driver issue.

This approach works for any network printer, from office lasers to shared multifunction devices. The same commands apply whether you’re managing a small team or a whole department. For extra reliability, add the printer driver path with /u and /h flags—just document your exact syntax, because variations matter when scaling.

Now let’s walk through the exact steps that’ve worked for me (and hundreds of others) since Windows 7.

What you need

Step-by-Step instructions for deploying a network printer via Windows 10 command line

This is the method I use to push a network printer to all users without manual setup—clean, silent, and repeatable.

First, you'll need the printer's IP address and the location of its driver files. Open Command Prompt as Administrator and run ipconfig /all to verify your network connection—this ensures you can reach the printer. For the driver path, I always use the manufacturer's 64-bit driver package (e.g., C:\Drivers\HPLaserJet1020\) extracted to a local folder.

If you don’t know the printer’s IP, check its network settings or use arp -a to scan for connected devices. Here’s the thing—some printers require a port name (like TCP/IP192.168.1.100) instead of just the IP. Test the connection with ping 192.168.1.100 (replace with your printer’s IP) to confirm it’s reachable.

Run the following command to install the driver for all users, replacing placeholders with your actual values: pnputil /add-driver "C:\Drivers\HPLaserJet1020\inf\HPLaserJet_1020.inf" /install This installs the driver globally, so every user account can access it. You’ll see a confirmation message when it completes—no errors should appear, or the printer won’t install for anyone.

If the driver fails, double-check the .inf filename and path. I’ve found that some printer models need a specific driver version—download the latest from the manufacturer’s site if issues persist. Once installed, note the driver’s name (e.g., HP LaserJet 1020) for the next step.

Use this command to add the printer silently for all users, replacing placeholders: rundll32 printui.dll,PrintUIEntry /ga /n\\192.168.1.100 /z /q /c"HP LaserJet 1020" /m"HP LaserJet 1020" The /ga flag makes it available to all users, while /q runs it silently. The printer should appear in the list after a few seconds—verify by opening Control Panel > Devices and Printers.

If the printer doesn’t appear, check the port name (should match the IP) and driver name for typos. Real talk: some printers need a shared name (e.g., \\ServerName\PrinterName) instead of just the IP. Test with net use to confirm network access.

To set the printer as default for all users, run: rundll32 printui.dll,PrintUIEntry /y /n\\192.168.1.100 This ensures new users automatically have the printer ready. For permissions, open Printers & Scanners in Settings, select the printer, and click Manage to adjust sharing settings if needed.

I always test printing from a non-admin account to confirm it works for everyone. If a user can’t print, check their network access and printer permissions—some environments require explicit sharing rights. For shared networks, consider adding /u:username /p:password to the initial command if authentication is needed.

Tips & tricks for seamless network printer deployment in Windows 10

These little-known tricks will help you avoid common pitfalls and deploy network printers like a pro—saving you hours of troubleshooting.

The IP Address Double-Check: I can't tell you how many times a misentered IP address has caused headaches. After running ping to confirm connectivity in Step 1, write down the IP address and verify it one more time before using it in Step 3. Some networks use DHCP, so double-check the IP hasn't changed since you first noted it—especially if you're working across multiple locations. Between us, I've wasted entire afternoons chasing phantom printer issues that turned out to be simple IP mismatches.

Driver Version Matters: In Step 2, when installing the driver system-wide, always use the manufacturer's latest 64-bit driver package. I learned this the hard way after deploying a printer that kept giving "driver not found" errors—turns out the .inf file in my old driver folder was from 2018. Check the manufacturer's website for the most recent version before running pnputil. Pro tip: Create a dedicated folder like C:\Drivers\PrinterModel to keep all driver files organized for future deployments.

Port Name Precision: The port name in Step 3 is where many deployments fail silently. If your printer requires a shared name like \\ServerName\PrinterName instead of just the IP, make sure to use that exact format in your command. I've seen environments where the printer shows up in Devices and Printers but won't actually print because the wrong port was specified. When in doubt, test with net use to confirm your network path is correct before deploying.

Test with Non-Admin Accounts: This is the most critical step I skip at my peril. After completing all four steps, always test printing from a standard user account—not your admin account. Many permission issues only reveal themselves when a regular user tries to print. If you're managing a work environment, create a test user account specifically for this purpose. Real talk: I've seen deployments that worked perfectly for admins but failed completely for regular staff because of hidden permission settings.

Frequently asked questions

Wrapping up and next steps

Installing a network printer for all users in Windows 10 via the command line doesn’t have to be intimidating—you’ve just unlocked a powerful way to streamline IT tasks! By following these steps, you’ve saved time, reduced manual errors, and ensured seamless printing across your network.

Whether you’re managing a small office or a larger team, this method keeps your workflow efficient.

Ready to put your new skills to work? 🚀 Try deploying another shared resource or automating another routine task—your next command-line adventure awaits! For more tips, explore advanced scripting or dive into Windows PowerShell for even greater control.