---
title: "The PrintNightmare Threat and Lasernet Service"
slug: "the-printnightmare-threat-and-lasernet-service"
description: "Microsoft has published recommendations regarding the 'PrintNightmare' threat. Read for more information."
tags: ["Lasernet service", "Printnightmare"]
updated: 2026-03-05T11:33:48Z
published: 2026-03-05T11:33:48Z
canonical: "kb.lasernetgroup.com/the-printnightmare-threat-and-lasernet-service"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.lasernetgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The PrintNightmare Threat and Lasernet Service

**Applies to:** Lasernet 9, Lasernet Core 10

> [!NOTE]
> Note
> 
> This article describes a software version that is no longer supported. Although the software will no longer receive updates or technical support, existing documentation, such as this article, will be retained for reference purposes but will no longer be updated. If you have any questions, contact [Lasernet Support](https://support.lasernetgroup.com/new-ticket).

There have been some recent published recommendations from Microsoft regarding the **PrintNightmare** threat. This involves a Windows Print Spooler remote code execution vulnerability.

[https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-34527](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-34527)

Multiple components of Lasernet (beyond just the physical printing of documents) rely on the Print Spooler Service to be able to function successfully and so deactivating the Spooler Service means that the Lasernet server becomes unusable. If users deactivate the LPD service, the Lasernet server will not receive any jobs (from AS400, for example).

In summary, the Lasernet service depends on the Print Spooler Service to function, so we recommend that it is not deactivated on the Lasernet server.

> [!NOTE]
> Update
> 
> This exploit has been patched on 21/09/2021 with patch **KB5005625**, any machine updated since then should not be affected by this vulnerability.