Software bricking

❗Article Status Notice: This Article is a stub

---

This article is underdeveloped, and needs additional work to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. Learn more ▼

Issues may include:

• This article needs to be expanded to provide meaningful information
• This article requires additional verifiable evidence to demonstrate systemic impact
• More documentation is needed to establish how this reflects broader consumer protection concerns
• The connection between individual incidents and company-wide practices needs to be better established
• The article is simply too short, and lacks sufficient content

How you can help:

• Add documented examples with verifiable sources
• Provide evidence of similar incidents affecting other consumers
• Include relevant company policies or communications that demonstrate systemic practices
• Link to credible reporting that covers these issues
• Flesh out the article with relevant information

This notice will be removed once the article is sufficiently developed. Once you believe the article is ready to have its notice removed, please visit the Moderator's noticeboard, or the Discord (join here) and post to the #appeals channel, or mention its status on the article's talk page.

A piece of software being referred to as "bricked" simply means the program has been rendered unusable. Software bricking is a malicious practice in which a company revokes user access to a previously purchased product in order to pressure the consumer to make another purchase. This anti consumer practice is a common way for companies to attempt to increase their sales.

Why this is a problem

Software bricking is a problematic practice as it allows issuers of software to revoke user access to their software for any reason. Software distribution companies can and have used this practice to encourage consumers to purchase the newer version of the software.

See Also

• DRM