HP systemic DRM and firmware lockouts

⚠️ Article status notice: This article has been marked as incomplete

This article needs additional work for its sourcing and verifiability to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues.

This notice will be removed once sufficient documentation has been added to establish the systemic nature of these issues. Once you believe the article is ready to have its notice removed, please visit the Moderator's noticeboard, or the discord and post to the #appeals channel.

Learn more ▼

This Article Requires Additional Verification

---

This article has been flagged due to verification concerns. While the topic might have merit, the claims presented lack citations that live up to our standards, or rely on sources that are questionable or unverifiable by our standards. Articles must meet the Moderator Guidelines and Mission statement; factual accuracy and systemic relevance are required for inclusion here!

Why This Article Is In Question

---

Articles in this wiki are required to:

• Provide verifiable & credible evidence to substantiate claims.
• Avoid relying on anecdotal, unsourced, or suspicious citations that lack legitimacy.
• Make sure that all claims are backed by reliable documentation or reporting from reputable sources.

Examples of issues that trigger this notice:

• A topic that heavily relies on forum posts, personal blogs, or other unverifiable sources.
• Unsupported claims with no evidence or citations to back them up.
• Citations to disreputable sources, like non-expert blogs or sites known for spreading misinformation.

How You Can Improve This Article

---

To address verification concerns:

• Replace or supplement weak citations with credible, verifiable sources.
• Make sure that claims are backed by reputable reporting or independent documentation.
• Provide additional evidence to demonstrate systemic relevance and factual accuracy. For example:
  • Avoid: Claims based entirely on personal anecdotes or hearsay without supporting documentation.
  • Include: Corporate policies, internal communications, receipts, repair logs, verifiable video evidence, or credible investigative reports.

If you believe this notice has been placed in error, or once the article has been updated to address these concerns, please visit the Moderator's noticeboard, or the #appeals channel on our Discord server: Join here.

HP is widely recognized for applying digital rights management (DRM) measures to its consumer inkjet and laser printers, systematically blocking the use of third-party cartridges via firmware “dynamic security” updates. These updates have repeatedly disabled printers for users attempting to use non-HP branded consumables, and in some cases, even affected official HP cartridges after updates. Numerous class-action lawsuits have been filed against HP in multiple countries, and firmware updates continue to prompt large-scale consumer complaints, with users reporting unexpected cartridge rejections and device lockouts.

HP printers may block third-party cartridges via firmware “dynamic security,” causing systemic disruptions for consumers and prompting legal and media scrutiny.

HP's implementation of DRM restricting third-party ink cartridge use started in 2016. In that year, HP pushed a controversial firmware update that introduced "dynamic security" measures designed to block non-HP cartridges, causing widespread printer lockouts and cartridge rejections. This update was initially rolled out quietly and activated later, sparking public outcry, campaigns by the Electronic Frontier Foundation (EFF), and media coverage describing it as a DRM "time bomb." HP responded with optional firmware to disable these restrictions but continued to use DRM measures going forward.

In summary, HP began systematically locking printers to OEM cartridges with DRM firmware updates starting in 2016, a practice that continues to evolve but originated in that year.