“We Can’t Install This Printer at the Moment” Error 740

Windows logo

Short answer: error #740 means Windows needs administrator rights to install the printer’s driver, and the person adding the printer is a standard user. Since the PrintNightmare security fixes, Windows no longer lets standard users install drivers from a print server. Have an administrator install the driver on the computer once, then the user can add the shared printer without the error.

An industrial business contacted us because one of their engineers could not add two shared label printers from the office print server to his laptop. Each time he clicked Add device, Windows said it could not install the printer at the moment, with error #740. The same thing had happened on the same laptop a few months earlier, and a technician had installed the printers by hand. That had worked around the problem without fixing it. This time we found the exact step that was failing in the Windows print logs, installed the driver on the laptop as an administrator, and both printers connected. Here is what we found and how to fix it.

Fixed by Kenn Cruz, IT Support Specialist at GCIT. Written up by Elliot Munro, CISO.

Symptoms

When you add a shared printer from a print server in Settings > Bluetooth & devices > Printers & scanners, or by double-clicking it on the server, a blue window titled “That didn’t work” appears:

We can’t install this printer at the moment. Try again later or contact your network administrator for help.
Error: #740

Windows error: That didn't work. We can't install this printer at the moment. Try again later or contact your network administrator for help. Error #740

Other signs:

  • The printer appears in the list with an Add device button, but adding it fails every time.
  • An administrator can add the same printer on the same computer without any problem.
  • Other printers that are already installed keep working.
  • In Event Viewer, Applications and Services Logs > Microsoft > Windows > PrintService > Admin shows Event ID 600: “The print spooler failed to import the printer driver that was downloaded from \\server\print$\… into the driver store”, with error code 800702e4.

Error 800702e4 is the long form of Windows error 740, “The requested operation requires elevation”. People also search for this as “printer error 740”, “0x000002e4 printer”, “can’t add network printer as standard user” or “Point and Print requires administrator”.

Affected Software

  • Operating System: Windows 10 and Windows 11 clients
  • Servers: Windows Server print servers sharing printers through Point and Print
  • Related Services: Print Spooler, Point and Print and Package Point and Print, printer driver packages

Cause

When you connect to a shared printer, Windows downloads the printer’s driver from the print server and installs it on your computer. This is called Point and Print. In 2021, after a series of print spooler vulnerabilities known as PrintNightmare, Microsoft changed the default so that installing a printer driver through Point and Print requires administrator rights. This is controlled by the RestrictDriverInstallationToAdministrators setting, which is on by default.

Most staff use standard accounts, which is good security practice. So if the driver for a shared printer is not already on their computer, the install fails. Windows 11 shows this as error #740, because the step that imports the driver into the Windows driver store needed elevation.

In our customer’s case, Point and Print had already been relaxed on that laptop and it still failed, because the driver arrived as a signed driver package and staging that package still asked for elevation. The reliable fix was to put the driver on the laptop as an administrator first.

Resolution

  1. Sign in to the computer with an administrator account, or ask your IT provider to connect.
  2. Add the shared printer while signed in as the administrator. This installs the driver into the computer’s driver store. Remove the printer again afterwards if you do not want it for the admin account.
  3. Alternatively, install the driver directly. Copy the driver files from the manufacturer or from the print server, then in an elevated Command Prompt run pnputil /add-driver "C:\Drivers\Printer\driver.inf" /install, and in PowerShell run Add-PrinterDriver -Name "Exact Driver Name". The driver name must match the name used on the print server exactly.
  4. Sign back in as the user and add the shared printer again. Because the driver is already installed, Windows only needs to create the connection, which a standard user can do.
  5. Print a test page to confirm.

Option 2: Deploy printers and drivers centrally

  1. Use Microsoft Intune, Group Policy or your remote management tool to install the printer driver on every computer that needs it, running as the system account.
  2. Deploy the printer connection itself the same way, for example with a Group Policy printer preference, or the command printui /ga /n"\\printserver\PrinterName" to add it for all users of that computer.
  3. Keep the driver version on the computers the same as the version on the print server. A mismatch makes Windows try to download the server’s driver again, and the error returns.

Option 3: Universal Print or a cloud print service

If you are replacing an ageing print server, Microsoft Universal Print and similar cloud print services remove Point and Print from the picture, because users add printers without downloading drivers from a server.

Important Notes

  • Do not turn the PrintNightmare protection off. Microsoft states that no combination of other settings is as safe as leaving RestrictDriverInstallationToAdministrators on. Setting it to 0 lets standard users install drivers from print servers, which attackers can abuse. If you must change it to get through an urgent install, change it back straight afterwards.
  • Do not give users admin rights to fix printing. Install the driver for them instead.
  • It will come back on new computers. Any computer that has not had the driver installed will hit the same error. Add the driver to your standard build or deployment so new and rebuilt computers get it automatically.
  • Driver updates on the server can trigger it again. When you update a driver on the print server, update it on the computers too.

If you need help rolling out printers to staff without giving them admin rights, get in touch with our team.

Was this article helpful?
Ready to secure and simplify your IT? Talk to a GCIT expert today.