Consumer Rights Wiki - User contributions [en]

Age verification

2026-05-01T18:15:23Z

Charlie 6: Added operating system age verification category, added threat to FOSS with citations

{{Incomplete}}
{{See also|Forced identification|De-anonymization}}

'''[[wikipedia:Age_verification|Age Verification]]''' (AV), also referred to as '''Age Affirmation''' (AA) and '''Age gating''', is the process in where a business requires some form of identification to verify your age, a mass surveillance measure disguised as child safety to de-anonymize the internet. This is usually done for more explicit or mature content. This practice has been widely spreading since the [[UK Online Safety Act|UK's Online Safety Act (OSA)]] has passed; requiring all individuals to verify themselves before accessing mature content. Ways of checking age include, but are not limited to: checking for a valid credit card, facial age estimation tools, government-issued ID, biometric data, account history behavior, and more.

As of December 2025, 25 US States require websites with mature content to verify age.<ref>{{Cite web |title=State Age Verification Laws - Action Center |url=https://action.freespeechcoalition.com/age-verification-resources/state-avs-laws/ |url-status=live |access-date=2025-12-22 |archive-url=https://web.archive.org/web/20251228121257/https://action.freespeechcoalition.com/age-verification-resources/state-avs-laws/ |archive-date=2025-12-28 }}</ref>

Open-source intelligence (OSINT) reveals Meta Platforms spent $26.3 million on federal lobbying and funded a "grassroot" Digital Childhood Alliance group, with $0 to child safety<ref>{{Cite web |last=upper-up |date=2026-03-24 |title=Meta Platforms: Lobbying, Dark Money, and the App Store Accountability Act |url=https://github.com/upper-up/meta-lobbying-and-other-findings |url-status=live |archive-url=https://web.archive.org/web/20260413033424/https://github.com/upper-up/meta-lobbying-and-other-findings |archive-date=2026-04-13 |access-date=2026-05-02 |website=[[Github]]}}</ref>.

==How it works==

=== Online Platform Age Verification ===
When accessing a platform or website that may contain content not suitable for all audiences may force you to register for the platform along with verifying your age by one of the methods mentioned previously. Sites that likely don't use any form of account system will probably have a popup instead requiring you to verify your age before even serving the content you were trying to access.

=== Operating System Age Verification ===
New legislation now mandates [[wikipedia:Operating_system|operating systems (OS)]] to block the user until they verify their age. This is done "for convenience" so that apps and websites don't individually prompt the user, instead those apps/websites can just query the platform (e.g. OS, web-browser, etc...) without the user noticing.

==Why is this a problem?==
The Online Safety Act is already exerting extraterritorial control through the age‑verification and validation changes it prompts, which are being implemented in the U.S. even though those companies customer bases are not at all subject to UK law, even Europeans that are also not under UK law are affected. This stems from the Act’s vague, overly broad language requiring companies to comply whenever users are located in the UK. Because the law effectively ignores national borders, non‑UK companies face only two options: geo‑block affected content for UK users or apply the same verification measures globally.

Geo‑blocking would severely disrupt services and business relationships that where already in place with UK customers before the Online Safety Act, so many companies choose to implement the changes for all users resulting in practical overreach beyond the UK. A reason for this is Ofcoms<ref>{{Cite web |date=2025-01-31 |title=What is Ofcom? |url=https://www.ofcom.org.uk/about-ofcom/what-we-do/what-is-ofcom |url-status=live |access-date=2026-04-07 |website=[[Ofcom]]}}</ref> statutory powers to require platforms to use “accredited technology” to detect illegal content. As such systems would have to be implemented onto all the content this again would be an overreach of their precieved authorities. Companys that do not comply are already beeing fined for this.

Even if the UK Government has “paused” its demand for implementing “accredited technologys” there is no practical way to meet the vague requirement set out by Ofcom in the Online Safety Act. The proposal ignores that smaller companies would likely be forced to close under the financial burden of compliance, producing a sterilized market with reduced competition only firms with deep pockets can comply. That still does not prevent Ofcom from fining companies that fail to comply.

Examples:

Webpage 4chan<ref>{{Cite web |date=2025-06-10 |title=Investigation into 4chan and its compliance with duties to protect its users from illegal content |url=https://www.ofcom.org.uk/online-safety/illegal-and-harmful-content/investigation-into-4chan-and-its-compliance-with-duties-to-protect-its-users-from-illegal-content |url-status=live |website=[[Ofcom]]}}</ref>

AVS GROUP LIMITED<ref>{{Cite web |date=2025-07-31 |title=Investigation into AVS Group Ltd’s compliance with the duty to prevent children from encountering pornographic content through the use of age assurance |url=https://www.ofcom.org.uk/online-safety/protecting-children/investigation-into-avs-group-ltds-compliance-with-the-duty-to-prevent-children-from-encountering-pornographic-content-through-the-use-of-age-assurance |url-status=live |website=[[Ofcom]]}}</ref>

The provider of Im.ge<ref>{{Cite web |date=2025-06-10 |title=Investigation into the provider of Im.ge and its compliance with duties to protect its users from illegal content |url=https://www.ofcom.org.uk/online-safety/illegal-and-harmful-content/investigation-into-the-provider-of-im.ge-and-its-compliance-with-duties-to-protect-its-users-from-illegal-content |url-status=live |website=[[Ofcom]]}}</ref>

Youngtek Solutions Ltd<ref>{{Cite web |date=2025-09-11 |title=Investigation into Youngtek Solutions Ltd’s compliance with the duty to prevent children from encountering pornographic content through the use of age assurance |url=https://www.ofcom.org.uk/online-safety/protecting-children/investigation-into-youngtek-solutions-ltds-compliance-with-the-duty-to-prevent-children-from-encountering-pornographic-content-through-the-use-of-age-assurance |url-status=live |website=[[Ofcom]]}}</ref>

===Customer Profiling===
Having companies easily able to identify you means they can track you more efficiently and sell that shared profile to other companies such as ad agencies that then start targeting you specifically. Age data stored in a computer's operating system is another data being used for device fingerprinting<ref>{{Cite web |last=Costa |first=C. da |date=2026-03-16 |title=Reddit User Uncovers Who Is Behind Meta’s $2B Lobbying for Invasive Age Verification Tech |url=https://www.gadgetreview.com/reddit-user-uncovers-who-is-behind-metas-2b-lobbying-for-invasive-age-verification-tech |url-status=live |archive-url=https://web.archive.org/web/20260415225107/https://www.gadgetreview.com/reddit-user-uncovers-who-is-behind-metas-2b-lobbying-for-invasive-age-verification-tech |archive-date=2026-04-15 |access-date=2026-05-01 |website=Gadget Review}}</ref>.

===Government overreach===
Governments can also more easily track online movements and find out who you are. Saying something that may go against their own agenda may end up with a police raid, heavy interrogation, and prison time.<ref>{{Cite news |last=Liu |first=John |date=2025-06-20 |title=China tightens internet controls with new centralized form of virtual ID |url=https://edition.cnn.com/2025/06/20/tech/china-censorship-internet-id-hnk-intl#:~:text=%E2%80%9CThis%20is%20a%20state%2Dled,an%20infrastructure%20of%20digital%20totalitarianism.%E2%80%9D |access-date=2025-09-04 |work=CNN |archive-url=https://web.archive.org/web/20250620233250/https://edition.cnn.com/2025/06/20/tech/china-censorship-internet-id-hnk-intl |archive-date=2025-06-20 }}</ref>

===Censorship===
Certain topics, such as adult content, politics, and LGBT+ topics, will likely be unfairly censored by the governing body or company that has a say on what platform has the '''potential''' to be inappropriate for minors or other age groups.<ref>{{Cite web |date=2025-09-01 |title=Strict Age Verification Laws: Balancing Content Restriction and Educational Rights |url=https://www.thinkacademy.ca/blog/strict-age-verification-laws-impact-k12-education/#:~:text=Impact%20on%20K12,affect%20these%20groups |access-date=2025-09-04 |website=Think Academy |archive-url=https://web.archive.org/web/20251018030711/https://www.thinkacademy.ca/blog/strict-age-verification-laws-impact-k12-education/ |archive-date=2025-10-18 }}</ref><ref name=":0">{{Cite web |last=Kelley |first=Jason |last2=Mackey |first2=Aaron |last3=Mullin |first3=Joe |date=2024-02-15 |title=Don’t Fall for the Latest Changes to the Dangerous Kids Online Safety Act |url=https://www.eff.org/deeplinks/2024/02/dont-fall-latest-changes-dangerous-kids-online-safety-act |access-date=2025-09-04 |website=Electronic Frontier Foundation |archive-url=https://web.archive.org/web/20240215234054/https://www.eff.org/deeplinks/2024/02/dont-fall-latest-changes-dangerous-kids-online-safety-act |archive-date=2024-02-15 }}</ref>

Platforms that host this type of content may also be more proactive in deleting/hiding posts that may get them in trouble or fined by laws or policies by local governments, leading to a more censored internet where opinions are streamlined to fit a set narrative or outlook.<ref name=":0" />

===Increased inequality and denial of service===
Some stores, such as grocery stores, prohibit young people from viewing their web sites or using [[loyalty cards]], which provide discounts and digital coupons. Age verification means that young people and families where the young person does the shopping pay more for essentials like food.<ref>{{Cite news |last=Pell |first=Miranda |date=25 Oct 2024 |title=Tesco, Lidl and Sainsbury's shoppers issued warning over little-known 'age limit' rules |url=https://www.manchestereveningnews.co.uk/whats-on/shopping/tesco-lidl-sainsburys-shoppers-issued-30233318 |access-date=20 Sep 2025 |work=Manchester evening news |archive-url=https://web.archive.org/web/20251021121644/https://www.manchestereveningnews.co.uk/whats-on/shopping/tesco-lidl-sainsburys-shoppers-issued-30233318 |archive-date=2025-10-21 }}</ref> Those who do not have ID, or do not chose to use it (for instance, those who fear domestic violence, or are members of a group subject to persecution) may also be locked out or have to pay more.

===Storage of private and biometric Information by age verification service providers===
A study commissioned by the Australian government found that age verification service providers accumulate a concerning amount of personal information, sometimes even biometric in nature, even when that was not necessary to provide the age verification service.<ref>{{Cite web |last=Meineck |first=Sebastian |date=2025-09-03 |title=Anbieter von Alterskontrollen horten biometrische Daten [Age Verification Providers are hoarding biometric Data] |url=https://netzpolitik.org/2025/australisches-gutachten-anbieter-von-alterskontrollen-horten-biometrische-daten/ |access-date=2025-09-03 |website=Netzpolitik.org |archive-url=https://web.archive.org/web/20250903115436/https://netzpolitik.org/2025/australisches-gutachten-anbieter-von-alterskontrollen-horten-biometrische-daten/ |archive-date=2025-09-03 }}</ref><ref>{{Cite web |last=Meineck |first=Sebastion |date=2025-09-03 |title=Anbieter von Alterskontrollen horten biometrische Daten [Google Translate English Version] |url=https://netzpolitik-org.translate.goog/2025/australisches-gutachten-anbieter-von-alterskontrollen-horten-biometrische-daten/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp |access-date=2025-09-03 |website=Netzpolitik.org |archive-url=https://web.archive.org/web/20251023063119/https://netzpolitik-org.translate.goog/2025/australisches-gutachten-anbieter-von-alterskontrollen-horten-biometrische-daten/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp |archive-date=2025-10-23 }}</ref>

===Driving users towards smaller and completely unregulated offerings===
Big platforms can be regulated and forced to comply with applicable laws since they need to have infrastructure such as servers in all major markets. Only these will be affected by the age restriction requirement.

However, users who do not wish to compromise their privacy or who are not of age will then go looking towards smaller niche platforms, often in other regions not affected by the regulation or the [[wikipedia:Darknet|darknet]].<ref name=":1">{{Cite web |last=Kaleta |first=Miroslav |date=2025-08-20 |title=The Cost of Data Privacy Negligence (And How to Avoid It) |url=https://countly.com/blog/data-privacy-negligence#:~:text=2.%20Losing%20Customer,IBM%20Report. |url-status=live |archive-url=http://web.archive.org/web/20251217003447/https://countly.com/blog/data-privacy-negligence |archive-date=17 Dec 2025|access-date=2025-09-04 |website=Countly Blog}}</ref> With these offerings, there is little to no leverage with regards to removal of illegal content. Increased exposure to illegal content can then lead to both a strengthening of illegal content providers<ref>{{Cite web |last=Branley |first=Dawn |last2=Covey |first2=Judith |date=2016-06-06 |title=Is exposure to online content depicting risky behavior related to viewers' own risky behavior offline? |url=https://www.sciencedirect.com/science/article/pii/S0747563217303357 |url-status=live |archive-url=https://web.archive.org/web/20220403233150/https://www.sciencedirect.com/science/article/pii/S0747563217303357 |archive-date=2022-04-03 |access-date=2025-09-04 |website=ScienceDirect}}</ref> and significantly increased danger to minors, who may not yet be able to differentiate between legal and illegal content as well as an adult.<ref>{{Cite web |date= |title=Potential risks of content, features, and functions: The science of how social media affects youth |url=https://www.apa.org/topics/social-media-internet/youth-social-media-2024 |url-status=live |archive-url=https://web.archive.org/web/20240416042251/https://www.apa.org/topics/social-media-internet/youth-social-media-2024 |archive-date=2024-04-16 |access-date=2025-09-04 |website=American Psychological Association}}</ref> 

===Increased damage from data breaches===
Platforms which implement age checks that require sensitive information such as a government-issued ID will likely be more of a target for cyber criminals.<ref>{{Cite web |date=2025-04-02 |title=Cybercriminals Target These Industries the Most – Here’s Why and How to Stay Safe |url=https://brandefense.io/blog/cybercriminals-target-these-industries/#:~:text=The%20Most%20Vulnerable%20Industries%20to,information%20stored%20within%20their%20networks. |url-status=live |archive-url=http://web.archive.org/web/20260119030330/https://brandefense.io/blog/cybercriminals-target-these-industries/ |archive-date=19 Jan 2026|access-date=2025-09-04 |website=Brandefense}}</ref> As more platforms comply with the age checks, it becomes more likely that a data breach on at least one of these platforms can reveal extremely sensitive information. In the case of a data breach, it can be catastrophic if users' sensitive information were exposed, which can likely result in identity theft.<ref>{{Cite web |last=Popov |first=Cristina |date=2023-03-22 |title=Why breaches can affect you long after they occur |url=https://www.bitdefender.com/en-us/blog/hotforsecurity/why-breaches-can-affect-you-long-after-they-occur#:~:text=%232%3A%20Breaches%20can,for%20online%20accounts. |url-status=live |archive-url=http://web.archive.org/web/20260104220250/https://www.bitdefender.com/en-us/blog/hotforsecurity/why-breaches-can-affect-you-long-after-they-occur |archive-date=4 Jan 2026|access-date=2025-09-04 |website=Bitdefender}}</ref>

Platforms already experience major losses and consumer distrust from data breaches that reveal information less sensitive than government-issued IDs or biometric data.<ref name=":1" /> A data breach involving information this sensitive will seriously damage a business, and the users even more so. As stated previously, users who foresee these privacy risks will turn away from platforms which implement the policy, and towards niche platforms.

===Inaccuracy===
Researches about age verification software that estimates age via face scans are inaccurate, identifying children as adults or vice versa. These inaccurate estimations might lead to have to use more privacy-invasive methods like submitting a picture of a personal ID. {{Citation needed}}

=== Threat to Free and Open Source Software (FOSS) ===
Age verification, especially identity verification, are fundamentally incompatible with the four essential freedoms of free software<ref>{{Cite web |date=2026-01-28 |title=What is Free Software? |url=https://www.gnu.org/philosophy/free-sw.html |url-status=live |archive-url=https://web.archive.org/web/20260426185514/https://www.gnu.org/philosophy/free-sw.html |archive-date=2026-04-26 |access-date=2026-05-01 |website=GNU Operating System}}</ref>. Legislation that mandates nationwide operating system age verification could outlaw GNU/Linux, consolidating monopolistic power to proprietary operating systems<ref>{{Cite web |last=Trevino |first=Sam |date=2026-03-06 |title=Age Assurance Laws and the End of General Purpose Computing |url=https://samtrevino.substack.com/p/age-assurance-laws-and-the-end-of |url-status=live |archive-url=https://archive.org/details/age-assurance-laws-and-the-end-of-general-purpose-computing-report |archive-date=2026-03-11 |access-date=2026-05-01}}</ref>.

==Examples==
*[[YouTube age verification|YouTube's age verification]] and account estimation algorithm.

*[[Spotify]]'s Age affirmation for MA rated songs and content.

*[[Discord's Mandatory Age Verification|Discord's age verification]] for accounts determining what eligible servers are available.

*[[Roblox#ID & face scan age verification|Roblox's age verification]] and account estimation algorithm for talking with users of similar age.

==External links==

*[https://agelesslinux.org/distros.html Ageless Linux — Distro Compliance Tracker]
*[https://github.com/BryanLunduke/DoesItAgeVerify GitHub BryanLunduke - List Tracking Operating Systems Not Implementing Age Verification]
*[https://www.eff.org/pages/age-verification-bills-are-unconstitutional EFF explains how OS-level age-verification is unconstitutional]
*[https://www.congress.gov/bill/119th-congress/house-bill/8250/all-info All Information (Except Text) for H.R.8250 - Parents Decide Act]

==See also==

*[[Chat Control]]

==References==
{{reflist}}

[[Category:Common terms]]

Forced BIOS firmware update

2026-04-03T03:55:12Z

Charlie 6: added two feature removal with sources

Basic Input/Output System, also known as BIOS, is a type of firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process (power-on startup)<ref>{{Cite web |last=Kozierok |first=Charles M |date=2001-04-17 |title=Ref — System BIOS |url=https://www.pcguide.com/ref/mbsys/bios/index.htm |url-status=dead |archive-url=https://web.archive.org/web/20190218194254/https://www.pcguide.com/ref/mbsys/bios/index.htm |archive-date=2019-02-18 |access-date=2025-12-18 |website=The PC Guide}}</ref>.

Generally speaking, a working computer's BIOS doesn't need to be updated frequently due to the instinct risk of BIOS flashing<ref>{{Cite web |date=2025-04-12 |title=FlashBIOS |url=https://wiki.debian.org/FlashBIOS |url-status=live |access-date=2025-12-31 |website=Debian Wiki |archive-url=http://web.archive.org/web/20251118135550/https://wiki.debian.org/FlashBIOS |archive-date=18 Nov 2025}}</ref><ref>{{Cite web |date=2025-12-12 |title=Flashing BIOS from Linux |url=https://wiki.archlinux.org/title/Flashing_BIOS_from_Linux |url-status=live |access-date=2025-12-31 |website=ArchWiki |archive-url=http://web.archive.org/web/20260218024432/https://wiki.archlinux.org/title/Flashing_BIOS_from_Linux |archive-date=18 Feb 2026}}</ref>. However more and more mainstream computer manufactures starts pushing BIOS updates, often without user's consent or against the user's will, causing more issues and paves the way of controlling the device further.

==How it works==

===Pushing the BIOS update as non-optional Windows Update===
Traditionally, BIOS updates are done via a USB stick, which contains a FAT32 partition with bootloader and BIOS content. Recently the BIOS firmware is listed under Windows driver updates. Nowadays these updates are no longer under the "optional" category<ref>{{Cite web |last=@fec32a4de |date=2025-11-19 |title=How do I prevent Windows update from updating BIOS |url=https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |url-status=live |archive-url=https://web.archive.org/web/20251218145243/https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref><ref name=":0">{{Cite web |last=@redxps630 |date=2022-07-16 |title=how to prevent Windows Update from updating your bios |url=https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |url-status=live |archive-url=https://web.archive.org/web/20231021113238/https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |archive-date=2023-10-21 |access-date=2023-10-21 |website=Dell Community}}</ref>.

===Blocking BIOS downgrade===
In some computer models and BIOS versions, downgrade is blocked or "unsupported"<ref name=":1">{{Cite web |last=@ronyh |first= |date=2022-11-23 |title=BIOS Update blocked due to unsupported downgrade |url=https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |url-status=live |archive-url=https://web.archive.org/web/20240225053720/https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |archive-date=2024-02-25 |access-date=2025-12-18 |website=Dell Community}}</ref>, preventing the user from regaining lost functionalities.

===Removal of previous BIOS download link===

==Why it is a problem==

===Retroactive removal of functionalities===
Here's a non-exclusive list of removed functionalities:

*ACPI S3 sleep state<ref name=":2">{{Cite web |last=@mcgrubhub |date=2022-01-24 |title=Enable S3 Sleep State in BIOS Firmware Options |url=https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |url-status=live |archive-url=https://web.archive.org/web/20251218153346/https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |archive-date=2025-12-18 |access-date=2025-12-18 |website=HP Community}}</ref>, also known as "deep" sleep or "suspend-to-RAM"
*Undervolting<ref name=":3">{{Cite web |last=@u/DarkKnight04081995 |date=2020-11-17 |title=[GUIDE] Inspiron 7567: Bios downgrade from v1.12.1 to v1.11.0 |url=https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |url-status=live |archive-url=https://web.archive.org/web/20251218154156/https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, a method of reducing power consumption without decreasing performance
*CPU thermal design power (TDP)<ref name=":4">{{Cite web |last=@eXplode |date=2024-12-18 |title=How to Stop Automatic BIOS Updates and some hate for BIOS 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |url-status=live |archive-url=https://web.archive.org/web/20251002181913/https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |archive-date=2025-10-02 |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>
*Fan control.<ref>{{Cite web |last=@Mell |date=2025-10-04 |title=G713qm fan problem bios 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/g713qm-fan-problem-bios-331/td-p/1118443 |url-status=live |access-date=2025-12-18 |website=Republic of Gamers Forum |archive-url=http://web.archive.org/web/20251117101016/https://rog-forum.asus.com/t5/rog-strix-series/g713qm-fan-problem-bios-331/td-p/1118443 |archive-date=17 Nov 2025}}</ref>

===Reduced reliability/Planned obsolescence===
[[File:Asus bat chg v low.png|thumb|216x216px|Asus lowered the battery charging voltage to less than 16.6V, despite its 17.6V limited charging voltage.]]
Users reporting increased coil whine after a certain BIOS update<ref>{{Cite web |last=@ tom.m.culle150a02ca |date=2024-01-12 |title=Coil whine after bios update |url=https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |url-status=live |archive-url=https://web.archive.org/web/20251218183546/https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=MSI Global English Forum}}</ref>, possibly reducing reliability and increasing the failure rate.

Due to its unpredictable and forced nature, uncommanded BIOS updates have a higher chance of bricking the computer<ref name=":5">{{Cite web |last=@Parts-People Dell Laptop Experts |date=2025-11-02 |title=New Day, Another Bricked Laptop From Windows Update! |url=https://www.youtube.com/watch?v=8tRSjfFBtME |url-status=live |access-date=2025-12-18 |website=[[YouTube]] |archive-url=https://preservetube.com/watch?v=8tRSjfFBtME |archive-date=23 Feb 2026}}</ref>, such as interrupted BIOS update in the user's backpack due to over-temperature or battery depletion.

On some laptops, the battery capacity is restricted by reducing the charging voltage after a BIOS update, causing premature battery endurance decline. This practice is similar to [[Google Pixel 6a Battery Performance Program]] but without official announcement.

===Undermining ownership===
Manufacturers who force BIOS update often claim that blocking downgrade as "security features" to stop "bad player" from accessing the BIOS<ref name=":1" />. This is a classic example of "secure against the user"<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html#universal |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>.

==Examples==
[[File:Alienwarebiosrollback.png|thumb|From a comment on a laptop repair video<ref>{{Cite web |last=@Parts-People Dell Laptop Experts |date=2024-12-28 |title=Laptop Destroyed By Windows Update {{!}} Make It Stop! Microsoft |url=https://www.youtube.com/watch?v=pvhUPIkKt1s |url-status=live |access-date=2025-12-31 |website=[[YouTube]]}} ([https://preservetube.com/watch?v=pvhUPIkKt1s Archived])</ref>, a Dell user had to roll back a forced BIOS update to restore GPU performance.]]
These examples are non-exhaustive, some known instances are currently not listed due to insufficient source(s). All the examples below have BIOS update as non-optional Windows Update.

===Dell===
Blocked downgrade<ref name=":1" />, disabled ACPI S3 sleep state<ref>{{Cite web |last=okwei |date=2018-08-08 |title=XPS 15-9570, BIOS 1.3.0, sleep mode gone? |url=https://www.dell.com/community/en/conversations/xps/xps-15-9570-bios-130-sleep-mode-gone/647f7bd2f4ccf8a8dea1c8d4 |url-status=live |archive-url=https://web.archive.org/web/20241201142957/https://www.dell.com/community/en/conversations/xps/xps-15-9570-bios-130-sleep-mode-gone/647f7bd2f4ccf8a8dea1c8d4 |archive-date=2024-12-01 |access-date=2026-04-02 |website=Dell Community}}</ref>, removed undervolting<ref name=":3" /><ref>{{Cite web |last=@WorldDj |date=2020-09-20 |title=Another victim of the BIOS update unfortunately |url=https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |url-status=live |archive-url=https://web.archive.org/web/20251218173346/https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref>, removed previous BIOS download links<ref>{{Cite web |title=Driver unavailable |url=https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=c5jy9 |access-date=2025-12-18 |website=Dell Product Support}}</ref>.

===Asus===
[[File:Ec update bricked bms 1.png|thumb|224x224px|A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful]]
Reduced TDP<ref name=":4" />, blocked downgrade, bricked battery.

===HP===
Blocked RAM speed<ref>{{Cite web |last=@Gburns53 |date=2021-10-25 |title=Forced BIOS update |url=https://h30434.www3.hp.com/t5/Gaming-Desktops/Forced-BIOS-update/td-p/8198864 |url-status=live |archive-date=15 Feb 2026 |access-date=2025-12-28 |website=HP Community |archive-url=http://web.archive.org/web/20260215152218/https://h30434.www3.hp.com/t5/Gaming-Desktops/Forced-BIOS-update/td-p/8198864 }}</ref>, disabled ACPI S3 sleep state<ref name=":2" />, blocked downgrade.

===Lenovo===
Disabled ACPI S3 sleep state<ref>{{Cite web |last=@Matusaprod |date=2023-07-15 |title=Linux sleep mode on newer thinkpad missing? |url=https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |url-status=live |archive-url=https://web.archive.org/web/20251218181844/https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, added battery whitelist<ref>{{Cite web |last=@Bob297586 |date=2020-03-27 |title=Help with Lenovo thinkpad w530 battery whitelist |url=https://linustechtips.com/topic/1200330-help-with-lenovo-thinkpad-w530-battery-whitelist/ |url-status=live |access-date=2026-02-26 |website=Linus Tech Tips}}</ref><ref name=":6">{{Cite web |last=@OrganicBrian |date=2023-12-27 |title=Thinkpad T420 battery suddenly rejected by the laptop: could an update have caused this? |url=https://forums.linuxmint.com/viewtopic.php?t=409942 |url-status=live |access-date=2026-02-26 |website=Linux Mint Forums}}</ref><ref>{{Cite web |last=@Scorpion8 |date=2020-04-27 |title=Thinkpad Battery "Whitelist" ... how does it work? |url=https://thinkpads.com/forum/viewtopic.php?t=130513 |url-status=live |access-date=2026-02-26 |website=thinkpads.com Support Community}}</ref>, removed hardware codec<ref>{{Cite web |last=Rautio |first=Loki |date=2021-07-14 |title=Lenovo laptops silently stripped of important feature in BIOS updates |url=https://www.notebookcheck.net/Lenovo-laptops-silently-stripped-of-important-feature-in-BIOS-updates.550673.0.html |url-status=live |archive-url=https://web.archive.org/web/20250722091254/https://www.notebookcheck.net/Lenovo-laptops-silently-stripped-of-important-feature-in-BIOS-updates.550673.0.html |archive-date=2025-07-22 |access-date=2026-04-02 |website=Notebookcheck}}</ref>.

==Countermeasures==

===Disabling UEFI Encapsulation===
On some computer models, UEFI Encapsulation can be disabled in BIOS settings<ref name=":0" /><ref>{{Cite web |date=2023-04-30 |title=How to disable BIOS updates completely |url=https://old.reddit.com/r/Alienware/comments/133h83x/how_to_disable_bios_updates_completely/ |url-status=live |access-date=2026-02-26 |website=[[Reddit]]}}</ref>, disallowing the exchange of configuration data between the operating system and the UEFI firmware.

===Enabling "Do not include drivers with windows updates" in Group Policy===
Using Group Policy editor (gpedit.msc), users are able to exclude driver updates from Windows update<ref name=":0" /> since BIOS is often considered under drivers category. However, this method does not grantee success.

===Using a free operating system===
Free operating systems such as GNU/Linux respect user freedom. BIOS updates can be manually initiated using LVFS/fwupd. Although rare, it's not impossible for some Linux distributions to install BIOS updates automatically<ref name=":6" />.

===Board-level repair===
Flashing BIOS firmware on a bricked laptop can be done by using a custom programmer<ref name=":5" />.

===Non-BIOS mitigation methods===
Some functions can be re-enabled without downgrading BIOS. Advanced BIOS<ref>{{Cite web |last=@u/Dijkmeneer |date=2022-12-19 |title=How to disable Modern sleep and enable s3 sleep on a lenovo laptop |url=https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |url-status=live |archive-url=https://web.archive.org/web/20240520204041/https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |archive-date=2024-05-20 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, OpenCore<ref>{{Cite web |last=@MotorBottle |date=2023-10-01 |title=Enable S3 Sleep on ROG X13/G14/15 2021/2022 using OpenCore |url=https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |url-status=live |archive-url=https://web.archive.org/web/20250618061353/https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |archive-date=2025-06-18 |access-date=2025-12-19 |website=[[Github]]}}</ref>, Smokeless_UMAF<ref>{{Cite web |last=@DavidS95 |date=2023-05-07 |title=Bios Flasher? Where We’re Going, We Don’t Need Bios Flasher? |url=https://github.com/DavidS95/Smokeless_UMAF |url-status=live |archive-url=https://web.archive.org/web/20250925010047/https://github.com/DavidS95/Smokeless_UMAF/ |archive-date=2025-09-25 |access-date=2025-12-19 |website=[[Github]]}}</ref>.

==References==
{{reflist}}

[[Category:Common terms]]

Systemd adds age indication ahead of schedule

2026-03-21T03:35:53Z

Charlie 6: /* Consumer response */ fixed a source error

{{IncidentCargo
|Status=Active
|Product=Linux
|ArticleType=Product
|Type=Privacy
|Description=Systemd added age bracket ahead of schedule, the merge was quickly done while the revert attempt was blocked, with possible influence from Microsoft
}}systemd is criticized of being monolithic, non-modular and deviates from Unix philosophy<ref>{{Cite web |last=Russell |first=Sean E. |date=2025-07-30 |title=systemd really, really sucks |url=https://ser1.net/post/systemd-really,-really-sucks/ |url-status=live |archive-url=https://web.archive.org/web/20260214043401/https://ser1.net/post/systemd-really,-really-sucks/ |archive-date=2026-02-14 |access-date=2026-03-20}}</ref>.

==Background==
systemd is an initialization system, a suite of basic building blocks for a Linux system. It provides a system and service manager that runs as PID 1 and starts the rest of the system<ref>{{Cite web |date=2024-02-22 |title=systemd System and Service Manager |url=https://www.freedesktop.org/wiki/Software/systemd/ |url-status=live |archive-url=https://web.archive.org/web/20260106163143/https://www.freedesktop.org/wiki/Software/systemd/ |archive-date=2026-01-06 |access-date=2026-03-20 |website=freedesktop.org}}</ref>.

==[Incident]==
In Mar 5 2026, Dylan M. Taylor, a developer and tech enthusiast made two commits on systemd "userdb: add birthDate field to JSON user records", commenting<ref>{{Cite web |last=Taylor |first=Dylan M. |date=2026-03-19 |title=userdb: add birthDate field to JSON user records |url=https://github.com/systemd/systemd/pull/40954 |url-status=live |archive-url=https://web.archive.org/web/20260320055709/https://github.com/systemd/systemd/pull/40954 |archive-date=2026-03-20 |access-date=2026-03-20 |website=[[GitHub]]}}</ref><blockquote>Stores the user's birth date for age verification, as required by recent laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc.</blockquote>In Mar 19 2026, Luca Boccassi<ref>{{Cite web |title=Luca Boccassi |url=https://github.com/bluca |url-status=live |archive-url=https://web.archive.org/web/20260320172404/https://github.com/bluca |archive-date=2026-03-20 |access-date=2026-03-20 |website=[[GitHub]]}}</ref>, a member of Systemd and a Microsoft employee, merged the commit.

Lennart Poettering, the creator of systemd, known for having [[wikipedia:Lennart_Poettering#Controversies|controversial technical and architectural]] positions regarding the Linux ecosystem, has clarified that this change is:<blockquote>An optional field in the userdb JSON object. It's not a policy engine, not an API for apps. We just define the field, so that it's standardized if people want to store the date there, but it's entirely optional<ref>{{Cite web |last=Rudra |first=Sourav |date=2026-03-20 |title=Systemd’s New Feature Brings Age Verification Option to Linux |url=https://itsfoss.com/news/systemd-age-verification/ |url-status=live |archive-url=https://web.archive.org/web/20260320123152/https://itsfoss.com/news/systemd-age-verification/ |archive-date=2026-03-20 |access-date=2026-03-20 |website=It's FOSS}}</ref>.</blockquote>

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
Consumer response is mixed. Some says the age is manually entered so it doesn't affect privacy, others warn about the slippery slope and the potential to add national ID on system boot or installation. Users also point out Microsoft's influence over systemd<ref>{{Cite web |last=u/KestrelVO |date=2026-03-20 |title=Systemd’s New Feature Brings Age Verification Option to Linux |url=https://old.reddit.com/r/privacy/comments/1rz5zmh/systemds_new_feature_brings_age_verification/ |url-status=live |archive-url=https://web.archive.org/web/20260321032725/https://old.reddit.com/r/privacy/comments/1rz5zmh/systemds_new_feature_brings_age_verification/ |archive-date=2026-03-21 |access-date=2026-03-21 |website=[[Reddit]]}}</ref><ref>{{Cite web |last=u/ChamplooAttitude |first= |date=2026-03-20 |title=Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp. |url=https://old.reddit.com/r/privacy/comments/1rz8i4r/dylan_useful_idiot_with_commit_access_pushed_age/ |url-status=live |archive-url=https://web.archive.org/web/20260321005304/https://old.reddit.com/r/privacy/comments/1rz8i4r/dylan_useful_idiot_with_commit_access_pushed_age/ |archive-date=2026-03-21 |access-date=2026-03-21 |website=[[Reddit]]}}</ref>.

Users have been migrating to Artix Linux, Void Linux, Devuan and other systemd-free Linux distributions.

==References==
{{reflist}}

{{Ph-I-C}}

Systemd adds age indication ahead of schedule

2026-03-21T03:35:10Z

Charlie 6: added another source in Consumer response

{{IncidentCargo
|Status=Active
|Product=Linux
|ArticleType=Product
|Type=Privacy
|Description=Systemd added age bracket ahead of schedule, the merge was quickly done while the revert attempt was blocked, with possible influence from Microsoft
}}systemd is criticized of being monolithic, non-modular and deviates from Unix philosophy<ref>{{Cite web |last=Russell |first=Sean E. |date=2025-07-30 |title=systemd really, really sucks |url=https://ser1.net/post/systemd-really,-really-sucks/ |url-status=live |archive-url=https://web.archive.org/web/20260214043401/https://ser1.net/post/systemd-really,-really-sucks/ |archive-date=2026-02-14 |access-date=2026-03-20}}</ref>.

==Background==
systemd is an initialization system, a suite of basic building blocks for a Linux system. It provides a system and service manager that runs as PID 1 and starts the rest of the system<ref>{{Cite web |date=2024-02-22 |title=systemd System and Service Manager |url=https://www.freedesktop.org/wiki/Software/systemd/ |url-status=live |archive-url=https://web.archive.org/web/20260106163143/https://www.freedesktop.org/wiki/Software/systemd/ |archive-date=2026-01-06 |access-date=2026-03-20 |website=freedesktop.org}}</ref>.

==[Incident]==
In Mar 5 2026, Dylan M. Taylor, a developer and tech enthusiast made two commits on systemd "userdb: add birthDate field to JSON user records", commenting<ref>{{Cite web |last=Taylor |first=Dylan M. |date=2026-03-19 |title=userdb: add birthDate field to JSON user records |url=https://github.com/systemd/systemd/pull/40954 |url-status=live |archive-url=https://web.archive.org/web/20260320055709/https://github.com/systemd/systemd/pull/40954 |archive-date=2026-03-20 |access-date=2026-03-20 |website=[[GitHub]]}}</ref><blockquote>Stores the user's birth date for age verification, as required by recent laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc.</blockquote>In Mar 19 2026, Luca Boccassi<ref>{{Cite web |title=Luca Boccassi |url=https://github.com/bluca |url-status=live |archive-url=https://web.archive.org/web/20260320172404/https://github.com/bluca |archive-date=2026-03-20 |access-date=2026-03-20 |website=[[GitHub]]}}</ref>, a member of Systemd and a Microsoft employee, merged the commit.

Lennart Poettering, the creator of systemd, known for having [[wikipedia:Lennart_Poettering#Controversies|controversial technical and architectural]] positions regarding the Linux ecosystem, has clarified that this change is:<blockquote>An optional field in the userdb JSON object. It's not a policy engine, not an API for apps. We just define the field, so that it's standardized if people want to store the date there, but it's entirely optional<ref>{{Cite web |last=Rudra |first=Sourav |date=2026-03-20 |title=Systemd’s New Feature Brings Age Verification Option to Linux |url=https://itsfoss.com/news/systemd-age-verification/ |url-status=live |archive-url=https://web.archive.org/web/20260320123152/https://itsfoss.com/news/systemd-age-verification/ |archive-date=2026-03-20 |access-date=2026-03-20 |website=It's FOSS}}</ref>.</blockquote>

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
Consumer response is mixed. Some says the age is manually entered so it doesn't affect privacy, others warn about the slippery slope and the potential to add national ID on system boot or installation. Users also point out Microsoft's influence over systemd<ref>{{Cite web |last=u/KestrelVO |date=2026-03-20 |title=Systemd’s New Feature Brings Age Verification Option to Linux |url=https://old.reddit.com/r/privacy/comments/1rz5zmh/systemds_new_feature_brings_age_verification/ |url-status=live |archive-url=https://web.archive.org/web/20260321032725/https://old.reddit.com/r/privacy/comments/1rz5zmh/systemds_new_feature_brings_age_verification/ |archive-date=2026-03-21 |access-date=2026-03-21 |website=[[Reddit]]}}</ref><ref>{{Cite web |first=u/ChamplooAttitude |date=2026-03-20 |title=Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp. |url=https://old.reddit.com/r/privacy/comments/1rz8i4r/dylan_useful_idiot_with_commit_access_pushed_age/ |url-status=live |archive-url=https://web.archive.org/web/20260321005304/https://old.reddit.com/r/privacy/comments/1rz8i4r/dylan_useful_idiot_with_commit_access_pushed_age/ |archive-date=2026-03-21 |access-date=2026-03-21 |website=[[Reddit]]}}</ref>.

Users have been migrating to Artix Linux, Void Linux, Devuan and other systemd-free Linux distributions.

==References==
{{reflist}}

{{Ph-I-C}}

Systemd adds age indication ahead of schedule

2026-03-21T03:28:33Z

Charlie 6: work in progress of this ongoing event

{{IncidentCargo
|Status=Active
|Product=Linux
|ArticleType=Product
|Type=Privacy
|Description=Systemd added age bracket ahead of schedule, the merge was quickly done while the revert attempt was blocked, with possible influence from Microsoft
}}systemd is criticized of being monolithic, non-modular and deviates from Unix philosophy<ref>{{Cite web |last=Russell |first=Sean E. |date=2025-07-30 |title=systemd really, really sucks |url=https://ser1.net/post/systemd-really,-really-sucks/ |url-status=live |archive-url=https://web.archive.org/web/20260214043401/https://ser1.net/post/systemd-really,-really-sucks/ |archive-date=2026-02-14 |access-date=2026-03-20}}</ref>.

==Background==
systemd is an initialization system, a suite of basic building blocks for a Linux system. It provides a system and service manager that runs as PID 1 and starts the rest of the system<ref>{{Cite web |date=2024-02-22 |title=systemd System and Service Manager |url=https://www.freedesktop.org/wiki/Software/systemd/ |url-status=live |archive-url=https://web.archive.org/web/20260106163143/https://www.freedesktop.org/wiki/Software/systemd/ |archive-date=2026-01-06 |access-date=2026-03-20 |website=freedesktop.org}}</ref>.

==[Incident]==
In Mar 5 2026, Dylan M. Taylor, a developer and tech enthusiast made two commits on systemd "userdb: add birthDate field to JSON user records", commenting<ref>{{Cite web |last=Taylor |first=Dylan M. |date=2026-03-19 |title=userdb: add birthDate field to JSON user records |url=https://github.com/systemd/systemd/pull/40954 |url-status=live |archive-url=https://web.archive.org/web/20260320055709/https://github.com/systemd/systemd/pull/40954 |archive-date=2026-03-20 |access-date=2026-03-20 |website=[[GitHub]]}}</ref><blockquote>Stores the user's birth date for age verification, as required by recent laws in California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), etc.</blockquote>In Mar 19 2026, Luca Boccassi<ref>{{Cite web |title=Luca Boccassi |url=https://github.com/bluca |url-status=live |archive-url=https://web.archive.org/web/20260320172404/https://github.com/bluca |archive-date=2026-03-20 |access-date=2026-03-20 |website=[[GitHub]]}}</ref>, a member of Systemd and a Microsoft employee, merged the commit.

Lennart Poettering, the creator of systemd, known for having [[wikipedia:Lennart_Poettering#Controversies|controversial technical and architectural]] positions regarding the Linux ecosystem, has clarified that this change is:<blockquote>An optional field in the userdb JSON object. It's not a policy engine, not an API for apps. We just define the field, so that it's standardized iff people want to store the date there, but it's entirely optional<ref>{{Cite web |last=Rudra |first=Sourav |date=2026-03-20 |title=Systemd’s New Feature Brings Age Verification Option to Linux |url=https://itsfoss.com/news/systemd-age-verification/ |url-status=live |archive-url=https://web.archive.org/web/20260320123152/https://itsfoss.com/news/systemd-age-verification/ |archive-date=2026-03-20 |access-date=2026-03-20 |website=It's FOSS}}</ref>.</blockquote>

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
Consumer response is mixed. Some says the age is manually entered so it doesn't affect privacy, others warn about the slippery slope and the potential to add national ID on system boot or installation. Users also point out Microsoft's influence over systemd<ref>{{Cite web |last=u/KestrelVO |date=2026-03-20 |title=Systemd’s New Feature Brings Age Verification Option to Linux |url=https://old.reddit.com/r/privacy/comments/1rz5zmh/systemds_new_feature_brings_age_verification/ |url-status=live |archive-url=https://web.archive.org/web/20260321032725/https://old.reddit.com/r/privacy/comments/1rz5zmh/systemds_new_feature_brings_age_verification/ |archive-date=2026-03-20 |access-date=2026-03-20 |website=[[Reddit]]}}</ref>.

Users have been migrating to Artix Linux, Void Linux, Devuan and other systemd-free Linux distributions.

==References==
{{reflist}}

{{Ph-I-C}}

Systemd adds age indication ahead of schedule

2026-03-21T02:18:18Z

Charlie 6: Systemd added age bracket ahead of schedule, the merge was quickly done while the revert attempt was blocked, with possible influence from Microsoft

{{IncidentCargo
|Status=Active
|Product=Linux
|ArticleType=Product
|Type=Privacy
|Description=Systemd added age bracket ahead of schedule, the merge was quickly done while the revert attempt was blocked, with possible influence from Microsoft
}}
{{Ph-I-Int}}
==Background==
{{Ph-I-B}}

==[Incident]==
{{Ph-I-I}}

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
{{Ph-I-ConR}}

==References==
{{reflist}}

{{Ph-I-C}}

ATSC 3.0

2026-03-03T15:03:30Z

Charlie 6: /* Incidents */ rephrased the last sentence

{{InfoboxProductLine
| Title = {{PAGENAME}}
| Release Year =2017
| Product Type =Television Transmission Protocol
| In Production =Yes
| Official Website =https://watchnextgentv.com/
| Logo =NextGenTVBug.png
}}

'''[[wikipedia:ATSC_3.0|ATSC 3.0]]''', also known as '''NextGenTV (in the US) or TV 3.0 DTV+ (in Brazil)'''<ref>{{Cite web |title=Decreto vai confirmar padrão ATSC e faixa de 300 MHz para a TV 3.0 |trans-title=Decree will confirm ATSC standard and 300 MHz band for TV 3.0 |url=https://telesintese.com.br/decreto-vai-confirmar-padrao-atsc-e-faixa-de-300-mhz-para-a-tv-3-0/ |archive-url=https://web.archive.org/web/20251019023924/https://telesintese.com.br/decreto-vai-confirmar-padrao-atsc-e-faixa-de-300-mhz-para-a-tv-3-0/ |archive-date=19 Oct 2025 |website=Telesintese |language=pt-br}}</ref><ref>{{Cite web |title=Globo inaugura primeira estação de TV 3.0 do Brasil e inicia testes com DTV+ |trans-title=Globo inaugurates Brazil's first TV 3.0 station and begins DTV+ tests |url=https://www.minhaoperadora.com.br/2025/06/globo-inaugura-primeira-estacao-de-tv-3-0-do-brasil-e-inicia-testes-com-dtv.html |archive-url=https://web.archive.org/web/20251017095229/https://www.minhaoperadora.com.br/2025/06/globo-inaugura-primeira-estacao-de-tv-3-0-do-brasil-e-inicia-testes-com-dtv.html |archive-date=17 Oct 2025 |website=Minha Operadora |language=pt-br}}</ref>''',''' is a television protocol for terrestrial (over-the-air) broadcasting. It promises to deliver over 4K resolution and 120 FPS broadcast television using modern standards like HEVC, HDR, Dolby AC-4, and MPEG-H 3D audio, alongside better "interaction among the broadcasters and the users".

==Consumer impact summary==
NextGenTV has had privacy concerns over internet-based viewer metrics/analytics and targeted advertising, voiced by FCC commissioner Geoffrey Starks in 2020.<ref>{{Cite web |last=Balderston |first=Michael |date=29 Jan 2020 |title=Starks Warns of Potential Privacy, Data Issues With ATSC 3.0 |url=https://www.tvtechnology.com/atsc3/starks-warns-of-potential-privacy-data-issues-with-atsc-3-0 |url-status=live |archive-url=https://web.archive.org/web/20251017223604/https://www.tvtechnology.com/atsc3/starks-warns-of-potential-privacy-data-issues-with-atsc-3-0 |archive-date=17 Oct 2025 |access-date=28 Mar 2025 |website=tvtech}}</ref> More importantly, NextGenTV introduced [[Digital rights management]] and encryption to freely available television airwaves.

The authority for encryption in ATSC 3.0 is called A3SA.<ref>{{Cite web |title=Paving the Way for Enhanced Security |url=https://a3sa.com/ |url-status=live |archive-url=https://web.archive.org/web/20251215183632/https://a3sa.com/ |archive-date=15 Dec 2025 |access-date=28 Mar 2025 |website=A3SA}}</ref> According to a article on Techhive,<ref name=":0">{{Cite web |last=Newman |first=Jared |date=28 Jul 2023 |title=NextGen TV’s DRM puts future of the over-the-air DVR in doubt |url=https://www.techhive.com/article/2009693/nextgen-tv-drm-puts-future-of-the-over-the-air-dvr-in-doubt.html |url-status=live |archive-url=https://web.archive.org/web/20251213194219/https://www.techhive.com/article/2009693/nextgen-tv-drm-puts-future-of-the-over-the-air-dvr-in-doubt.html |archive-date=13 Dec 2025 |access-date=28 Mar 2025 |website=TechHive}}</ref> restrictions that could be imposed by A3SA's DRM might include:

*Blocking or setting expiry dates on recordings
*Blocking the remote access of tuners
*Always-on internet is required for viewing/streaming/playback.
*Pairing recordings to the tuner from which it was recorded
*"Blessing" devices that pass the A3SA's DRM certification and licensing program
The Techhive article also describes that implementing DRM could increase the cost of tuners due to the required licensing and certification programs for vendors.

Lon Seidman also discovered that tuner decryption certificates can expire after 10 to 30 years on certified devices.<ref>{{Cite web |last=Seidman |first=Lon |date=30 Jan 2024 |title=ATSC 3 TV Tuners Have an Expiration Date, Slow Progress on Gateway Devices and More.. |url=https://blog.lon.tv/2024/01/30/atsc-3-tv-tuners-have-an-expiration-date-slow-progress-on-gateway-devices-and-more/ |url-status=live |archive-url=https://web.archive.org/web/20240130134957/https://blog.lon.tv/2024/01/30/atsc-3-tv-tuners-have-an-expiration-date-slow-progress-on-gateway-devices-and-more/ |archive-date=30 Jan 2024 |access-date=28 Mar 2025 |website=Lon.tv}}</ref>

==Incidents==
Many major US ATSC 3.0 pilot stations started encrypting their broadcasts in 2023,<ref name=":0" /><ref>{{Cite web |last=Seidman |first=Lon |date=15 May 2023 |title=Broadcasters Roll Out Restrictive DRM Encryption on ATSC 3.0 Broadcasts |url=https://blog.lon.tv/2023/05/15/broadcasters-roll-out-restrictive-drm-encryption-on-atsc-3-0-broadcasts/ |url-status=live |archive-url=https://web.archive.org/web/20230516000510/https://blog.lon.tv/2023/05/15/broadcasters-roll-out-restrictive-drm-encryption-on-atsc-3-0-broadcasts/ |archive-date=16 May 2023 |access-date=28 Mar 2025 |website=Lon.tv}}</ref> locking out users of all pre-certification ATSC 3.0 tuners without decryption support. This has led to some resource websites like [https://www.rabbitears.info/ rabbitears.info] to become concerned about their future providing information on channels due to encryption becoming more widespread. They warn that the site may be unable to operate as the tools for analysis of channels become inoperable on encrypted channels.<ref>{{Cite web |title=ATSC 3.0 Encryption |url=https://www.rabbitears.info/static.php?name=atsc3_encryption |url-status=live |archive-url=https://web.archive.org/web/20251215044905/https://www.rabbitears.info/static.php?name=atsc3_encryption |archive-date=15 Dec 2025 |access-date= |website=RabbitEars}}</ref>

In cases where encrypted channels could be decrypted using certified tuners, it has been reported that an active internet connection is required to tune or switch between encrypted channels.<ref>{{Cite web |last=Seidman |first=Lon |date=3 Sep 2023 |title=The ADTH Nextgen TV Box Shows Us Just How Bad ATSC 3.0 Encryption Will Be.. |url=https://blog.lon.tv/2023/09/03/the-adth-nextgen-tv-box-shows-us-just-how-bad-atsc-3-0-encrpytion-will-be/ |url-status=live |archive-url=https://web.archive.org/web/20251101180100/https://blog.lon.tv/2023/09/03/the-adth-nextgen-tv-box-shows-us-just-how-bad-atsc-3-0-encrpytion-will-be/ |archive-date=2025-11-01 |access-date=28 Mar 2025 |website=Lon.tv}}</ref>

LG has also encountered patent issues trying to incorporate tuners into its TVs, which resulted in a dispute with Constellation Design Inc. that ended ATSC 3.0 tuner support in new LG televisions as of September 2023.<ref>{{Cite web |last=Seidman |first=Lon |date=26 Sep 2023 |title=New LG Televisions Will Not Have ATSC 3 Tuners Due to Patent Dispute |url=https://blog.lon.tv/2023/09/26/new-lg-televisions-will-not-have-atsc-3-tuners-due-to-patent-dispute/ |url-status=live |archive-url=https://web.archive.org/web/20251017091339/https://blog.lon.tv/2023/09/26/new-lg-televisions-will-not-have-atsc-3-tuners-due-to-patent-dispute/ |archive-date=2025-10-17 |access-date=28 Mar 2025 |website=Lon.tv}}</ref>

SiliconDust of HDHomeRun has engaged in official correspondence with the Federal Communications Commission (FCC) in response to Pearl TV (ATSC 3.0) with regards to "Authorizing the Permissive Use of the “Next Generation” Broadcast Television Standard (GN Docket No. 16-142)"<ref name=":1">{{Cite web |date=2025-07-18 |title=Pearl Ex Parte Letter re HD HomeRun (7-18-25) |url=https://www.fcc.gov/ecfs/document/107180407509394/1 |url-status=live |archive-url=https://web.archive.org/web/20260104093516/https://www.fcc.gov/ecfs/document/107180407509394/1 |archive-date=2026-01-04 |website=FCC.gov}}</ref> pointing out Pearl TV is acting as a '''gatekeeper''' by deciding which tuners to allow and not allow even after being "certified" for NextGenTV ATSC 3.0 as well as making mention that strict '''exclusive use of (google) widevine''' prevents popular devices such as Roku, Xbox, Apple TV, iPhone, iPad, Windows, or Mac from ever accessing the encrypted channels.<ref>{{Cite web |date=2025-07-22 |title=Silicondust Response to Pearl Ex Parte Letter (7-22-25) |url=https://www.fcc.gov/ecfs/document/10722712322683/1 |url-status=live |archive-url=https://web.archive.org/web/20251019215257/https://www.fcc.gov/ecfs/document/10722712322683/1 |archive-date=2025-10-19 |website=FCC.gov}}</ref> The two responded back and forth, and Pearl TV attempted to claim that SiliconDust was using a black-listed chip. Pearl also claimed that SiliconDust must have a Widevine CDM license.<ref>{{Cite web |date=2025-07-25 |title=Pearl Ex Parte Letter re HD HomeRun (Reply 7-25-25) |url=https://www.fcc.gov/ecfs/document/1072583827524/1 |url-status=live |archive-url=https://web.archive.org/web/20260104094613/https://www.fcc.gov/ecfs/document/1072583827524/1 |archive-date=2026-01-04 |website=FCC.gov}}</ref> SiliconDust responded by claiming Pearl continues to push false narratives. They point out they are "not required or expected to have the Level 1 CDM license described by Pearl," as well as stating that the "SoC part used in a video gateway device [the blacklisted chip], is not relevant in any way to viewers accessing ATSC 3.0 content."<ref>{{Cite web |date=2025-07-29 |title=SiliconDust Reply to 2nd Pearl |url=https://www.fcc.gov/ecfs/document/107301849911610/1 |url-status=live |archive-url=https://web.archive.org/web/20260104094355/https://www.fcc.gov/ecfs/document/107301849911610/1 |archive-date=2026-01-04 |website=FCC.gov}}</ref> In follow-up to this incident, Nicholas J Kelsey – President of Silicondust met with the FCC where he goes over in detail how the broadcast industry is attempting to use ATSC 3.0 DRM to limit access to public airwaves illegally, "The TV receiver market is being regulated by the private broadcast industry (a different industry)" by acting as gatekeeper, Stifling innovation, having "secret A3SA rules" as well as many other key points in relation to these issues.<ref>{{Cite web |date=2025-08-01 |title=SiliconDust Ex Parte Letter re FCC meeting (7-31-25) |url=https://www.fcc.gov/ecfs/document/1080140138248/1 |url-status=live |archive-url=https://web.archive.org/web/20260104094159/https://www.fcc.gov/ecfs/document/1080140138248/1 |archive-date=2026-01-04 |website=FCC.gov}}</ref> ''(*'''It should be noted that discussions regarding the A3SA specifications and rules are forbidden from being referenced in filings due to NDAs'''.)''

Pearl TV accuses SiliconDust HDHomeRun devices of using a chip manufactured by Chinese HiSilicon, which is black-listed by the US government. It uses their reasoning to not approve SiliconDust HDHomeRun for DRM certification. This suggests that any component from a black-listed company violates the industry’s secret, non-disclosable rules concerning decryption<ref name=":1" />. However, the SiliconDust devices have FCC certification & approval for sale in the USA, indicating broadcast networks are trying to regulate tuner devices despite private industry having no authority. It is also worth noting that A3SA & Pearl's use of "Selectively enforcing this rule" is based on the fact that their own DRM-certified device (Converter X1 by GTMedia (''A Chinese company'')) contains a similar chip that the US government also blacklists. Moreover, GTMedia devices ran an outdated Android OS with known security vulnerabilities. This also caused a requirement for all apps to be side-loaded.<ref>{{Cite web |last=Seidman |first=Lon |date=2025-07-22 |title=Did TV Broadcasters Just Admit to Selectively Enforcing Their Own Encryption Rules? |url=https://blog.lon.tv/2025/07/22/did-tv-broadcasters-just-admit-to-selectively-enforcing-their-own-encryption-rules/ |url-status=live |archive-url=https://web.archive.org/web/20250927172546/https://blog.lon.tv/2025/07/22/did-tv-broadcasters-just-admit-to-selectively-enforcing-their-own-encryption-rules/ |archive-date=2025-09-27 |website=Lon.TV Blog}}</ref>

==See also==

*[https://www.rabbitears.info/market.php?request=atsc3 rabbitears.info page on ATSC 3.0, listing encrypted channels.]
*[https://blog.lon.tv/2023/07/10/the-fcc-responds-to-my-atsc-3-encryption-complaint-they-want-to-hear-from-you/ Lon Seidman Blogpost on the FCC response to ATSC DRM]

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]
[[Category:Articles in need of additional work]]

MSI motherboard CMOS battery obsolescence

2026-03-02T10:05:10Z

Charlie 6: /* Consumer-impact summary */ added overheating concern

{{Cleanup}}
{{ProductLineCargo|ReleaseYear=2025-Current|Website=https://us.msi.com/Motherboards/Products|InProduction=Yes|Company=MicroStar International (MSI)|Category=PC Motherboards}}
[[File:MSIBatteryZoom.png|alt=MSI CMOS Battery Page in Manual |thumb|MSI Manual Citation |none]]

==Consumer-impact summary==
MSI Mainboard CMOS CR2032 batteries are no longer contained within a standard easily accessible clip-mount holder. Instead the CMOS battery is hidden beneath the Voltage Regulator Module (VRM) heatsink assembly, and is affixed to the mainboard via a lead, and mounted with adhesives and shrink-wrap plastic.<ref>{{Cite web |date=2022-04-15 |title=MSI Pro B660M-A CMOS battery location? |url=https://forum-en.msi.com/index.php?threads/msi-pro-b660m-a-cmos-battery-location.374514/ |url-status=live |archive-url=https://web.archivep75mbjunhxc6x4j5mwjmomyxb573v42baldlqu56ruil2oiad.onion/web/20260302095843/https://forum-en.msi.com/index.php?threads/msi-pro-b660m-a-cmos-battery-location.374514/ |archive-date=2026-03-02 |access-date=2026-03-02 |website=MSI Global English Forum}}</ref><ref>{{Cite web |date=2023-11-29 |title=Where is the location of CMOS battery on this motherboard? |url=https://www.msi.com/faq/9918 |url-status=live |access-date=2026-03-02 |website=MSI Global}}</ref> Some of the lower-end tier models of MSI motherboard still have a clip-mount, but it is blocked by heatsinks (that are not part of the VRM assembly). All current models (2025-2026) of motherboard have a line of text in the user manual that states the following:

<code>● This product contains an irreplaceable battery.</code>

This is False. The battery is a standard CR2032 battery. It is not rechargeable, or unique, and is replaceable, with some extended effort.

While the battery remains a standard CR2032 coin battery, and the mounting mechanism is not completely inaccessible, due to this misleading language in the manual and obfuscated location of the battery, it is a blatant attempt to make the mainboard obsolete when the battery dies. Replacement requires service from an experienced technician, leading to more device turnover. For 40 years of mainboard design, replacing a CMOS battery has required locating the battery on the face of the mainboard, pressing a clearly marked tab and removing the old battery out of the standardized component clip slot, and putting a replacement one in its place. There is no reason to have changed this.

The operating temperature of a CR coin cell is typically -30°C to 85°C, it's recommended to consult the manufacturer should the temperature exceeds 70°C<ref>{{Cite web |date=2024-07 |title=CR2032 CR Coin-type Lithium Battery |url=https://energy.panasonic.com/dam/master/pdf/en/datasheet/lithium/CR2032_Datasheet_EN_240701.pdf |url-status=live |access-date=2026-03-02 |website=Panasonic Energy}}</ref>. VRM runs at a higher temperature typically around 80°C to 90°C, with safe operating temperature exceeds 100°C<ref>{{Cite web |last=@jayyywhattt |date=2022-01-07 |title=Motherboard, vrm temperatures |url=https://old.reddit.com/r/overclocking/comments/ry9cdc/motherboard_vrm_temperatures/ |url-status=live |access-date=2026-03-02 |website=[[Reddit]]}}</ref>. Mounting the CMOS battery at or very close to the VRM heatsink can reduce the battery life.

==Workarounds==
If your CMOS battery dies and needs replacing, here are some steps to follow to replace your 'irreplaceable' battery.
[[File:CSWiki-MainboardBatteryMSI.png|alt=CMOS Battery Location|397x397px|thumb|MSI Z890 Edge TI Wifi Mainboard with VRM heatsink removed and CMOS battery highlighted]]
*Obtain a new standard CR2032 battery.
*Un-mount your mainboard from your computer case and look for several screws on the reverse side of the board opposing the VRM assembly. Removing these allows you to remove the VRM heatsink.
*Be mindful of the exposed thermal pads, and keep them clean while performing this process. Cover exposed pads with plastic wrap if your work environment is not clean.
*If your model contains an RGB lighting assembly on the VRM heatsink watch for the cable that is attached to the mainboard to enable this. Carefully unplug that cable if present.
*Locate the CMOS battery and unplug the leads. The leads should be a pair of black and red wires leading to a miniature mainboard plug. Unplug the connector.
*Dismantle the wrapping on the battery unit itself and un-mount the leads from the battery surface by either force, desoldering, or clipping them.
*[[File:CSWiki MSIZ890Assembled.jpg|thumb|The same mainboard with VRM heatsink installed]]Solder each lead to a piece of nickle strip, and use a tackwelder to re-anchor each strip to the correct polarity battery surface. Alternatively, simply wrap some electricians tape to re-anchor leads to the terminals, though be mindful, that tape adhesive will weaken over time, leading to possible loose connections. Tack welding is preferable. Upon completing this assembly to your satisfaction, move on to the next step.
*Encase the new battery with electrical tape and re-mount it near the original location. Standard double sided foam tape should function nicely for this. Hotglue also works.
*Replace the VRM heatsink, ensuring good contact across all thermal pads, and reconnecting the RGB lighting connector if it is present.
*Re-Anchor the screws on the opposing side of the PCB.

Congratulations! Your CMOS battery has now been changed.

==Products==
MSI MEG & MPG Motherboards 2025-2026(Current)

MSI MAG Motherboards (2025-2026) still have standard clip-holder mounts for their batteries. (Though the manual still reads "This product contains an irreplaceable battery").

==References==
{{reflist}}
https://consumerrights.wiki/w/File:CSWiki-MainboardBatteryMSI_IrreplaceableBatt.png

https://consumerrights.wiki/w/File:CSWiki_MSIZ890Assembled.jpg

https://consumerrights.wiki/w/File:CSWiki-MainboardBatteryMSI.png

MSI MEGZ890 GODLIKE, Manual pg. 104 https://download-2.msi.com/archive/mnu_exe/mb/MEGZ890GODLIKE_English.pdf

MSI MEGX879E ACE MAX, Manual pg. 84 https://download-2.msi.com/archive/mnu_exe/mb/MEGX870EACEMAX_English.pdf

MSI MEGZ890 UNIFY X, Manual pg. 89 https://download-2.msi.com/archive/mnu_exe/mb/MEGZ890UNIFY-X_English.pdf

MSI MEGZ790 GODLIKE, Manual pg.81 https://download-2.msi.com/archive/mnu_exe/mb/MEGZ790GODLIKE_EN.pdf

MSI MPGX879E CARBON MAX, Manual pg.79 https://download-2.msi.com/archive/mnu_exe/mb/MPGX870ECARBONMAXWIFI_English.pdf

MSI MPGZ890 ACE, Manual pg.84 https://download-2.msi.com/archive/mnu_exe/mb/MEGZ890ACE_English.pdf

MSI MAG X870E TOMAHAWK MAX WIFI PZ, Manual pg.79 https://download-2.msi.com/archive/mnu_exe/mb/MAGX870ETOMAHAWKMAXWIFIPZ_English.pdf

[[Category:Computers]]

Talk:MSI motherboard CMOS battery obsolescence

2026-03-02T09:53:26Z

Charlie 6: /* Workarounds */

==More Details==

Please add a photo with VRM heatsink installed to show how hard (or easy) to remove it and access the CR2032. Compare it with "This product contains an irreplaceable battery" claim. [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 12:33, 26 February 2026 (UTC)

:I appended an "Assembled" Photo in the references section when I wrote the article. I'm somewhat new to writing wiki's so I wasn't quite too sure where/ how to append such information. But any included examples of a specific mainboard is also sort of missing the greater point, which is that the '''entire current product lineup''' from MSI has this hardware configuration. It's not just the Z890 board, it's ALL of them. [[User:LizzyLamia|LizzyLamia]] ([[User talk:LizzyLamia|talk]]) 18:46, 27 February 2026 (UTC)
::I added the photo with caption, please check and proofread. [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 09:48, 2 March 2026 (UTC)

==If anyone else has a current MSI Mainboard and can assist with filling this wiki page out. Please do.==

Each motherboard model seems to have a unique and specific "hiding location" for the CMOS battery. All the manual entries list "This product contains an Irreplaceable Battery" but the exact obfuscation/location of the battery varies from model to model. Most of the high end boards * MAG and MPG * seem to have it located underneath the VRM Heatsink. Others seem to have it buried under heatsinks on other board locations. I don't have the resources, nor patience to hunt down the battery placement board-by-board. There are some models that contain this text in the manual that have overtly displayed CR2032 batteries in the product promotion images, like normal boards ought to. I very much doubt anyone really cares enough to help out, but, on the off chance they do. Thank you very much. [[User:LizzyLamia|LizzyLamia]] ([[User talk:LizzyLamia|talk]]) 19:50, 27 February 2026 (UTC)

:I got a MSI mobo so I checked inside my case to see if its CMOS battery be hidden. Couldn't find it so did a model number search and on their site they had pictures. The CMOS battery is hidden on mine, but behind the GPU (lol). Granted its a 2023 board so not "current". Product images could be a way we can identify which boards have obfuscated CMOS batts. [[User:SinexTitan|SinexTitan]] ([[User talk:SinexTitan|talk]]) 21:38, 27 February 2026 (UTC)
::actually my board's much older I just bought it on 2023. regardless I took a glance at their current selection and noticed a lot of them use cover plates that may or may not hide the CR2032. checking images is a manual process but checking manuals can be automated. under the "Overview of Components" section in the PDF they showcase a "battery" in a CR2032-like enclosure or just a circular battery icon. out of the first 6 boards from the [https://us.msi.com/Motherboards/Products#?tag=MAG-Series MAG series] half of them show the use of a battery. [[User:SinexTitan|SinexTitan]] ([[User talk:SinexTitan|talk]]) 21:57, 27 February 2026 (UTC)
:::Thank you for looking! It seems to be only the higher end of their product line-up (MEG & MPG) has this new battery location, and only on their recently released boards. Prior to the 2025/2026 release cycle they all had standard mounts in obscure places. I have no issue with board designers hiding the battery out of view, behind the GPU or under a quick release NVME heat-sink, but not being able to even disconnect it for testing purposes without disassembling the whole top-side of the board makes the computer much more difficult to service. The whole reason I even noticed this, was my new MSI Box has had some stability issues, and I went to pull the CMOS batt, just to do a clean hard reset and had that ... "Wait... Where is it?" , moment. Which led to research, nagging my friend who owns a computer repair shop about it, etc etc. [[User:LizzyLamia|LizzyLamia]] ([[User talk:LizzyLamia|talk]]) 16:18, 1 March 2026 (UTC)

==Notability discussion==

This is obviously well put together article, and a relevant repairability issue, but I have concerns about its notability, since this seems to be original research by the author (see: https://consumerrights.wiki/w/Consumer_Rights_Wiki:Wiki_content_policies#Verifiability).

At a minimum, we should at least have a citation pointing to some discussion of this issue online

If there's no external sources for it, it might be something that's better hosted in userspace (i.e. /User:[Username]/[Pagename]). [[User:Keith|Keith]] ([[User talk:Keith|talk]]) 22:04, 1 March 2026 (UTC)

:I found a discussion on MSI's Forum and a post on their FAQ addressing the CMOS battery. I will add these as citations [[User:SinexTitan|SinexTitan]] ([[User talk:SinexTitan|talk]]) 09:53, 2 March 2026 (UTC)

==Workarounds==

There are CMOS batteries with the cables and connector already soldered available for purchase on the market, welding or gluing on one's own is not worth the labor cost and can be dangerous due to risk of intermittent connection. Please edit the steps. The "Congratulations" seems to be AI generated [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 09:51, 2 March 2026 (UTC)

Talk:MSI motherboard CMOS battery obsolescence

2026-03-02T09:51:48Z

Charlie 6: /* Workarounds */ new section

==More Details==

Please add a photo with VRM heatsink installed to show how hard (or easy) to remove it and access the CR2032. Compare it with "This product contains an irreplaceable battery" claim. [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 12:33, 26 February 2026 (UTC)

:I appended an "Assembled" Photo in the references section when I wrote the article. I'm somewhat new to writing wiki's so I wasn't quite too sure where/ how to append such information. But any included examples of a specific mainboard is also sort of missing the greater point, which is that the '''entire current product lineup''' from MSI has this hardware configuration. It's not just the Z890 board, it's ALL of them. [[User:LizzyLamia|LizzyLamia]] ([[User talk:LizzyLamia|talk]]) 18:46, 27 February 2026 (UTC)
::I added the photo with caption, please check and proofread. [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 09:48, 2 March 2026 (UTC)

==If anyone else has a current MSI Mainboard and can assist with filling this wiki page out. Please do.==

Each motherboard model seems to have a unique and specific "hiding location" for the CMOS battery. All the manual entries list "This product contains an Irreplaceable Battery" but the exact obfuscation/location of the battery varies from model to model. Most of the high end boards * MAG and MPG * seem to have it located underneath the VRM Heatsink. Others seem to have it buried under heatsinks on other board locations. I don't have the resources, nor patience to hunt down the battery placement board-by-board. There are some models that contain this text in the manual that have overtly displayed CR2032 batteries in the product promotion images, like normal boards ought to. I very much doubt anyone really cares enough to help out, but, on the off chance they do. Thank you very much. [[User:LizzyLamia|LizzyLamia]] ([[User talk:LizzyLamia|talk]]) 19:50, 27 February 2026 (UTC)

:I got a MSI mobo so I checked inside my case to see if its CMOS battery be hidden. Couldn't find it so did a model number search and on their site they had pictures. The CMOS battery is hidden on mine, but behind the GPU (lol). Granted its a 2023 board so not "current". Product images could be a way we can identify which boards have obfuscated CMOS batts. [[User:SinexTitan|SinexTitan]] ([[User talk:SinexTitan|talk]]) 21:38, 27 February 2026 (UTC)
::actually my board's much older I just bought it on 2023. regardless I took a glance at their current selection and noticed a lot of them use cover plates that may or may not hide the CR2032. checking images is a manual process but checking manuals can be automated. under the "Overview of Components" section in the PDF they showcase a "battery" in a CR2032-like enclosure or just a circular battery icon. out of the first 6 boards from the [https://us.msi.com/Motherboards/Products#?tag=MAG-Series MAG series] half of them show the use of a battery. [[User:SinexTitan|SinexTitan]] ([[User talk:SinexTitan|talk]]) 21:57, 27 February 2026 (UTC)
:::Thank you for looking! It seems to be only the higher end of their product line-up (MEG & MPG) has this new battery location, and only on their recently released boards. Prior to the 2025/2026 release cycle they all had standard mounts in obscure places. I have no issue with board designers hiding the battery out of view, behind the GPU or under a quick release NVME heat-sink, but not being able to even disconnect it for testing purposes without disassembling the whole top-side of the board makes the computer much more difficult to service. The whole reason I even noticed this, was my new MSI Box has had some stability issues, and I went to pull the CMOS batt, just to do a clean hard reset and had that ... "Wait... Where is it?" , moment. Which led to research, nagging my friend who owns a computer repair shop about it, etc etc. [[User:LizzyLamia|LizzyLamia]] ([[User talk:LizzyLamia|talk]]) 16:18, 1 March 2026 (UTC)

==Notability discussion==

This is obviously well put together article, and a relevant repairability issue, but I have concerns about its notability, since this seems to be original research by the author (see: https://consumerrights.wiki/w/Consumer_Rights_Wiki:Wiki_content_policies#Verifiability).

At a minimum, we should at least have a citation pointing to some discussion of this issue online

If there's no external sources for it, it might be something that's better hosted in userspace (i.e. /User:[Username]/[Pagename]). [[User:Keith|Keith]] ([[User talk:Keith|talk]]) 22:04, 1 March 2026 (UTC)

== Workarounds ==

There are CMOS batteries with the cables and connector available on the market, welding or gluing on one's own is not worth the labor cost and can be dangerous due to risk of intermittent connection. Please edit the steps. The "Congratulations" seems to be AI generated [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 09:51, 2 March 2026 (UTC)

Talk:MSI motherboard CMOS battery obsolescence

2026-03-02T09:48:40Z

Charlie 6: /* More Details */ Reply

MSI motherboard CMOS battery obsolescence

2026-03-02T09:47:51Z

Charlie 6: Added caption for the mainboard photo and another photo with VRM installed

{{Cleanup}}
{{ProductLineCargo|ReleaseYear=2025-Current|Website=https://us.msi.com/Motherboards/Products|InProduction=Yes|Company=MicroStar International (MSI)|Category=PC Motherboards}}
[[File:MSIBatteryZoom.png|alt=MSI CMOS Battery Page in Manual |thumb|MSI Manual Citation |none]]

==Consumer-impact summary==
MSI Mainboard CMOS CR2032 batteries are no longer contained within a standard easily accessible clip-mount holder. Instead the CMOS battery is hidden beneath the Voltage Regulator Module (VRM) heatsink assembly, and is affixed to the mainboard via a lead, and mounted with adhesives and shrink-wrap plastic. Some of the lower-end tier models of MSI motherboard still have a clip-mount, but it is blocked by heatsinks (that are not part of the VRM assembly). All current models (2025-2026) of motherboard have a line of text in the user manual that states the following:

<code>● This product contains an irreplaceable battery.</code>

This is False. The battery is a standard CR2032 battery. It is not rechargeable, or unique, and is replaceable, with some extended effort.

While the battery remains a standard CR2032 coin battery, and the mounting mechanism is not completely inaccessible, due to this misleading language in the manual and obfuscated location of the battery, it is a blatant attempt to make the mainboard obsolete when the battery dies. Replacement requires service from an experienced technician, leading to more device turnover. For 40 years of mainboard design, replacing a CMOS battery has required locating the battery on the face of the mainboard, pressing a clearly marked tab and removing the old battery out of the standardized component clip slot, and putting a replacement one in its place. There is no reason to have changed this.

==Workarounds==
If your CMOS battery dies and needs replacing, here are some steps to follow to replace your 'irreplaceable' battery.
[[File:CSWiki-MainboardBatteryMSI.png|alt=CMOS Battery Location|397x397px|thumb|MSI Z890 Edge TI Wifi Mainboard with VRM heatsink removed and CMOS battery highlighted]]
*Obtain a new standard CR2032 battery.
*Un-mount your mainboard from your computer case and look for several screws on the reverse side of the board opposing the VRM assembly. Removing these allows you to remove the VRM heatsink.
*Be mindful of the exposed thermal pads, and keep them clean while performing this process. Cover exposed pads with plastic wrap if your work environment is not clean.
*If your model contains an RGB lighting assembly on the VRM heatsink watch for the cable that is attached to the mainboard to enable this. Carefully unplug that cable if present.
*Locate the CMOS battery and unplug the leads. The leads should be a pair of black and red wires leading to a miniature mainboard plug. Unplug the connector.
*Dismantle the wrapping on the battery unit itself and un-mount the leads from the battery surface by either force, desoldering, or clipping them.
*[[File:CSWiki MSIZ890Assembled.jpg|thumb|The same mainboard with VRM heatsink installed]]Solder each lead to a piece of nickle strip, and use a tackwelder to re-anchor each strip to the correct polarity battery surface. Alternatively, simply wrap some electricians tape to re-anchor leads to the terminals, though be mindful, that tape adhesive will weaken over time, leading to possible loose connections. Tack welding is preferable. Upon completing this assembly to your satisfaction, move on to the next step.
*Encase the new battery with electrical tape and re-mount it near the original location. Standard double sided foam tape should function nicely for this. Hotglue also works.
*Replace the VRM heatsink, ensuring good contact across all thermal pads, and reconnecting the RGB lighting connector if it is present.
*Re-Anchor the screws on the opposing side of the PCB.

Congratulations! Your CMOS battery has now been changed.

==Products==
MSI MEG & MPG Motherboards 2025-2026(Current)

MSI MAG Motherboards (2025-2026) still have standard clip-holder mounts for their batteries. ( Though the manual still reads "This product contains an irreplaceable battery" ).

==References==
{{reflist}}
https://consumerrights.wiki/w/File:CSWiki-MainboardBatteryMSI_IrreplaceableBatt.png

https://consumerrights.wiki/w/File:CSWiki_MSIZ890Assembled.jpg

https://consumerrights.wiki/w/File:CSWiki-MainboardBatteryMSI.png

MSI MEGZ890 GODLIKE, Manual pg. 104 https://download-2.msi.com/archive/mnu_exe/mb/MEGZ890GODLIKE_English.pdf

MSI MEGX879E ACE MAX, Manual pg. 84 https://download-2.msi.com/archive/mnu_exe/mb/MEGX870EACEMAX_English.pdf

MSI MEGZ890 UNIFY X, Manual pg. 89 https://download-2.msi.com/archive/mnu_exe/mb/MEGZ890UNIFY-X_English.pdf

MSI MEGZ790 GODLIKE, Manual pg.81 https://download-2.msi.com/archive/mnu_exe/mb/MEGZ790GODLIKE_EN.pdf

MSI MPGX879E CARBON MAX, Manual pg.79 https://download-2.msi.com/archive/mnu_exe/mb/MPGX870ECARBONMAXWIFI_English.pdf

MSI MPGZ890 ACE, Manual pg.84 https://download-2.msi.com/archive/mnu_exe/mb/MEGZ890ACE_English.pdf

MSI MAG X870E TOMAHAWK MAX WIFI PZ, Manual pg.79 https://download-2.msi.com/archive/mnu_exe/mb/MAGX870ETOMAHAWKMAXWIFIPZ_English.pdf

[[Category:Computers]]

Minecraft

2026-03-01T02:03:07Z

Charlie 6: /* Mojang requires age verification in order to chat in the UK */ added a main article link

{{ProductCargo
|Company=Mojang, Microsoft
|ProductLine=Minecraft
|Logo=Minecraft logo.svg
|ReleaseYear=2011
|InProduction=Yes
|ArticleType=Service
|Category=Video Games
|Website=https://www.minecraft.net/en-us
|Description=Minecraft is a sandbox video game meant for younger audiences
}}

'''{{wplink|Minecraft|Minecraft}}''' is a 2011 multiplayer sandbox game made by [[Mojang|Mojang Studios]]. Once acquired by [[Microsoft]], the game began to harvest telemetry data, force users to comply with an ever shifting EULA to keep access to the paid game, and hide various clauses in the EULA from the public.

==Consumer impact summary==
Under [[Microsoft]]'s ownership, Minecraft has undergone multiple anti-consumer changes in order to acquire more user data and utilizing undisclosed and an ever changing EULA terms to censor user-generated content. These practices are especially concerning since a significant amount of Minecraft players are children.<ref>{{Cite web |last=Capel |first=Chris J |date=2019-09-25 |title=Believe it or not, the average age of a Minecraft player is 24 |url=https://www.pcgamesn.com/minecraft/player-age |url-status=live |archive-url=https://web.archive.org/web/20191018082457/https://www.pcgamesn.com/minecraft/player-age |archive-date=2019-10-18 |access-date=2025-08-30 |website=PCGamesN}}</ref>

==Incidents==
This is a list of all consumer protection incidents related to this product. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].

===Minecraft account migration===
{{Main|Minecraft account migration}}
On October 21st, 2020, [[Mojang]] announced that all Minecraft Java Edition users must migrate their Mojang accounts to Microsoft accounts to retain access to the game. On December 18th, 2023, consumers who did not do so lost access and needed to re-purchase the game to regain it. Any game progress, including purchased first and third party in-game items were lost.

===Minecraft post-purchase ownership rights changes===
{{Main|Minecraft post-purchase ownership rights changes}}
Before Microsoft's acquisition of Mojang, the sole developer of Minecraft, Markus Persson, advocating for consumer ownership, promised [[Digital rights management|DRM]]-free, free optional software updates, and a free copy of the fully released version for every earlier buyer.<ref name=":22">,{{Cite web |date=2011-09-23 |title=Minecraft - About the game |url=http://www.minecraft.net/store/game |url-status=dead |archive-url=https://web.archive.org/web/20110923112156/http://www.minecraft.net/store/game |archive-date=2011-09-23 |website=www.minecraft.net}}</ref>

Post acquisition of Mojang, all the previous buyers of Minecraft who failed to stop accepting updates in time, had to choose between forfeiting ownership or losing the option to use the software offline. Microsoft enacted several EULA changes which turned the game into a license with DRM that can be terminated by the company anytime.<ref name=":6">{{Cite web |date=2024-09-30 |title=Microsoft Services Agreement |url=https://www.microsoft.com/servicesagreement |url-status=deviated |archive-url=https://web.archive.org/web/20240930001856/https://www.microsoft.com/en-us/servicesagreement |archive-date=2024-09-30 |access-date=2025-08-18 |website=microsoft.com}}</ref>

===Minecraft enforcing undisclosed server EULA terms===
{{Main|Minecraft enforcing undisclosed server EULA terms}}
Minecraft began taking action against mod developers and servers in 2023 for using firearms, which was deemed 'adult' by their [[End-user license agreement|EULA]]. When asked for clarification of the changes made to their EULA, Mojang gave little response, and eventually pointed them to a new EULA which had been changed without either informing consumers about the change or asking for permission to change the contract. This information was available only internally, and was later revealed by whistleblowers, since the documents holding the internal changes to their EULA was held under NDA.

In addition they selectively ignore their own EULA rules on "gambling" (loot boxes and literally gambling) servers, and even made contract with [[wikipedia:Nerf|Nerf]] to create Minecraft inspired weapons and in game items, while still refusing to allow weapon mods.<ref>{{Cite web |last=Anderca |first=Cristina |date=2023-10-02 |title=NERF World brings blasters into Minecraft |url=https://www.minecraft.net/en-us/article/nerf-world-brings-blasters-minecraft |url-status=live |archive-url=https://web.archive.org/web/20231002180846/https://www.minecraft.net/en-us/article/nerf-world-brings-blasters-minecraft |archive-date=2023-10-02 |access-date=2025-08-19 |work=Minecraft}}</ref>

===Mojang shuts down community-run Minecraft servers===
{{Main|Mojang shuts down community-run Minecraft servers}}

For the past 5-8 years, [[Mojang]] have enforced countless server shutdowns citing violations of the Minecraft End User License Agreement (EULA). However, said enforcements have been unfairly biased against operators of smaller [[Minecraft]] Java Edition servers, abusing vague and often inaccessible community guidelines to shut down these servers.<ref name=":0">{{Cite web |last=Brose |first=Kian |date=Dec 3, 2024 |title=Hold Mojang Accountable For Their Unlawful Behaviour |url=https://www.gofundme.com/f/hold-mojang-accountable-for-their-unlawful-behaviour |access-date=May 12, 2024 |website=GoFundMe |archive-url=http://web.archive.org/web/20260211012327/https://www.gofundme.com/f/hold-mojang-accountable-for-their-unlawful-behaviour |archive-date=11 Feb 2026}}</ref><ref name=":1">{{Cite web |last=Brose |first=Kian |date=Dec 3, 2024 |title=Suing Minecraft Because They Broke The Law & Pissed Me Off |url=https://www.youtube.com/watch?v=C5RvoPQZQeM |access-date=May 12, 2024 |website=YouTube |archive-url=https://preservetube.com/watch?v=C5RvoPQZQeM |archive-date=23 Feb 2026}}</ref><ref name=":2">{{Cite web |last=Brose |first=Kian |title=Lawsuit Video Accompanying Document |url=https://docs.google.com/document/d/1l3fxs_pZBTdWu7q_iiRKwQdhkEKp8zkuw0O3KBVWC-I/edit?tab=t.0#heading=h.8vmqv8enui5u |access-date=May 12, 2025 |website=Google Docs |archive-url=http://web.archive.org/web/20260203004450/https://docs.google.com/document/d/1l3fxs_pZBTdWu7q_iiRKwQdhkEKp8zkuw0O3KBVWC-I/edit?tab=t.0 |archive-date=3 Feb 2026}}</ref>

An example of this occurred in late 2024 involving the [[Minecraft]] server '''McWar''<nowiki/>', wherein Mojang contacted the developer of the server to shut it down.<ref name=":0" /><ref name=":1" /><ref name=":2" />

Mods that bypass the IP Address blocklist that enforce these shutdowns have received takedowns by Tracer on the behalf of Microsoft under §1201 of the DMCA.<ref>{{Cite web |date=2025-10-23 |title=dmca/2025/10/2025-10-23-minecraft-3.md at aad92ffb439b3a6b5f0666fe56c669a01f568052 · github/dmca |url=https://github.com/github/dmca/blob/aad92ffb439b3a6b5f0666fe56c669a01f568052/2025/10/2025-10-23-minecraft-3.md?plain=1#L45 |url-status=live |website=GitHub}}</ref>

===Minecraft Beta pre-1.8's lack of authentication===
{{Main|Minecraft Beta pre-1.8's lack of authentication}}
In version Beta 1.8, Mojang has changed the endpoint used for authentication on Minecraft servers from "www.minecraft.net" to "session.minecraft.net". Unknown amount of time later the original endpoint used for the authentication was shut down, breaking authentication support for several old Minecraft versions, despite no actual changes in the behavior of the endpoint. The latter endpoint still works, despite being insecure (supports HTTP requests, with token being within the URL parameters) - this means that the shutdown is likely not a security concern.

Lack of authentication has caused several Minecraft servers to:

*lose part of the playerbase due to a need of modding the game client (and server) to fix the authentication issue,
*become completely insecure by allowing non-premium Minecraft users to join (e.g. opens the risk of botting the server, or brute-forcing user login passwords),
*break the EULA of the game due to allowing non-premium Minecraft users to join their server.

===Mojang requires age verification in order to chat in the UK===
{{Incomplete section}}{{Main|Minecraft Chat Reporting and Restriction}}
In February 2026, Mojang has decided to implement mandatory age verification in the United Kingdom to access some features.{{Citation needed}} Although players still have access to play the game, they miss out on social features.{{Citation needed}} The big issue is players will now be locked out of the chat feature in the game which is essentially what keeps the online connection alive in the many servers players have access to.{{Citation needed}} In order to get this feature that has always been included automatically (regardless of age) UK residents must now verify their identity by using Yoti (a third-party service).{{Citation needed}} This is a huge blow to the Minecraft community as many of the games players are children.{{Citation needed}} Famous players such as TommyInnit (who's career took off due to his Minecraft streams and VODS later posted on YouTube) were under the age of 18 when they started to gain popularity.{{Citation needed}} Although these players had access to outside game voice chats with other players, many don't have access to the proper equipment required to do so, solely relying on the in-game chat. This mass majority of players in the UK will now have to verify their age and sell their data to a third-party service in order to get one of the most essential features in the game.<ref>{{Cite web |last=Kabra |first=Akshat |date=2026-02-22 |title=Age verification in Minecraft: Everything you need to know |url=https://www.sportskeeda.com/minecraft/age-verification-minecraft-everything-need-know |url-status=live |access-date=2022-02-28 |website=sportskeeda}}</ref>

===DMCA takedowns of competing games===
There has been a documented history of Microsoft submitting [[Digital Millennium Copyright Act|DMCA]] takedown notices to various voxel-based sandbox games which act as competition to Minecraft. As of ''February 10th, 2026'', the latest takedown was the project Allumeria,<ref>{{Cite web |last=Mazeriio |date=Feb 10, 2026 |title=Tweet from Mazeriio |url=https://xcancel.com/Mazeriio/status/2021128578742513930 |access-date=Feb 10, 2026 |website=X formerly [[Twitter]]}}</ref> which existed as a wholly original project that was unreasonably delisted from Steam. The following is a complete list of competing games taken down by Microsoft.
{| class="wikitable"
|+
!Game
!Takedown Date
!Summary
!Related Article (if applicable)
|-
|MC.JS
|Circa Aug. 2019
|Microsoft issued a DMCA takedown notice to a developer who created MC.JS, a [[JavaScript]]-based browser version of Minecraft hosted on GitHub.<ref>{{Cite web |last=Maxwell |first=Andy |date=September 1, 2019 |title=Microsoft Puts Blocks On In-Browser Minecraft Clone |url=https://torrentfreak.com/microsoft-puts-blocks-on-in-browser-minecraft-clone-190831/ |access-date=Feb 10, 2026 |website=Torrent Freak |archive-url=http://web.archive.org/web/20260215012038/https://torrentfreak.com/microsoft-puts-blocks-on-in-browser-minecraft-clone-190831/ |archive-date=15 Feb 2026}}</ref> The notice cited copyright infringement, trademark violations, and unauthorized use of Minecraft's imagery and textures, resulting in the project being removed from GitHub. An archived snapshot of the page shows that the only infringing contents were referring to itself as a "Minecraft clone" and using a singular texture from the game,<ref>{{Cite web |last=Tominous |title=MC.JS Github page |url=https://github.com/ideaplexus/mc.js/ |archive-url=https://web.archive.org/web/20201125143334/https://github.com/ideaplexus/mc.js/ |archive-date=Nov 25, 2020 |access-date=Feb 10, 2026 |website=[[GitHub]]}}</ref> both of which could have easily been requested to be removed.
|
|-
|Eaglercraft
|Circa Feb. 2023
|Microsoft issued a DMCA takedown to 92 individual repositories hosting Eaglercraft, a decompilation of Minecraft. Microsoft claimed it was a violation of the EULA and Terms of Use of Minecraft.<ref>{{Cite news |last=Van der Sar |first=Ernesto |date=February 24, 2023 |title=Mojang Targets Repositories of Browser-Based Minecraft Copy ‘Eaglercraft’ |url=https://torrentfreak.com/mojang-targets-repositories-of-browser-based-minecraft-copy-eaglercraft-230224/ |access-date=Feb 10, 2026 |work=Torrent Freak |archive-url=http://web.archive.org/web/20260213042505/https://torrentfreak.com/mojang-targets-repositories-of-browser-based-minecraft-copy-eaglercraft-230224/ |archive-date=13 Feb 2026}}</ref>
|[[Eaglercraft Takedows]]
|-
|Luanti
|Circa Mar. 2023
|Luanti (formerly known as Minetest at the time), an open source voxel game platform had its Android app taken down from Google Play by a DMCA takedown from a company representing Mojang, claiming it was infringing of their copyright.<ref>https://github.com/luanti-org/luanti/issues/13363#issuecomment-1485528633 ([http://web.archive.org/web/20250313234718/https://github.com/luanti-org/luanti/issues/13363 Archived])</ref> The app was later restored in May after filing a counter-notice with no response.
|
|-
|N/A
|Jan. 29, 2025
|Mojang enforcement issued a DMCA takedown notice to [[Cloudflare]] over the chat service Revolt (now Stoat) supposedly being a Minecraft clone because of the platform hosting screenshots of an unknown Minecraft clone.<ref name=":3">{{Cite web |date=2025-01-29 |title=2025-01-29 mojang copyright infringement complaint |url=https://wiki.revolt.chat/notes/transparency/abuse-reports/2025-01-29-mojang-copyright-infringement-complaint/ |access-date=Feb 10, 2026 |website=Revolt Wiki |archive-url=http://web.archive.org/web/20260211025827/https://wiki.revolt.chat/notes/transparency/abuse-reports/2025-01-29-mojang-copyright-infringement-complaint/ |archive-date=11 Feb 2026}}</ref> In a subsequent email, a different actor representing [[Microsoft]], [[Tracer.ai]], sent another takedown notice over the same assets.<ref name=":3" />
|
|-
|Allumeria
|Feb. 10, 2026
|[[Microsoft]] submitted a [[DMCA]] notice to [[Valve]] via [[Tracer.ai]] over Allumeria after its systems detected that the game was supposedly using stolen assets from the game.<ref>{{Cite web |last=Mazeriio |date=Feb 10, 2026 |title=Tweet from Mazeriio |url=https://xcancel.com/Mazeriio/status/2021128578742513930 |access-date=Feb 10, 2026 |website=X formerly [[Twitter]]}}</ref> In an archived snapshot of Allumeria's [[Steam]] page, no assets were discernibly taken from Minecraft.<ref>{{Cite web |last=Unomelon |title=Allumeria's Steam page |url=https://store.steampowered.com/app/3516590/Allumeria/ |archive-url=https://web.archive.org/web/20250308151651/https://store.steampowered.com/app/3516590/Allumeria/ |archive-date=Mar 8, 2025 |access-date=Feb 10, 2026 |website=[[Steam]]}}</ref> A day later, Microsoft withdrew the complaint and Allumeria was reinstated on Steam store page.<ref>[[File:Screenshot_from_Allumeria_Discord_server.png|thumb|Screenshot from Allumeria Discord server announcing that game has been reinstated on Steam.]]
</ref><ref>{{Cite web |last=Unomelon |date=2026-02-11 |title=Post by @unomelon.bsky.social |url=https://bsky.app/profile/unomelon.bsky.social/post/3mekpz2kras2t |url-status=live |archive-url=https://web.archive.org/web/20260211090940/https://bsky.app/profile/unomelon.bsky.social/post/3mekpz2kras2t |archive-date=2026-02-11 |access-date=2026-02-28 |website=Bluesky}}</ref>
|
|-
|
|
|
|
|}

==See also==

*[[Microsoft]]
*[[Mojang]]

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]
[[Category:Microsoft]]

Battery firmware lockout

2026-02-26T15:16:34Z

Charlie 6: /* Consumer reactions */ added mention of compatible third-party battery packs

Most devices with rechargeable batteries has a [[wikipedia:Battery_management_system|battery management system (BMS)]] module. This module monitors and regulate key variables and capable of communicating with the device and preventing unsafe usage that could cause failure. However, many of them contains proprietary code that locks the battery from operation, "bricking" it and prevent the battery from third-party repair. Effectively making the whole device that depends on said battery unusable.

==How it works==
When the battery is outside its operating range, such as overcharged, overcharged, overheated, unbalanced(in multi-celled battery packs), the BMS prevents the battery from further usage, limiting damage. However, the BMS should resume normal operation when the battery is back within operating range. Instead, the BMS changes bytes in its memory, leading to a "Permanent Fail (PF)" state, preventing the use of said battery even after reconditioning or repairing.

Documentations from known BMS manufacturers such as Texas Instruments said the device can permanently disable the use of the battery pack in case of a "severe failure"<ref>[https://www.ti.com/lit/ug/sluua43a/sluua43a.pdf? https://www.ti.com/lit/ug/sluua43a/sluua43a.pdf?] ([http://web.archive.org/web/20250604023257/https://www.ti.com/lit/ug/sluua43a/sluua43a.pdf Archived])</ref>. However users report the battery is "bricked" after scenarios like long-term storage, discharging laptop overnight or use a power tool in warm environment while charging it cool, indicating the manufacturers have abused the BMS program, exaggerating the nature of the failure as a from of [[self-destructive design]].

To make matters worse, many of the BMS needs "access code" to read and change it's parameters, including runtime ones like the "Permanent Fail" flag. The unlock or unseal code is kept secret by the battery's manufacturer, making user and third-parties very difficult, if not impossible, to repair said battery<ref>{{Cite web |date=28 Sep 2019 |title=Experiences with TI BQ management IC’s when re-building laptop batteries? |url=https://www.eevblog.com/forum/chat/experiences-with-ti-bq-management-ics-when-revelling-laptop-batteries/?all |url-status=live |archive-url=https://web.archive.org/web/20240926193741/https://www.eevblog.com/forum/chat/experiences-with-ti-bq-management-ics-when-revelling-laptop-batteries/?all |archive-date=26 Sep 2024 |access-date=13 Sep 2025 |website=EEVblog Electronics Community Forum}}</ref>.

Alarmingly, the condition of "bricking" includes "Capacity Degradation Permanent Failure"<ref>[https://www.ti.com/lit/ds/symlink/bq40z50.pdf? https://www.ti.com/lit/ds/symlink/bq40z50.pdf?] ([http://web.archive.org/web/20250826014752/https://www.ti.com/lit/ds/symlink/bq40z50.pdf Archived])</ref>, which means the manufacturers can artificially limit the battery pack's lifespan, making it unusable after a certain health (e.g 80%).

==Why it is a problem==

===Increased repair cost===
When the battery is bricked, most users would buy an entire battery pack, increasing the total cost of ownership. The "access code" lock prevents third-parties from replacing individual cells and refurbishing the battery pack, reducing its lifespan.

===Environmental impact===
Lithium-ion batteries are 95% recyclable, however, only about 5% of them are actually recycled<ref>{{Cite web |date=22 Sep 2022 |title=Lithium ion battery recycling |url=https://www.cas.org/resources/cas-insights/lithium-ion-battery-recycling?utm_source=chatgpt.com |url-status=live |archive-url=http://web.archive.org/web/20260216013331/https://www.cas.org/resources/cas-insights/lithium-ion-battery-recycling?utm_source=chatgpt.com |archive-date=16 Feb 2026}}</ref>. BMS firmware lockout increases the number of battery packs end up in waste, increasing pollution. Some of the materials like cobalt, are hazardous.

===Undermining ownership===
When the purchase is complete. The ownership is transferred to the user of the device. Locking out the battery after purchase is akin to installing a lock on someone else's property, and should be considered "Digital Handcuffs"<ref>{{Cite web |title=Words to Avoid (or Use with Care) Because They Are Loaded or Confusing |url=https://www.gnu.org/philosophy/words-to-avoid.html |url-status=live |archive-url=https://web.archive.org/web/20250909175856/https://www.gnu.org/philosophy/words-to-avoid.html |archive-date=2025-09-09 |access-date=2025-09-13 |website=GNU Operating System}}</ref>.

==Examples==

===Consumer electronics===
[[File:BQ40Z50R3 1.jpg|thumb|A screenshot of a "bricked" battery pack with healthy cells, note the red "PF_EN"]]
The most common consumer electronics using sophisticated battery management system for their multi-cell battery pack are laptop computers. There are many discussions about the battery "lockout" after replacing or recharging individual cells, indicating battery firmware lockout is the main obstacle of battery repair<ref>{{Cite web |date=2022-10-06 |title=How can I reset the laptop battery BMS? |url=https://electronics.stackexchange.com/questions/570919/how-can-i-reset-the-laptop-battery-bms |url-status=live |archive-url=https://web.archive.org/web/20250913130751/https://electronics.stackexchange.com/questions/570919/how-can-i-reset-the-laptop-battery-bms |archive-date=2025-09-13 |access-date=2025-09-13 |website=Stack Exchange}}</ref><ref>{{Cite web |date=30 Oct 2023 |title=(i changed every cell in laptop battery then bms locked How to unlock bms of acer e5 laptop battery, total battery in series is 15v but in bms output voltage is 0v i tried to short battery positive to output positive, but still no output, i think bms is locked how to unlock without software help |url=https://old.reddit.com/r/batteries/comments/17jogjr/i_changed_every_cell_in_laptop_battery_then_bms/ |url-status=live |archive-url=https://web.archive.org/web/20250913133735/https://old.reddit.com/r/batteries/comments/17jogjr/i_changed_every_cell_in_laptop_battery_then_bms/ |archive-date=13 Sep 2025 |access-date=13 Sep 2025 |website=[[Reddit]]}}</ref>.

===Commercial UAVs===
{{Main|DJI}}
DJI, a well known commercial UAV manufacturer, locks out the battery after long-term storage, claiming over-discharging damages the battery, even if the chemistry is still recoverable. Users who successfully "revives" the battery packs by charging their cells using a bench power supply and clearing the failure code, reports restored functionality<ref>{{Cite web |date=2024-03-21 |title=Reviving dead batteries - a heads up |url=https://mavicpilots.com/threads/reviving-dead-batteries-a-heads-up.146169/ |url-status=live |archive-url=https://web.archive.org/web/20250618000130/https://mavicpilots.com/threads/reviving-dead-batteries-a-heads-up.146169/ |archive-date=2025-06-18 |access-date=2025-09-13 |website=MavicPilots}}</ref><ref>{{Cite web |date=2023-08-02 |title=DJI Battery Killer repairing tool |url=https://greyarro.ws/t/dji-battery-killer-repairing-tool/68863 |url-status=live |access-date=2025-09-13 |website=Grey Arrows Drone Club |archive-url=http://web.archive.org/web/20260210084910/https://greyarro.ws/t/dji-battery-killer-repairing-tool/68863 |archive-date=10 Feb 2026}}</ref><ref>{{Cite web |last=McLoughlin |first=Liam |date=2023-10-01 |title=Repairing the DJI Spark Drone Battery with DJI Battery Killer, CP2112, & 9V battery |url=https://leelum.com/projects/repairing-the-dji-spark-drone-battery-with-dji-battery-killer-cp2112-9v-battery/ |url-status=live |archive-url=https://web.archive.org/web/20241211065622/https://leelum.com/projects/repairing-the-dji-spark-drone-battery-with-dji-battery-killer-cp2112-9v-battery/ |archive-date=2024-12-11 |access-date=2025-09-13 |website=Leelum}}</ref><ref>{{Cite web |title=DJI Battery Killer: Reviving Bricked DJI Drone Batteries with CP2112 & BMS Reset |url=https://www.elektroda.com/qa,dji-battery-killer-cp2112-bms-reset.html |url-status=live |website=elektroda |archive-url=http://web.archive.org/web/20260216013455/https://www.elektroda.com/qa,dji-battery-killer-cp2112-bms-reset.html |archive-date=16 Feb 2026}}</ref>. However some users reported "authentication failed"<ref>{{Cite web |date=2024-03-23 |title=Mavic pro battery authentication failed after clear pf |url=https://mavicpilots.com/threads/mavic-pro-battery-authentication-failed-after-clear-pf.144987/ |url-status=live |access-date=2025-09-13 |website=MavicPilots |archive-url=http://web.archive.org/web/20250517190808/https://mavicpilots.com/threads/mavic-pro-battery-authentication-failed-after-clear-pf.144987/ |archive-date=17 May 2025}}</ref> suggesting the possibility of parts serialization<ref>{{Cite web |last=Greenlee |first=Lauren |date=2023-01-17 |title=How Parts Pairing Kills Independent Repair |url=https://www.ifixit.com/News/69320/how-parts-pairing-kills-independent-repair |url-status=live |archive-url=https://web.archive.org/web/20250811033531/https://www.ifixit.com/News/69320/how-parts-pairing-kills-independent-repair |archive-date=2025-08-11 |access-date=2025-09-13 |website=iFixit}}</ref>.

===Home appliances===
{{Main|Dyson battery lifespan reduced by design and difficult to repair}}
Dyson appliances often come with battery packs omitting balancing resistors, leading to higher battery degradation. When the battery cells are unbalanced, repaired or replaced. The BMS chip will lockout. This can be mitigated with added resistors and a custom firmware that doesn't brick the battery upon maintenance<ref name=":2">{{Cite web |last=@tinfever |title=(Unofficial) Firmware Upgrade for Dyson V6/V7 Vacuum Battery Management System |url=https://github.com/tinfever/FW-Dyson-BMS |url-status=live |archive-url=https://web.archive.org/web/20250912021607/https://github.com/tinfever/FW-Dyson-BMS |archive-date=2025-09-12 |access-date=25 Mar 2025 |website=GitHub}}</ref>.

===Power tools===
{{Main|Milwaukee battery drm}}
Power tool manufacturers such as Ryobi and Makita are known to lock battery backs, causing good ones to fail and ended up in repair centers, or worse, landfills. Badar, a known electrical engineer, managed to recover 30 "bricked" battery pack back to normal, reducing e-waste<ref>https://www.youtube.com/watch?v=NQ_lyDyzEHY ([https://preservetube.com/watch?v=NQ_lyDyzEHY Archived])</ref>. Although 19% of them deeply discharged were no longer safe to charge. 65% of bricked batteries were purely due to software lockout with no performance impact after unbricking and recharging. Additionally, 13% had unbalanced cell, which were easily resolved by using an external power supply to bring the cells to the same level one by one, however, "unbricking" procedure is still required for normal use<ref>{{Cite web |last=Kayani |first=Badar Jahangir |date=2025-08-24 |title=Ryobi Battery Repair Guide |url=https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ |url-status=live |archive-url=https://web.archive.org/web/20250915074416/https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ |archive-date=2025-09-15 |access-date=2025-09-15 |website=Badar Jahangir Kayani}}</ref>.

===Electric vehicles===
Tesla cuts the range of some Model S and Model X by up to 20% by an OTA update. Some of the batteries became totally unusable, showing a "BMS_u029" error. Some users are able to reverse the change by flashing an older firmware, other users are forced to replace the entire battery pack, costing over $15,000<ref name=":0">{{Cite web |last=Crandall |first=Christine |date=2023-05-18 |title=How Tesla’s New OTA Software Update Cut EV Range By A Massive 20%, Owners Move To Sue |url=https://www.hotcars.com/tesla-software-update-cut-ev-range-owners-move-to-sue/ |archive-url=https://web.archive.org/web/20250413101832/https://www.hotcars.com/tesla-software-update-cut-ev-range-owners-move-to-sue/ |archive-date=2025-04-13 |access-date=2025-09-13 |website=Hotcars}}</ref>.

==Consumer reactions==
Although some consumers rationalize such behavior of increasing safety or avoiding liability. Many of them condemn such practices and describing it as planned obsolescence.

There are ways of tackling battery firmware lockout:

*Replacing the battery pack: This is the simplest way of "repairing" a "bricked" battery. However doing so is costly, increases e-waste production and further fuels planned obsolescence of said manufacturers. Some compatible third-party battery packs don't have lockout mechanism, making it possible for the user to replace cells in the pack and cycle charge to calibrate its meter. However, the exact makes and models aren't well-known.
*Extracting the BMS code: Certain logic analyzers can extract the code from communications to and from the BMS chip. Users or repair technicians can use this way to extract the "unseal" password, then reset the "permanent fail" flag and recalibrate the battery's capacity.
*Acquiring the unlock password: Some of the battery models' BMS code has been leaked, some of them are publicized<ref>{{Cite web |last=@davext |date=25 Jun 2024 |title=unbrick-dji |url=https://github.com/davext/unbrick-dji/blob/main/src/main.cpp |url-status=live |archive-url=https://web.archive.org/web/20250914163205/https://github.com/davext/unbrick-dji/blob/main/src/main.cpp |archive-date=14 Sep 2025 |access-date=14 Sep 2025 |website=[Github]}}</ref>. For others, it might be possible to purchase it in the grey market, however, there's a risk of scam as some of the passwords can be as expensive as the pack itself, and there's no guarantee of working.
*Resetting the BMS: Some specialized hardware and software can be used to clear the PF flag, reviving the battery without the need of knowing the battery's parameters. Most of the users don't have a need for modify the battery's parameters after repairing<ref>{{Cite web |date=2019-08-15 |title=Reset-BQ20xx |url=https://github.com/otofoto/Reset-BQ20xx |url-status=live |archive-url=https://web.archive.org/web/20220923061011/https://github.com/otofoto/Reset-BQ20xx |archive-date=2022-09-23 |access-date=2025-09-13 |website=[[Github]]}}</ref>.
*Install a custom (or OEM) BMS chip: Buying a brand new BMS chip and write own program. The main challenge is the knowledge of the working mechanism of the battery and its BMS. Different battery chemistries have different voltage and current characteristics, using the wrong data may cause incorrect capacity reading at best, or battery/device malfunction at worst.

==Lawsuits==
Four plaintiffs are suing Tesla over an automatic over-the-air (OTA) software update that they say reduced the driving range of their vehicles by 20 percent. Forced updates by Tesla may violate California's Computer Fraud and Abuse Act and the Unfair Competition Law<ref name=":0" />.

==References==
{{reflist}}

[[Category:Common terms]]

Forced BIOS firmware update

2026-02-26T15:07:48Z

Charlie 6: /* Lenovo */ added battery whitelist, with sources

Basic Input/Output System, also known as BIOS, is a type of firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process (power-on startup)<ref>{{Cite web |last=Kozierok |first=Charles M |date=2001-04-17 |title=Ref — System BIOS |url=https://www.pcguide.com/ref/mbsys/bios/index.htm |url-status=dead |archive-url=https://web.archive.org/web/20190218194254/https://www.pcguide.com/ref/mbsys/bios/index.htm |archive-date=2019-02-18 |access-date=2025-12-18 |website=The PC Guide}}</ref>.

Generally speaking, a working computer's BIOS doesn't need to be updated frequently due to the instinct risk of BIOS flashing<ref>{{Cite web |date=2025-04-12 |title=FlashBIOS |url=https://wiki.debian.org/FlashBIOS |url-status=live |access-date=2025-12-31 |website=Debian Wiki |archive-url=http://web.archive.org/web/20251118135550/https://wiki.debian.org/FlashBIOS |archive-date=18 Nov 2025}}</ref><ref>{{Cite web |date=2025-12-12 |title=Flashing BIOS from Linux |url=https://wiki.archlinux.org/title/Flashing_BIOS_from_Linux |url-status=live |access-date=2025-12-31 |website=ArchWiki |archive-url=http://web.archive.org/web/20260218024432/https://wiki.archlinux.org/title/Flashing_BIOS_from_Linux |archive-date=18 Feb 2026}}</ref>. However more and more mainstream computer manufactures starts pushing BIOS updates, often without user's consent or against the user's will, causing more issues and paves the way of controlling the device further.

==How it works==

===Pushing the BIOS update as non-optional Windows Update===
Traditionally, BIOS updates are done via a USB stick, which contains a FAT32 partition with bootloader and BIOS content. Recently the BIOS firmware is listed under Windows driver updates. Nowadays these updates are no longer under the "optional" category<ref>{{Cite web |last=@fec32a4de |date=2025-11-19 |title=How do I prevent Windows update from updating BIOS |url=https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |url-status=live |archive-url=https://web.archive.org/web/20251218145243/https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref><ref name=":0">{{Cite web |last=@redxps630 |date=2022-07-16 |title=how to prevent Windows Update from updating your bios |url=https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |url-status=live |archive-url=https://web.archive.org/web/20231021113238/https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |archive-date=2023-10-21 |access-date=2023-10-21 |website=Dell Community}}</ref>.

===Blocking BIOS downgrade===
In some computer models and BIOS versions, downgrade is blocked or "unsupported"<ref name=":1">{{Cite web |last=@ronyh |first= |date=2022-11-23 |title=BIOS Update blocked due to unsupported downgrade |url=https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |url-status=live |archive-url=https://web.archive.org/web/20240225053720/https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |archive-date=2024-02-25 |access-date=2025-12-18 |website=Dell Community}}</ref>, preventing the user from regaining lost functionalities.

===Removal of previous BIOS download link===

==Why it is a problem==

===Retroactive removal of functionalities===
Here's a non-exclusive list of removed functionalities:

*ACPI S3 sleep state<ref name=":2">{{Cite web |last=@mcgrubhub |date=2022-01-24 |title=Enable S3 Sleep State in BIOS Firmware Options |url=https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |url-status=live |archive-url=https://web.archive.org/web/20251218153346/https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |archive-date=2025-12-18 |access-date=2025-12-18 |website=HP Community}}</ref>, also known as "deep" sleep or "suspend-to-RAM"
*Undervolting<ref name=":3">{{Cite web |last=@u/DarkKnight04081995 |date=2020-11-17 |title=[GUIDE] Inspiron 7567: Bios downgrade from v1.12.1 to v1.11.0 |url=https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |url-status=live |archive-url=https://web.archive.org/web/20251218154156/https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, a method of reducing power consumption without decreasing performance
*CPU thermal design power (TDP)<ref name=":4">{{Cite web |last=@eXplode |date=2024-12-18 |title=How to Stop Automatic BIOS Updates and some hate for BIOS 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |url-status=live |archive-url=https://web.archive.org/web/20251002181913/https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |archive-date=2025-10-02 |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>
*Fan control.<ref>{{Cite web |last=@Mell |date=2025-10-04 |title=G713qm fan problem bios 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/g713qm-fan-problem-bios-331/td-p/1118443 |url-status=live |access-date=2025-12-18 |website=Republic of Gamers Forum |archive-url=http://web.archive.org/web/20251117101016/https://rog-forum.asus.com/t5/rog-strix-series/g713qm-fan-problem-bios-331/td-p/1118443 |archive-date=17 Nov 2025}}</ref>

===Reduced reliability/Planned obsolescence===
[[File:Asus bat chg v low.png|thumb|216x216px|Asus lowered the battery charging voltage to less than 16.6V, despite its 17.6V limited charging voltage.]]
Users reporting increased coil whine after a certain BIOS update<ref>{{Cite web |last=@ tom.m.culle150a02ca |date=2024-01-12 |title=Coil whine after bios update |url=https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |url-status=live |archive-url=https://web.archive.org/web/20251218183546/https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=MSI Global English Forum}}</ref>, possibly reducing reliability and increasing the failure rate.

Due to its unpredictable and forced nature, uncommanded BIOS updates have a higher chance of bricking the computer<ref name=":5">{{Cite web |last=@Parts-People Dell Laptop Experts |date=2025-11-02 |title=New Day, Another Bricked Laptop From Windows Update! |url=https://www.youtube.com/watch?v=8tRSjfFBtME |url-status=live |access-date=2025-12-18 |website=[[YouTube]] |archive-url=https://preservetube.com/watch?v=8tRSjfFBtME |archive-date=23 Feb 2026}}</ref>, such as interrupted BIOS update in the user's backpack due to over-temperature or battery depletion.

On some laptops, the battery capacity is restricted by reducing the charging voltage after a BIOS update, causing premature battery endurance decline. This practice is similar to [[Google Pixel 6a Battery Performance Program]] but without official announcement.

===Undermining ownership===
Manufacturers who force BIOS update often claim that blocking downgrade as "security features" to stop "bad player" from accessing the BIOS<ref name=":1" />. This is a classic example of "secure against the user"<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html#universal |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>.

==Examples==
[[File:Alienwarebiosrollback.png|thumb|From a comment on a laptop repair video<ref>{{Cite web |last=@Parts-People Dell Laptop Experts |date=2024-12-28 |title=Laptop Destroyed By Windows Update {{!}} Make It Stop! Microsoft |url=https://www.youtube.com/watch?v=pvhUPIkKt1s |url-status=live |access-date=2025-12-31 |website=[[YouTube]]}} ([https://preservetube.com/watch?v=pvhUPIkKt1s Archived])</ref>, a Dell user had to roll back a forced BIOS update to restore GPU performance.]]
These examples are non-exhaustive, some known instances are currently not listed due to insufficient source(s). All the examples below have BIOS update as non-optional Windows Update.

===Dell===
Blocked downgrade<ref name=":1" />, removed undervolting<ref name=":3" /><ref>{{Cite web |last=@WorldDj |date=2020-09-20 |title=Another victim of the BIOS update unfortunately |url=https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |url-status=live |archive-url=https://web.archive.org/web/20251218173346/https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref>, removed previous BIOS download links<ref>{{Cite web |title=Driver unavailable |url=https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=c5jy9 |access-date=2025-12-18 |website=Dell Product Support}}</ref>.

===Asus===
[[File:Ec update bricked bms 1.png|thumb|224x224px|A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful]]
Reduced TDP<ref name=":4" />, blocked downgrade, bricked battery.

===HP===
Blocked RAM speed<ref>{{Cite web |last=@Gburns53 |date=2021-10-25 |title=Forced BIOS update |url=https://h30434.www3.hp.com/t5/Gaming-Desktops/Forced-BIOS-update/td-p/8198864 |url-status=live |archive-date=15 Feb 2026 |access-date=2025-12-28 |website=HP Community |archive-url=http://web.archive.org/web/20260215152218/https://h30434.www3.hp.com/t5/Gaming-Desktops/Forced-BIOS-update/td-p/8198864 }}</ref>, disabled ACPI S3 sleep state<ref name=":2" />, blocked downgrade.

===Lenovo===
Disabled ACPI S3 sleep state<ref>{{Cite web |last=@Matusaprod |date=2023-07-15 |title=Linux sleep mode on newer thinkpad missing? |url=https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |url-status=live |archive-url=https://web.archive.org/web/20251218181844/https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, added battery whitelist<ref>{{Cite web |last=@Bob297586 |date=2020-03-27 |title=Help with Lenovo thinkpad w530 battery whitelist |url=https://linustechtips.com/topic/1200330-help-with-lenovo-thinkpad-w530-battery-whitelist/ |url-status=live |access-date=2026-02-26 |website=Linus Tech Tips}}</ref><ref name=":6">{{Cite web |last=@OrganicBrian |date=2023-12-27 |title=Thinkpad T420 battery suddenly rejected by the laptop: could an update have caused this? |url=https://forums.linuxmint.com/viewtopic.php?t=409942 |url-status=live |access-date=2026-02-26 |website=Linux Mint Forums}}</ref><ref>{{Cite web |last=@Scorpion8 |date=2020-04-27 |title=Thinkpad Battery "Whitelist" ... how does it work? |url=https://thinkpads.com/forum/viewtopic.php?t=130513 |url-status=live |access-date=2026-02-26 |website=thinkpads.com Support Community}}</ref>.

==Countermeasures==

===Disabling UEFI Encapsulation===
On some computer models, UEFI Encapsulation can be disabled in BIOS settings<ref name=":0" /><ref>{{Cite web |date=2023-04-30 |title=How to disable BIOS updates completely |url=https://old.reddit.com/r/Alienware/comments/133h83x/how_to_disable_bios_updates_completely/ |url-status=live |access-date=2026-02-26 |website=[[Reddit]]}}</ref>, disallowing the exchange of configuration data between the operating system and the UEFI firmware.

===Enabling "Do not include drivers with windows updates" in Group Policy===
Using Group Policy editor (gpedit.msc), users are able to exclude driver updates from Windows update<ref name=":0" /> since BIOS is often considered under drivers category. However, this method does not grantee success.

===Using a free operating system===
Free operating systems such as GNU/Linux respect user freedom. BIOS updates can be manually initiated using LVFS/fwupd. Although rare, it's not impossible for some Linux distributions to install BIOS updates automatically<ref name=":6" />.

===Board-level repair===
Flashing BIOS firmware on a bricked laptop can be done by using a custom programmer<ref name=":5" />.

===Non-BIOS mitigation methods===
Some functions can be re-enabled without downgrading BIOS. Advanced BIOS<ref>{{Cite web |last=@u/Dijkmeneer |date=2022-12-19 |title=How to disable Modern sleep and enable s3 sleep on a lenovo laptop |url=https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |url-status=live |archive-url=https://web.archive.org/web/20240520204041/https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |archive-date=2024-05-20 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, OpenCore<ref>{{Cite web |last=@MotorBottle |date=2023-10-01 |title=Enable S3 Sleep on ROG X13/G14/15 2021/2022 using OpenCore |url=https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |url-status=live |archive-url=https://web.archive.org/web/20250618061353/https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |archive-date=2025-06-18 |access-date=2025-12-19 |website=[[Github]]}}</ref>, Smokeless_UMAF<ref>{{Cite web |last=@DavidS95 |date=2023-05-07 |title=Bios Flasher? Where We’re Going, We Don’t Need Bios Flasher? |url=https://github.com/DavidS95/Smokeless_UMAF |url-status=live |archive-url=https://web.archive.org/web/20250925010047/https://github.com/DavidS95/Smokeless_UMAF/ |archive-date=2025-09-25 |access-date=2025-12-19 |website=[[Github]]}}</ref>.

==References==
{{reflist}}

[[Category:Common terms]]

Talk:MSI motherboard CMOS battery obsolescence

2026-02-26T12:33:06Z

Charlie 6: /* More Details */ new section

Framework

2026-02-16T04:15:20Z

Charlie 6: /* Positive Incidents */ changed title to "Positivities"

{{CompanyCargo
| Description =
| Founded = 2020-01
| Industry = Computer Hardware
| Logo = Framework Computer logo.svg
| ParentCompany =
| Type = Private
| Website = https://frame.work
}}

'''{{wplink|Framework Computer|Framework Computer, Inc.}}''' is an American personal computer manufacturer. It was founded in January 2020, by current CEO Nirav Patel. The company specializes in customization and repairability, the latter also helping the environment through making less laptops needing to be thrown out.

==Consumer impact summary==

===Freedom===
As a result of their products being highly modular and Framework not utilizing {{wplink|Right to repair#Software|parts pairing}}, consumers can heavily customize devices to their liking. Framework also offers DIY editions of their products which offers consumers the option to utilize their own sourced memory, storage and operating system.
===User Privacy===
As Framework sells solely the hardware and not the software, it doesn't need any more information than is necessary.

===Transparency===
Detailed assembly, repair and maintenance videos can be watched at the official knowledgebase<ref>{{Cite web |title=Welcome to the Framework Knowledge Base |url=https://knowledgebase.frame.work/ |url-status=live |website=Help Center}}</ref>. BIOS, firmware and driver updates are visible on e-mail subscription, knowledge base and (commentable) Framework Community posts<ref>{{Cite web |last=@ Quin_Chou |title=Framework Laptop 16 Ryzen 7040 BIOS 4.03 Release STABLE |url=https://community.frame.work/t/framework-laptop-16-ryzen-7040-bios-4-03-release-stable/79274 |url-status=live |access-date=2026-01-14 |website=Framework Community}}</ref>. No [[Forced BIOS Firmware Update|forced BIOS updates]] for Windows users.

===Business Model===
Framework's business model is to make repairable and customizable computers, at a hardware level.

===Market Control===
Framework is a relatively new player in the OEM PC sector, but in the niche they occupy, they are a significant player, mostly due to a lack of competition.

==Incidents==

===Laptop 13 61Wh Battery Swelling:===
The high energy density 61Wh battery has more swelling incidents than the previous 55Wh battery<ref>{{Cite web |last=@Adam_Schindler |date=2025-09-13 |title=61Wh Battery Inflated |url=https://community.frame.work/t/61wh-battery-inflated/75169 |url-status=live |access-date=2026-01-24 |website=Framework Community}}</ref><ref>{{Cite web |last=@John_Goerzen |date=2024-09-18 |title=Swollen Battery <1yr in, How to address? |url=https://community.frame.work/t/swollen-battery-1yr-in-how-to-address/57848 |url-status=live |access-date=2026-01-24 |website=Framework Community}}</ref><ref>{{Cite web |last=@qemu-system-x86_64 |date=2025-11-12 |title=Battery swelling (FL13 / amd 7040 / 61Wh) |url=https://community.frame.work/t/battery-swelling-fl13-amd-7040-61wh/77653 |url-status=live |access-date=2026-01-24 |website=Framework Community}}</ref>. Framework mitigated this problem by having the battery automatic discharge down to 85% after fully charged and connected on AC adapter for more than three days<ref>{{Cite web |last=@Kieran_Levin |date=2024-10-25 |title=BIOS update required to prevent premature aging of 61Wh battery |url=https://community.frame.work/t/bios-update-required-to-prevent-premature-aging-of-61wh-battery/59580 |url-status=live |access-date=2026-01-24 |website=Framework Community}}</ref>. However, this function may interfere with manual charge limit setting.

===Laptop 16 Overheating:===
Early models have liquid metal as the thermal interface between the CPU and its heat sink, which is known to degrade, leading to worse and uneven heat transfer<ref>{{Cite web |last=@zachary_stout |date=2024-08-04 |title=Uneven CPU thermals! |url=https://community.frame.work/t/uneven-cpu-thermals/55614/1 |url-status=live |access-date=2026-01-14 |website=Framework Community}}</ref>. Later models replaced it with PTM7958 phase change materials, early users can request PTM7958 for free, however removing the liquid metal can be challenging.{{Citation needed}}

==Positivities ==

===Assisting repairability:===
Framework utilizes QR codes on parts of their devices which users can scan to get support, view guides, order replacements or upgrades.<ref>{{Cite web |title=Try It Out |url=https://frame.work/try-it-out |url-status=live |access-date=2026-01-24 |website=Framework}}</ref>

===Highly favourable reviews on iFixit:===
The Laptop 12,<ref>{{Cite web |last=Chamberlain |first=Elizabeth |date=2025-06-18 |title=Tough, Tiny, and Totally Repairable: Inside the Framework 12 |url=https://www.ifixit.com/News/111201/tough-tiny-and-totally-repairable-inside-the-framework-12 |url-status=live |access-date=2026-01-24 |website=iFixit}}</ref> 13<ref>{{Cite web |last=Dixon |first=Taylor |date=2021-07-28 |title=Framework Laptop Teardown: 10/10, But is it Perfect? |url=https://www.ifixit.com/News/51614/framework-laptop-teardown-10-10-but-is-it-perfect |url-status=live |access-date=2026-01-24 |website=iFixit}}</ref> and 16<ref>{{Cite web |last=iFixit |date=2024-01-23 |title=The Framework 16 Teardown!-Best Teardown of the year already?? |url=https://youtube.com/watch?v=Y8uv8fajOrc |url-status=live |access-date=2026-01-24 |website=YouTube}}</ref> have all received highly favourable reviews on [https://www.ifixit.com iFixit], a pro consumer repair outlet, for their repairability.

==Products==

*'''Framework Desktop (''February 2025''):''' a mini-computer designed to have it's case be more customizable through tiles that are able to be taken out and put back somewhere else.

*'''Framework Laptop 12 (''February 2025''):''' is told as being a customizable laptop with 360° support and it comes with a stylus, being able to practically be used as a tablet.<ref>https://frame.work/laptop12</ref>

*'''Framework Laptop 13 (''July 2021''):''' is closer to your usual laptop, but is more repairable, it is seen as the most popular option by far from the other products.

*'''Framework Laptop 16 (''March 2023''):''' It is the second most popular option and offers more customization than the Laptop 13. It can provide greater performance, and its keyboard is customizable, allowing it to be removed and repositioned. The keypad can also be removed and replaced with lighting modules, enabling a higher level of personalization.

==See also==

*Framework About Us: https://frame.work/about
*Framework Guides: https://guides.frame.work/

==References==
{{reflist}}
[[Category:{{PAGENAME}}]]

Oneplus phone update introduces hardware anti-rollback

2026-01-29T02:40:33Z

Charlie 6: removed "protection" from anti-rollback and changed to "restriction" and "mechanism" respectively

{{IncidentCargo
|Company=OnePlus, OPPO, BBK Electronics
|StartDate=2026-01
|EndDate=
|Status=Ongoing
|ProductLine=
|Product=OnePlus 13, OnePlus 13T, OnePlus 15
|ArticleType=Product
|Type=Bricking, Firmware Restriction, Right to Repair, Planned Obsolescence
|Description=OnePlus firmware update introduces permanent hardware-level anti-rollback mechanism that bricks devices attempting to downgrade
}}{{OngoingEvent}}

The OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident refers to the January 2026 deployment of firmware updates by [[OnePlus]] that introduced a hardware-level anti-rollback mechanism. This permanently prevents users from downgrading their devices or installing custom ROMs. The updates, which affected the OnePlus 13, OnePlus 13T, and OnePlus 15, irreversibly blow electronic fuses inside the device's [[Qualcomm]] processor. Any subsequent attempt to install older firmware results in a permanent "hard brick" - the device becomes unusable. This cannot be repaired through standard methods.<ref name="xda-warning">{{cite web |url=https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/ |title=[CRITICAL WARNING] ColorOS 16.0.3.501 Updates = PERMANENT Anti-Rollback (ARB) & Fuse Blown. DO NOT DOWNGRADE! |website=XDA Forums |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

OnePlus has not issued any official statement addressing the mechanism.<ref name="android-authority">{{cite web |url=https://www.androidauthority.com/oneplus-arb-protection-3633783/ |title=New OnePlus updates can permanently lock your phone's software future |author=Adamya Sharma |website=Android Authority |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

==Background==

OnePlus was founded on December 16, 2013, by Pete Lau and Carl Pei, both former OPPO executives, with OPPO Electronics as the primary investor. The company's first device, the OnePlus One, shipped with [[wikipedia:CyanogenMod|CyanogenMod]], a commercial variant of the popular custom ROM, through an exclusive licensing agreement with Cyanogen Inc.This partnership positioned OnePlus as a choice for modding enthusiasts.

When that partnership collapsed due to Cyanogen's exclusivity deal with Micromax in India, OnePlus developed OxygenOS for global markets and HydrogenOS for China. In July 2021, OnePlus merged OxygenOS with OPPO's ColorOS, sharing a common codebase while maintaining separate branding for different regions.

==Timeline==

On January 18, 2026, users who updated to ColorOS 16.0.3.501 began reporting that their devices could not be reverted to previous versions. One OnePlus 13 owner reported that after flashing ColorOS 15, the phone entered EDL mode and was detected as "Qualcomm HS-USB QDLoader 9008," with the Chimera Rescue Tool unable to find a working programmer.<ref name="hard-brick-report">{{cite web |url=https://xdaforums.com/t/hard-brick-oneplus-13-pjz110.4775945/ |title=Hard Brick Oneplus 13 (PJZ110) |website=XDA Forums |date=January 18, 2026 |access-date=January 22, 2026}}</ref>

On January 19, 2026, XDA Forums member AdaUnlocked posted a warning thread documenting the issue with evidence including chat logs showing that the CPU anti-rollback fuse had been blown, warnings from paid unbrick services stating that Snapdragon 8 Elite devices updated to the affected build should not be downgraded, & user reports confirming that motherboard replacement was required after failed downgrade attempts.<ref name="xda-warning" />

DroidWin confirmed that OnePlus had removed the download links for the OnePlus 13 downgrade firmware for all regions and that OnePlus 12 downgrade packages had been removed as well.<ref name="droidwin">{{cite web |url=https://droidwin.com/oneplus-android-16-anti-rollback-is-here/ |title=OnePlus Android 16 Anti Rollback is Here! |author=Sadique Hassan |website=DroidWin |date=January 20, 2026 |access-date=January 22, 2026}}</ref>

==Affected devices==

The following devices and firmware versions have been confirmed to trigger the anti-rollback fuse:

*OnePlus 13 / 13T: ColorOS 16.0.3.501<ref name="xda-warning" />
*OnePlus 15: ColorOS 16.0.3.503<ref name="xda-warning" />
*OnePlus Nord CE 3: OOS 15.0.0.1301

Android Authority reported that the OPPO Find X8 series is also considered at high risk.<ref name="android-authority" />

The XDA thread advises users to avoid any OTA update ending in .500, .501, or .503 until community verification confirms safety.<ref name="xda-warning" />

==Technical mechanism==

The anti-rollback mechanism uses Qfprom (Qualcomm Fuse Programmable Read-Only Memory), a region on Qualcomm processors containing one-time programmable electronic fuses. These microscopic components are physically altered when "blown"; a controlled voltage pulse permanently changes the fuse's state from "0" to "1." This change cannot be reversed by any software means.<ref name="xda-warning" /> A complete motherboard replacement is the only possible method to remedy it.

DroidWin explained that the implementation works similarly to how Knox gets tripped on Samsung devices: both are e-fuses embedded in the motherboard that become permanently fused upon triggering. Changing the motherboard is the only way to restore the default state.<ref name="droidwin" />

When the device powers on, the Primary Boot Loader (PBL) in the processor's ROM loads and verifies the eXtensible Boot Loader (XBL). The PBL reads the current anti-rollback version from the Qfprom fuses and compares it against the firmware's embedded version number. If the firmware version is lower than the fuse value, boot is rejected. When newer firmware successfully boots, the bootloader issues commands through Qualcomm's TrustZone to blow additional fuses, permanently recording the new minimum version.<ref name="xda-warning" />

EDL (Emergency Download Mode), historically the last-resort recovery option using USB interface 9008, cannot bypass this restriction. While EDL operates from the Primary Boot Loader ROM and allows direct storage writes, the eFuses remain in the processor silicon. EDL's Firehose programmers must be OEM-signed and contain their own anti-rollback versions; previously functional unbrick tools now fail because the fuse has been blown.<ref name="xda-warning" />

As explained on the XDA thread, the term "Fuse Blown" refers to the Qfprom eFuses (Electronic Fuses) inside the Snapdragon chipset being electrically switched from "0" to "1", effectively preventing older software from running, rather than a physical fuse burnout.<ref name="xda-warning" />

==Impact on custom ROMs==

The XDA warning describes the situation as dangerous for custom ROM users. Flashing incompatible firmware on top of ColorOS 16.0.3.501 (or newer) will result in an immediate hard brick. Custom ROMs package firmware components from the stock firmware they were built against. If a user's device has been updated to a fused firmware version & they flash a custom ROM built against older firmware, the anti-rollback mechanism triggers immediately.<ref name="xda-warning" />

The community recommendation is that users who have updated should not flash any custom ROM until developers explicitly announce support for fused devices with the new firmware base.<ref name="xda-warning" />

==Company response==

As of 23 January, 2026, OnePlus and OPPO have issued no official statement addressing the anti-rollback fuse mechanism. No press releases, community forum responses, or social media acknowledgments explain the policy or respond to reports of bricked devices.<ref name="android-authority-opinion">{{cite web |url=https://www.androidauthority.com/oneplus-fan-modding-bootloader-changes-breaking-point-3634505/ |title=I've been a OnePlus fan for 12 years, but this latest update is my breaking point |author=Dhruv Bhutani |website=Android Authority |date=January 23, 2026 |access-date=January 26, 2026}}</ref>

The removal of official downgrade packages from OnePlus' community forums on 19 January, 2026, was interpreted by users as confirmation that the mechanism was intentional.<ref name="droidwin" />

On January 27th 2026, in response to Android Authority OnePlus issued the following statement.<ref>{{Cite web |last=Simons |first=Hadlee |date=2026-01-27 |title=Here's why OnePlus bricked your phone when you tried downgrading it |url=https://www.androidauthority.com/oneplus-brick-phones-statement-3635475/ |url-status=live |access-date=2026-01-27 |website=Android Authority}}</ref><blockquote>To further strengthen device security, we’ve temporarily paused the ability to downgrade from 16.0.2.50x software builds to older builds. We will be restoring the ability to downgrade software builds in our next routine software update, but in the meantime customers looking to downgrade their build can contact OnePlus after sales channels directly.</blockquote>

==Comparison with other manufacturers==

Anti-rollback mechanism exists across the smartphone industry, but implementations vary in their impact on users.

[[Samsung Knox]] implements fuse-based security that trips permanently when non-OEM firmware is flashed, disabling Samsung Pay and Secure Folder. Android Authority noted that the new OnePlus implementation is functionally identical to Samsung's model, where eFuses serve as irreversible warrants of system integrity, punishing modification with permanent hardware states.<ref name="android-authority" />

==See also==

*[[Right to repair]]

*[[Planned obsolescence]]
*[[Self-destructive design]]

*[[Bootloader unlocking]]

*[[Custom ROM]]

*[[Samsung Knox]]

==References==

{{reflist}}

[[Category:2026 in technology]]

[[Category:OnePlus]]

[[Category:Right to repair]]

[[Category:Consumer protection]]

[[Category:Smartphone software]]

[[Category:Controversies]]

Minecraft Chat Reporting and Restriction

2026-01-26T04:11:28Z

Charlie 6: a reference

{{IncidentCargo
|Company=Microsoft
|Status=Active
|Product=Minecraft
|ArticleType=Product
|Type=Privacy
}}
{{Ph-I-Int}}
==Background==
Minecraft is a block-based multiplayer sandbox game made by [[Mojang|Mojang Studios]]. The game received criticism following Mojang's acquisition by [[Microsoft]].

==[Incident]==

===Chat reporting===
Introduced in Minecraft version 1.19.1, on 1.20.2, player skins are reportable<ref>{{Cite web |date=2025-12-23 |title=Java Edition 1.19.1 |url=https://minecraft.wiki/w/Java_Edition_1.19.1 |url-status=live |access-date=2026-01-26 |website=Minecraft Wiki}}</ref>. When a player is reported, they could be banned, temporarily or permanently, on all mutiplayer gameplay, including private servers and local area network (LAN) game. On Realms server, chat messages are automatically scanned and player can be banned even if their massages haven't been reported by anyone else<ref>{{Cite web |title=Our Commitment to Player Safety |url=https://help.minecraft.net/hc/en-us/articles/8047895358605-Our-Commitment-to-Player-Safety |url-status=live |archive-url=https://web.archive.org/web/20251230010733/https://help.minecraft.net/hc/en-us/articles/8047895358605-Our-Commitment-to-Player-Safety |archive-date=2025-12-30 |access-date=2026-01-26 |website=Minecraft Help Center}}</ref>.

===Chat restriction===
The mechanism used for chat restriction was implemented in 1.16.3 for parental control<ref>{{Cite web |last=@Aizistral |date=2026-01-26 |title=Minecraft's New Chat Restrictions are WORSE Than You Think |url=https://www.youtube.com/watch?v=tI0ZGoaTgMg |url-status=live |access-date=2021-01-26 |website=[[Youtube]]}}</ref>. However, since the "user flags" are connected to the player's Microsoft account. Microsoft can alter them under its own discretion, without the user's (or the user's parents' if parental control is enabled) consent.

In January 2026, Microsoft announced that in February 2026, Minecraft from UK region are blocked (Java Edition) or friend-only (PE, Xbox and Bedrock Edition) unless the client's Xbox account is age-verified. Microsoft is planning to expand the restriction to other regions.

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
The restrictions are done on client-side. Minecraft players made mods to get around these restrictions

===No Chat Reports===
This mod removes cryptographically signatures from chat messages, making them unreportable. It also disables telemetry<ref>{{Cite web |last=@Aizistral |title=No Chat Reports |url=https://modrinth.com/mod/no-chat-reports |url-status=live |archive-url=https://web.archive.org/web/20260114145643/https://modrinth.com/mod/no-chat-reports |archive-date=2026-01-14 |access-date=2026-01-26 |website=Modrinth}}</ref>.

===SecureChat===
This mod adds encryption to your chat<ref>{{Cite web |last=@BRNSystems |title=SecureChat |url=https://modrinth.com/mod/securechat |url-status=live |access-date=2026-01-26 |website=Modrinth}}</ref>.

===No Chat Restrictions===
A work in progress mod that removes the restrictions around the use of multiplayer features, in particular in-game chat<ref>{{Cite web |last=@Aizistral |date=2026-01-25 |title=No Chat Restrictions |url=https://legacy.curseforge.com/minecraft/mc-mods/no-chat-restrictions |url-status=live |access-date=2026-01-26 |website=Curseforge}}</ref>.

==References==
{{reflist}}

{{Ph-I-C}}

Minecraft Chat Reporting and Restriction

2026-01-26T03:47:36Z

Charlie 6: /* Consumer response */ added contents

{{IncidentCargo
|Company=Microsoft
|Status=Active
|Product=Minecraft
|ArticleType=Product
|Type=Privacy
}}
{{Ph-I-Int}}
==Background==
Minecraft is a block-based multiplayer sandbox game made by [[Mojang|Mojang Studios]]. The game received criticism following Mojang's acquisition by [[Microsoft]].

==[Incident]==

===Chat reporting===
Introduced in Minecraft version 1.19.1, on 1.20.2, player skins are reportable<ref>{{Cite web |date=2025-12-23 |title=Java Edition 1.19.1 |url=https://minecraft.wiki/w/Java_Edition_1.19.1 |url-status=live |access-date=2026-01-26 |website=Minecraft Wiki}}</ref>. When a player is reported, they could be banned, temporarily or permanently, on all mutiplayer gameplay, including private servers and local area network (LAN) game. On Realms server, chat messages are automatically scanned and player can be banned even if their massages haven't been reported by anyone else.

===Chat restriction===
The mechanism used for chat restriction was implemented in 1.16.3 for parental control<ref>{{Cite web |last=@Aizistral |date=2026-01-26 |title=Minecraft's New Chat Restrictions are WORSE Than You Think |url=https://www.youtube.com/watch?v=tI0ZGoaTgMg |url-status=live |access-date=2021-01-26 |website=[[Youtube]]}}</ref>. However, since the "user flags" are connected to the player's Microsoft account. Microsoft can alter them under its own discretion, without the user's (or the user's parents' if parental control is enabled) consent.

In January 2026, Microsoft announced that in February 2026, Minecraft from UK region are blocked (Java Edition) or friend-only (PE, Xbox and Bedrock Edition) unless the client's Xbox account is age-verified. Microsoft is planning to expand the restriction to other regions.

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
The restrictions are done on client-side. Minecraft players made mods to get around these restrictions

===No Chat Reports===
This mod removes cryptographically signatures from chat messages, making them unreportable. It also disables telemetry<ref>{{Cite web |last=@Aizistral |title=No Chat Reports |url=https://modrinth.com/mod/no-chat-reports |url-status=live |archive-url=https://web.archive.org/web/20260114145643/https://modrinth.com/mod/no-chat-reports |archive-date=2026-01-14 |access-date=2026-01-26 |website=Modrinth}}</ref>.

===SecureChat===
This mod adds encryption to your chat<ref>{{Cite web |last=@BRNSystems |title=SecureChat |url=https://modrinth.com/mod/securechat |url-status=live |access-date=2026-01-26 |website=Modrinth}}</ref>.

===No Chat Restrictions===
A work in progress mod that removes the restrictions around the use of multiplayer features, in particular in-game chat<ref>{{Cite web |last=@Aizistral |date=2026-01-25 |title=No Chat Restrictions |url=https://legacy.curseforge.com/minecraft/mc-mods/no-chat-restrictions |url-status=live |access-date=2026-01-26 |website=Curseforge}}</ref>.

==References==
{{reflist}}

{{Ph-I-C}}

Oneplus phone update introduces hardware anti-rollback

2026-01-26T03:01:54Z

Charlie 6: /* See also */ added link to self-destructive design

{{IncidentCargo
|incident_name = OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident
|date = January 2026
|company = OnePlus, OPPO, BBK Electronics
|industry = Consumer electronics, Smartphones
|category = Firmware restriction, Right to repair
|status = Ongoing
|description = OnePlus firmware update introduces permanent hardware-level anti-rollback mechanism that bricks devices attempting to downgrade
}}{{OngoingEvent}}

The OnePlus ColorOS 16.0.3.501 Anti-Rollback Fuse Incident refers to the January 2026 deployment of firmware updates by [[OnePlus]] that introduced a hardware-level anti-rollback mechanism. This permanently preventing users from downgrading their devices or installing custom ROMs. The updates, which affected the OnePlus 13, OnePlus 13T, and OnePlus 15, blow irreversible electronic fuses in the device's [[Qualcomm]] processor. Any subsequent attempt to install older firmware results in a permanent "hard brick" - the device becomes unusable. This cannot be repaired through standard methods.<ref name="xda-warning">{{cite web |url=https://xdaforums.com/t/critical-warning-coloros-16-0-3-501-updates-permanent-anti-rollback-arb-fuse-blown-do-not-downgrade.4775930/ |title=[CRITICAL WARNING] ColorOS 16.0.3.501 Updates = PERMANENT Anti-Rollback (ARB) & Fuse Blown. DO NOT DOWNGRADE! |website=XDA Forums |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

OnePlus has not issued any official statement addressing the mechanism.<ref name="android-authority">{{cite web |url=https://www.androidauthority.com/oneplus-arb-protection-3633783/ |title=New OnePlus updates can permanently lock your phone's software future |author=Adamya Sharma |website=Android Authority |date=January 19, 2026 |access-date=January 22, 2026}}</ref>

==Background==

OnePlus was founded on December 16, 2013, by Pete Lau and Carl Pei, both former OPPO executives, with OPPO Electronics as the primary investor. The company's first device, the OnePlus One, shipped with [[wikipedia:CyanogenMod|CyanogenMod]], a commercial variant of the popular custom ROM, through an exclusive licensing agreement with Cyanogen Inc.This partnership positioned OnePlus as a choice for modding enthusiasts.

When that partnership collapsed due to Cyanogen's exclusivity deal with Micromax in India, OnePlus developed OxygenOS for global markets and HydrogenOS for China. In July 2021, OnePlus merged OxygenOS with OPPO's ColorOS, sharing a common codebase while maintaining separate branding for different regions.

==Timeline==

On January 18, 2026, users who updated to ColorOS 16.0.3.501 began reporting that their devices could not be reverted to previous versions. One OnePlus 13 owner reported that after flashing ColorOS 15, the phone entered EDL mode and was detected as "Qualcomm HS-USB QDLoader 9008," with the Chimera Rescue Tool unable to find a working programmer.<ref name="hard-brick-report">{{cite web |url=https://xdaforums.com/t/hard-brick-oneplus-13-pjz110.4775945/ |title=Hard Brick Oneplus 13 (PJZ110) |website=XDA Forums |date=January 18, 2026 |access-date=January 22, 2026}}</ref>

On January 19, 2026, XDA Forums member AdaUnlocked posted a warning thread documenting the issue with evidence including chat logs showing that the CPU anti-rollback fuse had been blown, warnings from paid unbrick services stating that Snapdragon 8 Elite devices updated to the affected build should not be downgraded, & user reports confirming that motherboard replacement was required after failed downgrade attempts.<ref name="xda-warning" />

DroidWin confirmed that OnePlus had removed the download links for the OnePlus 13 downgrade firmware for all regions and that OnePlus 12 downgrade packages had been removed as well.<ref name="droidwin">{{cite web |url=https://droidwin.com/oneplus-android-16-anti-rollback-is-here/ |title=OnePlus Android 16 Anti Rollback is Here! |author=Sadique Hassan |website=DroidWin |date=January 20, 2026 |access-date=January 22, 2026}}</ref>

==Affected devices==

The following devices and firmware versions have been confirmed to trigger the anti-rollback fuse:

*OnePlus 13 / 13T: ColorOS 16.0.3.501<ref name="xda-warning" />
*OnePlus 15: ColorOS 16.0.3.503<ref name="xda-warning" />

Android Authority reported that the OPPO Find X8 series is also considered at high risk.<ref name="android-authority" />

The XDA thread advises users to avoid any OTA update ending in .500, .501, or .503 until community verification confirms safety.<ref name="xda-warning" />

==Technical mechanism==

The anti-rollback mechanism uses Qfprom (Qualcomm Fuse Programmable Read-Only Memory), a region on Qualcomm processors containing one-time programmable electronic fuses. These microscopic components are physically altered when "blown"; a controlled voltage pulse permanently changes the fuse's state from "0" to "1." This change cannot be reversed by any software means.<ref name="xda-warning" /> A complete motherboard replacement is the only possible method to remedy it.

DroidWin explained that the implementation works similarly to how Knox gets tripped on Samsung devices: both are e-fuses embedded in the motherboard that become permanently fused upon triggering. Changing the motherboard is the only way to restore the default state.<ref name="droidwin" />

When the device powers on, the Primary Boot Loader (PBL) in the processor's ROM loads and verifies the eXtensible Boot Loader (XBL). The PBL reads the current anti-rollback version from the Qfprom fuses and compares it against the firmware's embedded version number. If the firmware version is lower than the fuse value, boot is rejected. When newer firmware successfully boots, the bootloader issues commands through Qualcomm's TrustZone to blow additional fuses, permanently recording the new minimum version.<ref name="xda-warning" />

EDL (Emergency Download Mode), historically the last-resort recovery option using USB interface 9008, cannot bypass this protection. While EDL operates from the Primary Boot Loader ROM and allows direct storage writes, the eFuses remain in the processor silicon. EDL's Firehose programmers must be OEM-signed and contain their own anti-rollback versions; previously functional unbrick tools now fail because the fuse has been blown.<ref name="xda-warning" />

As explained on the XDA thread, the term "Fuse Blown" refers to the Qfprom eFuses (Electronic Fuses) inside the Snapdragon chipset being electrically switched from "0" to "1", effectively preventing older software from running, rather than a physical fuse burnout.<ref name="xda-warning" />

==Impact on custom ROMs==

The XDA warning describes the situation as dangerous for custom ROM users. Flashing incompatible firmware on top of ColorOS 16.0.3.501 (or newer) will result in an immediate hard brick. Custom ROMs package firmware components from the stock firmware they were built against. If a user's device has been updated to a fused firmware version & they flash a custom ROM built against older firmware, the anti-rollback mechanism triggers immediately.<ref name="xda-warning" />

The community recommendation is that users who have updated should not flash any custom ROM until developers explicitly announce support for fused devices with the new firmware base.<ref name="xda-warning" />

==Company response==

As of 23 January, 2026, OnePlus and OPPO have issued no official statement addressing the anti-rollback fuse mechanism. No press releases, community forum responses, or social media acknowledgments explain the policy or respond to reports of bricked devices.<ref name="android-authority-opinion">{{cite web |url=https://www.androidauthority.com/oneplus-fan-modding-bootloader-changes-breaking-point-3634505/ |title=I've been a OnePlus fan for 12 years, but this latest update is my breaking point |author=Dhruv Bhutani |website=Android Authority |date=January 23, 2026 |access-date=January 26, 2026}}</ref>

The removal of official downgrade packages from OnePlus' community forums on 19 January, 2026, was interpreted by users as confirmation that the mechanism was intentional.<ref name="droidwin" />

==Comparison with other manufacturers==

Anti-rollback protection exists across the smartphone industry, but implementations vary in their impact on users.

[[Samsung Knox]] implements fuse-based security that trips permanently when non-OEM firmware is flashed, disabling Samsung Pay and Secure Folder. Android Authority noted that the new OnePlus implementation is functionally identical to Samsung's model, where eFuses serve as irreversible warrants of system integrity, punishing modification with permanent hardware states.<ref name="android-authority" />

==See also==

*[[Right to repair]]

*[[Planned obsolescence]]
*[[Self-destructive design]]

*[[Bootloader unlocking]]

*[[Custom ROM]]

*[[Samsung Knox]]

==References==

{{reflist}}

[[Category:2026 in technology]]

[[Category:OnePlus]]

[[Category:Right to repair]]

[[Category:Consumer protection]]

[[Category:Smartphone software]]

[[Category:Controversies]]

Minecraft Chat Reporting and Restriction

2026-01-26T02:39:28Z

Charlie 6: Create page, basic sub heading

Minecraft Chat Reporting and Restriction

2026-01-26T02:22:28Z

Charlie 6: Created page with "{{IncidentCargo |Company=Microsoft |Status=Active |Product=Minecraft |ArticleType=Product |Type=Privacy }} {{Ph-I-Int}} ==Background== {{Ph-I-B}} ==[Incident]== {{Ph-I-I}} ===[Company]'s response=== {{Ph-I-ComR}} ==Lawsuit== {{Ph-I-L}} ==Consumer response== {{Ph-I-ConR}} ==References== {{reflist}} {{Ph-I-C}}"

{{IncidentCargo
|Company=Microsoft
|Status=Active
|Product=Minecraft
|ArticleType=Product
|Type=Privacy
}}
{{Ph-I-Int}}
==Background==
{{Ph-I-B}}

==[Incident]==
{{Ph-I-I}}

===[Company]'s response===
{{Ph-I-ComR}}

==Lawsuit==
{{Ph-I-L}}

==Consumer response==
{{Ph-I-ConR}}

==References==
{{reflist}}

{{Ph-I-C}}

Self-destructive design

2026-01-25T12:06:39Z

Charlie 6: added a type of self-destructive design: kill switch

'''Self-destructive design''' is a generic form of product design whereby it is possible that some if not all functions of the device will cease functioning. Self-destructive design can occur unintentionally due to oversights but it can be implemented intentionally. Self-destructive design is split into numerous types: '''discontinuation bricking, digital discontinuation bricking, end-of-life product discontinuation,''' and '''planned obsolescence'''. All forms of self-destructive design harm consumers in that it reduces product lifetime and increases waste production.

*'''Planned obsolescence''' is a business strategy where a product is designed in such a way that it will inevitably fail or become obsolete and require replacement with a non-obsolete product.
*'''End-of-life product discontinuation (EOL)''' is a generic term describing the discontinuation of production of a product and its parts.
**'''Discontinuation bricking,''' also known as '''Physical discontinuation bricking''' is a symptom of EOL where a product completely ceases functioning, likely because it is no longer reparable.
**'''Digital discontinuation bricking''' is a symptom of EOL where a product that depends on a network connection ceases functioning either because the company remotely shut down the product or shut down services the product depends upon.
*'''Kill-switch.''' A mechanism to render the device unusable, often done remotely and deliberately.

==Overall impacts==
All types of self-destructive design share common negative impacts on consumer rights.

===Actively malicious behavior===
All types of self-destructive design can occur out of malicious intent to ruin a consumer's product.

*'''Planned obsolescence''' is the only type of self-destructive design that can be attributed as totally malicious; companies that institute planned obsolescence in their designs do so to ensure their customers buy more products. In addition invisible planned obsolescence can make consumers buy products they otherwise would not have bought with the knowledge of the dark practice.
*'''EOL''' is less likely to be malicious as it actually does provide real benefits for companies; no one expects early 20th century cars to remain supported or in production in the 21st century. There is room for malicious EOL decisions with the intent to make consumers buy more products.
**'''Discontinuation bricking''' is also less likely to be malicious as it can occur when a company goes out of business, but for when companies just decide to take the product offline entirely it is more questionable. There is definitely room for malicious bricking incidents to occur.
*'''Kill switch''' is a hardware mechanism is implemented on the device by the manufacturer. Which can be later "activated" often remotely by a software update. Should the condition met, the kill switch will trigger, render the hardware permanently unusable.

It should also be noted that EOL products can fall into the category of planned obsolescence if there is evidence to support the producer designed the product such that it would become obsolete.

===Environmental harm===
Excessive waste of all forms are inevitable in all types of self-destructive design. The loss of product or component functionality will create justification for consumers to discard their product and replace it with a functioning one.

*'''Planned obsolescence''' is special in this case because its sole intent is to make products become waste so that consumers buy more products.
*'''EOL''' will generate waste due to the decrease in repairability. If it becomes to expensive to repair an EOL product it becomes waste.
**'''Physical Discontinuation bricking''' usually results from design choices that make the device hard to repair.
**'''Digital discontinuation bricking''' is even more severe in this regard due to dependence on remote servers, most consumers will not build their own server architecture for the sake of running a digital app or device. Additionally for the small subset of consumers that would be interested, they are rendered incapable of doing so since these servers often will use proprietary software, which often is not publicly accessible for personal usage.

The result of self-destructive design is an inevitable harm to the environment even though many companies claim to be "sustainable" while engaging in the practice.<ref>[https://web.archive.org/web/20250128190650/https://www.apple.com/environment/ Environment - Apple] - archive.org - archived 2025-01-28</ref>

===Hard vs soft bricking===
The term '''"bricking"''' refers to the process of a product losing functionality to the point that it becomes "brick-like" -- just a useless object. A product becomes '''hard-bricked''' if all its functionality is lost, usually in a very sudden manner -- in the flick of a switch. Hard-bricked devices are often difficult to de-brick. A product becomes '''soft-bricked''' when some of its functionality is lost. Soft-bricking can occur quickly but it can also slowly progress into hard-bricking; I.E: [[Intel CPUs stability issue|oxidation of a processor slowly killing it]].

*'''Planned obsolescence''' usually has a soft-bricking effect because designers tend to use a "slow-burn" effect which slowly harms the functioning of the device. The practice is unlikely to immediately destroy all functionality and is very difficult to detect as it might take several years to have a major impact.
*'''EOL''' is unpredictable in the bricking severity. Some EOL products may survive several years without requiring any repairs at all -- this is evidence of good design -- others may fail very quickly.
**'''Physical Discontinuation bricking''' occurs when it is impossible to continue maintaining an EOL resulting in a total failure.
**'''Digital discontinuation bricking''' is unique in that the product's functionality is almost always kept intact, just some digital system blocks using any of the features; it is hard to determine if this is "soft" or "hard" bricking because while all functionality is lost, its lost because the device blocking the function.

===Dependence on third-parties for repairs and bypasses===
Some consumers will wish to repair their products after it has been damaged which results in them contacting third-parties. Some third-party services may be untrustworthy and could open the user to [[security]] and [[safety]] risks

*'''Planned obsolescence''' is often the least harmful in terms of reparability as a side effect of its invisible nature. Often times it is possible to simply replace obsolete components with working ones. Companies attempt to prevent third party repair of obsolete components by using other dark practices such as [[Component pairing|anti-repair component pairing]].
*'''EOL''' is more significant due to the disappearance of repair components over time and anti-repair practices that prevent consumers from repairing their products with custom components.
**'''Digital discontinuation bricking''' is perhaps the most difficult to deal with due to the complexity of bypasses. A product that has ceased functioning because an authorization server has gone offline will require the user to either setup their own servers or bypass the remote authorization, malicious third-parties can take advantage of desperate consumers whose digital products have been disabled. In addition the more digital products depend on remote servers, the more difficult it will be to replace the hardware.

===Third-party sale falsification===
Products are often resold on the internet, and may be put on sale before self-destructive design defects appear. These sales will include valid information but become invalidated afterwards causing [[false advertising]]. This has many implications:

#Sellers may be completely unaware of the defect and will continue selling their product, hurting seller reputation once the buyer discovers the defect.
#Buyers may be completely unaware of the defect and will buy the product, only to discover the defect and harm the buyer.
#Customers may learn about the defect and decide to sell the product without providing adequate details, even without any malicious intent, solely to recoup loss.

*'''Planned obsolescence''' is unlikely to cause sale falsification due to its invisible and constant nature which usually makes it undetected but sellers who are aware of this dark pattern should inform buyers.
*'''EOL''' announcements can cause sale falsification if the product is declared EOL after the product is put up for sale -- which invalidates the seller's information.
**'''Digital discontinuation bricking''' is highly likely to cause sale falsification due to its sudden and often unannounced nature, sudden bricking also contributes the highest amount of misinformation around a products functioning state.

{| class="wikitable mw-collapsible" style="margin: auto;"
|+Types of self-destructive design and their impacts
!<nowiki>Type | Impact</nowiki>
!Actively malicious behavior
!Environmental harm
!Soft-brick
!Hard-brick
!Required repairs
!Sale Falsification
|-
|Planned Obsolescence
|Always
|Guaranteed
|Likely
|Possible but unlikely as of now
|Usually minimal
|Unlikely
|-
|Discontinuation Bricking
|Sometimes
|Guaranteed
|Unlikely
|Often
|Minimal to extreme
|Very Likely
|-
|EOL Irreparability
|Sometimes
|Guaranteed
|Likely
|Likely
|Significant
|Likely
|}

==Examples==

===Planned obsolescence===

*[[IPhone planned obsolescence incidencies|IPhone planned obsolescence incidences]]

=== Kill switch ===

* [[Oneplus phone update introduces hardware anti-rollback]]. Smartphone with [[Qualcomm]] SoC have so-called eFuse than can be "blown" by software means. The switch is manufactured in a way that once the bit in the EEPROM is written. it can't be undone except replacing the mainboard. This machanism is used by [[OnePlus]] to hard brick smartphones that users attempted to install a third-party ROM on.

===EOL repair blocking actions===

*[[Autodesk]]

===Digital discontinuation bricking===

==References==
<references />
[[Category:Common terms]]
[[Category:Articles in need of additional work]]

Framework

2026-01-24T15:30:52Z

Charlie 6: /* Consumer impact summary */ Added Transparency /* Incidents */ Added two incidents

{{CompanyCargo
| Description =
| Founded = 2020-01
| Industry = Computer Hardware
| Logo = Framework Computer logo.svg
| ParentCompany =
| Type = Private
| Website = https://frame.work
}}

'''{{wplink|Framework Computer|Framework Computer, Inc.}}''' is an American personal computer manufacturer. It was founded in January 2020, by current CEO Nirav Patel. The company specializes in customization and repairability, the latter also helping the environment through making less laptops needing to be thrown out.

==Consumer impact summary==

===Freedom===
Framework allows its consumers to easily customize laptops, by having built-in options to change things they wouldn't normally be able to do, especially with the DIY version of their laptops. The customers are given the tools and instructions to teach them how to build their laptop with a great deal of freedom.

===User Privacy===
As Framework sells solely the hardware and not the software, it doesn't need any more information than is necessary.

=== Transparency ===
Detailed assembly, repair and maintenance videos can be watched at the official knowledgebase<ref>{{Cite web |title=Welcome to the Framework Knowledge Base |url=https://knowledgebase.frame.work/ |url-status=live |website=Help Center}}</ref>. BIOS, firmware and driver updates are visible on e-mail subscription, knowledge base and (commentable) Framework Community posts<ref>{{Cite web |last=@ Quin_Chou |title=Framework Laptop 16 Ryzen 7040 BIOS 4.03 Release STABLE |url=https://community.frame.work/t/framework-laptop-16-ryzen-7040-bios-4-03-release-stable/79274 |url-status=live |access-date=2026-01-14 |website=Framework Community}}</ref>. No [[Forced BIOS Firmware Update|forced BIOS updates]] for Windows users.

===Business Model===
Framework business model is to make repairable and customizable computers, at a hardware level.

===Market Control===
Framework is known for making highly modular and user-upgradeable laptops - [https://www.windowscentral.com/best-upgradeable-laptop some reviews even call it one of the only fully upgradeable consumer laptops] available with replaceable motherboard, CPU, ports, etc. But that doesn’t mean it “controls the whole market” because there isn’t a sizeable established “modular laptop market” with traditional competitors and market share metrics the way you would see in mainstream laptop segments rather than part by part.

==Incidents==

=== Laptop 13 61Wh Battery Swelling: ===
The high energy density 61Wh battery has more swelling incidents than the previous 55Wh battery<ref>{{Cite web |last=@Adam_Schindler |date=2025-09-13 |title=61Wh Battery Inflated |url=https://community.frame.work/t/61wh-battery-inflated/75169 |url-status=live |access-date=2026-01-24 |website=Framework Community}}</ref><ref>{{Cite web |last=@John_Goerzen |date=2024-09-18 |title=Swollen Battery <1yr in, How to address? |url=https://community.frame.work/t/swollen-battery-1yr-in-how-to-address/57848 |url-status=live |access-date=2026-01-24 |website=Framework Community}}</ref><ref>{{Cite web |last=@qemu-system-x86_64 |date=2025-11-12 |title=Battery swelling (FL13 / amd 7040 / 61Wh) |url=https://community.frame.work/t/battery-swelling-fl13-amd-7040-61wh/77653 |url-status=live |access-date=2026-01-24 |website=Framework Community}}</ref>. Framework mitigated this problem by having the battery automatic discharge down to 85% after fully charged and connected on AC adapter for more than three days<ref>{{Cite web |last=@Kieran_Levin |date=2024-10-25 |title=BIOS update required to prevent premature aging of 61Wh battery |url=https://community.frame.work/t/bios-update-required-to-prevent-premature-aging-of-61wh-battery/59580 |url-status=live |access-date=2026-01-24 |website=Framework Community}}</ref>. However, this function may interfere with manual charge limit setting.

=== Laptop 16 Overheating: ===
Early models have liquid metal as the thermal interface between the CPU and its heat sink, which is known to degrade, leading to worse and uneven heat transfer<ref>{{Cite web |last=@zachary_stout |date=2024-08-04 |title=Uneven CPU thermals! |url=https://community.frame.work/t/uneven-cpu-thermals/55614/1 |url-status=live |access-date=2026-01-14 |website=Framework Community}}</ref>. Later models replaced it with PTM7958 phase change materials, early users can request PTM7958 for free, however removing the liquid metal can be challenging.

==Positive Incidents==

===Assisting repairability:===
Framework utilizes QR codes on parts of their devices which users can scan to get support, view guides, order replacements or upgrades<ref>{{Cite web |title=Try It Out |url=https://frame.work/try-it-out |url-status=live |access-date=2026-01-24 |website=Framework}}</ref>

===Highly favourable reviews on iFixit:===
The Laptop 12,<ref>{{Cite web |last=Chamberlain |first=Elizabeth |date=2025-06-18 |title=Tough, Tiny, and Totally Repairable: Inside the Framework 12 |url=https://www.ifixit.com/News/111201/tough-tiny-and-totally-repairable-inside-the-framework-12 |url-status=live |access-date=2026-01-24 |website=iFixit}}</ref> 13<ref>{{Cite web |last=Dixon |first=Taylor |date=2021-07-28 |title=Framework Laptop Teardown: 10/10, But is it Perfect? |url=https://www.ifixit.com/News/51614/framework-laptop-teardown-10-10-but-is-it-perfect |url-status=live |access-date=2026-01-24 |website=iFixit}}</ref> and 16<ref>{{Cite web |last=iFixit |date=2024-01-23 |title=The Framework 16 Teardown!-Best Teardown of the year already?? |url=https://youtube.com/watch?v=Y8uv8fajOrc |url-status=live |access-date=2026-01-24 |website=YouTube}}</ref> have all received highly favourable reviews on [https://www.ifixit.com iFixit], a pro consumer repair outlet, for their repairability.

==Products==

*'''Framework Desktop (''February 2025''):''' a mini-computer designed to have it's case be more customizable through tiles that are able to be taken out and put back somewhere else.

*'''Framework Laptop 12 (''February 2025''):''' is told as being a customizable laptop with 360° support and it comes with a stylus, being able to practically be used as a tablet.<ref>https://frame.work/laptop12</ref>

*'''Framework Laptop 13 (''July 2021''):''' is closer to your usual laptop, but is more repairable, it is seen as the most popular option by far from the other products.

*'''Framework Laptop 16 (''March 2023''):''' It is the second most popular option and offers more customization than the Laptop 13. It can provide greater performance, and its keyboard is customizable, allowing it to be removed and repositioned. The keypad can also be removed and replaced with lighting modules, enabling a higher level of personalization.

==See also==

*Framework About Us: https://frame.work/about
*Framework Guides: https://guides.frame.work/

==References==
{{reflist}}6. https://www.windowscentral.com/best-upgradeable-laptop
[[Category:{{PAGENAME}}]]

Forced BIOS firmware update

2025-12-31T10:43:13Z

Charlie 6: added references about Arch and Debian wiki pages warning the risk of flashing bios

Basic Input/Output System, also known as BIOS, is a type of firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process (power-on startup)<ref>{{Cite web |last=Kozierok |first=Charles M |date=2001-04-17 |title=Ref — System BIOS |url=http://www.pcguide.com/ref/mbsys/bios/index.htm |url-status=dead |archive-url=https://web.archive.org/web/20190218194254/http://www.pcguide.com/ref/mbsys/bios/index.htm |archive-date=2019-02-18 |access-date=2025-12-18 |website=The PC Guide}}</ref>.

Generally speaking, a working computer's BIOS doesn't need to be updated frequently due to the instinct risk of BIOS flashing<ref>{{Cite web |date=2025-04-12 |title=FlashBIOS |url=https://wiki.debian.org/FlashBIOS |url-status=live |access-date=2025-12-31 |website=Debian Wiki}}</ref><ref>{{Cite web |date=2025-12-12 |title=Flashing BIOS from Linux |url=https://wiki.archlinux.org/title/Flashing_BIOS_from_Linux |url-status=live |access-date=2025-12-31 |website=ArchWiki}}</ref>. However more and more mainstream computer manufactures starts pushing BIOS updates, often without user's consent or against the user's will, causing more issues and paves the way of controlling the device further.

==How it works==

===Pushing the BIOS update as non-optional Windows Update===
Traditionally, BIOS updates are done via a USB stick, which contains a FAT32 partition with bootloader and BIOS content. Recently the BIOS firmware is listed under Windows driver updates. Nowadays these updates are no longer under the "optional" category<ref>{{Cite web |last=@fec32a4de |date=2025-11-19 |title=How do I prevent Windows update from updating BIOS |url=https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |url-status=live |archive-url=https://web.archive.org/web/20251218145243/https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref><ref name=":0">{{Cite web |last=@redxps630 |date=2022-07-16 |title=how to prevent Windows Update from updating your bios |url=https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |url-status=live |archive-url=https://web.archive.org/web/20231021113238/https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |archive-date=2023-10-21 |access-date=2023-10-21 |website=Dell Community}}</ref>.

===Blocking BIOS downgrade===
In some computer models and BIOS versions, downgrade is blocked or "unsupported"<ref name=":1">{{Cite web |last=@ronyh |first= |date=2022-11-23 |title=BIOS Update blocked due to unsupported downgrade |url=https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |url-status=live |archive-url=https://web.archive.org/web/20240225053720/https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |archive-date=2024-02-25 |access-date=2025-12-18 |website=Dell Community}}</ref>, preventing the user from regaining lost functionalities.

===Removal of previous BIOS download link===

==Why it is a problem==

===Retroactive removal of functionalities===
Here's a non-exclusive list of removed functionalities:

*ACPI S3 sleep state<ref name=":2">{{Cite web |last=@mcgrubhub |date=2022-01-24 |title=Enable S3 Sleep State in BIOS Firmware Options |url=https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |url-status=live |archive-url=https://web.archive.org/web/20251218153346/https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |archive-date=2025-12-18 |access-date=2025-12-18 |website=HP Community}}</ref>, also known as "deep" sleep or "suspend-to-RAM"
*Undervolting<ref name=":3">{{Cite web |last=@u/DarkKnight04081995 |date=2020-11-17 |title=[GUIDE] Inspiron 7567: Bios downgrade from v1.12.1 to v1.11.0 |url=https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |url-status=live |archive-url=https://web.archive.org/web/20251218154156/https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, a method of reducing power consumption without decreasing performance
*CPU thermal design power (TDP)<ref name=":4">{{Cite web |last=@eXplode |date=2024-12-18 |title=How to Stop Automatic BIOS Updates and some hate for BIOS 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |url-status=live |archive-url=https://web.archive.org/web/20251002181913/https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |archive-date=2025-10-02 |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>
*Fan control.<ref>{{Cite web |last=@Mell |date=2025-10-4 |title=G713qm fan problem bios 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/g713qm-fan-problem-bios-331/td-p/1118443 |url-status=live |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>

===Reduced reliability/Planned obsolescence===
[[File:Asus bat chg v low.png|thumb|216x216px|Asus lowered the battery charging voltage to less than 16.6V, despite its 17.6V limited charging voltage.]]
Users reporting increased coil whine after a certain BIOS update<ref>{{Cite web |last=@ tom.m.culle150a02ca |date=2024-01-12 |title=Coil whine after bios update |url=https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |url-status=live |archive-url=https://web.archive.org/web/20251218183546/https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=MSI Global English Forum}}</ref>, possibly reducing reliability and increasing the failure rate.

Due to its unpredictable and forced nature, uncommanded BIOS updates have a higher chance of bricking the computer<ref name=":5">{{Cite web |last=@Parts-People Dell Laptop Experts |date=2025-11-02 |title=New Day, Another Bricked Laptop From Windows Update! |url=https://www.youtube.com/watch?v=8tRSjfFBtME |url-status=live |access-date=2025-12-18 |website=[[YouTube]]}}</ref>, such as interrupted BIOS update in the user's backpack due to over-temperature or battery depletion.

On some laptops, the battery capacity is restricted by reducing the charging voltage after a BIOS update, causing premature battery endurance decline. This practice is similar to [[Google Pixel 6a Battery Performance Program]] but without official announcement.

===Undermining ownership===
Manufacturers who force BIOS update often claim that blocking downgrade as "security features" to stop "bad player" from accessing the BIOS<ref name=":1" />. This is a classic example of "secure against the user"<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html#universal |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>.

==Examples==
[[File:Alienwarebiosrollback.png|thumb|From a comment on a laptop repair video<ref>{{Cite web |last=@Parts-People Dell Laptop Experts |date=2024-12-28 |title=Laptop Destroyed By Windows Update {{!}} Make It Stop! Microsoft |url=https://www.youtube.com/watch?v=pvhUPIkKt1s |url-status=live |access-date=2025-12-31 |website=[[YouTube]]}}</ref>, a Dell user had to roll back a forced BIOS update to restore GPU performance.]]
These examples are non-exhaustive, some known instances are currently not listed due to insufficient source(s). All the examples below have BIOS update as non-optional Windows Update.

===Dell===
Blocked downgrade<ref name=":1" />, removed undervolting<ref name=":3" /><ref>{{Cite web |last=@WorldDj |date=2020-09-20 |title=Another victim of the BIOS update unfortunately |url=https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |url-status=live |archive-url=https://web.archive.org/web/20251218173346/https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref>, removed previous BIOS download links<ref>{{Cite web |title=Driver unavailable |url=https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=c5jy9 |access-date=2025-12-18 |website=Dell Product Support}}</ref>.

===Asus===
[[File:Ec update bricked bms 1.png|thumb|224x224px|A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful]]
Reduced TDP<ref name=":4" />, blocked downgrade, bricked battery.

===HP===
Blocked RAM speed<ref>{{Cite web |last=@Gburns53 |date=2021-10-25 |title=Forced BIOS update |url=https://h30434.www3.hp.com/t5/Gaming-Desktops/Forced-BIOS-update/td-p/8198864 |url-status=live |archive-date= |access-date=2025-12-28 |website=HP Community}}</ref>, disabled ACPI S3 sleep state<ref name=":2" />, blocked downgrade.

===Lenovo===
Disabled ACPI S3 sleep state<ref>{{Cite web |last=@Matusaprod |date=2023-07-15 |title=Linux sleep mode on newer thinkpad missing? |url=https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |url-status=live |archive-url=https://web.archive.org/web/20251218181844/https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>.

==Countermeasures==

===Disabling UEFI Encapsulation===
On some computer models, UEFI Encapsulation can be disabled in BIOS settings<ref name=":0" />, disallowing the exchange of configuration data between the operating system and the UEFI firmware.

===Enabling "Do not include drivers with windows updates" in Group Policy===
Using Group Policy editor (gpedit.msc), users are able to exclude driver updates from Windows update<ref name=":0" /> since BIOS is often considered under drivers category. However, this method does not grantee success.

===Using a free operating system===
Free operating systems such as GNU/Linux respect user freedom. BIOS updates can be manually initiated using LVFS/fwupd

===Board-level repair===
Flashing BIOS firmware on a bricked laptop can be done by using a custom programmer<ref name=":5" />.

===Non-BIOS mitigation methods===
Some functions can be re-enabled without downgrading BIOS. Advanced BIOS<ref>{{Cite web |last=@u/Dijkmeneer |date=2022-12-19 |title=How to disable Modern sleep and enable s3 sleep on a lenovo laptop |url=https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |url-status=live |archive-url=https://web.archive.org/web/20240520204041/https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |archive-date=2024-05-20 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, OpenCore<ref>{{Cite web |last=@MotorBottle |date=2023-10-01 |title=Enable S3 Sleep on ROG X13/G14/15 2021/2022 using OpenCore |url=https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |url-status=live |archive-url=https://web.archive.org/web/20250618061353/https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |archive-date=2025-06-18 |access-date=2025-12-19 |website=[[Github]]}}</ref>, Smokeless_UMAF<ref>{{Cite web |last=@DavidS95 |date=2023-05-07 |title=Bios Flasher? Where We’re Going, We Don’t Need Bios Flasher? |url=https://github.com/DavidS95/Smokeless_UMAF |url-status=live |archive-url=https://web.archive.org/web/20250925010047/https://github.com/DavidS95/Smokeless_UMAF/ |archive-date=2025-09-25 |access-date=2025-12-19 |website=[[Github]]}}</ref>.

==References==
{{reflist}}

[[Category:Common terms]]

Forced BIOS firmware update

2025-12-31T10:19:08Z

Charlie 6: /* Examples */ added a picture

Basic Input/Output System, also known as BIOS, is a type of firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process (power-on startup)<ref>{{Cite web |last=Kozierok |first=Charles M |date=2001-04-17 |title=Ref — System BIOS |url=http://www.pcguide.com/ref/mbsys/bios/index.htm |url-status=dead |archive-url=https://web.archive.org/web/20190218194254/http://www.pcguide.com/ref/mbsys/bios/index.htm |archive-date=2019-02-18 |access-date=2025-12-18 |website=The PC Guide}}</ref>.

Generally speaking, a good running computer's BIOS doesn't need to be updated frequently due to the instinct risk of BIOS flashing. However more and more mainstream computer manufactures starts pushing BIOS updates, often without user's consent or against the user's will, causing more issues and paves the way of controlling the device further.

==How it works==

===Pushing the BIOS update as non-optional Windows Update===
Traditionally, BIOS updates are done via a USB stick, which contains a FAT32 partition with bootloader and BIOS content. Recently the BIOS firmware is listed under Windows driver updates. Nowadays these updates are no longer under the "optional" category<ref>{{Cite web |last=@fec32a4de |date=2025-11-19 |title=How do I prevent Windows update from updating BIOS |url=https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |url-status=live |archive-url=https://web.archive.org/web/20251218145243/https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref><ref name=":0">{{Cite web |last=@redxps630 |date=2022-07-16 |title=how to prevent Windows Update from updating your bios |url=https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |url-status=live |archive-url=https://web.archive.org/web/20231021113238/https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |archive-date=2023-10-21 |access-date=2023-10-21 |website=Dell Community}}</ref>.

===Blocking BIOS downgrade===
In some computer models and BIOS versions, downgrade is blocked or "unsupported"<ref name=":1">{{Cite web |last=@ronyh |first= |date=2022-11-23 |title=BIOS Update blocked due to unsupported downgrade |url=https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |url-status=live |archive-url=https://web.archive.org/web/20240225053720/https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |archive-date=2024-02-25 |access-date=2025-12-18 |website=Dell Community}}</ref>, preventing the user from regaining lost functionalities.

===Removal of previous BIOS download link===

==Why it is a problem==

===Retroactive removal of functionalities===
Here's a non-exclusive list of removed functionalities:

*ACPI S3 sleep state<ref name=":2">{{Cite web |last=@mcgrubhub |date=2022-01-24 |title=Enable S3 Sleep State in BIOS Firmware Options |url=https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |url-status=live |archive-url=https://web.archive.org/web/20251218153346/https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |archive-date=2025-12-18 |access-date=2025-12-18 |website=HP Community}}</ref>, also known as "deep" sleep or "suspend-to-RAM"
*Undervolting<ref name=":3">{{Cite web |last=@u/DarkKnight04081995 |date=2020-11-17 |title=[GUIDE] Inspiron 7567: Bios downgrade from v1.12.1 to v1.11.0 |url=https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |url-status=live |archive-url=https://web.archive.org/web/20251218154156/https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, a method of reducing power consumption without decreasing performance
*CPU thermal design power (TDP)<ref name=":4">{{Cite web |last=@eXplode |date=2024-12-18 |title=How to Stop Automatic BIOS Updates and some hate for BIOS 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |url-status=live |archive-url=https://web.archive.org/web/20251002181913/https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |archive-date=2025-10-02 |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>
*Fan control.<ref>{{Cite web |last=@Mell |date=2025-10-4 |title=G713qm fan problem bios 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/g713qm-fan-problem-bios-331/td-p/1118443 |url-status=live |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>

===Reduced reliability/Planned obsolescence===
[[File:Asus bat chg v low.png|thumb|216x216px|Asus lowered the battery charging voltage to less than 16.6V, despite its 17.6V limited charging voltage.]]
Users reporting increased coil whine after a certain BIOS update<ref>{{Cite web |last=@ tom.m.culle150a02ca |date=2024-01-12 |title=Coil whine after bios update |url=https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |url-status=live |archive-url=https://web.archive.org/web/20251218183546/https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=MSI Global English Forum}}</ref>, possibly reducing reliability and increasing the failure rate.

Due to its unpredictable and forced nature, uncommanded BIOS updates have a higher chance of bricking the computer<ref name=":5">{{Cite web |last=@Parts-People Dell Laptop Experts |date=2025-11-02 |title=New Day, Another Bricked Laptop From Windows Update! |url=https://www.youtube.com/watch?v=8tRSjfFBtME |url-status=live |access-date=2025-12-18 |website=[[YouTube]]}}</ref>, such as interrupted BIOS update in the user's backpack due to over-temperature or battery depletion.

On some laptops, the battery capacity is restricted by reducing the charging voltage after a BIOS update, causing premature battery endurance decline. This practice is similar to [[Google Pixel 6a Battery Performance Program]] but without official announcement.

===Undermining ownership===
Manufacturers who force BIOS update often claim that blocking downgrade as "security features" to stop "bad player" from accessing the BIOS<ref name=":1" />. This is a classic example of "secure against the user"<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html#universal |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>.

==Examples==
[[File:Alienwarebiosrollback.png|thumb|From a comment on a laptop repair video<ref>{{Cite web |last=@Parts-People Dell Laptop Experts |date=2024-12-28 |title=Laptop Destroyed By Windows Update {{!}} Make It Stop! Microsoft |url=https://www.youtube.com/watch?v=pvhUPIkKt1s |url-status=live |access-date=2025-12-31 |website=[[YouTube]]}}</ref>, a Dell user had to roll back a forced BIOS update to restore GPU performance.]]
These examples are non-exhaustive, some known instances are currently not listed due to insufficient source(s). All the examples below have BIOS update as non-optional Windows Update.

===Dell===
Blocked downgrade<ref name=":1" />, removed undervolting<ref name=":3" /><ref>{{Cite web |last=@WorldDj |date=2020-09-20 |title=Another victim of the BIOS update unfortunately |url=https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |url-status=live |archive-url=https://web.archive.org/web/20251218173346/https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref>, removed previous BIOS download links<ref>{{Cite web |title=Driver unavailable |url=https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=c5jy9 |access-date=2025-12-18 |website=Dell Product Support}}</ref>.

===Asus===
[[File:Ec update bricked bms 1.png|thumb|224x224px|A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful]]
Reduced TDP<ref name=":4" />, blocked downgrade, bricked battery.

===HP===
Blocked RAM speed<ref>{{Cite web |last=@Gburns53 |date=2021-10-25 |title=Forced BIOS update |url=https://h30434.www3.hp.com/t5/Gaming-Desktops/Forced-BIOS-update/td-p/8198864 |url-status=live |archive-date= |access-date=2025-12-28 |website=HP Community}}</ref>, disabled ACPI S3 sleep state<ref name=":2" />, blocked downgrade.

===Lenovo===
Disabled ACPI S3 sleep state<ref>{{Cite web |last=@Matusaprod |date=2023-07-15 |title=Linux sleep mode on newer thinkpad missing? |url=https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |url-status=live |archive-url=https://web.archive.org/web/20251218181844/https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>.

==Countermeasures==

===Disabling UEFI Encapsulation===
On some computer models, UEFI Encapsulation can be disabled in BIOS settings<ref name=":0" />, disallowing the exchange of configuration data between the operating system and the UEFI firmware.

===Enabling "Do not include drivers with windows updates" in Group Policy===
Using Group Policy editor (gpedit.msc), users are able to exclude driver updates from Windows update<ref name=":0" /> since BIOS is often considered under drivers category. However, this method does not grantee success.

===Using a free operating system===
Free operating systems such as GNU/Linux respect user freedom. BIOS updates can be manually initiated using LVFS/fwupd

===Board-level repair===
Flashing BIOS firmware on a bricked laptop can be done by using a custom programmer<ref name=":5" />.

===Non-BIOS mitigation methods===
Some functions can be re-enabled without downgrading BIOS. Advanced BIOS<ref>{{Cite web |last=@u/Dijkmeneer |date=2022-12-19 |title=How to disable Modern sleep and enable s3 sleep on a lenovo laptop |url=https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |url-status=live |archive-url=https://web.archive.org/web/20240520204041/https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |archive-date=2024-05-20 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, OpenCore<ref>{{Cite web |last=@MotorBottle |date=2023-10-01 |title=Enable S3 Sleep on ROG X13/G14/15 2021/2022 using OpenCore |url=https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |url-status=live |archive-url=https://web.archive.org/web/20250618061353/https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |archive-date=2025-06-18 |access-date=2025-12-19 |website=[[Github]]}}</ref>, Smokeless_UMAF<ref>{{Cite web |last=@DavidS95 |date=2023-05-07 |title=Bios Flasher? Where We’re Going, We Don’t Need Bios Flasher? |url=https://github.com/DavidS95/Smokeless_UMAF |url-status=live |archive-url=https://web.archive.org/web/20250925010047/https://github.com/DavidS95/Smokeless_UMAF/ |archive-date=2025-09-25 |access-date=2025-12-19 |website=[[Github]]}}</ref>.

==References==
{{reflist}}

[[Category:Common terms]]

File:Alienware BIOS rollback.png

2025-12-31T10:15:51Z

Charlie 6: @dredre2k11 A Dell user had to roll back a forced BIOS update to restore GPU performance

== Summary ==
@dredre2k11 A Dell user had to roll back a forced BIOS update to restore GPU performance

Forced BIOS firmware update

2025-12-31T09:39:36Z

Charlie 6: /* Pushing the BIOS update as non-optional Windows Update */ Fixed a wrong link

Basic Input/Output System, also known as BIOS, is a type of firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process (power-on startup)<ref>{{Cite web |last=Kozierok |first=Charles M |date=2001-04-17 |title=Ref — System BIOS |url=http://www.pcguide.com/ref/mbsys/bios/index.htm |url-status=dead |archive-url=https://web.archive.org/web/20190218194254/http://www.pcguide.com/ref/mbsys/bios/index.htm |archive-date=2019-02-18 |access-date=2025-12-18 |website=The PC Guide}}</ref>.

Generally speaking, a good running computer's BIOS doesn't need to be updated frequently due to the instinct risk of BIOS flashing. However more and more mainstream computer manufactures starts pushing BIOS updates, often without user's consent or against the user's will, causing more issues and paves the way of controlling the device further.

==How it works==

===Pushing the BIOS update as non-optional Windows Update===
Traditionally, BIOS updates are done via a USB stick, which contains a FAT32 partition with bootloader and BIOS content. Recently the BIOS firmware is listed under Windows driver updates. Nowadays these updates are no longer under the "optional" category<ref>{{Cite web |last=@fec32a4de |date=2025-11-19 |title=How do I prevent Windows update from updating BIOS |url=https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |url-status=live |archive-url=https://web.archive.org/web/20251218145243/https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref><ref name=":0">{{Cite web |last=@redxps630 |date=2022-07-16 |title=how to prevent Windows Update from updating your bios |url=https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |url-status=live |archive-url=https://web.archive.org/web/20231021113238/https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |archive-date=2023-10-21 |access-date=2023-10-21 |website=Dell Community}}</ref>.

===Blocking BIOS downgrade===
In some computer models and BIOS versions, downgrade is blocked or "unsupported"<ref name=":1">{{Cite web |last=@ronyh |first= |date=2022-11-23 |title=BIOS Update blocked due to unsupported downgrade |url=https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |url-status=live |archive-url=https://web.archive.org/web/20240225053720/https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |archive-date=2024-02-25 |access-date=2025-12-18 |website=Dell Community}}</ref>, preventing the user from regaining lost functionalities.

===Removal of previous BIOS download link===

==Why it is a problem==

===Retroactive removal of functionalities===
Here's a non-exclusive list of removed functionalities:

*ACPI S3 sleep state<ref name=":2">{{Cite web |last=@mcgrubhub |date=2022-01-24 |title=Enable S3 Sleep State in BIOS Firmware Options |url=https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |url-status=live |archive-url=https://web.archive.org/web/20251218153346/https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |archive-date=2025-12-18 |access-date=2025-12-18 |website=HP Community}}</ref>, also known as "deep" sleep or "suspend-to-RAM"
*Undervolting<ref name=":3">{{Cite web |last=@u/DarkKnight04081995 |date=2020-11-17 |title=[GUIDE] Inspiron 7567: Bios downgrade from v1.12.1 to v1.11.0 |url=https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |url-status=live |archive-url=https://web.archive.org/web/20251218154156/https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, a method of reducing power consumption without decreasing performance
*CPU thermal design power (TDP)<ref name=":4">{{Cite web |last=@eXplode |date=2024-12-18 |title=How to Stop Automatic BIOS Updates and some hate for BIOS 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |url-status=live |archive-url=https://web.archive.org/web/20251002181913/https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |archive-date=2025-10-02 |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>
*Fan control.<ref>{{Cite web |last=@Mell |date=2025-10-4 |title=G713qm fan problem bios 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/g713qm-fan-problem-bios-331/td-p/1118443 |url-status=live |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>

===Reduced reliability/Planned obsolescence===
[[File:Asus bat chg v low.png|thumb|216x216px|Asus lowered the battery charging voltage to less than 16.6V, despite its 17.6V limited charging voltage.]]
Users reporting increased coil whine after a certain BIOS update<ref>{{Cite web |last=@ tom.m.culle150a02ca |date=2024-01-12 |title=Coil whine after bios update |url=https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |url-status=live |archive-url=https://web.archive.org/web/20251218183546/https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=MSI Global English Forum}}</ref>, possibly reducing reliability and increasing the failure rate.

Due to its unpredictable and forced nature, uncommanded BIOS updates have a higher chance of bricking the computer<ref name=":5">{{Cite web |last=@Parts-People Dell Laptop Experts |date=2025-11-02 |title=New Day, Another Bricked Laptop From Windows Update! |url=https://www.youtube.com/watch?v=8tRSjfFBtME |url-status=live |access-date=2025-12-18 |website=[[YouTube]]}}</ref>, such as interrupted BIOS update in the user's backpack due to over-temperature or battery depletion.

On some laptops, the battery capacity is restricted by reducing the charging voltage after a BIOS update, causing premature battery endurance decline. This practice is similar to [[Google Pixel 6a Battery Performance Program]] but without official announcement.

===Undermining ownership===
Manufacturers who force BIOS update often claim that blocking downgrade as "security features" to stop "bad player" from accessing the BIOS<ref name=":1" />. This is a classic example of "secure against the user"<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html#universal |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>.

==Examples==
These examples are non-exhaustive, some known instances are currently not listed due to insufficient source(s). All the examples below have BIOS update as non-optional Windows Update.

===Dell===
Blocked downgrade<ref name=":1" />, removed undervolting<ref name=":3" /><ref>{{Cite web |last=@WorldDj |date=2020-09-20 |title=Another victim of the BIOS update unfortunately |url=https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |url-status=live |archive-url=https://web.archive.org/web/20251218173346/https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref>, removed previous BIOS download links<ref>{{Cite web |title=Driver unavailable |url=https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=c5jy9 |access-date=2025-12-18 |website=Dell Product Support}}</ref>.

===Asus===
[[File:Ec update bricked bms 1.png|thumb|224x224px|A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful]]
Reduced TDP<ref name=":4" />, blocked downgrade, bricked battery.

===HP===
Blocked RAM speed<ref>{{Cite web |last=@Gburns53 |date=2021-10-25 |title=Forced BIOS update |url=https://h30434.www3.hp.com/t5/Gaming-Desktops/Forced-BIOS-update/td-p/8198864 |url-status=live |archive-date= |access-date=2025-12-28 |website=HP Community}}</ref>, disabled ACPI S3 sleep state<ref name=":2" />, blocked downgrade.

===Lenovo===
Disabled ACPI S3 sleep state<ref>{{Cite web |last=@Matusaprod |date=2023-07-15 |title=Linux sleep mode on newer thinkpad missing? |url=https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |url-status=live |archive-url=https://web.archive.org/web/20251218181844/https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>.

==Countermeasures==

===Disabling UEFI Encapsulation===
On some computer models, UEFI Encapsulation can be disabled in BIOS settings<ref name=":0" />, disallowing the exchange of configuration data between the operating system and the UEFI firmware.

===Enabling "Do not include drivers with windows updates" in Group Policy===
Using Group Policy editor (gpedit.msc), users are able to exclude driver updates from Windows update<ref name=":0" /> since BIOS is often considered under drivers category. However, this method does not grantee success.

===Using a free operating system===
Free operating systems such as GNU/Linux respect user freedom. BIOS updates can be manually initiated using LVFS/fwupd

===Board-level repair===
Flashing BIOS firmware on a bricked laptop can be done by using a custom programmer<ref name=":5" />.

===Non-BIOS mitigation methods===
Some functions can be re-enabled without downgrading BIOS. Advanced BIOS<ref>{{Cite web |last=@u/Dijkmeneer |date=2022-12-19 |title=How to disable Modern sleep and enable s3 sleep on a lenovo laptop |url=https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |url-status=live |archive-url=https://web.archive.org/web/20240520204041/https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |archive-date=2024-05-20 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, OpenCore<ref>{{Cite web |last=@MotorBottle |date=2023-10-01 |title=Enable S3 Sleep on ROG X13/G14/15 2021/2022 using OpenCore |url=https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |url-status=live |archive-url=https://web.archive.org/web/20250618061353/https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |archive-date=2025-06-18 |access-date=2025-12-19 |website=[[Github]]}}</ref>, Smokeless_UMAF<ref>{{Cite web |last=@DavidS95 |date=2023-05-07 |title=Bios Flasher? Where We’re Going, We Don’t Need Bios Flasher? |url=https://github.com/DavidS95/Smokeless_UMAF |url-status=live |archive-url=https://web.archive.org/web/20250925010047/https://github.com/DavidS95/Smokeless_UMAF/ |archive-date=2025-09-25 |access-date=2025-12-19 |website=[[Github]]}}</ref>.

==References==
{{reflist}}

[[Category:Common terms]]

Forced BIOS firmware update

2025-12-28T21:20:08Z

Charlie 6: /* HP */ added blocked RAM speed

Basic Input/Output System, also known as BIOS, is a type of firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process (power-on startup)<ref>{{Cite web |last=Kozierok |first=Charles M |date=2001-04-17 |title=Ref — System BIOS |url=http://www.pcguide.com/ref/mbsys/bios/index.htm |url-status=dead |archive-url=https://web.archive.org/web/20190218194254/http://www.pcguide.com/ref/mbsys/bios/index.htm |archive-date=2019-02-18 |access-date=2025-12-18 |website=The PC Guide}}</ref>.

Generally speaking, a good running computer's BIOS doesn't need to be updated frequently due to the instinct risk of BIOS flashing. However more and more mainstream computer manufactures starts pushing BIOS updates, often without user's consent or against the user's will, causing more issues and paves the way of controlling the device further.

==How it works==

===Pushing the BIOS update as non-optional Windows Update===
Traditionally, BIOS updates are done via a USB stick, which contains a FAT32 partition with bootloader and BIOS content. Recently the BIOS firmware is listed under Windows driver updates. Nowadays these updates are no longer under the "optional" category<ref>{{Cite web |last=@fec32a4de |date=2025-11-19 |title=How do I prevent Windows update from updating BIOS |url=https://www.reddit.com/r/HPOmen/comments/13lh22k/new_omen_wont_turn_off_lights_and_fan_in_sleep/ |url-status=live |archive-url=https://web.archive.org/web/20251218145243/https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref><ref name=":0">{{Cite web |last=@redxps630 |date=2022-07-16 |title=how to prevent Windows Update from updating your bios |url=https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |url-status=live |archive-url=https://web.archive.org/web/20231021113238/https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |archive-date=2023-10-21 |access-date=2023-10-21 |website=Dell Community}}</ref>.

===Blocking BIOS downgrade===
In some computer models and BIOS versions, downgrade is blocked or "unsupported"<ref name=":1">{{Cite web |last=@ronyh |first= |date=2022-11-23 |title=BIOS Update blocked due to unsupported downgrade |url=https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |url-status=live |archive-url=https://web.archive.org/web/20240225053720/https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |archive-date=2024-02-25 |access-date=2025-12-18 |website=Dell Community}}</ref>, preventing the user from regaining lost functionalities.

===Removal of previous BIOS download link===

==Why it is a problem==

===Retroactive removal of functionalities===
Here's a non-exclusive list of removed functionalities:

*ACPI S3 sleep state<ref name=":2">{{Cite web |last=@mcgrubhub |date=2022-01-24 |title=Enable S3 Sleep State in BIOS Firmware Options |url=https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |url-status=live |archive-url=https://web.archive.org/web/20251218153346/https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |archive-date=2025-12-18 |access-date=2025-12-18 |website=HP Community}}</ref>, also known as "deep" sleep or "suspend-to-RAM"
*Undervolting<ref name=":3">{{Cite web |last=@u/DarkKnight04081995 |date=2020-11-17 |title=[GUIDE] Inspiron 7567: Bios downgrade from v1.12.1 to v1.11.0 |url=https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |url-status=live |archive-url=https://web.archive.org/web/20251218154156/https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, a method of reducing power consumption without decreasing performance
*CPU thermal design power (TDP)<ref name=":4">{{Cite web |last=@eXplode |date=2024-12-18 |title=How to Stop Automatic BIOS Updates and some hate for BIOS 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |url-status=live |archive-url=https://web.archive.org/web/20251002181913/https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |archive-date=2025-10-02 |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>
*Fan control.<ref>{{Cite web |last=@Mell |date=2025-10-4 |title=G713qm fan problem bios 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/g713qm-fan-problem-bios-331/td-p/1118443 |url-status=live |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>

===Reduced reliability/Planned obsolescence===
[[File:Asus bat chg v low.png|thumb|216x216px|Asus lowered the battery charging voltage to less than 16.6V, despite its 17.6V limited charging voltage.]]
Users reporting increased coil whine after a certain BIOS update<ref>{{Cite web |last=@ tom.m.culle150a02ca |date=2024-01-12 |title=Coil whine after bios update |url=https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |url-status=live |archive-url=https://web.archive.org/web/20251218183546/https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=MSI Global English Forum}}</ref>, possibly reducing reliability and increasing the failure rate.

Due to its unpredictable and forced nature, uncommanded BIOS updates have a higher chance of bricking the computer<ref name=":5">{{Cite web |last=@Parts-People Dell Laptop Experts |date=2025-11-02 |title=New Day, Another Bricked Laptop From Windows Update! |url=https://www.youtube.com/watch?v=8tRSjfFBtME |url-status=live |access-date=2025-12-18 |website=[[YouTube]]}}</ref>, such as interrupted BIOS update in the user's backpack due to over-temperature or battery depletion.

On some laptops, the battery capacity is restricted by reducing the charging voltage after a BIOS update, causing premature battery endurance decline. This practice is similar to [[Google Pixel 6a Battery Performance Program]] but without official announcement.

===Undermining ownership===
Manufacturers who force BIOS update often claim that blocking downgrade as "security features" to stop "bad player" from accessing the BIOS<ref name=":1" />. This is a classic example of "secure against the user"<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html#universal |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>.

==Examples==
These examples are non-exhaustive, some known instances are currently not listed due to insufficient source(s). All the examples below have BIOS update as non-optional Windows Update.

===Dell===
Blocked downgrade<ref name=":1" />, removed undervolting<ref name=":3" /><ref>{{Cite web |last=@WorldDj |date=2020-09-20 |title=Another victim of the BIOS update unfortunately |url=https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |url-status=live |archive-url=https://web.archive.org/web/20251218173346/https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref>, removed previous BIOS download links<ref>{{Cite web |title=Driver unavailable |url=https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=c5jy9 |access-date=2025-12-18 |website=Dell Product Support}}</ref>.

===Asus===
[[File:Ec update bricked bms 1.png|thumb|224x224px|A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful]]
Reduced TDP<ref name=":4" />, blocked downgrade, bricked battery.

===HP===
Blocked RAM speed<ref>{{Cite web |last=@Gburns53 |date=2021-10-25 |title=Forced BIOS update |url=https://h30434.www3.hp.com/t5/Gaming-Desktops/Forced-BIOS-update/td-p/8198864 |url-status=live |archive-date= |access-date=2025-12-28 |website=HP Community}}</ref>, disabled ACPI S3 sleep state<ref name=":2" />, blocked downgrade.

===Lenovo===
Disabled ACPI S3 sleep state<ref>{{Cite web |last=@Matusaprod |date=2023-07-15 |title=Linux sleep mode on newer thinkpad missing? |url=https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |url-status=live |archive-url=https://web.archive.org/web/20251218181844/https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>.

==Countermeasures==

===Disabling UEFI Encapsulation===
On some computer models, UEFI Encapsulation can be disabled in BIOS settings<ref name=":0" />, disallowing the exchange of configuration data between the operating system and the UEFI firmware.

===Enabling "Do not include drivers with windows updates" in Group Policy===
Using Group Policy editor (gpedit.msc), users are able to exclude driver updates from Windows update<ref name=":0" /> since BIOS is often considered under drivers category. However, this method does not grantee success.

===Using a free operating system===
Free operating systems such as GNU/Linux respect user freedom. BIOS updates can be manually initiated using LVFS/fwupd

===Board-level repair===
Flashing BIOS firmware on a bricked laptop can be done by using a custom programmer<ref name=":5" />.

===Non-BIOS mitigation methods===
Some functions can be re-enabled without downgrading BIOS. Advanced BIOS<ref>{{Cite web |last=@u/Dijkmeneer |date=2022-12-19 |title=How to disable Modern sleep and enable s3 sleep on a lenovo laptop |url=https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |url-status=live |archive-url=https://web.archive.org/web/20240520204041/https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |archive-date=2024-05-20 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, OpenCore<ref>{{Cite web |last=@MotorBottle |date=2023-10-01 |title=Enable S3 Sleep on ROG X13/G14/15 2021/2022 using OpenCore |url=https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |url-status=live |archive-url=https://web.archive.org/web/20250618061353/https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |archive-date=2025-06-18 |access-date=2025-12-19 |website=[[Github]]}}</ref>, Smokeless_UMAF<ref>{{Cite web |last=@DavidS95 |date=2023-05-07 |title=Bios Flasher? Where We’re Going, We Don’t Need Bios Flasher? |url=https://github.com/DavidS95/Smokeless_UMAF |url-status=live |archive-url=https://web.archive.org/web/20250925010047/https://github.com/DavidS95/Smokeless_UMAF/ |archive-date=2025-09-25 |access-date=2025-12-19 |website=[[Github]]}}</ref>.

==References==
{{reflist}}

[[Category:Common terms]]

Riot Vanguard

2025-12-23T13:46:40Z

Charlie 6: /* Technical Implications */ Fixed link (?) on Archived

{{InfoboxProductLine
| Title = {{PAGENAME}}
| Release Year = 2020
| Product Type = Anti-cheat Software
| In Production = Yes
| Logo = Riot_Vanguard_Logo.png
|Official Website=https://support-valorant.riotgames.com/hc/en-us/articles/360046160933-What-is-Vanguard}}

[[wikipedia:Riot_Vanguard|Riot Vanguard]] is an anti-cheat system developed by Riot Games, initially released for VALORANT in 2020 and later expanded to League of Legends in April of 2024.

==Consumer impact summary==
Overview of concerns that arise from the conduct towards users of the product:
*Privacy: Vanguard is a kernel-level (ring 0) anti-cheat. It has access to everything on your computer. Riot Games is owned by Tencent which has strong ties with the Chinese government.
*Control: Users must have Vanguard running from computer startup to play any Riot games, even when not playing.
*Access: As a [[kernel level anti-cheats|kernel level anti-cheat]], Vanguard has the highest level of access to your computer.

==Incidents==
This is a list of all consumer protection incidents related to this software. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===League of Legends Implementation (April 2024)===
In April 2024, Riot Games announced that Vanguard would become mandatory for all League of Legends players. <ref>https://support-leagueoflegends.riotgames.com/hc/en-us/articles/24169857932435-Riot-Vanguard-FAQ-League-of-Legends</ref> This decision was particularly controversial for several reasons:

*The requirement affected a 14-year-old game that had previously operated without kernel-level anti-cheat.
*Players were required to install Vanguard to continue accessing their accounts and purchased content.
*No opt-out option was provided for players who did not wish to install kernel-level software.
*The implementation affected all regions globally, including areas with strict privacy regulations.
*Players using Linux through Wine/Proton would no longer be able to play the game.

==Concerns==
===Tencent Ownership and Chinese Government Ties===
A major concern surrounding Vanguard stems from Riot Games' ownership by Tencent Holdings, a Chinese technology conglomerate. This ownership, combined with Vanguard's kernel-level access, raises significant security and privacy implications due to Chinese legal requirements, particularly the [[wikipedia:National_Intelligence_Law_of_the_People's_Republic_of_China|National Intelligence Law of the People's Republic of China]] (2017).
The law mandates cooperation with national intelligence efforts from all organizations and citizens. Relevant articles include:<blockquote>Article 7: All organizations and citizens shall support, assist, and cooperate with national intelligence efforts in accordance with law, and shall protect national intelligence work secrets they are aware of.

Article 10: As necessary for their work, national intelligence work institutions are to use the necessary means, tactics, and channels to carry out intelligence efforts, domestically and abroad.

Article 18: As required for work, and in accordance with relevant national provisions, national intelligence work institutions may ask organs such as for customs and entry-exit border inspection to provide facilitation such as exemptions from inspection.</blockquote>These legal requirements raise several concerns:
*Tencent, as a Chinese company, could be legally compelled to provide data or access through Vanguard.
*The kernel-level access could potentially be leveraged for surveillance or data collection beyond anti-cheat purposes.
*An attack on Riot's Vanguard servers could have catastrophic consequences
*Users have no way to verify if or when such access might be utilized.
*The combination of mandatory installation, kernel-level access, and Chinese ownership creates potential security risks for:
**Government employees.
**Corporate users with sensitive data.
**Military personnel.
**Users with access to critical infrastructure.
**Critics of the Chinese government.

===Technical Implications===
The kernel-level access combined with potential government compulsion is particularly concerning because:
*Ring 0 access provides complete system control.
*Users cannot monitor or restrict Vanguard's activities at this level.
*The always-on requirement means the system is potentially vulnerable even when not gaming.
*The software could theoretically be used as a backdoor if compelled by authorities.
*The software could have a negative performance impact even when doing other things on your computer since the driver is running 24/7
*Enforced UEFI firmware update can reduce performance and potentially brick the hardware<ref>{{Cite web |last=Maruccia |first=Alfonso |date=2025-12-20 |title=Riot is forcing Valorant players to update their PC firmware to keep playing |url=https://www.techspot.com/news/110663-riot-forcing-valorant-players-update-their-pc-firmware.html |url-status=live |archive-url=https://web.archive.org/web/20251223133910/https://www.techspot.com/news/110663-riot-forcing-valorant-players-update-their-pc-firmware.html |archive-date=2025-12-23 |access-date=2025-12-23 |website=Techspot}}</ref>.

==Company Response==
===Official Statements===
Riot Games has responded to various concerns about Vanguard through multiple official channels:

{Sources to be added}

*Following the League of Legends implementation announcement, Riot published a detailed FAQ addressing community concerns. They maintained that Vanguard's kernel driver is focused solely on game integrity and doesn't process any personal information.<ref>https://support-leagueoflegends.riotgames.com/hc/en-us/articles/24169857932435-Riot-Vanguard-FAQ-League-of-Legends</ref>
*Riot Security Team published a technical blog post explaining that Vanguard's kernel-level implementation is necessary to detect and prevent sophisticated cheating methods that operate at the same level.<ref>https://www.riotgames.com/en/news/a-message-about-vanguard-from-our-security-privacy-teams</ref>

<blockquote>We understand the decision to run the driver component in kernel-mode can raise concerns, and that some of you want to know more about the tech behind Vanguard. We can't get too deep into the technical specifics without potentially compromising Vanguard... plus we can assure you that it has been reviewed by both internal and external security experts.|[[Riot Games]]<ref>[https://www.riotgames.com/en/news/a-message-about-vanguard-from-our-security-privacy-teams "A Message About Vanguard from our Security & Privacy Teams"] ''Riot Games''. Retrieved 2024-02-16</ref></blockquote>

Riot Games has expressed that kernel level anti cheat is becoming an industry standard however no other anti cheat software is as invasive as Vanguard. Riot claims that to defeat cheaters operating at the kernel level, it is necessary to also be operating at the same level. This is untrue. They claim the only way to stop account botting, ranked boosting and to ban cheaters permanently via using hardware identifiers is to compromise your privacy despite the fact that other companies within the gaming industry whom are capable of banning bots and cheaters including hardware banning customers can do so without the need of kernel-level anti cheat detection that runs even when you are not playing their games.

Riot Vanguard is the only anticheat that requires it to be running at all times.

===Privacy and Security Assurances===
Riot Games has provided several assurances regarding Vanguard's security:
*The company stated that Vanguard's code has undergone multiple third-party security audits from independent cybersecurity firms.
*Riot maintains that the kernel driver cannot be remotely activated or modified without triggering operating system security protocols.
*The company emphasizes that all data collection is limited to game integrity verification, with strict internal controls preventing mission creep.

====Community Response====
The announcement led to significant backlash from the League of Legends community:
*Multiple Reddit threads reached the front page of r/leagueoflegends expressing concerns.
*Linux users can no longer play League of Legends. r/LeagueofLinux
*Players raised issues about the necessity of kernel-level anti-cheat for a MOBA game.
*Privacy advocates questioned the expansion of kernel-level software to a larger player base.

==References==
{{reflist}}
[[Category:{{PAGENAME}}]]

Riot Vanguard

2025-12-23T13:41:52Z

Charlie 6: /* Technical Implications */ Added forced firmware update

{{InfoboxProductLine
| Title = {{PAGENAME}}
| Release Year = 2020
| Product Type = Anti-cheat Software
| In Production = Yes
| Logo = Riot_Vanguard_Logo.png
|Official Website=https://support-valorant.riotgames.com/hc/en-us/articles/360046160933-What-is-Vanguard}}

[[wikipedia:Riot_Vanguard|Riot Vanguard]] is an anti-cheat system developed by Riot Games, initially released for VALORANT in 2020 and later expanded to League of Legends in April of 2024.

==Consumer impact summary==
Overview of concerns that arise from the conduct towards users of the product:
*Privacy: Vanguard is a kernel-level (ring 0) anti-cheat. It has access to everything on your computer. Riot Games is owned by Tencent which has strong ties with the Chinese government.
*Control: Users must have Vanguard running from computer startup to play any Riot games, even when not playing.
*Access: As a [[kernel level anti-cheats|kernel level anti-cheat]], Vanguard has the highest level of access to your computer.

==Incidents==
This is a list of all consumer protection incidents related to this software. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
===League of Legends Implementation (April 2024)===
In April 2024, Riot Games announced that Vanguard would become mandatory for all League of Legends players. <ref>https://support-leagueoflegends.riotgames.com/hc/en-us/articles/24169857932435-Riot-Vanguard-FAQ-League-of-Legends</ref> This decision was particularly controversial for several reasons:

*The requirement affected a 14-year-old game that had previously operated without kernel-level anti-cheat.
*Players were required to install Vanguard to continue accessing their accounts and purchased content.
*No opt-out option was provided for players who did not wish to install kernel-level software.
*The implementation affected all regions globally, including areas with strict privacy regulations.
*Players using Linux through Wine/Proton would no longer be able to play the game.

==Concerns==
===Tencent Ownership and Chinese Government Ties===
A major concern surrounding Vanguard stems from Riot Games' ownership by Tencent Holdings, a Chinese technology conglomerate. This ownership, combined with Vanguard's kernel-level access, raises significant security and privacy implications due to Chinese legal requirements, particularly the [[wikipedia:National_Intelligence_Law_of_the_People's_Republic_of_China|National Intelligence Law of the People's Republic of China]] (2017).
The law mandates cooperation with national intelligence efforts from all organizations and citizens. Relevant articles include:<blockquote>Article 7: All organizations and citizens shall support, assist, and cooperate with national intelligence efforts in accordance with law, and shall protect national intelligence work secrets they are aware of.

Article 10: As necessary for their work, national intelligence work institutions are to use the necessary means, tactics, and channels to carry out intelligence efforts, domestically and abroad.

Article 18: As required for work, and in accordance with relevant national provisions, national intelligence work institutions may ask organs such as for customs and entry-exit border inspection to provide facilitation such as exemptions from inspection.</blockquote>These legal requirements raise several concerns:
*Tencent, as a Chinese company, could be legally compelled to provide data or access through Vanguard.
*The kernel-level access could potentially be leveraged for surveillance or data collection beyond anti-cheat purposes.
*An attack on Riot's Vanguard servers could have catastrophic consequences
*Users have no way to verify if or when such access might be utilized.
*The combination of mandatory installation, kernel-level access, and Chinese ownership creates potential security risks for:
**Government employees.
**Corporate users with sensitive data.
**Military personnel.
**Users with access to critical infrastructure.
**Critics of the Chinese government.

===Technical Implications===
The kernel-level access combined with potential government compulsion is particularly concerning because:
*Ring 0 access provides complete system control.
*Users cannot monitor or restrict Vanguard's activities at this level.
*The always-on requirement means the system is potentially vulnerable even when not gaming.
*The software could theoretically be used as a backdoor if compelled by authorities.
*The software could have a negative performance impact even when doing other things on your computer since the driver is running 24/7
*Enforced UEFI firmware update can reduce performance and potentially brick the hardware<ref>{{Cite web |last=Maruccia |first=Alfonso |date=2025-12-20 |title=Riot is forcing Valorant players to update their PC firmware to keep playing |url=https://www.techspot.com/news/110663-riot-forcing-valorant-players-update-their-pc-firmware.html |url-status=live |archive-url=https://web.archive.org/web/20251223133910/https://www.techspot.com/web/20251223133910/https://www.techspot.com/news/110663-riot-forcing-valorant-players-update-their-pc-firmware.html |archive-date=2025-12-23 |access-date=2025-12-23 |website=Techspot}}</ref>.

==Company Response==
===Official Statements===
Riot Games has responded to various concerns about Vanguard through multiple official channels:

{Sources to be added}

*Following the League of Legends implementation announcement, Riot published a detailed FAQ addressing community concerns. They maintained that Vanguard's kernel driver is focused solely on game integrity and doesn't process any personal information.<ref>https://support-leagueoflegends.riotgames.com/hc/en-us/articles/24169857932435-Riot-Vanguard-FAQ-League-of-Legends</ref>
*Riot Security Team published a technical blog post explaining that Vanguard's kernel-level implementation is necessary to detect and prevent sophisticated cheating methods that operate at the same level.<ref>https://www.riotgames.com/en/news/a-message-about-vanguard-from-our-security-privacy-teams</ref>

<blockquote>We understand the decision to run the driver component in kernel-mode can raise concerns, and that some of you want to know more about the tech behind Vanguard. We can't get too deep into the technical specifics without potentially compromising Vanguard... plus we can assure you that it has been reviewed by both internal and external security experts.|[[Riot Games]]<ref>[https://www.riotgames.com/en/news/a-message-about-vanguard-from-our-security-privacy-teams "A Message About Vanguard from our Security & Privacy Teams"] ''Riot Games''. Retrieved 2024-02-16</ref></blockquote>

Riot Games has expressed that kernel level anti cheat is becoming an industry standard however no other anti cheat software is as invasive as Vanguard. Riot claims that to defeat cheaters operating at the kernel level, it is necessary to also be operating at the same level. This is untrue. They claim the only way to stop account botting, ranked boosting and to ban cheaters permanently via using hardware identifiers is to compromise your privacy despite the fact that other companies within the gaming industry whom are capable of banning bots and cheaters including hardware banning customers can do so without the need of kernel-level anti cheat detection that runs even when you are not playing their games.

Riot Vanguard is the only anticheat that requires it to be running at all times.

===Privacy and Security Assurances===
Riot Games has provided several assurances regarding Vanguard's security:
*The company stated that Vanguard's code has undergone multiple third-party security audits from independent cybersecurity firms.
*Riot maintains that the kernel driver cannot be remotely activated or modified without triggering operating system security protocols.
*The company emphasizes that all data collection is limited to game integrity verification, with strict internal controls preventing mission creep.

====Community Response====
The announcement led to significant backlash from the League of Legends community:
*Multiple Reddit threads reached the front page of r/leagueoflegends expressing concerns.
*Linux users can no longer play League of Legends. r/LeagueofLinux
*Players raised issues about the necessity of kernel-level anti-cheat for a MOBA game.
*Privacy advocates questioned the expansion of kernel-level software to a larger player base.

==References==
{{reflist}}
[[Category:{{PAGENAME}}]]

Forced BIOS firmware update

2025-12-20T04:42:20Z

Charlie 6: Fixed a typo, added two references

Basic Input/Output System, also known as BIOS, is a type of firmware used to provide runtime services for operating systems and programs and to perform hardware initialization during the booting process (power-on startup)<ref>{{Cite web |last=Kozierok |first=Charles M |date=2001-04-17 |title=Ref — System BIOS |url=http://www.pcguide.com/ref/mbsys/bios/index.htm |url-status=dead |archive-url=https://web.archive.org/web/20190218194254/http://www.pcguide.com/ref/mbsys/bios/index.htm |archive-date=2019-02-18 |access-date=2025-12-18 |website=The PC Guide}}</ref>.

Generally speaking, a good running computer's BIOS doesn't need to be updated frequently due to the instinct risk of BIOS flashing. However more and more mainstream computer manufactures starts pushing BIOS updates, often without user's consent or against the user's will, causing more issues and paves the way of controlling the device further.

==How it works==

===Pushing the BIOS update as non-optional Windows Update===
Traditionally, BIOS updates are done via a USB stick, which contains a FAT32 partition with bootloader and BIOS content. Recently the BIOS firmware is listed under Windows driver updates. Nowadays these updates are no longer under the "optional" category<ref>{{Cite web |last=@fec32a4de |date=2025-11-19 |title=How do I prevent Windows update from updating BIOS |url=https://www.reddit.com/r/HPOmen/comments/13lh22k/new_omen_wont_turn_off_lights_and_fan_in_sleep/ |url-status=live |archive-url=https://web.archive.org/web/20251218145243/https://www.techpowerup.com/forums/threads/how-do-i-prevent-windows-update-from-updating-bios.343076/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref><ref name=":0">{{Cite web |last=@redxps630 |date=2022-07-16 |title=how to prevent Windows Update from updating your bios |url=https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |url-status=live |archive-url=https://web.archive.org/web/20231021113238/https://www.dell.com/community/en/conversations/xps-desktops/how-to-prevent-windows-update-from-updating-your-bios/647f9de8f4ccf8a8de267068 |archive-date=2023-10-21 |access-date=2023-10-21 |website=Dell Community}}</ref>.

===Blocking BIOS downgrade===
In some computer models and BIOS versions, downgrade is blocked or "unsupported"<ref name=":1">{{Cite web |last=@ronyh |first= |date=2022-11-23 |title=BIOS Update blocked due to unsupported downgrade |url=https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |url-status=live |archive-url=https://web.archive.org/web/20240225053720/https://www.dell.com/community/en/conversations/optiplex-desktops/bios-update-blocked-due-to-unsupported-downgrade/647fa0dff4ccf8a8de5fbbd1 |archive-date=2024-02-25 |access-date=2025-12-18 |website=Dell Community}}</ref>, preventing the user from regaining lost functionalities.

===Removal of previous BIOS download link===

==Why it is a problem==

===Retroactive removal of functionalities===
Here's a non-exclusive list of removed functionalities:

*ACPI S3 sleep state<ref name=":2">{{Cite web |last=@mcgrubhub |date=2022-01-24 |title=Enable S3 Sleep State in BIOS Firmware Options |url=https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |url-status=live |archive-url=https://web.archive.org/web/20251218153346/https://h30434.www3.hp.com/t5/Desktops-Archive-Read-Only/Enable-S3-Sleep-State-in-BIOS-Firmware/td-p/8283201 |archive-date=2025-12-18 |access-date=2025-12-18 |website=HP Community}}</ref>, also known as "deep" sleep or "suspend-to-RAM"
*Undervolting<ref name=":3">{{Cite web |last=@u/DarkKnight04081995 |date=2020-11-17 |title=[GUIDE] Inspiron 7567: Bios downgrade from v1.12.1 to v1.11.0 |url=https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |url-status=live |archive-url=https://web.archive.org/web/20251218154156/https://old.reddit.com/r/Dell/comments/jw06pe/guide_inspiron_7567_bios_downgrade_from_v1121_to/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, a method of reducing power consumption without decreasing performance
*CPU thermal design power (TDP)<ref name=":4">{{Cite web |last=@eXplode |date=2024-12-18 |title=How to Stop Automatic BIOS Updates and some hate for BIOS 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |url-status=live |archive-url=https://web.archive.org/web/20251002181913/https://rog-forum.asus.com/t5/rog-strix-series/how-to-stop-automatic-bios-updates-and-some-hate-for-bios-331/td-p/1064184 |archive-date=2025-10-02 |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>
*Fan control.<ref>{{Cite web |last=@Mell |date=2025-10-4 |title=G713qm fan problem bios 331 |url=https://rog-forum.asus.com/t5/rog-strix-series/g713qm-fan-problem-bios-331/td-p/1118443 |url-status=live |access-date=2025-12-18 |website=Republic of Gamers Forum}}</ref>

===Reduced reliability/Planned obsolescence===
[[File:Asus bat chg v low.png|thumb|216x216px|Asus lowered the battery charging voltage to less than 16.6V, despite its 17.6V limited charging voltage.]]
Users reporting increased coil whine after a certain BIOS update<ref>{{Cite web |last=@ tom.m.culle150a02ca |date=2024-01-12 |title=Coil whine after bios update |url=https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |url-status=live |archive-url=https://web.archive.org/web/20251218183546/https://forum-en.msi.com/index.php?threads/coil-whine-after-bios-update.392641/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=MSI Global English Forum}}</ref>, possibly reducing reliability and increasing the failure rate.

Due to its unpredictable and forced nature, uncommanded BIOS updates have a higher chance of bricking the computer<ref name=":5">{{Cite web |last=@Parts-People Dell Laptop Experts |date=2025-11-02 |title=New Day, Another Bricked Laptop From Windows Update! |url=https://www.youtube.com/watch?v=8tRSjfFBtME |url-status=live |access-date=2025-12-18 |website=[[YouTube]]}}</ref>, such as interrupted BIOS update in the user's backpack due to over-temperature or battery depletion.

On some laptops, the battery capacity is restricted by reducing the charging voltage after a BIOS update, causing premature battery endurance decline. This practice is similar to [[Google Pixel 6a Battery Performance Program]] but without official announcement.

===Undermining ownership===
Manufacturers who force BIOS update often claim that blocking downgrade as "security features" to stop "bad player" from accessing the BIOS<ref name=":1" />. This is a classic example of "secure against the user"<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html#universal |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>.

==Examples==
These examples are non-exhaustive, some known instances are currently not listed due to insufficient source(s). All the examples below have BIOS update as non-optional Windows Update.

===Dell===
Blocked downgrade<ref name=":1" />, removed undervolting<ref name=":3" /><ref>{{Cite web |last=@WorldDj |date=2020-09-20 |title=Another victim of the BIOS update unfortunately |url=https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |url-status=live |archive-url=https://web.archive.org/web/20251218173346/https://www.techpowerup.com/forums/threads/another-victim-of-the-bios-update-unfortunately.272361/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=TechPowerUp}}</ref>, removed previous BIOS download links<ref>{{Cite web |title=Driver unavailable |url=https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=c5jy9 |access-date=2025-12-18 |website=Dell Product Support}}</ref>.

===Asus===
[[File:Ec update bricked bms 1.png|thumb|224x224px|A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful]]
Reduced TDP<ref name=":4" />, blocked downgrade, bricked battery.

===HP===
Disabled ACPI S3 sleep state<ref name=":2" />, blocked downgrade.

===Lenovo===
Disabled ACPI S3 sleep state<ref>{{Cite web |last=@Matusaprod |date=2023-07-15 |title=Linux sleep mode on newer thinkpad missing? |url=https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |url-status=live |archive-url=https://web.archive.org/web/20251218181844/https://old.reddit.com/r/thinkpad/comments/1505if1/linux_sleep_mode_on_newer_thinkpad_missing/ |archive-date=2025-12-18 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>.

==Countermeasures==

===Disabling UEFI Encapsulation===
On some computer models, UEFI Encapsulation can be disabled in BIOS settings<ref name=":0" />, disallowing the exchange of configuration data between the operating system and the UEFI firmware.

===Enabling "Do not include drivers with windows updates" in Group Policy===
Using Group Policy editor (gpedit.msc), users are able to exclude driver updates from Windows update<ref name=":0" /> since BIOS is often considered under drivers category. However, this method does not grantee success.

===Using a free operating system===
Free operating systems such as GNU/Linux respect user freedom. BIOS updates can be manually initiated using LVFS/fwupd

===Board-level repair===
Flashing BIOS firmware on a bricked laptop can be done by using a custom programmer<ref name=":5" />.

===Non-BIOS mitigation methods===
Some functions can be re-enabled without downgrading BIOS. Advanced BIOS<ref>{{Cite web |last=@u/Dijkmeneer |date=2022-12-19 |title=How to disable Modern sleep and enable s3 sleep on a lenovo laptop |url=https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |url-status=live |archive-url=https://web.archive.org/web/20240520204041/https://old.reddit.com/r/Lenovo/comments/zq3tc5/how_to_disable_modern_sleep_and_enable_s3_sleep/ |archive-date=2024-05-20 |access-date=2025-12-18 |website=[[Reddit]]}}</ref>, OpenCore<ref>{{Cite web |last=@MotorBottle |date=2023-10-01 |title=Enable S3 Sleep on ROG X13/G14/15 2021/2022 using OpenCore |url=https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |url-status=live |archive-url=https://web.archive.org/web/20250618061353/https://github.com/MotorBottle/S3-Sleep-on-Rog-X13-G14-15-2021-2022-using-OpenCore |archive-date=2025-06-18 |access-date=2025-12-19 |website=[[Github]]}}</ref>, Smokeless_UMAF<ref>{{Cite web |last=@DavidS95 |date=2023-05-07 |title=Bios Flasher? Where We’re Going, We Don’t Need Bios Flasher? |url=https://github.com/DavidS95/Smokeless_UMAF |url-status=live |archive-url=https://web.archive.org/web/20250925010047/https://github.com/DavidS95/Smokeless_UMAF/ |archive-date=2025-09-25 |access-date=2025-12-19 |website=[[Github]]}}</ref>.

==References==
{{reflist}}

[[Category:Common terms]]

File:Ec update bricked bms 1.png

2025-12-20T04:33:53Z

Charlie 6: Work-in-progress/* Licensing */

==Summary==
A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful
==Licensing==
The original poster said "You can go ahead and use any messages". Will update this section when a more suitable licensing that meets this description is found.

Forced BIOS firmware update

2025-12-18T19:51:08Z

Charlie 6: Created the page, added descriptions, still WIP

File:Ec update bricked bms 1.png

2025-12-18T19:49:33Z

Charlie 6: A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful

== Summary ==
A forced EC firmware update bricked an ASUS user's battery. Customer support was unhelpful
== Licensing ==
{{Permission}}

File:Asus bat chg v low.png

2025-12-18T19:14:40Z

Charlie 6: Charlie 6 uploaded a new version of File:Asus bat chg v low.png

Asus lowered the battery charging voltage, causing a massive drop of battery health displayed on KDE Info Center. The battery never exceed 16.6V during charging, despite it's 17.6V limited charging voltage.

File:Asus bat chg v low.png

2025-12-18T18:40:55Z

Charlie 6:

Brother printers causing issues with third party inks

2025-12-18T17:54:14Z

Charlie 6: Edited the link of FSF's comment

[[Brother Industries Ltd.|'''Brother''']] is a printer company that has allowed the use of third-party toner cartridges with their printer devices. Recent firmware updates have changed this practice by displaying an error message when consumers attempt to install their third-party toner that was previously allowed. When using the Brother printer with the toner of their choice, some users report a significant decrease in print quality, functionally disabling the printer unless OEM toner is installed.<ref name="reddit" />

==Relevant practices==
*'''Post-Sale Function Removal''' – Firmware updates retroactively remove previously available features, such as automatic color registration, for users using non-OEM toner.<ref name="reddit">[https://www.reddit.com/r/printers/comments/s9b2eg Brother MFC firmware update - non-genuine toner now disables critical features.]</ref><ref name="reddit-2">[https://www.reddit.com/r/printers/comments/w60687/brother_mfcl3370cdw_firmware_downgrade_needed/ Brother MFC-L3370CDW Firmware Downgrade needed]</ref>
*'''Vendor lock-in via DRM''' – Printers continue to function with third-party toner but print at lower quality unless OEM toner is installed.
*'''Anti-consumer software practices''' – Firmware updates cannot be easily rolled back, preventing consumers from restoring lost functionality.<ref name="github-fwupd">[https://github.com/sedrubal/brother_printer_fwupd/issues/9 Brother printer firmware downgrade discussion.]</ref>
*'''Deceptive practices''' – Printers do not reject third-party toner but intentionally cause a toner failure, which discourages use of third party toners.<ref name="hackernews">[https://news.ycombinator.com/item?id=31860131 Tell HN: Brother printers now locking out non-OEM paraphernalia.]</ref><ref name="reddit-2" />

==How it works==
1. Consumers purchase a Brother laser printer that previously accepted third-party toner.

2. A firmware update (e.g., W1.56) is pushed and does not notify users of any major changes in core functionality.

3. After updating, users report:

*Color registration fails by default, causing misaligned prints.<ref name="cups">[https://wiki.archlinux.org/title/CUPS/Printer-specific_problems#Updating_the_firmware ArchWiki - Printer-specific problems with Brother.]</ref>
4. Brother support acknowledges that installing OEM toner will immediately resolve the issue.<ref name="hackernews" />
*Older firmware versions are removed from Brother’s servers, preventing firmware downgrades that would fix the issue while also allowing consumers to use their preferred toner.<ref name="github-ohbrother">[https://github.com/CauldronDevelopmentLLC/oh-brother/issues/30 Discussion on firmware rollback for Brother printers.]</ref>

==Impact on consumer protection==
*Consumers may no longer use the ink provider of their choice without compromising the functionality of their printer.
*Consumers previously able to save money by purchasing third-party toner are now required to purchase OEM toner at a higher cost to maintain printer functionality.
*No prior warning of change in the printer's core functionality had been given before these firmware updates were installed.
*Workarounds tend to involve blocking the firmware updates or attempting downgrading the firmware, both of which Brother actively discourages.
==User evidence & reports==
===Hacker News Discussion (2022)===
*Users have noticed that Brother's printers do accept third-party toner instead of outright rejection. This leads some to suspect the consequential loss of print quality may be a deliberate act. One user stated:
<blockquote>''Brother seems to be apparently accepting the ink, but then purposefully making the print quality poorer.''<ref name="hackernews" /></blockquote>
===Free Software Foundation===
*FSF has listed this incident under the "Installing, deleting or disabling programs" in "Proprietary Back Doors" chapter<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html#install-delete |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>:
<blockquote>When connected to the internet, some Brother printers suffer a firmware downgrade that degrades the printing quality when using third-party toner. This proves that these printers have a back door which lets Brother control them.

As a general precaution, users should make sure their printer can't connect to the manufacturer's server, for example by shielding it from the internet by a firewall. This will not restore the ability of printers to use third-party toner if they have already lost it, but will prevent any future downgrades. All printer manufacturers are concerned, not only Brother.</blockquote>

===Reddit reports (r/printers)===
*A firmware update on the Brother MFC-3750 disabled automatic color registration when third-party toner was detected.<ref name="reddit" />
*A Brother support agent confirmed that installing OEM toner would "fix" the issue instantly, supporting user claims that the printer was being artificially restricted.

===GitHub developer investigation===
*A project analyzing Brother firmware updates discovered that older firmware versions were removed from Brother’s servers, making it impossible for users to roll back to a working version.<ref name="github-fwupd" />
*Another GitHub discussion showed that Brother firmware updates continue to lock out more non-Brother toner cartridges with each update.<ref name="github-ohbrother" />
*This is similar to [[HP Dynamic Security]], which blocks non-OEM cartridges.

===Quality example===
[[File:Brother HL-L9310CDW 1.69 1.32 before registration deleted.png|alt=Brother HL-L9310CDW 1.69 1.32, before deletion of colour registration.|none|thumb|800x800px|Brother HL-L9310CDW 1.69 1.32, before deletion of color registration.]]

==Brother's response==
On March 5th 2025, following the publication of a video on the Louis Rossmann YouTube channel, Brother addressed the issue in a response given to Ars Technica and stated the following: <ref name="ars-response">[https://arstechnica.com/gadgets/2025/03/brother-denies-using-firmware-updates-to-brick-printers-with-third-party-ink/ Brother denies using firmware updates to brick printers with third-party ink]</ref>
<blockquote>
"We are aware of the recent false claims suggesting that a Brother firmware update may have restricted the use of third-party ink cartridges. Please be assured that Brother firmware updates do not block the use of third-party ink in our machines."
</blockquote>
They also detailed that:
<blockquote>
"Brother printers do not intentionally degrade print quality based on whether a Brother Genuine or non-genuine ink/ toner cartridge is used. Brother cannot verify the quality of printing that will result when using a third-party compatible with a Brother printer."
</blockquote>
In their conclusion, they've attributed consumers' confusion and frustration to the following:
<blockquote>
"Brother encourages the use of Brother Genuine ink and toner for optimal performance and reliability, and it is standard practice that we perform a Brother Genuine check when troubleshooting a Brother printer. Compatible supplies may range in quality, and in order to verify that a printer is working properly, we like to troubleshoot with Brother Genuine supplies. We believe this check in the process may have led to a misunderstanding[,] but as we confirmed, the firmware update would not be responsible for the degradation of quality or removal of printer features."
</blockquote>While Brother's response indicates a simple issue with compatibility, the previous acceptance of third-party cartridges indicates a software-based compatibility issue rather than hardware-based. This implies that a software update has the potential to fix the compatibility issue and allow users to return to their previously accepted cartridges.

==Comparison to other industry decisions==
Other printer companies such as HP, Epson, and Canon have similar errors that actively promote more purchases of OEM cartridges even if the core issue is unrelated:
{| class="wikitable"
!Company!!Tactic Used
|-
|'''HP'''||"Dynamic Security" firmware updates blocking non-OEM ink
|-
|'''Epson'''||Ink expiration DRM, even when cartridges are full
|-
|'''Canon'''||Firmware updates that disable scanning when ink is low
|-
|'''Brother'''||Print degradation for non-OEM toner users
|}
==Mitigations available to users==
#'''Avoid Firmware Updates''' – Disable auto-updates to prevent forced function removal. This may, however, lead to security risks.
#'''Attempt to downgrade''' – Some users have managed to roll back firmware, though this is becoming increasingly difficult.<ref name="github-ohbrother" />
#'''HL-L9310CDW (with firmware main 1.69, sub 1.31):''' On the menu of the printer, delete the color registration to improve quality by reducing the misalignment of the individual colors. However, the best solution is to have a configuration option to set the offset individual (X, Y) for each color with the smallest possible increment, perhaps through an external (CUPS) printer driver.

==See also==

*[[HP Dynamic Security|'''HP Dynamic Security''']]

==References==
{{Reflist}}

[[Category:Brother]]
[[Category:Digital restrictions]]
[[Category:Vendor lock-in]]
[[Category:Post-sale firmware lockouts]]

Brother printers causing issues with third party inks

2025-12-18T17:52:51Z

Charlie 6: Edited the link of FSF's comment

[[Brother Industries Ltd.|'''Brother''']] is a printer company that has allowed the use of third-party toner cartridges with their printer devices. Recent firmware updates have changed this practice by displaying an error message when consumers attempt to install their third-party toner that was previously allowed. When using the Brother printer with the toner of their choice, some users report a significant decrease in print quality, functionally disabling the printer unless OEM toner is installed.<ref name="reddit" />

==Relevant practices==
*'''Post-Sale Function Removal''' – Firmware updates retroactively remove previously available features, such as automatic color registration, for users using non-OEM toner.<ref name="reddit">[https://www.reddit.com/r/printers/comments/s9b2eg Brother MFC firmware update - non-genuine toner now disables critical features.]</ref><ref name="reddit-2">[https://www.reddit.com/r/printers/comments/w60687/brother_mfcl3370cdw_firmware_downgrade_needed/ Brother MFC-L3370CDW Firmware Downgrade needed]</ref>
*'''Vendor lock-in via DRM''' – Printers continue to function with third-party toner but print at lower quality unless OEM toner is installed.
*'''Anti-consumer software practices''' – Firmware updates cannot be easily rolled back, preventing consumers from restoring lost functionality.<ref name="github-fwupd">[https://github.com/sedrubal/brother_printer_fwupd/issues/9 Brother printer firmware downgrade discussion.]</ref>
*'''Deceptive practices''' – Printers do not reject third-party toner but intentionally cause a toner failure, which discourages use of third party toners.<ref name="hackernews">[https://news.ycombinator.com/item?id=31860131 Tell HN: Brother printers now locking out non-OEM paraphernalia.]</ref><ref name="reddit-2" />

==How it works==
1. Consumers purchase a Brother laser printer that previously accepted third-party toner.

2. A firmware update (e.g., W1.56) is pushed and does not notify users of any major changes in core functionality.

3. After updating, users report:

*Color registration fails by default, causing misaligned prints.<ref name="cups">[https://wiki.archlinux.org/title/CUPS/Printer-specific_problems#Updating_the_firmware ArchWiki - Printer-specific problems with Brother.]</ref>
4. Brother support acknowledges that installing OEM toner will immediately resolve the issue.<ref name="hackernews" />
*Older firmware versions are removed from Brother’s servers, preventing firmware downgrades that would fix the issue while also allowing consumers to use their preferred toner.<ref name="github-ohbrother">[https://github.com/CauldronDevelopmentLLC/oh-brother/issues/30 Discussion on firmware rollback for Brother printers.]</ref>

==Impact on consumer protection==
*Consumers may no longer use the ink provider of their choice without compromising the functionality of their printer.
*Consumers previously able to save money by purchasing third-party toner are now required to purchase OEM toner at a higher cost to maintain printer functionality.
*No prior warning of change in the printer's core functionality had been given before these firmware updates were installed.
*Workarounds tend to involve blocking the firmware updates or attempting downgrading the firmware, both of which Brother actively discourages.
==User evidence & reports==
===Hacker News Discussion (2022)===
*Users have noticed that Brother's printers do accept third-party toner instead of outright rejection. This leads some to suspect the consequential loss of print quality may be a deliberate act. One user stated:
<blockquote>''Brother seems to be apparently accepting the ink, but then purposefully making the print quality poorer.''<ref name="hackernews" /></blockquote>
===Free Software Foundation===
*FSF has listed this incident under the "Installing, deleting or disabling programs" in "Proprietary Back Doors" chapter<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html#universal |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>:
<blockquote>When connected to the internet, some Brother printers suffer a firmware downgrade that degrades the printing quality when using third-party toner. This proves that these printers have a back door which lets Brother control them.

As a general precaution, users should make sure their printer can't connect to the manufacturer's server, for example by shielding it from the internet by a firewall. This will not restore the ability of printers to use third-party toner if they have already lost it, but will prevent any future downgrades. All printer manufacturers are concerned, not only Brother.</blockquote>

===Reddit reports (r/printers)===
*A firmware update on the Brother MFC-3750 disabled automatic color registration when third-party toner was detected.<ref name="reddit" />
*A Brother support agent confirmed that installing OEM toner would "fix" the issue instantly, supporting user claims that the printer was being artificially restricted.

===GitHub developer investigation===
*A project analyzing Brother firmware updates discovered that older firmware versions were removed from Brother’s servers, making it impossible for users to roll back to a working version.<ref name="github-fwupd" />
*Another GitHub discussion showed that Brother firmware updates continue to lock out more non-Brother toner cartridges with each update.<ref name="github-ohbrother" />
*This is similar to [[HP Dynamic Security]], which blocks non-OEM cartridges.

===Quality example===
[[File:Brother HL-L9310CDW 1.69 1.32 before registration deleted.png|alt=Brother HL-L9310CDW 1.69 1.32, before deletion of colour registration.|none|thumb|800x800px|Brother HL-L9310CDW 1.69 1.32, before deletion of color registration.]]

==Brother's response==
On March 5th 2025, following the publication of a video on the Louis Rossmann YouTube channel, Brother addressed the issue in a response given to Ars Technica and stated the following: <ref name="ars-response">[https://arstechnica.com/gadgets/2025/03/brother-denies-using-firmware-updates-to-brick-printers-with-third-party-ink/ Brother denies using firmware updates to brick printers with third-party ink]</ref>
<blockquote>
"We are aware of the recent false claims suggesting that a Brother firmware update may have restricted the use of third-party ink cartridges. Please be assured that Brother firmware updates do not block the use of third-party ink in our machines."
</blockquote>
They also detailed that:
<blockquote>
"Brother printers do not intentionally degrade print quality based on whether a Brother Genuine or non-genuine ink/ toner cartridge is used. Brother cannot verify the quality of printing that will result when using a third-party compatible with a Brother printer."
</blockquote>
In their conclusion, they've attributed consumers' confusion and frustration to the following:
<blockquote>
"Brother encourages the use of Brother Genuine ink and toner for optimal performance and reliability, and it is standard practice that we perform a Brother Genuine check when troubleshooting a Brother printer. Compatible supplies may range in quality, and in order to verify that a printer is working properly, we like to troubleshoot with Brother Genuine supplies. We believe this check in the process may have led to a misunderstanding[,] but as we confirmed, the firmware update would not be responsible for the degradation of quality or removal of printer features."
</blockquote>While Brother's response indicates a simple issue with compatibility, the previous acceptance of third-party cartridges indicates a software-based compatibility issue rather than hardware-based. This implies that a software update has the potential to fix the compatibility issue and allow users to return to their previously accepted cartridges.

==Comparison to other industry decisions==
Other printer companies such as HP, Epson, and Canon have similar errors that actively promote more purchases of OEM cartridges even if the core issue is unrelated:
{| class="wikitable"
!Company!!Tactic Used
|-
|'''HP'''||"Dynamic Security" firmware updates blocking non-OEM ink
|-
|'''Epson'''||Ink expiration DRM, even when cartridges are full
|-
|'''Canon'''||Firmware updates that disable scanning when ink is low
|-
|'''Brother'''||Print degradation for non-OEM toner users
|}
==Mitigations available to users==
#'''Avoid Firmware Updates''' – Disable auto-updates to prevent forced function removal. This may, however, lead to security risks.
#'''Attempt to downgrade''' – Some users have managed to roll back firmware, though this is becoming increasingly difficult.<ref name="github-ohbrother" />
#'''HL-L9310CDW (with firmware main 1.69, sub 1.31):''' On the menu of the printer, delete the color registration to improve quality by reducing the misalignment of the individual colors. However, the best solution is to have a configuration option to set the offset individual (X, Y) for each color with the smallest possible increment, perhaps through an external (CUPS) printer driver.

==See also==

*[[HP Dynamic Security|'''HP Dynamic Security''']]

==References==
{{Reflist}}

[[Category:Brother]]
[[Category:Digital restrictions]]
[[Category:Vendor lock-in]]
[[Category:Post-sale firmware lockouts]]

Brother printers causing issues with third party inks

2025-12-18T06:26:38Z

Charlie 6: /* User evidence & reports */ added mention of this incident on GNU website

[[Brother Industries Ltd.|'''Brother''']] is a printer company that has allowed the use of third-party toner cartridges with their printer devices. Recent firmware updates have changed this practice by displaying an error message when consumers attempt to install their third-party toner that was previously allowed. When using the Brother printer with the toner of their choice, some users report a significant decrease in print quality, functionally disabling the printer unless OEM toner is installed.<ref name="reddit" />

==Relevant practices==
*'''Post-Sale Function Removal''' – Firmware updates retroactively remove previously available features, such as automatic color registration, for users using non-OEM toner.<ref name="reddit">[https://www.reddit.com/r/printers/comments/s9b2eg Brother MFC firmware update - non-genuine toner now disables critical features.]</ref><ref name="reddit-2">[https://www.reddit.com/r/printers/comments/w60687/brother_mfcl3370cdw_firmware_downgrade_needed/ Brother MFC-L3370CDW Firmware Downgrade needed]</ref>
*'''Vendor lock-in via DRM''' – Printers continue to function with third-party toner but print at lower quality unless OEM toner is installed.
*'''Anti-consumer software practices''' – Firmware updates cannot be easily rolled back, preventing consumers from restoring lost functionality.<ref name="github-fwupd">[https://github.com/sedrubal/brother_printer_fwupd/issues/9 Brother printer firmware downgrade discussion.]</ref>
*'''Deceptive practices''' – Printers do not reject third-party toner but intentionally cause a toner failure, which discourages use of third party toners.<ref name="hackernews">[https://news.ycombinator.com/item?id=31860131 Tell HN: Brother printers now locking out non-OEM paraphernalia.]</ref><ref name="reddit-2" />

==How it works==
1. Consumers purchase a Brother laser printer that previously accepted third-party toner.

2. A firmware update (e.g., W1.56) is pushed and does not notify users of any major changes in core functionality.

3. After updating, users report:

*Color registration fails by default, causing misaligned prints.<ref name="cups">[https://wiki.archlinux.org/title/CUPS/Printer-specific_problems#Updating_the_firmware ArchWiki - Printer-specific problems with Brother.]</ref>
4. Brother support acknowledges that installing OEM toner will immediately resolve the issue.<ref name="hackernews" />
*Older firmware versions are removed from Brother’s servers, preventing firmware downgrades that would fix the issue while also allowing consumers to use their preferred toner.<ref name="github-ohbrother">[https://github.com/CauldronDevelopmentLLC/oh-brother/issues/30 Discussion on firmware rollback for Brother printers.]</ref>

==Impact on consumer protection==
*Consumers may no longer use the ink provider of their choice without compromising the functionality of their printer.
*Consumers previously able to save money by purchasing third-party toner are now required to purchase OEM toner at a higher cost to maintain printer functionality.
*No prior warning of change in the printer's core functionality had been given before these firmware updates were installed.
*Workarounds tend to involve blocking the firmware updates or attempting downgrading the firmware, both of which Brother actively discourages.
==User evidence & reports==
===Hacker News Discussion (2022)===
*Users have noticed that Brother's printers do accept third-party toner instead of outright rejection. This leads some to suspect the consequential loss of print quality may be a deliberate act. One user stated:
<blockquote>''Brother seems to be apparently accepting the ink, but then purposefully making the print quality poorer.''<ref name="hackernews" /></blockquote>
===Free Software Foundation ===
*FSF has listed this incident under the "Installing, deleting or disabling programs" in "Proprietary Back Doors" chapter<ref>{{Cite web |date=2025-12-14 |title=Proprietary Back Doors |url=https://www.gnu.org/proprietary/proprietary-back-doors.html |url-status=live |archive-url=https://web.archive.org/web/20251218062339/https://www.gnu.org/proprietary/proprietary-back-doors.html |archive-date=2025-12-18 |access-date=2025-12-18 |website=GNU Operating System}}</ref>:
<blockquote>When connected to the internet, some Brother printers suffer a firmware downgrade that degrades the printing quality when using third-party toner. This proves that these printers have a back door which lets Brother control them.

As a general precaution, users should make sure their printer can't connect to the manufacturer's server, for example by shielding it from the internet by a firewall. This will not restore the ability of printers to use third-party toner if they have already lost it, but will prevent any future downgrades. All printer manufacturers are concerned, not only Brother.</blockquote>

===Reddit reports (r/printers)===
*A firmware update on the Brother MFC-3750 disabled automatic color registration when third-party toner was detected.<ref name="reddit" />
*A Brother support agent confirmed that installing OEM toner would "fix" the issue instantly, supporting user claims that the printer was being artificially restricted.

===GitHub developer investigation===
*A project analyzing Brother firmware updates discovered that older firmware versions were removed from Brother’s servers, making it impossible for users to roll back to a working version.<ref name="github-fwupd" />
*Another GitHub discussion showed that Brother firmware updates continue to lock out more non-Brother toner cartridges with each update.<ref name="github-ohbrother" />
*This is similar to [[HP Dynamic Security]], which blocks non-OEM cartridges.

===Quality example===
[[File:Brother HL-L9310CDW 1.69 1.32 before registration deleted.png|alt=Brother HL-L9310CDW 1.69 1.32, before deletion of colour registration.|none|thumb|800x800px|Brother HL-L9310CDW 1.69 1.32, before deletion of color registration.]]

==Brother's response==
On March 5th 2025, following the publication of a video on the Louis Rossmann YouTube channel, Brother addressed the issue in a response given to Ars Technica and stated the following: <ref name="ars-response">[https://arstechnica.com/gadgets/2025/03/brother-denies-using-firmware-updates-to-brick-printers-with-third-party-ink/ Brother denies using firmware updates to brick printers with third-party ink]</ref>
<blockquote>
"We are aware of the recent false claims suggesting that a Brother firmware update may have restricted the use of third-party ink cartridges. Please be assured that Brother firmware updates do not block the use of third-party ink in our machines."
</blockquote>
They also detailed that:
<blockquote>
"Brother printers do not intentionally degrade print quality based on whether a Brother Genuine or non-genuine ink/ toner cartridge is used. Brother cannot verify the quality of printing that will result when using a third-party compatible with a Brother printer."
</blockquote>
In their conclusion, they've attributed consumers' confusion and frustration to the following:
<blockquote>
"Brother encourages the use of Brother Genuine ink and toner for optimal performance and reliability, and it is standard practice that we perform a Brother Genuine check when troubleshooting a Brother printer. Compatible supplies may range in quality, and in order to verify that a printer is working properly, we like to troubleshoot with Brother Genuine supplies. We believe this check in the process may have led to a misunderstanding[,] but as we confirmed, the firmware update would not be responsible for the degradation of quality or removal of printer features."
</blockquote>While Brother's response indicates a simple issue with compatibility, the previous acceptance of third-party cartridges indicates a software-based compatibility issue rather than hardware-based. This implies that a software update has the potential to fix the compatibility issue and allow users to return to their previously accepted cartridges.

==Comparison to other industry decisions==
Other printer companies such as HP, Epson, and Canon have similar errors that actively promote more purchases of OEM cartridges even if the core issue is unrelated:
{| class="wikitable"
!Company!!Tactic Used
|-
|'''HP'''||"Dynamic Security" firmware updates blocking non-OEM ink
|-
|'''Epson'''||Ink expiration DRM, even when cartridges are full
|-
|'''Canon'''||Firmware updates that disable scanning when ink is low
|-
|'''Brother'''||Print degradation for non-OEM toner users
|}
==Mitigations available to users==
#'''Avoid Firmware Updates''' – Disable auto-updates to prevent forced function removal. This may, however, lead to security risks.
#'''Attempt to downgrade''' – Some users have managed to roll back firmware, though this is becoming increasingly difficult.<ref name="github-ohbrother" />
#'''HL-L9310CDW (with firmware main 1.69, sub 1.31):''' On the menu of the printer, delete the color registration to improve quality by reducing the misalignment of the individual colors. However, the best solution is to have a configuration option to set the offset individual (X, Y) for each color with the smallest possible increment, perhaps through an external (CUPS) printer driver.

==See also==

*[[HP Dynamic Security|'''HP Dynamic Security''']]

==References==
{{Reflist}}

[[Category:Brother]]
[[Category:Digital restrictions]]
[[Category:Vendor lock-in]]
[[Category:Post-sale firmware lockouts]]

Talk:Battery firmware lockout

2025-09-17T17:24:08Z

Charlie 6: /* Reconditioning */

== On Texas Instruments BQ-series BMS ==

This type of BMSes is the most common type used on laptop computers.

Unlike the BMS in power tools that you can dump the firmware, the Texas Instruments BQ series BMS has something like "a chip within a chip", similar to Intel Management Engine or fTPM.

I learned from some friends who worked with power electronics. The BQ series needs password to access the internal memory. Unfortunately, the "Permanent Fail" is gated the same "height" of the "wall" as flashing firmware. If you know the password you can read and even write (both official and custom) firmware, if you don't know the password you can't even clear the PF error code.

The BMS sends the battery's current status like the voltage, current, temperature, cycle count and the limitations like charge max voltage/current, discharge min voltage/max current, etc, to the device. It's know that some computer models use different battery packs, the EC supplies the correct voltage and current to the battery because the BMS tells these values to the EC. These messages are not encrypted and are read by embedded controller (EC) on the computer's motherboard.

Thus, we can technically build our own FOSS BMS using the same way of communication with the EC, without any "lockout" logic, or we can just buy a BQ chip from TI, use the official firmware but without setting a custom password. If the "community driven" custom BMS gains traction and reaches mass production, we can solve the "battery firmware lockout" once and for all.

The reason why few people talk about it, I think, is the "baseline" reliability difference. The reliability of a product depends on the least reliable part, so laptop batteries have to be very reliable. As a result, they don't fail randomly. Given the high quality standard, non-OEM battery manufacturers and independent repair technicians can rarely reach the reliability standard of the original ones. Therefore there's low incentive for those people to find a reliable way of unbricking the BMS. [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 13:13, 17 September 2025 (UTC)

== On Battery Safety and the Justification of Lockout ==

There are many online misinformation about the safety of Li-ion batteries, both in discussion threads and video comments. Some of these comments are trying to justify the lockout by saying the exaggerated values/criteria, such as saying it's not safe to charge below 2.5V to 2.8V when the actual values are between 1.5V to 2.0V.

Conclusion first, in case technical details are too long to read.

=== Conclusion ===

==== Non malicious ====
Low voltage cutout(according to the specification): Disable discharging when the voltage is too low or the battery is too unbalanced. If the voltage is too low (<2.5V) wear will increase and performance will degrade faster, but the battery is still safe to use.

Unsafe voltage cutout: Disable charging if the voltage is way too low (<1.5V), as chemical decomposition could occur causing the battery to be less safe (can be tested, see reconditioning section).

==== Malicious ====
"Fragile ego": The disable voltage is way higher than the overdischarged unsafe voltage, wasting good batteries.

No balancing circuit: Faster degradation.

Password: preventing reconditioning/refurbishment.

Timer: Brick after X days or discharge cycles regardless of battery health, which is planned obsolescence.

=== Reconditioning ===
The voltages written in this section are '''open circuit voltages''' i.e the measured voltage when neither charging nor discharging. This is only a general guideline, the actual voltage may be higher or lower depends on the battery chemistry.

==== Disclaimer ====
Troubleshooting Li-ion batteries can be dangerous, this section is for informational purposes only. You are responsible for your own safety. Always wear appropriate protection and consult the specification of the equipment carefully.

==== 2.5V or above ====
charge normally.

==== 2.0V<voltage<2.5V ====
Charge slowly (<0.1C), resume normal charging speed above 3.0V, then do a charge/discharge cycle normally and measure the capacity, if normal continue to use, if lower replace it with a matched sell or put this cell to another pack with worn cells to match them.

==== 1.0V<voltage<2.0V ====
Charge very slowly (<0.05C). Observe the voltage and temperature carefully. If voltage fails to rise or temperature rises rapidly, chemical decomposition has occurred, do not use. When the voltage reaches nominal (around 3.7V), stop charging and wait for several hours, if the voltage is gone do not use, if not, proceed to normal charging. Do a charge/discharge cycle normally and measure the capacity. If capacity is way lower or internal resistance is way higher than before, do not use.

==== <1.0V ====
Replace the cells. It may be possible to revive it, but massive performance loss and additional safety risk is almost guaranteed. Don't even bother.

==== Unbalanced ====
Charge the lower(est) cell(s) to the voltage of other cells and perform a cycle. Observe the voltage of each cell, replace the ones with much higher/lower during charging/discharging.

=== Interpreting the specifications ===
There are many values (voltage, current, temperature) on the datasheet of the battery cells and the packs that are made of these cells. For discussing firmware lockout, we mostly focus on two values: discharge cut-off voltage and safety cutout voltage.

==== Discharge cut-off voltage ====
This voltage is a '''loaded voltage''' i.e measured during discharging. It is when the current should be turned off during discharging. Since batteries have internal resistance, this voltage is not the "0% charge" voltage. Assume discharging to 2.5V, the voltage will climb to 3.0V or even 3.3V after removing the current.

The discharge cut-off voltage is highly related to cycle life. The battery's rated cycle life is measured by charging and discharging repeatedly at predetermined voltage, current and temperature.

Discharging to a higher voltage doesn't use up the full capacity of the battery but the actual life will increase. Discharging to a lower voltage gives very little gain at the cost of significant wear. Thus, the discharge cut-off voltage specification is determined with a balance of cycle life and discharge capacity.

==== Safety cutout voltage ====
Commonly referred as "Do not charge" voltage, this voltage is where chemical decomposition occurs and it's no longer safe to charge due to elevated risks.

This is an '''open circuit voltage'''. If you somehow discharge the battery to this voltage but it bounced back to above discharge cut-off voltage after switching off the device, it's still safe to use, but don't do this intentionally, the gain is not worth the cost. If it bounces back to between these two voltages, see below.

The voltage between the safety cutout voltage and discharge cut-off voltage is the "pre-charge" range, where a very low charging current is applied to safely bring the battery pack back to normal.

A common "self destructive design" is to program the BMS "Permanent Fail" low voltage to way higher than the battery's safety cutout voltage. If the voltage is set to as high as the discharge cut-off voltage, the battery may brick itself if a large instantaneous load is applied(common on power tools) while the battery is at low charge.

==== Zero voltage ====
If the battery pack is discharged even momentarily after one cell has reached zero voltage, internal short circuit will occur within that cell due to reverse polarity. The cell will be destroyed immediately and permanently, without any chance of recovery.

=== Sources ===
[https://lygte-info.dk/info/BatteryLowVoltage%20UK.html How far can LiIon be discharged?] Written by Henrik K. Jensen, an independent battery reviewer. This is more of a theoretical analysis and explanation about the theories behind them, using technical handbooks as the sources.

[https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ Ryobi Battery Repair Guide]. Written by Badar Jahangir Kayani, an electrical engineer. This is more of a practical take of reconditioning "bricked" battery packs. He consider <1V per cell (<5V per pack) as deep discharged and not safe to use. Despite that, he managed to recover them (for testing, not for actual usage). According to "Gathering Data" section of his video, the Permanent Firmware Lockout occurs at a voltage as high as 2.82V, way higher than the safety cutout voltage and may be even higher than discharge cut-off voltage. It's a solid evidence that Ryobi did the malicious "fragile ego" on their BMS.

=== Comments ===

==== Why focusing on discharge voltage? ====
Because partial knowledge can be as misleading as zero knowledge.

When a li-ion battery is deeply overcharged, it's a common consensus that safety risk is imminent as the excessive energy has to go somewhere immediately. When it's deeply overdischarged, the safety risk is lower since there's little, if any, energy in the battery. That's the reason the unsafe high voltage is only slightly higher than the maximum charge voltage but the unsafe low voltage is significantly lower than the minimum discharge voltage. Misinformed users are sometimes convinced that overdischarging is as dangerous as overcharging.

The difference between discharge cut-off voltage safety cutout voltage must be explained clearly. Some people confuse these two and justifying cutting off charging when the voltage is at or only slightly blow the discharge cut-off voltage. This is made worse by anti-consumer manufacturers "stirring the water". [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 17:11, 17 September 2025 (UTC)

Talk:Battery firmware lockout

2025-09-17T17:17:44Z

Charlie 6: /* Why focusing on discharge voltage? */

== On Texas Instruments BQ-series BMS ==

This type of BMSes is the most common type used on laptop computers.

Unlike the BMS in power tools that you can dump the firmware, the Texas Instruments BQ series BMS has something like "a chip within a chip", similar to Intel Management Engine or fTPM.

I learned from some friends who worked with power electronics. The BQ series needs password to access the internal memory. Unfortunately, the "Permanent Fail" is gated the same "height" of the "wall" as flashing firmware. If you know the password you can read and even write (both official and custom) firmware, if you don't know the password you can't even clear the PF error code.

The BMS sends the battery's current status like the voltage, current, temperature, cycle count and the limitations like charge max voltage/current, discharge min voltage/max current, etc, to the device. It's know that some computer models use different battery packs, the EC supplies the correct voltage and current to the battery because the BMS tells these values to the EC. These messages are not encrypted and are read by embedded controller (EC) on the computer's motherboard.

Thus, we can technically build our own FOSS BMS using the same way of communication with the EC, without any "lockout" logic, or we can just buy a BQ chip from TI, use the official firmware but without setting a custom password. If the "community driven" custom BMS gains traction and reaches mass production, we can solve the "battery firmware lockout" once and for all.

The reason why few people talk about it, I think, is the "baseline" reliability difference. The reliability of a product depends on the least reliable part, so laptop batteries have to be very reliable. As a result, they don't fail randomly. Given the high quality standard, non-OEM battery manufacturers and independent repair technicians can rarely reach the reliability standard of the original ones. Therefore there's low incentive for those people to find a reliable way of unbricking the BMS. [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 13:13, 17 September 2025 (UTC)

== On Battery Safety and the Justification of Lockout ==

There are many online misinformation about the safety of Li-ion batteries, both in discussion threads and video comments. Some of these comments are trying to justify the lockout by saying the exaggerated values/criteria, such as saying it's not safe to charge below 2.5V to 2.8V when the actual values are between 1.5V to 2.0V.

Conclusion first, in case technical details are too long to read.

=== Conclusion ===

==== Non malicious ====
Low voltage cutout(according to the specification): Disable discharging when the voltage is too low or the battery is too unbalanced. If the voltage is too low (<2.5V) wear will increase and performance will degrade faster, but the battery is still safe to use.

Unsafe voltage cutout: Disable charging if the voltage is way too low (<1.5V), as chemical decomposition could occur causing the battery to be less safe (can be tested, see reconditioning section).

==== Malicious ====
"Fragile ego": The disable voltage is way higher than the overdischarged unsafe voltage, wasting good batteries.

No balancing circuit: Faster degradation.

Password: preventing reconditioning/refurbishment.

Timer: Brick after X days or discharge cycles regardless of battery health, which is planned obsolescence.

=== Reconditioning ===
The voltages written in this section are a '''open circuit voltage''' i.e the measured voltage when neither charging nor discharging. This is only a general guideline, the actual voltage may be higher or lower depends on the battery chemistry.

==== Disclaimer ====
Troubleshooting Li-ion batteries can be dangerous, this section is for informational purposes only. You are responsible for your own safety. Always wear appropriate protection and consult the specification of the equipment carefully.

==== 2.5V or above ====
charge normally.

==== 2.0V<voltage<2.5V ====
Charge slowly (<0.1C), resume normal charging speed above 3.0V, then do a charge/discharge cycle normally and measure the capacity, if normal continue to use, if lower replace it with a matched sell or put this cell to another pack with worn cells to match them.

==== 1.0V<voltage<2.0V ====
Charge very slowly (<0.05C). Observe the voltage and temperature carefully. If voltage fails to rise or temperature rises rapidly, chemical decomposition has occurred, do not use. When the voltage reaches nominal (around 3.7V), stop charging and wait for several hours, if the voltage is gone do not use, if not, proceed to normal charging. Do a charge/discharge cycle normally and measure the capacity. If capacity is way lower or internal resistance is way higher than before, do not use.

==== <1.0V ====
Replace the cells. It may be possible to revive it, but massive performance loss and additional safety risk is almost guaranteed. Don't even bother.

==== Unbalanced ====
Charge the lower(est) cell(s) to the voltage of other cells and perform a cycle. Observe the voltage of each cell, replace the ones with much higher/lower during charging/discharging.

=== Interpreting the specifications ===
There are many values (voltage, current, temperature) on the datasheet of the battery cells and the packs that are made of these cells. For discussing firmware lockout, we mostly focus on two values: discharge cut-off voltage and safety cutout voltage.

==== Discharge cut-off voltage ====
This voltage is a '''loaded voltage''' i.e measured during discharging. It is when the current should be turned off during discharging. Since batteries have internal resistance, this voltage is not the "0% charge" voltage. Assume discharging to 2.5V, the voltage will climb to 3.0V or even 3.3V after removing the current.

The discharge cut-off voltage is highly related to cycle life. The battery's rated cycle life is measured by charging and discharging repeatedly at predetermined voltage, current and temperature.

Discharging to a higher voltage doesn't use up the full capacity of the battery but the actual life will increase. Discharging to a lower voltage gives very little gain at the cost of significant wear. Thus, the discharge cut-off voltage specification is determined with a balance of cycle life and discharge capacity.

==== Safety cutout voltage ====
Commonly referred as "Do not charge" voltage, this voltage is where chemical decomposition occurs and it's no longer safe to charge due to elevated risks.

This is an '''open circuit voltage'''. If you somehow discharge the battery to this voltage but it bounced back to above discharge cut-off voltage after switching off the device, it's still safe to use, but don't do this intentionally, the gain is not worth the cost. If it bounces back to between these two voltages, see below.

The voltage between the safety cutout voltage and discharge cut-off voltage is the "pre-charge" range, where a very low charging current is applied to safely bring the battery pack back to normal.

A common "self destructive design" is to program the BMS "Permanent Fail" low voltage to way higher than the battery's safety cutout voltage. If the voltage is set to as high as the discharge cut-off voltage, the battery may brick itself if a large instantaneous load is applied(common on power tools) while the battery is at low charge.

==== Zero voltage ====
If the battery pack is discharged even momentarily after one cell has reached zero voltage, internal short circuit will occur within that cell due to reverse polarity. The cell will be destroyed immediately and permanently, without any chance of recovery.

=== Sources ===
[https://lygte-info.dk/info/BatteryLowVoltage%20UK.html How far can LiIon be discharged?] Written by Henrik K. Jensen, an independent battery reviewer. This is more of a theoretical analysis and explanation about the theories behind them, using technical handbooks as the sources.

[https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ Ryobi Battery Repair Guide]. Written by Badar Jahangir Kayani, an electrical engineer. This is more of a practical take of reconditioning "bricked" battery packs. He consider <1V per cell (<5V per pack) as deep discharged and not safe to use. Despite that, he managed to recover them (for testing, not for actual usage). According to "Gathering Data" section of his video, the Permanent Firmware Lockout occurs at a voltage as high as 2.82V, way higher than the safety cutout voltage and may be even higher than discharge cut-off voltage. It's a solid evidence that Ryobi did the malicious "fragile ego" on their BMS.

=== Comments ===

==== Why focusing on discharge voltage? ====
Because partial knowledge can be as misleading as zero knowledge.

When a li-ion battery is deeply overcharged, it's a common consensus that safety risk is imminent as the excessive energy has to go somewhere immediately. When it's deeply overdischarged, the safety risk is lower since there's little, if any, energy in the battery. That's the reason the unsafe high voltage is only slightly higher than the maximum charge voltage but the unsafe low voltage is significantly lower than the minimum discharge voltage. Misinformed users are sometimes convinced that overdischarging is as dangerous as overcharging.

The difference between discharge cut-off voltage safety cutout voltage must be explained clearly. Some people confuse these two and justifying cutting off charging when the voltage is at or only slightly blow the discharge cut-off voltage. This is made worse by anti-consumer manufacturers "stirring the water". [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 17:11, 17 September 2025 (UTC)

Talk:Battery firmware lockout

2025-09-17T17:14:33Z

Charlie 6:

== On Texas Instruments BQ-series BMS ==

This type of BMSes is the most common type used on laptop computers.

Unlike the BMS in power tools that you can dump the firmware, the Texas Instruments BQ series BMS has something like "a chip within a chip", similar to Intel Management Engine or fTPM.

I learned from some friends who worked with power electronics. The BQ series needs password to access the internal memory. Unfortunately, the "Permanent Fail" is gated the same "height" of the "wall" as flashing firmware. If you know the password you can read and even write (both official and custom) firmware, if you don't know the password you can't even clear the PF error code.

The BMS sends the battery's current status like the voltage, current, temperature, cycle count and the limitations like charge max voltage/current, discharge min voltage/max current, etc, to the device. It's know that some computer models use different battery packs, the EC supplies the correct voltage and current to the battery because the BMS tells these values to the EC. These messages are not encrypted and are read by embedded controller (EC) on the computer's motherboard.

Thus, we can technically build our own FOSS BMS using the same way of communication with the EC, without any "lockout" logic, or we can just buy a BQ chip from TI, use the official firmware but without setting a custom password. If the "community driven" custom BMS gains traction and reaches mass production, we can solve the "battery firmware lockout" once and for all.

The reason why few people talk about it, I think, is the "baseline" reliability difference. The reliability of a product depends on the least reliable part, so laptop batteries have to be very reliable. As a result, they don't fail randomly. Given the high quality standard, non-OEM battery manufacturers and independent repair technicians can rarely reach the reliability standard of the original ones. Therefore there's low incentive for those people to find a reliable way of unbricking the BMS. [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 13:13, 17 September 2025 (UTC)

== On Battery Safety and the Justification of Lockout ==

There are many online misinformation about the safety of Li-ion batteries, both in discussion threads and video comments. Some of these comments are trying to justify the lockout by saying the exaggerated values/criteria, such as saying it's not safe to charge below 2.5V to 2.8V when the actual values are between 1.5V to 2.0V.

Conclusion first, in case technical details are too long to read.

=== Conclusion ===

==== Non malicious ====
Low voltage cutout(according to the specification): Disable discharging when the voltage is too low or the battery is too unbalanced. If the voltage is too low (<2.5V) wear will increase and performance will degrade faster, but the battery is still safe to use.

Unsafe voltage cutout: Disable charging if the voltage is way too low (<1.5V), as chemical decomposition could occur causing the battery to be less safe (can be tested, see reconditioning section).

==== Malicious ====
"Fragile ego": The disable voltage is way higher than the overdischarged unsafe voltage, wasting good batteries.

No balancing circuit: Faster degradation.

Password: preventing reconditioning/refurbishment.

Timer: Brick after X days or discharge cycles regardless of battery health, which is planned obsolescence.

=== Reconditioning ===
The voltages written in this section are a '''open circuit voltage''' i.e the measured voltage when neither charging nor discharging. This is only a general guideline, the actual voltage may be higher or lower depends on the battery chemistry.

==== Disclaimer ====
Troubleshooting Li-ion batteries can be dangerous, this section is for informational purposes only. You are responsible for your own safety. Always wear appropriate protection and consult the specification of the equipment carefully.

==== 2.5V or above ====
charge normally.

==== 2.0V<voltage<2.5V ====
Charge slowly (<0.1C), resume normal charging speed above 3.0V, then do a charge/discharge cycle normally and measure the capacity, if normal continue to use, if lower replace it with a matched sell or put this cell to another pack with worn cells to match them.

==== 1.0V<voltage<2.0V ====
Charge very slowly (<0.05C). Observe the voltage and temperature carefully. If voltage fails to rise or temperature rises rapidly, chemical decomposition has occurred, do not use. When the voltage reaches nominal (around 3.7V), stop charging and wait for several hours, if the voltage is gone do not use, if not, proceed to normal charging. Do a charge/discharge cycle normally and measure the capacity. If capacity is way lower or internal resistance is way higher than before, do not use.

==== <1.0V ====
Replace the cells. It may be possible to revive it, but massive performance loss and additional safety risk is almost guaranteed. Don't even bother.

==== Unbalanced ====
Charge the lower(est) cell(s) to the voltage of other cells and perform a cycle. Observe the voltage of each cell, replace the ones with much higher/lower during charging/discharging.

=== Interpreting the specifications ===
There are many values (voltage, current, temperature) on the datasheet of the battery cells and the packs that are made of these cells. For discussing firmware lockout, we mostly focus on two values: discharge cut-off voltage and safety cutout voltage.

==== Discharge cut-off voltage ====
This voltage is a '''loaded voltage''' i.e measured during discharging. It is when the current should be turned off during discharging. Since batteries have internal resistance, this voltage is not the "0% charge" voltage. Assume discharging to 2.5V, the voltage will climb to 3.0V or even 3.3V after removing the current.

The discharge cut-off voltage is highly related to cycle life. The battery's rated cycle life is measured by charging and discharging repeatedly at predetermined voltage, current and temperature.

Discharging to a higher voltage doesn't use up the full capacity of the battery but the actual life will increase. Discharging to a lower voltage gives very little gain at the cost of significant wear. Thus, the discharge cut-off voltage specification is determined with a balance of cycle life and discharge capacity.

==== Safety cutout voltage ====
Commonly referred as "Do not charge" voltage, this voltage is where chemical decomposition occurs and it's no longer safe to charge due to elevated risks.

This is an '''open circuit voltage'''. If you somehow discharge the battery to this voltage but it bounced back to above discharge cut-off voltage after switching off the device, it's still safe to use, but don't do this intentionally, the gain is not worth the cost. If it bounces back to between these two voltages, see below.

The voltage between the safety cutout voltage and discharge cut-off voltage is the "pre-charge" range, where a very low charging current is applied to safely bring the battery pack back to normal.

A common "self destructive design" is to program the BMS "Permanent Fail" low voltage to way higher than the battery's safety cutout voltage. If the voltage is set to as high as the discharge cut-off voltage, the battery may brick itself if a large instantaneous load is applied(common on power tools) while the battery is at low charge.

==== Zero voltage ====
If the battery pack is discharged even momentarily after one cell has reached zero voltage, internal short circuit will occur within that cell due to reverse polarity. The cell will be destroyed immediately and permanently, without any chance of recovery.

=== Sources ===
[https://lygte-info.dk/info/BatteryLowVoltage%20UK.html How far can LiIon be discharged?] Written by Henrik K. Jensen, an independent battery reviewer. This is more of a theoretical analysis and explanation about the theories behind them, using technical handbooks as the sources.

[https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ Ryobi Battery Repair Guide]. Written by Badar Jahangir Kayani, an electrical engineer. This is more of a practical take of reconditioning "bricked" battery packs. He consider <1V per cell (<5V per pack) as deep discharged and not safe to use. Despite that, he managed to recover them (for testing, not for actual usage). According to "Gathering Data" section of his video, the Permanent Firmware Lockout occurs at a voltage as high as 2.82V, way higher than the safety cutout voltage and may be even higher than discharge cut-off voltage. It's a solid evidence that Ryobi did the malicious "fragile ego" on their BMS.

=== Comments ===

==== Why focusing on discharge voltage? ====
Because partial knowledge can be as misleading as zero knowledge.

When a li-ion battery is deeply overcharged, safety risk is imminent as the excessive energy has to go somewhere immediately. When it's deeply overdischarged, the safety risk is lower since there's little, if any, energy in the battery. That's the reason the unsafe high voltage is only slightly higher than the maximum charge voltage but the unsafe low voltage is significantly lower than the minimum discharge voltage. Misinformed users are sometimes convinced that overdischarging is as dangerous as overcharging.

The difference between discharge cut-off voltage safety cutout voltage must be explained clearly. Some people confuse these two and justifying cutting off charging when the voltage is at or only slightly blow the discharge cut-off voltage. This is made worse by anti-consumer manufacturers "stirring the water". [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 17:11, 17 September 2025 (UTC)

Talk:Battery firmware lockout

2025-09-17T17:11:00Z

Charlie 6: /* On Battery Safety and the Justification of Lockout */ new section

== On Texas Instruments BQ-series BMS ==

This type of BMSes is the most common type used on laptop computers.

Unlike the BMS in power tools that you can dump the firmware, the Texas Instruments BQ series BMS has something like "a chip within a chip", similar to Intel Management Engine or fTPM.

I learned from some friends who worked with power electronics. The BQ series needs password to access the internal memory. Unfortunately, the "Permanent Fail" is gated the same "height" of the "wall" as flashing firmware. If you know the password you can read and even write (both official and custom) firmware, if you don't know the password you can't even clear the PF error code.

The BMS sends the battery's current status like the voltage, current, temperature, cycle count and the limitations like charge max voltage/current, discharge min voltage/max current, etc, to the device. It's know that some computer models use different battery packs, the EC supplies the correct voltage and current to the battery because the BMS tells these values to the EC. These messages are not encrypted and are read by embedded controller (EC) on the computer's motherboard.

Thus, we can technically build our own FOSS BMS using the same way of communication with the EC, without any "lockout" logic, or we can just buy a BQ chip from TI, use the official firmware but without setting a custom password. If the "community driven" custom BMS gains traction and reaches mass production, we can solve the "battery firmware lockout" once and for all.

The reason why few people talk about it, I think, is the "baseline" reliability difference. The reliability of a product depends on the least reliable part, so laptop batteries have to be very reliable. As a result, they don't fail randomly. Given the high quality standard, non-OEM battery manufacturers and independent repair technicians can rarely reach the reliability standard of the original ones. Therefore there's low incentive for those people to find a reliable way of unbricking the BMS. [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 13:13, 17 September 2025 (UTC)

== On Battery Safety and the Justification of Lockout ==

There are many online misinformation about the safety of Li-ion batteries, both in discussion threads and video comments. Some of these comments are trying to justify the lockout by saying the exaggerated values/criteria, such as saying it's not safe to charge below 2.5V to 2.8V when the actual values are between 1.5V to 2.0V.

Conclusion first, in case technical details are too long to read.

== Conclusion ==

=== Non malicious ===
Low voltage cutout(according to the specification): Disable discharging when the voltage is too low or the battery is too unbalanced. If the voltage is too low (<2.5V) wear will increase and performance will degrade faster, but the battery is still safe to use.

Unsafe voltage cutout: Disable charging if the voltage is way too low (<1.5V), as chemical decomposition could occur causing the battery to be less safe (can be tested, see reconditioning section).

=== Malicious ===
"Fragile ego": The disable voltage is way higher than the overdischarged unsafe voltage, wasting good batteries.

No balancing circuit: Faster degradation.

Password: preventing reconditioning/refurbishment.

Timer: Brick after X days or discharge cycles regardless of battery health, which is planned obsolescence.

== Reconditioning ==
The voltages written in this section are a '''open circuit voltage''' i.e the measured voltage when neither charging nor discharging. This is only a general guideline, the actual voltage may be higher or lower depends on the battery chemistry.

=== Disclaimer ===
Troubleshooting Li-ion batteries can be dangerous, this section is for informational purposes only. You are responsible for your own safety. Always wear appropriate protection and consult the specification of the equipment carefully.

=== 2.5V or above ===
charge normally.

=== 2.0V<voltage<2.5V ===
Charge slowly (<0.1C), resume normal charging speed above 3.0V, then do a charge/discharge cycle normally and measure the capacity, if normal continue to use, if lower replace it with a matched sell or put this cell to another pack with worn cells to match them.

=== 1.0V<voltage<2.0V ===
Charge very slowly (<0.05C). Observe the voltage and temperature carefully. If voltage fails to rise or temperature rises rapidly, chemical decomposition has occurred, do not use. When the voltage reaches nominal (around 3.7V), stop charging and wait for several hours, if the voltage is gone do not use, if not, proceed to normal charging. Do a charge/discharge cycle normally and measure the capacity. If capacity is way lower or internal resistance is way higher than before, do not use.

=== <1.0V ===
Replace the cells. It may be possible to revive it, but massive performance loss and additional safety risk is almost guaranteed. Don't even bother.

=== Unbalanced ===
Charge the lower(est) cell(s) to the voltage of other cells and perform a cycle. Observe the voltage of each cell, replace the ones with much higher/lower during charging/discharging.

== Interpreting the specifications ==
There are many values (voltage, current, temperature) on the datasheet of the battery cells and the packs that are made of these cells. For discussing firmware lockout, we mostly focus on two values: discharge cut-off voltage and safety cutout voltage.

=== Discharge cut-off voltage ===
This voltage is a '''loaded voltage''' i.e measured during discharging. It is when the current should be turned off during discharging. Since batteries have internal resistance, this voltage is not the "0% charge" voltage. Assume discharging to 2.5V, the voltage will climb to 3.0V or even 3.3V after removing the current.

The discharge cut-off voltage is highly related to cycle life. The battery's rated cycle life is measured by charging and discharging repeatedly at predetermined voltage, current and temperature.

Discharging to a higher voltage doesn't use up the full capacity of the battery but the actual life will increase. Discharging to a lower voltage gives very little gain at the cost of significant wear. Thus, the discharge cut-off voltage specification is determined with a balance of cycle life and discharge capacity.

=== Safety cutout voltage ===
Commonly referred as "Do not charge" voltage, this voltage is where chemical decomposition occurs and it's no longer safe to charge due to elevated risks.

This is an '''open circuit voltage'''. If you somehow discharge the battery to this voltage but it bounced back to above discharge cut-off voltage after switching off the device, it's still safe to use, but don't do this intentionally, the gain is not worth the cost. If it bounces back to between these two voltages, see below.

The voltage between the safety cutout voltage and discharge cut-off voltage is the "pre-charge" range, where a very low charging current is applied to safely bring the battery pack back to normal.

A common "self destructive design" is to program the BMS "Permanent Fail" low voltage to way higher than the battery's safety cutout voltage. If the voltage is set to as high as the discharge cut-off voltage, the battery may brick itself if a large instantaneous load is applied(common on power tools) while the battery is at low charge.

=== Zero voltage ===
If the battery pack is discharged even momentarily after one cell has reached zero voltage, internal short circuit will occur within that cell due to reverse polarity. The cell will be destroyed immediately and permanently, without any chance of recovery.

== Sources ==
[https://lygte-info.dk/info/BatteryLowVoltage%20UK.html How far can LiIon be discharged?] Written by Henrik K. Jensen, an independent battery reviewer. This is more of a theoretical analysis and explanation about the theories behind them, using technical handbooks as the sources.

[https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ Ryobi Battery Repair Guide]. Written by Badar Jahangir Kayani, an electrical engineer. This is more of a practical take of reconditioning "bricked" battery packs. He consider <1V per cell (<5V per pack) as deep discharged and not safe to use. Despite that, he managed to recover them (for testing, not for actual usage). According to "Gathering Data" section of his video, the Permanent Firmware Lockout occurs at a voltage as high as 2.82V, way higher than the safety cutout voltage and may be even higher than discharge cut-off voltage. It's a solid evidence that Ryobi did the malicious "fragile ego" on their BMS.

== Comments ==

=== Why focusing on discharge voltage? ===
Because partial knowledge can be as misleading as zero knowledge.

When a li-ion battery is deeply overcharged, safety risk is imminent as the excessive energy has to go somewhere immediately. When it's deeply overdischarged, the safety risk is lower since there's little, if any, energy in the battery. That's the reason the unsafe high voltage is only slightly higher than the maximum charge voltage but the unsafe low voltage is significantly lower than the minimum discharge voltage. Misinformed users are sometimes convinced that overdischarging is as dangerous as overcharging.

The difference between discharge cut-off voltage safety cutout voltage must be explained clearly. Some people confuse these two and justifying cutting off charging when the voltage is at or only slightly blow the discharge cut-off voltage. This is made worse by anti-consumer manufacturers "stirring the water". [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 17:11, 17 September 2025 (UTC)

Talk:Battery firmware lockout

2025-09-17T13:13:46Z

Charlie 6: /* On Texas Instruments BQ-series BMS */ new section

Battery Health Assistance

2025-09-16T05:05:23Z

Charlie 6: /* Battery Performance issues */ added yet another source of explaining the "removing a second portion of the battery"

Battery Health Assistance is an anti-feature by Google, used on Google Pixel Smartphones since Pixel 6a and later. While on some models it can be turned off. For Pixel 9a and Pixel 10 series, it can't be turned off.

Google claims Battery Health Assistance is to "stabilize performance and aging". Critics point out the forced nature and performance degradation over time can be considered planned obsolescence. Users report worse, not better, battery health measured on both Android 16 and third-party software, contrary to Google's claim.

==Background==

===Pixel 4a Battery Performance Program<ref>{{Cite web |date=6 Jan 2025 |title=Pixel 4a Battery Performance Program |url=https://support.google.com/pixelphone/answer/15701861 |url-status=deviated |archive-url=https://web.archive.org/web/20250107002112/https://support.google.com/pixelphone/answer/15701861 |archive-date=7 Jan 2025 |access-date=25 Mar 2025 |website=[[Google]]}}</ref>===
{{Main|Pixel 4a Battery Performance Program}}
Google is known for reducing the charging voltage of Pixel 4a from 4.4V to 3.95V via a software update, resulting in a 44% drop in theoretical usable charge.<ref name=":2">{{Cite web |last=Wojciechowska |first=Kamila |date=5 Feb 2025 |title=There is even more to the Google Pixel 4a's horrific battery update than we thought |url=https://www.androidauthority.com/pixel-4a-battery-update-explained-3522417/ |url-status=live |access-date=4 Apr 2025 |website=AndroidAuthority}}</ref> Pixel 4a users report much higher real-world runtime loss.

===Pixel 9a===
The [[Google Pixel|'''Google Pixel''']] 9a is an Android smartphone designed, developed and marketed by [[Google]]. The release date was April 10 in US, Canada and UK.<ref name=":0">{{Cite web |last=Brecher |first=Hannes |last2=Fisher |first2=Jacob |date=2 Apr 2025 |title=Google Pixel 9a comes with new feature that weakens the battery after just 200 charging cycles |url=https://www.notebookcheck.net/Google-Pixel-9a-comes-with-new-feature-that-weakens-the-battery-after-just-200-charging-cycles.991310.0.html |url-status=live |access-date=2 Apr 2025 |website=Notebookcheck}}</ref> On March 31, 2025, Google announced its Battery Health Assistance<ref name=":1">{{Cite web |date=1 Apr 2025 |title=Understand your Pixel battery |url=https://support.google.com/pixelphone/answer/15738128 |url-status=live |archive-url=https://web.archive.org/web/20250704165953/https://support.google.com/pixelphone/answer/15738128 |archive-date=4 Jul 2025 |access-date=4 Apr 2025 |website=[[Google]]}}</ref> to users:<blockquote>For Pixel 9a:

Lithium-ion batteries are consumable components that eventually require replacement. Your Pixel 9a will receive a '''software update''' that automatically helps manage the long term health and performance of its battery as it ages. This software will '''adjust the battery’s maximum voltage''' in stages that start at 200 charge cycles and continue gradually until 1000 charge cycles to help stabilize battery performance and aging.

You may notice small decreases in your battery’s runtime as your battery ages. Battery health assistance will also '''tune the phone’s charging speed''' based '''on adjusted capacity'''. You may notice a slight change in battery charging performance. Battery health assistance settings on Pixel 9a '''aren’t customizable by the user.'''</blockquote>

Google claimed that this Battery Health Assistance will be voluntary for previously launched devices.<ref>{{Cite web |last=Li |first=Abner |date=31 Mar 2025 |title=Google Pixel adding ‘Battery health assistance’ for long-term use, starting with Pixel 9a |url=https://9to5google.com/2025/03/31/pixel-battery-health-assistance/ |url-status=live |access-date=4 Apr 2025 |website=9to5Google}}</ref> . It's confirmed that Battery Health Assistance cannot be turned off on Pixel 10 series<ref name=":5">{{Cite web |last=Simons |first=Hadlee |date=20 Aug 2025 |title=Google will throttle your Pixel 10's battery, and there's nothing you can do about it |url=https://www.androidauthority.com/google-pixel-10-battery-health-assistance-3585863/ |url-status=live |archive-url=https://web.archive.org/web/20250823225719/https://www.androidauthority.com/google-pixel-10-battery-health-assistance-3585863/ |archive-date=23 Aug 2025 |access-date=23 Aug 2025 |website=AndroidAuthority}}</ref>.

In July 2, 2025, an APK teardown of Google’s Settings Services app version v1.1.0771997146 hints that Battery Health Assistance may no longer be optional on other models if battery health drops below a certain point. It's not confirmed whether this change is final and no official announcement has been made by Google<ref>{{Cite web |last=Thomas |first=Chris |date=2 Jul 2025 |title=Google could force more Pixels to throttle charging and capacity as they age |url=https://www.androidpolice.com/battery-health-assistance-pixel-phones-mandatory/ |url-status=live |archive-url=https://web.archive.org/web/20250703034710/https://www.androidpolice.com/battery-health-assistance-pixel-phones-mandatory/ |archive-date=3 Jul 2025 |access-date=3 Jul 2025 |website=Android Police}}</ref><ref>{{Cite web |last=Siddiqui |first=Aamir |date=2 Jul 2025 |title=Mandatory battery throttling is coming for more Pixels with poor battery health (APK teardown) |url=https://www.androidauthority.com/pixel-battery-health-assistance-mandatory-apk-teardown-3573263/ |url-status=live |archive-url=https://web.archive.org/web/20250703035344/https://www.androidauthority.com/pixel-battery-health-assistance-mandatory-apk-teardown-3573263/ |archive-date=3 Jul 2025 |access-date=3 Jul 2025 |website=Android Authority}}</ref>.
==Potential effects of software update==
Google has not provided detailed technical explanations for the update. The adjusted battery's maximum voltage and charging speed are yet to be disclosed.

===Battery Performance issues===
Charging the battery at a lower voltage will not fully charge it. A partly charged battery exhibit shorter runtime. Lowering the charging voltage by 0.1V lowers the capacity by about 10%.<ref name=":3">{{Cite web |date=25 Oct 2021 |title=BU-409: Charging Lithium-ion |url=https://batteryuniversity.com/article/bu-409-charging-lithium-ion |url-status=live |access-date=4 Apr 2025 |website=Battery University}}</ref> Charging the battery at a lower current will increase the charging time.

Google claimed that on Pixel 8a and later, the battery "should retain up to 80% capacity for about 1000 charge cycles".<ref name=":1" /> However, Google also said that "your battery’s actual lifespan depends on usage patterns and other factors".<ref name=":1" /> The "Battery Health Assistance", being a "factor", potentially causing battery lifespan to be considerably worse than advertised after the first thousand charging cycles.

====Analysis====

*Charging the battery in shorter capacity periods leads to less runtime.<ref name=":2" /><ref name=":3" />
*Charging the battery at lower percentages slows down battery aging.<ref name=":4" />

Both factors lead to two possible outcomes that need to be differentiated very clearly to prevent misunderstanding, improve battery usage and identify anti-consumer practices:

*When the user recharges the battery to a lower percentage frequently (only charging to 100% when necessary), the battery is aged less, which ultimately result in better battery health and longer runtime should the user need 100% capacity, compared to always fully charging.
*The manufacturer blocked part of the available capacity ''after'' a certain amount of charging cycles. Meaning that after the user has degraded a certain amount of the battery, the manufacturer artificially limits its capabilities by further removing a second portion of the battery<ref>{{Cite web |last=Bonggolto |first=Jay |date=25 Aug 2025 |title=The Pixel 10’s battery takes a hit after 200 cycles, courtesy of a feature you can’t switch off |url=https://www.androidcentral.com/phones/google-pixel/the-pixel-10s-battery-takes-a-hit-after-200-cycles-courtesy-of-a-feature-you-cant-switch-off |url-status=live |archive-url=https://web.archive.org/web/20250827074849/https://www.androidcentral.com/phones/google-pixel/the-pixel-10s-battery-takes-a-hit-after-200-cycles-courtesy-of-a-feature-you-cant-switch-off |archive-date=27 Aug 2025 |access-date=16 Sep 2025 |website=Android Central}}</ref>. In other words, Battery Health Assistance feature essentially reduces the phone’s battery capacity over and above standard degradation<ref name=":5" />.

==Possible technical rationale==

===Prolonging battery life===
Charging the battery at a lower percentage slows down battery degradation,<ref name=":4">Xu, Bolun & Oudalov, Alexandre & Ulbig, Andreas & Andersson, Göran. (2016). Modeling of Lithium-Ion Battery Degradation for Cell Life Assessment. IEEE Transactions on Smart Grid. 99. 1-1. 10.1109/TSG.2016.2578950. </ref> However, there are some key differences between "Charging Optimization" and the future "Battery Health Assistance":

'''Charging Optimization''' has two options, Adaptive Charging and Limit to 80%.<ref>{{Cite web |title=Get the most life from your Pixel phone battery |url=https://support.google.com/pixelphone/answer/6090612 |url-status=live |access-date=4 Apr 2025 |website=Pixel Phone Help}}</ref> Adaptive Charging can prolong the life of the battery by fully charging it just before the user unplugs, reducing the time spend at high charge levels. The user can select Limit to 80% option to help extend the lifespan of the battery with a drawback of a reduced runtime. The smart phone can always resume maximum available capacity should the user deselect the limit and charge it to 100%. Pixel users can '''enable and disable the feature at will'''.

'''Battery Health Assistance''' lowers the battery's maximum voltage and charging current in stages, from 200 cycles to 1000 cycles.<ref name=":1" /> This is irreversible as the '''only way to use the full voltage of the battery again is to replace the battery itself.'''<ref name=":0" /> This reduces runtime further as '''only part of the remaining battery capacity is available''', arguably defeating the purpose of preserving battery health.

===Safety consideration===
Concerns arise over the delayed launch date of Pixel 9a over an "an unnamed component issue", suspecting that the issue could be the battery.<ref>{{Cite web |last=Mundy |first=Jon |date=20 Mar 2025 |title=Pixel 9a flaw uncovered before it even hits shops |url=https://www.techadvisor.com/article/2643405/google-pixel-9a-delayed-due-to-component-issue.html |url-status=live |access-date=4 Apr 2025 |website=Tech Advisor}}</ref><ref>{{Cite web |last=Simons |first=Hadlee |date=11 Jun 2025 |title=The latest Android 16 beta now lets you throttle your Pixel's battery, charging |url=https://www.androidauthority.com/android-16-qpr1-beta-2-battery-health-assistance-3566396/ |url-status=live}}</ref> If the battery of the Pixel 9a is found to be defective, it might no longer be safe to charge at full voltage after 200 cycles.

{{Main|Google Pixel 6a Battery Performance Program}}

In June 11 2025, Google confirms a Pixel 6a update will reduce capacity in response of multiple devices catching fire<ref>{{Cite web |last=Rahman |first=Mishaal |date=11 Jun 2025 |title=Warning: Google will soon nerf the Pixel 6a’s battery due to an overheating issue |url=https://www.androidauthority.com/pixel-6a-battery-overheating-warning-3566640/ |url-status=live |archive-url=https://web.archive.org/web/20250613135314/https://www.androidauthority.com/pixel-6a-battery-overheating-warning-3566640/ |archive-date=13 Jun 2025 |access-date=16 Jun 2025 |website=Android Authority}}</ref>. This update will show a warning label when cycle count reaches 375 and reduce the charging voltage after 400 cycles.

==Consumer reaction==

Current and former Pixel users condemn this program and compared it with Apple's "Batterygate" and the Pixel 4a Battery Performance Program, saying that Battery Health Assistance is "worse", a "fancy name for planned obsolescence"<ref>{{Cite web |title=This is worse than Apple |url=https://old.reddit.com/r/GooglePixel/comments/1jp883q/google_will_gradually_reduce_pixel_9a_battery/ml6m0y7/?context=3 |url-status=live |archive-url=https://web.archive.org/web/20250405011000/https://old.reddit.com/r/GooglePixel/comments/1jp883q/google_will_gradually_reduce_pixel_9a_battery/ml6m0y7/?context=3 |archive-date=5 Apr 2025 |access-date=5 Apr 2025 |website=[[Reddit]]}}</ref><ref>{{Cite web |date=16 Apr 2025 |title=Pixel reducing battery capacity after 200 charge cycles |url=https://old.reddit.com/r/GooglePixel/comments/1k0r54v/pixel_reducing_battery_capacity_after_200_charge/ |url-status=live |archive-url=https://web.archive.org/web/20250616031438/https://old.reddit.com/r/GooglePixel/comments/1k0r54v/pixel_reducing_battery_capacity_after_200_charge/ |archive-date=16 Jun 2025 |access-date=16 Jun 2025 |website=[[Reddit]]}}</ref>. and the Pixel 4a incident is a "preview"<ref>{{Cite web |date=2 Apr 2025 |title=Pixel 9a will have battery "optimised" after 200 cycles |url=https://www.reddit.com/r/Pixel4a/comments/1jpk1db/pixel_9a_will_have_battery_optimised_after_200/ |url-status=live |access-date=3 Apr 2025 |website=[[Reddit]]}}</ref>

Users also find the wording of the support article on Google's website vague and lack of self-consistency,<ref>{{Cite web |date=1 Apr 2024 |title=So they want to reduce the wear out of the battery by... doing exactly the same? What's logic behind this? |url=https://www.reddit.com/r/GooglePixel/comments/1jp883q/comment/mkzu6lc/ |url-status=dead |access-date=2 Apr 2025 |website=[[Reddit]]}}</ref> saying the Google will "cause the thing they are supposedly trying to prevent"<ref>{{Cite web |date=2 Apr 2025 |title=Deliberate weakening after only 200 charging cycles: Google Pixel 9a limits battery voltage according to a planned schedule |url=https://www.notebookchat.com/index.php?topic=225600.msg645716#msg645716 |url-status=live |access-date=5 Apr 2025 |website=NotebookCHECK - Notebook Forum}}</ref>, forcing the user to replace the phone sooner that what would "naturally" happen<ref name=":6" />.

Users report shorter runtime<ref>{{Cite web |date=14 Jun 2025 |title=Absolutely disappointed with Google and their latest updates including A16 |url=https://old.reddit.com/r/GooglePixel/comments/1lb4i26/absolutely_disappointed_with_google_and_their/ |url-status=live |archive-url=https://web.archive.org/web/20250616034347/https://old.reddit.com/r/GooglePixel/comments/1lb4i26/absolutely_disappointed_with_google_and_their/ |archive-date=16 Jun 2025 |access-date=16 Jun 2025 |website=[[Reddit]]}}</ref>, slower charging speed<ref>{{Cite web |date=13 Jun 2025 |title=Did you notice that Battery optimization feature is the one that is forced on P9a? |url=https://old.reddit.com/r/pixel_phones/comments/1laiiok/did_you_notice_that_battery_optimization_feature/ |url-status=live |archive-url=https://web.archive.org/web/20250616040147/https://old.reddit.com/r/pixel_phones/comments/1laiiok/did_you_notice_that_battery_optimization_feature/ |archive-date=16 Jun 2025 |access-date=16 Jun 2025 |website=[[Reddit]]}}</ref> and lower battery health<ref>{{Cite web |date=14 Jun 2025 |title=Is this how Battery Health function of A16 works ? |url=https://old.reddit.com/r/pixel_phones/comments/1lb38ll/is_this_how_battery_health_function_of_a16_works/ |url-status=live |archive-url=https://web.archive.org/web/20250616040252/https://old.reddit.com/r/pixel_phones/comments/1lb38ll/is_this_how_battery_health_function_of_a16_works/ |archive-date=16 Jun 2025 |access-date=16 Jun 2025 |website=[[Reddit]]}}</ref> after updating to Android 16. The "slight" change in battery charging performance is much more significant. The battery health can be increased back to pre-update condition by switching off Battery Health Assistance.

There's an ongoing discussion of whether using a custom ROM like Graphene OS can bypass Battery Health Assistance, which depends on whether this anti-feature works on software or firmware level. If Battery Health Assistance is baked into the firmware of Pixel 10 and later, a custom ROM will not work<ref name=":6">{{Cite web |date=22 Aug 2025 |title=Google will throttle your Pixel 10's battery, and there's nothing you can do about it |url=https://old.reddit.com/r/GrapheneOS/comments/1mxgmq9/google_will_throttle_your_pixel_10s_battery_and/ |url-status=live |archive-url=https://web.archive.org/web/20250907084717/https://old.reddit.com/r/GrapheneOS/comments/1mxgmq9/google_will_throttle_your_pixel_10s_battery_and/ |archive-date=7 Sep 2025 |access-date=7 Sep 2025 |website=[[Reddit]]}}</ref>.

==References==
{{reflist}}
[[Category:Google Pixel 9a]]

Battery firmware lockout

2025-09-15T07:55:07Z

Charlie 6: /* Power tools */ slight edit of unbricking Ryobi batteries by Badar

Most devices with rechargeable batteries has a [[wikipedia:Battery_management_system|battery management system (BMS)]] module. This module monitors and regulate key variables and capable of communicating with the device and preventing unsafe usage that could cause failure. However, many of them contains proprietary code that locks the battery from operation, "bricking" it and prevent the battery from third-party repair. Effectively making the whole device that depends on said battery unusable.

==How it works==
When the battery is outside its operating range, such as overcharged, overcharged, overheated, unbalanced(in multi-celled battery packs), the BMS prevents the battery from further usage, limiting damage. However, the BMS should resume normal operation when the battery is back within operating range. Instead, the BMS changes bytes in its memory, leading to a "Permanent Fail (PF)" state, preventing the use of said battery even after reconditioning or repairing.

Documentations from known BMS manufacturers such as Texas Instruments said the device can permanently disable the use of the battery pack in case of a "severe failure"<ref>[https://www.ti.com/lit/ug/sluua43a/sluua43a.pdf? https://www.ti.com/lit/ug/sluua43a/sluua43a.pdf?]</ref>. However users report the battery is "bricked" after scenarios like long-term storage, discharging laptop overnight or use a power tool in warm environment while charging it cool, indicating the manufacturers have abused the BMS program, exaggerating the nature of the failure as a from of [[self-destructive design]].

To make matters worse, many of the BMS needs "access code" to read and change it's parameters, including runtime ones like the "Permanent Fail" flag. The unlock or unseal code is kept secret by the battery's manufacturer, making user and third-parties very difficult, if not impossible, to repair said battery<ref>{{Cite web |date=28 Sep 2019 |title=Experiences with TI BQ management IC’s when re-building laptop batteries? |url=https://www.eevblog.com/forum/chat/experiences-with-ti-bq-management-ics-when-revelling-laptop-batteries/?all |url-status=live |archive-url=https://web.archive.org/web/20240926193741/https://www.eevblog.com/forum/chat/experiences-with-ti-bq-management-ics-when-revelling-laptop-batteries/?all |archive-date=26 Sep 2024 |access-date=13 Sep 2025 |website=EEVblog Electronics Community Forum}}</ref>.

Alarmingly, the condition of "bricking" includes "Capacity Degradation Permanent Failure"<ref>[https://www.ti.com/lit/ds/symlink/bq40z50.pdf? https://www.ti.com/lit/ds/symlink/bq40z50.pdf?]</ref>, which means the manufacturers can artificially limit the battery pack's lifespan, making it unusable after a certain health (e.g 80%).

==Why it is a problem==

===Increased repair cost===
When the battery is bricked, most users would buy an entire battery pack, increasing the total cost of ownership. The "access code" lock prevents third-parties from replacing individual cells and refurbishing the battery pack, reducing its lifespan.

===Environmental impact===
Lithium-ion batteries are 95% recyclable, however, only about 5% of them are actually recycled<ref>{{Cite web |date=22 Sep 2022 |title=Lithium ion battery recycling |url=https://www.cas.org/resources/cas-insights/lithium-ion-battery-recycling?utm_source=chatgpt.com |url-status=live}}</ref>. BMS firmware lockout increases the number of battery packs end up in waste, increasing pollution. Some of the materials like cobalt, are hazardous.

===Undermining ownership===
When the purchase is complete. The ownership is transferred to the user of the device. Locking out the battery after purchase is akin to installing a lock on someone else's property, and should be considered "Digital Handcuffs"<ref>{{Cite web |title=Words to Avoid (or Use with Care) Because They Are Loaded or Confusing |url=https://www.gnu.org/philosophy/words-to-avoid.html |url-status=live |archive-url=https://web.archive.org/web/20250909175856/https://www.gnu.org/philosophy/words-to-avoid.html |archive-date=2025-09-09 |access-date=2025-09-13 |website=GNU Operating System}}</ref>.

==Examples==

===Consumer electronics===
[[File:BQ40Z50R3 1.jpg|thumb|A screenshot of a "bricked" battery pack with healthy cells, note the red "PF_EN"]]
The most common consumer electronics using sophisticated battery management system for their multi-cell battery pack are laptop computers. There are many discussions about the battery "lockout" after replacing or recharging individual cells, indicating battery firmware lockout is the main obstacle of battery repair<ref>{{Cite web |date=2022-10-06 |title=How can I reset the laptop battery BMS? |url=https://electronics.stackexchange.com/questions/570919/how-can-i-reset-the-laptop-battery-bms |url-status=live |archive-url=https://web.archive.org/web/20250913130751/https://electronics.stackexchange.com/questions/570919/how-can-i-reset-the-laptop-battery-bms |archive-date=2025-09-13 |access-date=2025-09-13 |website=Stack Exchange}}</ref><ref>{{Cite web |date=30 Oct 2023 |title=(i changed every cell in laptop battery then bms locked How to unlock bms of acer e5 laptop battery, total battery in series is 15v but in bms output voltage is 0v i tried to short battery positive to output positive, but still no output, i think bms is locked how to unlock without software help |url=https://old.reddit.com/r/batteries/comments/17jogjr/i_changed_every_cell_in_laptop_battery_then_bms/ |url-status=live |archive-url=https://web.archive.org/web/20250913133735/https://old.reddit.com/r/batteries/comments/17jogjr/i_changed_every_cell_in_laptop_battery_then_bms/ |archive-date=13 Sep 2025 |access-date=13 Sep 2025 |website=[[Reddit]]}}</ref>.

===Commercial UAVs===
{{Main|DJI}}
DJI, a well known commercial UAV manufacturer, locks out the battery after long-term storage, claiming over-discharging damages the battery, even if the chemistry is still recoverable. Users who successfully "revives" the battery packs by charging their cells using a bench power supply and clearing the failure code, reports restored functionality<ref>{{Cite web |date=2024-03-21 |title=Reviving dead batteries - a heads up |url=https://mavicpilots.com/threads/reviving-dead-batteries-a-heads-up.146169/ |url-status=live |archive-url=https://web.archive.org/web/20250618000130/https://mavicpilots.com/threads/reviving-dead-batteries-a-heads-up.146169/ |archive-date=2025-06-18 |access-date=2025-09-13 |website=MavicPilots}}</ref><ref>{{Cite web |date=2023-08-02 |title=DJI Battery Killer repairing tool |url=https://greyarro.ws/t/dji-battery-killer-repairing-tool/68863 |url-status=live |access-date=2025-09-13 |website=Grey Arrows Drone Club}}</ref><ref>{{Cite web |last=McLoughlin |first=Liam |date=2023-10-01 |title=Repairing the DJI Spark Drone Battery with DJI Battery Killer, CP2112, & 9V battery |url=https://leelum.com/projects/repairing-the-dji-spark-drone-battery-with-dji-battery-killer-cp2112-9v-battery/ |url-status=live |archive-url=https://web.archive.org/web/20241211065622/https://leelum.com/projects/repairing-the-dji-spark-drone-battery-with-dji-battery-killer-cp2112-9v-battery/ |archive-date=2024-12-11 |access-date=2025-09-13 |website=Leelum}}</ref><ref>{{Cite web |title=DJI Battery Killer: Reviving Bricked DJI Drone Batteries with CP2112 & BMS Reset |url=https://www.elektroda.com/qa,dji-battery-killer-cp2112-bms-reset.html |url-status=live |website=elektroda}}</ref>. However some users reported "authentication failed"<ref>{{Cite web |date=2024-03-23 |title=Mavic pro battery authentication failed after clear pf |url=https://mavicpilots.com/threads/mavic-pro-battery-authentication-failed-after-clear-pf.144987/ |url-status=live |access-date=2025-09-13 |website=MavicPilots}}</ref> suggesting the possibility of parts serialization<ref>{{Cite web |last=Greenlee |first=Lauren |date=2023-01-17 |title=How Parts Pairing Kills Independent Repair |url=https://www.ifixit.com/News/69320/how-parts-pairing-kills-independent-repair |url-status=live |archive-url=https://web.archive.org/web/20250811033531/https://www.ifixit.com/News/69320/how-parts-pairing-kills-independent-repair |archive-date=2025-08-11 |access-date=2025-09-13 |website=iFixit}}</ref>.

===Home appliances===
{{Main|Dyson battery lifespan reduced by design and difficult to repair}}
Dyson appliances often come with battery packs omitting balancing resistors, leading to higher battery degradation. When the battery cells are unbalanced, repaired or replaced. The BMS chip will lockout. This can be mitigated with added resistors and a custom firmware that doesn't brick the battery upon maintenance<ref name=":2">{{Cite web |last=@tinfever |title=(Unofficial) Firmware Upgrade for Dyson V6/V7 Vacuum Battery Management System |url=https://github.com/tinfever/FW-Dyson-BMS |url-status=live |archive-url=https://web.archive.org/web/20250912021607/https://github.com/tinfever/FW-Dyson-BMS |archive-date=2025-09-12 |access-date=25 Mar 2025 |website=GitHub}}</ref>.

===Power tools===
{{Main|Milwaukee battery drm}}
Power tool manufacturers such as Ryobi and Makita are known to lock battery backs, causing good ones to fail and ended up in repair centers, or worse, landfills. Badar, a known electrical engineer, managed to recover 30 "bricked" battery pack back to normal, reducing e-waste<ref>https://www.youtube.com/watch?v=NQ_lyDyzEHY</ref>. Although 19% of them deeply discharged were no longer safe to charge. 65% of bricked batteries were purely due to software lockout with no performance impact after unbricking and recharging. Additionally, 13% had unbalanced cell, which were easily resolved by using an external power supply to bring the cells to the same level one by one, however, "unbricking" procedure is still required for normal use<ref>{{Cite web |last=Kayani |first=Badar Jahangir |date=2025-08-24 |title=Ryobi Battery Repair Guide |url=https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ |url-status=live |archive-url=https://web.archive.org/web/20250915074416/https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ |archive-date=2025-09-15 |access-date=2025-09-15 |website=Badar Jahangir Kayani}}</ref>.

===Electric vehicles===
Tesla cuts the range of some Model S and Model X by up to 20% by an OTA update. Some of the batteries became totally unusable, showing a "BMS_u029" error. Some users are able to reverse the change by flashing an older firmware, other users are forced to replace the entire battery pack, costing over $15,000<ref name=":0">{{Cite web |last=Crandall |first=Christine |date=2023-05-18 |title=How Tesla’s New OTA Software Update Cut EV Range By A Massive 20%, Owners Move To Sue |url=https://www.hotcars.com/tesla-software-update-cut-ev-range-owners-move-to-sue/ |archive-url=https://web.archive.org/web/20250413101832/https://www.hotcars.com/tesla-software-update-cut-ev-range-owners-move-to-sue/ |archive-date=2025-04-13 |access-date=2025-09-13 |website=Hotcars}}</ref>.

==Consumer reactions==
Although some consumers rationalize such behavior of increasing safety or avoiding liability. Many of them condemn such practices and describing it as planned obsolescence.

There are ways of tackling battery firmware lockout:

*Replacing the battery pack: This is the simplest way of "repairing" a "bricked" battery. However doing so is costly, increases e-waste production and further fuels planned obsolescence of said manufacturers.
*Extracting the BMS code: Certain logic analyzers can extract the code from communications to and from the BMS chip. Users or repair technicians can use this way to extract the "unseal" password, then reset the "permanent fail" flag and recalibrate the battery's capacity.
*Acquiring the unlock password: Some of the battery models' BMS code has been leaked, some of them are publicized<ref>{{Cite web |last=@davext |date=25 Jun 2024 |title=unbrick-dji |url=https://github.com/davext/unbrick-dji/blob/main/src/main.cpp |url-status=live |archive-url=https://web.archive.org/web/20250914163205/https://github.com/davext/unbrick-dji/blob/main/src/main.cpp |archive-date=14 Sep 2025 |access-date=14 Sep 2025 |website=[Github]}}</ref>. For others, it might be possible to purchase it in the grey market, however, there's a risk of scam as some of the passwords can be as expensive as the pack itself, and there's no guarantee of working.
*Resetting the BMS: Some specialized hardware and software can be used to clear the PF flag, reviving the battery without the need of knowing the battery's parameters. Most of the users won't modify the battery pack after repairing<ref>{{Cite web |date=2019-08-15 |title=Reset-BQ20xx |url=https://github.com/otofoto/Reset-BQ20xx |url-status=live |archive-url=https://web.archive.org/web/20220923061011/https://github.com/otofoto/Reset-BQ20xx |archive-date=2022-09-23 |access-date=2025-09-13 |website=[[Github]]}}</ref>.
*Install a custom (or OEM) BMS chip: Buying a brand new BMS chip and write own program. The main challenge is the knowledge of the working mechanism of the battery and its BMS. Different battery chemistries have different voltage and current characteristics, using the wrong data may cause incorrect capacity reading at best, or battery/device malfunction at worst.

==Lawsuits==
Four plaintiffs are suing Tesla over an automatic over-the-air (OTA) software update that they say reduced the driving range of their vehicles by 20 percent. Forced updates by Tesla may violate California's Computer Fraud and Abuse Act and the Unfair Competition Law<ref name=":0" />.

==References==
{{reflist}}

[[Category:Common terms]]

Battery firmware lockout

2025-09-15T07:53:45Z

Charlie 6: /* Power Tools */ added a main page and more details about Badar's unbricking Ryobi batteries

Most devices with rechargeable batteries has a [[wikipedia:Battery_management_system|battery management system (BMS)]] module. This module monitors and regulate key variables and capable of communicating with the device and preventing unsafe usage that could cause failure. However, many of them contains proprietary code that locks the battery from operation, "bricking" it and prevent the battery from third-party repair. Effectively making the whole device that depends on said battery unusable.

==How it works==
When the battery is outside its operating range, such as overcharged, overcharged, overheated, unbalanced(in multi-celled battery packs), the BMS prevents the battery from further usage, limiting damage. However, the BMS should resume normal operation when the battery is back within operating range. Instead, the BMS changes bytes in its memory, leading to a "Permanent Fail (PF)" state, preventing the use of said battery even after reconditioning or repairing.

Documentations from known BMS manufacturers such as Texas Instruments said the device can permanently disable the use of the battery pack in case of a "severe failure"<ref>[https://www.ti.com/lit/ug/sluua43a/sluua43a.pdf? https://www.ti.com/lit/ug/sluua43a/sluua43a.pdf?]</ref>. However users report the battery is "bricked" after scenarios like long-term storage, discharging laptop overnight or use a power tool in warm environment while charging it cool, indicating the manufacturers have abused the BMS program, exaggerating the nature of the failure as a from of [[self-destructive design]].

To make matters worse, many of the BMS needs "access code" to read and change it's parameters, including runtime ones like the "Permanent Fail" flag. The unlock or unseal code is kept secret by the battery's manufacturer, making user and third-parties very difficult, if not impossible, to repair said battery<ref>{{Cite web |date=28 Sep 2019 |title=Experiences with TI BQ management IC’s when re-building laptop batteries? |url=https://www.eevblog.com/forum/chat/experiences-with-ti-bq-management-ics-when-revelling-laptop-batteries/?all |url-status=live |archive-url=https://web.archive.org/web/20240926193741/https://www.eevblog.com/forum/chat/experiences-with-ti-bq-management-ics-when-revelling-laptop-batteries/?all |archive-date=26 Sep 2024 |access-date=13 Sep 2025 |website=EEVblog Electronics Community Forum}}</ref>.

Alarmingly, the condition of "bricking" includes "Capacity Degradation Permanent Failure"<ref>[https://www.ti.com/lit/ds/symlink/bq40z50.pdf? https://www.ti.com/lit/ds/symlink/bq40z50.pdf?]</ref>, which means the manufacturers can artificially limit the battery pack's lifespan, making it unusable after a certain health (e.g 80%).

==Why it is a problem==

===Increased repair cost===
When the battery is bricked, most users would buy an entire battery pack, increasing the total cost of ownership. The "access code" lock prevents third-parties from replacing individual cells and refurbishing the battery pack, reducing its lifespan.

===Environmental impact===
Lithium-ion batteries are 95% recyclable, however, only about 5% of them are actually recycled<ref>{{Cite web |date=22 Sep 2022 |title=Lithium ion battery recycling |url=https://www.cas.org/resources/cas-insights/lithium-ion-battery-recycling?utm_source=chatgpt.com |url-status=live}}</ref>. BMS firmware lockout increases the number of battery packs end up in waste, increasing pollution. Some of the materials like cobalt, are hazardous.

===Undermining ownership===
When the purchase is complete. The ownership is transferred to the user of the device. Locking out the battery after purchase is akin to installing a lock on someone else's property, and should be considered "Digital Handcuffs"<ref>{{Cite web |title=Words to Avoid (or Use with Care) Because They Are Loaded or Confusing |url=https://www.gnu.org/philosophy/words-to-avoid.html |url-status=live |archive-url=https://web.archive.org/web/20250909175856/https://www.gnu.org/philosophy/words-to-avoid.html |archive-date=2025-09-09 |access-date=2025-09-13 |website=GNU Operating System}}</ref>.

==Examples==

===Consumer electronics===
[[File:BQ40Z50R3 1.jpg|thumb|A screenshot of a "bricked" battery pack with healthy cells, note the red "PF_EN"]]
The most common consumer electronics using sophisticated battery management system for their multi-cell battery pack are laptop computers. There are many discussions about the battery "lockout" after replacing or recharging individual cells, indicating battery firmware lockout is the main obstacle of battery repair<ref>{{Cite web |date=2022-10-06 |title=How can I reset the laptop battery BMS? |url=https://electronics.stackexchange.com/questions/570919/how-can-i-reset-the-laptop-battery-bms |url-status=live |archive-url=https://web.archive.org/web/20250913130751/https://electronics.stackexchange.com/questions/570919/how-can-i-reset-the-laptop-battery-bms |archive-date=2025-09-13 |access-date=2025-09-13 |website=Stack Exchange}}</ref><ref>{{Cite web |date=30 Oct 2023 |title=(i changed every cell in laptop battery then bms locked How to unlock bms of acer e5 laptop battery, total battery in series is 15v but in bms output voltage is 0v i tried to short battery positive to output positive, but still no output, i think bms is locked how to unlock without software help |url=https://old.reddit.com/r/batteries/comments/17jogjr/i_changed_every_cell_in_laptop_battery_then_bms/ |url-status=live |archive-url=https://web.archive.org/web/20250913133735/https://old.reddit.com/r/batteries/comments/17jogjr/i_changed_every_cell_in_laptop_battery_then_bms/ |archive-date=13 Sep 2025 |access-date=13 Sep 2025 |website=[[Reddit]]}}</ref>.

===Commercial UAVs===
{{Main|DJI}}
DJI, a well known commercial UAV manufacturer, locks out the battery after long-term storage, claiming over-discharging damages the battery, even if the chemistry is still recoverable. Users who successfully "revives" the battery packs by charging their cells using a bench power supply and clearing the failure code, reports restored functionality<ref>{{Cite web |date=2024-03-21 |title=Reviving dead batteries - a heads up |url=https://mavicpilots.com/threads/reviving-dead-batteries-a-heads-up.146169/ |url-status=live |archive-url=https://web.archive.org/web/20250618000130/https://mavicpilots.com/threads/reviving-dead-batteries-a-heads-up.146169/ |archive-date=2025-06-18 |access-date=2025-09-13 |website=MavicPilots}}</ref><ref>{{Cite web |date=2023-08-02 |title=DJI Battery Killer repairing tool |url=https://greyarro.ws/t/dji-battery-killer-repairing-tool/68863 |url-status=live |access-date=2025-09-13 |website=Grey Arrows Drone Club}}</ref><ref>{{Cite web |last=McLoughlin |first=Liam |date=2023-10-01 |title=Repairing the DJI Spark Drone Battery with DJI Battery Killer, CP2112, & 9V battery |url=https://leelum.com/projects/repairing-the-dji-spark-drone-battery-with-dji-battery-killer-cp2112-9v-battery/ |url-status=live |archive-url=https://web.archive.org/web/20241211065622/https://leelum.com/projects/repairing-the-dji-spark-drone-battery-with-dji-battery-killer-cp2112-9v-battery/ |archive-date=2024-12-11 |access-date=2025-09-13 |website=Leelum}}</ref><ref>{{Cite web |title=DJI Battery Killer: Reviving Bricked DJI Drone Batteries with CP2112 & BMS Reset |url=https://www.elektroda.com/qa,dji-battery-killer-cp2112-bms-reset.html |url-status=live |website=elektroda}}</ref>. However some users reported "authentication failed"<ref>{{Cite web |date=2024-03-23 |title=Mavic pro battery authentication failed after clear pf |url=https://mavicpilots.com/threads/mavic-pro-battery-authentication-failed-after-clear-pf.144987/ |url-status=live |access-date=2025-09-13 |website=MavicPilots}}</ref> suggesting the possibility of parts serialization<ref>{{Cite web |last=Greenlee |first=Lauren |date=2023-01-17 |title=How Parts Pairing Kills Independent Repair |url=https://www.ifixit.com/News/69320/how-parts-pairing-kills-independent-repair |url-status=live |archive-url=https://web.archive.org/web/20250811033531/https://www.ifixit.com/News/69320/how-parts-pairing-kills-independent-repair |archive-date=2025-08-11 |access-date=2025-09-13 |website=iFixit}}</ref>.

===Home appliances===
{{Main|Dyson battery lifespan reduced by design and difficult to repair}}
Dyson appliances often come with battery packs omitting balancing resistors, leading to higher battery degradation. When the battery cells are unbalanced, repaired or replaced. The BMS chip will lockout. This can be mitigated with added resistors and a custom firmware that doesn't brick the battery upon maintenance<ref name=":2">{{Cite web |last=@tinfever |title=(Unofficial) Firmware Upgrade for Dyson V6/V7 Vacuum Battery Management System |url=https://github.com/tinfever/FW-Dyson-BMS |url-status=live |archive-url=https://web.archive.org/web/20250912021607/https://github.com/tinfever/FW-Dyson-BMS |archive-date=2025-09-12 |access-date=25 Mar 2025 |website=GitHub}}</ref>.

===Power tools===
{{Main|Milwaukee battery drm}}
Power tool manufacturers such as Ryobi and Makita are known to lock battery backs, causing good ones to fail and ended up in repair centers, or worse, landfills. Badar, a known repair technician, managed to recover 30 "bricked" battery pack back to normal, reducing e-waste<ref>https://www.youtube.com/watch?v=NQ_lyDyzEHY</ref>. Although 19% of them deeply discharged were no longer safe to charge. 65% of bricked batteries were purely due to software lockout with no performance impact after unbricking and recharging. Additionally, 13% had unbalanced cell, which were easily resolved by using an external power supply to bring the cells to the same level one by one, however, "unbricking" procedure is still required for normal use<ref>{{Cite web |last=Kayani |first=Badar Jahangir |date=2025-08-24 |title=Ryobi Battery Repair Guide |url=https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ |url-status=live |archive-url=https://web.archive.org/web/20250915074416/https://badar.tech/2025/08/24/ryobi-battery-repair-guide/ |archive-date=2025-09-15 |access-date=2025-09-15 |website=Badar Jahangir Kayani}}</ref>.

===Electric vehicles===
Tesla cuts the range of some Model S and Model X by up to 20% by an OTA update. Some of the batteries became totally unusable, showing a "BMS_u029" error. Some users are able to reverse the change by flashing an older firmware, other users are forced to replace the entire battery pack, costing over $15,000<ref name=":0">{{Cite web |last=Crandall |first=Christine |date=2023-05-18 |title=How Tesla’s New OTA Software Update Cut EV Range By A Massive 20%, Owners Move To Sue |url=https://www.hotcars.com/tesla-software-update-cut-ev-range-owners-move-to-sue/ |archive-url=https://web.archive.org/web/20250413101832/https://www.hotcars.com/tesla-software-update-cut-ev-range-owners-move-to-sue/ |archive-date=2025-04-13 |access-date=2025-09-13 |website=Hotcars}}</ref>.

==Consumer reactions==
Although some consumers rationalize such behavior of increasing safety or avoiding liability. Many of them condemn such practices and describing it as planned obsolescence.

There are ways of tackling battery firmware lockout:

*Replacing the battery pack: This is the simplest way of "repairing" a "bricked" battery. However doing so is costly, increases e-waste production and further fuels planned obsolescence of said manufacturers.
*Extracting the BMS code: Certain logic analyzers can extract the code from communications to and from the BMS chip. Users or repair technicians can use this way to extract the "unseal" password, then reset the "permanent fail" flag and recalibrate the battery's capacity.
*Acquiring the unlock password: Some of the battery models' BMS code has been leaked, some of them are publicized<ref>{{Cite web |last=@davext |date=25 Jun 2024 |title=unbrick-dji |url=https://github.com/davext/unbrick-dji/blob/main/src/main.cpp |url-status=live |archive-url=https://web.archive.org/web/20250914163205/https://github.com/davext/unbrick-dji/blob/main/src/main.cpp |archive-date=14 Sep 2025 |access-date=14 Sep 2025 |website=[Github]}}</ref>. For others, it might be possible to purchase it in the grey market, however, there's a risk of scam as some of the passwords can be as expensive as the pack itself, and there's no guarantee of working.
*Resetting the BMS: Some specialized hardware and software can be used to clear the PF flag, reviving the battery without the need of knowing the battery's parameters. Most of the users won't modify the battery pack after repairing<ref>{{Cite web |date=2019-08-15 |title=Reset-BQ20xx |url=https://github.com/otofoto/Reset-BQ20xx |url-status=live |archive-url=https://web.archive.org/web/20220923061011/https://github.com/otofoto/Reset-BQ20xx |archive-date=2022-09-23 |access-date=2025-09-13 |website=[[Github]]}}</ref>.
*Install a custom (or OEM) BMS chip: Buying a brand new BMS chip and write own program. The main challenge is the knowledge of the working mechanism of the battery and its BMS. Different battery chemistries have different voltage and current characteristics, using the wrong data may cause incorrect capacity reading at best, or battery/device malfunction at worst.

==Lawsuits==
Four plaintiffs are suing Tesla over an automatic over-the-air (OTA) software update that they say reduced the driving range of their vehicles by 20 percent. Forced updates by Tesla may violate California's Computer Fraud and Abuse Act and the Unfair Competition Law<ref name=":0" />.

==References==
{{reflist}}

[[Category:Common terms]]

Battery firmware lockout

2025-09-14T16:36:29Z

Charlie 6: /* Consumer reactions */ added a source, slight paraphrase

Most devices with rechargeable batteries has a [[wikipedia:Battery_management_system|battery management system (BMS)]] module. This module monitors and regulate key variables and capable of communicating with the device and preventing unsafe usage that could cause failure. However, many of them contains proprietary code that locks the battery from operation, "bricking" it and prevent the battery from third-party repair. Effectively making the whole device that depends on said battery unusable.

==How it works==
When the battery is outside its operating range, such as overcharged, overcharged, overheated, unbalanced(in multi-celled battery packs), the BMS prevents the battery from further usage, limiting damage. However, the BMS should resume normal operation when the battery is back within operating range. Instead, the BMS changes bytes in its memory, leading to a "Permanent Fail (PF)" state, preventing the use of said battery even after reconditioning or repairing.

Documentations from known BMS manufacturers such as Texas Instruments said the device can permanently disable the use of the battery pack in case of a "severe failure"<ref>[https://www.ti.com/lit/ug/sluua43a/sluua43a.pdf? https://www.ti.com/lit/ug/sluua43a/sluua43a.pdf?]</ref>. However users report the battery is "bricked" after scenarios like long-term storage, discharging laptop overnight or use a power tool in warm environment while charging it cool, indicating the manufacturers have abused the BMS program, exaggerating the nature of the failure as a from of [[self-destructive design]].

To make matters worse, many of the BMS needs "access code" to read and change it's parameters, including runtime ones like the "Permanent Fail" flag. The unlock or unseal code is kept secret by the battery's manufacturer, making user and third-parties very difficult, if not impossible, to repair said battery<ref>{{Cite web |date=28 Sep 2019 |title=Experiences with TI BQ management IC’s when re-building laptop batteries? |url=https://www.eevblog.com/forum/chat/experiences-with-ti-bq-management-ics-when-revelling-laptop-batteries/?all |url-status=live |archive-url=https://web.archive.org/web/20240926193741/https://www.eevblog.com/forum/chat/experiences-with-ti-bq-management-ics-when-revelling-laptop-batteries/?all |archive-date=26 Sep 2024 |access-date=13 Sep 2025 |website=EEVblog Electronics Community Forum}}</ref>.

Alarmingly, the condition of "bricking" includes "Capacity Degradation Permanent Failure"<ref>[https://www.ti.com/lit/ds/symlink/bq40z50.pdf? https://www.ti.com/lit/ds/symlink/bq40z50.pdf?]</ref>, which means the manufacturers can artificially limit the battery pack's lifespan, making it unusable after a certain health (e.g 80%).

==Why it is a problem==

===Increased repair cost===
When the battery is bricked, most users would buy an entire battery pack, increasing the total cost of ownership. The "access code" lock prevents third-parties from replacing individual cells and refurbishing the battery pack, reducing its lifespan.

===Environmental impact===
Lithium-ion batteries are 95% recyclable, however, only about 5% of them are actually recycled<ref>{{Cite web |date=22 Sep 2022 |title=Lithium ion battery recycling |url=https://www.cas.org/resources/cas-insights/lithium-ion-battery-recycling?utm_source=chatgpt.com |url-status=live}}</ref>. BMS firmware lockout increases the number of battery packs end up in waste, increasing pollution. Some of the materials like cobalt, are hazardous.

===Undermining ownership===
When the purchase is complete. The ownership is transferred to the user of the device. Locking out the battery after purchase is akin to installing a lock on someone else's property, and should be considered "Digital Handcuffs"<ref>{{Cite web |title=Words to Avoid (or Use with Care) Because They Are Loaded or Confusing |url=https://www.gnu.org/philosophy/words-to-avoid.html |url-status=live |archive-url=https://web.archive.org/web/20250909175856/https://www.gnu.org/philosophy/words-to-avoid.html |archive-date=2025-09-09 |access-date=2025-09-13 |website=GNU Operating System}}</ref>.

==Examples==

===Consumer electronics===
[[File:BQ40Z50R3 1.jpg|thumb|A screenshot of a "bricked" battery pack with healthy cells, note the red "PF_EN"]]
The most common consumer electronics using sophisticated battery management system for their multi-cell battery pack are laptop computers. There are many discussions about the battery "lockout" after replacing or recharging individual cells, indicating battery firmware lockout is the main obstacle of battery repair<ref>{{Cite web |date=2022-10-06 |title=How can I reset the laptop battery BMS? |url=https://electronics.stackexchange.com/questions/570919/how-can-i-reset-the-laptop-battery-bms |url-status=live |archive-url=https://web.archive.org/web/20250913130751/https://electronics.stackexchange.com/questions/570919/how-can-i-reset-the-laptop-battery-bms |archive-date=2025-09-13 |access-date=2025-09-13 |website=Stack Exchange}}</ref><ref>{{Cite web |date=30 Oct 2023 |title=(i changed every cell in laptop battery then bms locked How to unlock bms of acer e5 laptop battery, total battery in series is 15v but in bms output voltage is 0v i tried to short battery positive to output positive, but still no output, i think bms is locked how to unlock without software help |url=https://old.reddit.com/r/batteries/comments/17jogjr/i_changed_every_cell_in_laptop_battery_then_bms/ |url-status=live |archive-url=https://web.archive.org/web/20250913133735/https://old.reddit.com/r/batteries/comments/17jogjr/i_changed_every_cell_in_laptop_battery_then_bms/ |archive-date=13 Sep 2025 |access-date=13 Sep 2025 |website=[[Reddit]]}}</ref>.

===Commercial UAVs===
{{Main|DJI}}
DJI, a well known commercial UAV manufacturer, locks out the battery after long-term storage, claiming over-discharging damages the battery, even if the chemistry is still recoverable. Users who successfully "revives" the battery packs by charging their cells using a bench power supply and clearing the failure code, reports restored functionality<ref>{{Cite web |date=2024-03-21 |title=Reviving dead batteries - a heads up |url=https://mavicpilots.com/threads/reviving-dead-batteries-a-heads-up.146169/ |url-status=live |archive-url=https://web.archive.org/web/20250618000130/https://mavicpilots.com/threads/reviving-dead-batteries-a-heads-up.146169/ |archive-date=2025-06-18 |access-date=2025-09-13 |website=MavicPilots}}</ref><ref>{{Cite web |date=2023-08-02 |title=DJI Battery Killer repairing tool |url=https://greyarro.ws/t/dji-battery-killer-repairing-tool/68863 |url-status=live |access-date=2025-09-13 |website=Grey Arrows Drone Club}}</ref><ref>{{Cite web |last=McLoughlin |first=Liam |date=2023-10-01 |title=Repairing the DJI Spark Drone Battery with DJI Battery Killer, CP2112, & 9V battery |url=https://leelum.com/projects/repairing-the-dji-spark-drone-battery-with-dji-battery-killer-cp2112-9v-battery/ |url-status=live |archive-url=https://web.archive.org/web/20241211065622/https://leelum.com/projects/repairing-the-dji-spark-drone-battery-with-dji-battery-killer-cp2112-9v-battery/ |archive-date=2024-12-11 |access-date=2025-09-13 |website=Leelum}}</ref><ref>{{Cite web |title=DJI Battery Killer: Reviving Bricked DJI Drone Batteries with CP2112 & BMS Reset |url=https://www.elektroda.com/qa,dji-battery-killer-cp2112-bms-reset.html |url-status=live |website=elektroda}}</ref>. However some users reported "authentication failed"<ref>{{Cite web |date=2024-03-23 |title=Mavic pro battery authentication failed after clear pf |url=https://mavicpilots.com/threads/mavic-pro-battery-authentication-failed-after-clear-pf.144987/ |url-status=live |access-date=2025-09-13 |website=MavicPilots}}</ref> suggesting the possibility of parts serialization<ref>{{Cite web |last=Greenlee |first=Lauren |date=2023-01-17 |title=How Parts Pairing Kills Independent Repair |url=https://www.ifixit.com/News/69320/how-parts-pairing-kills-independent-repair |url-status=live |archive-url=https://web.archive.org/web/20250811033531/https://www.ifixit.com/News/69320/how-parts-pairing-kills-independent-repair |archive-date=2025-08-11 |access-date=2025-09-13 |website=iFixit}}</ref>.

===Home appliances===
{{Main|Dyson battery lifespan reduced by design and difficult to repair}}
Dyson appliances often come with battery packs omitting balancing resistors, leading to higher battery degradation. When the battery cells are unbalanced, repaired or replaced. The BMS chip will lockout. This can be mitigated with added resistors and a custom firmware that doesn't brick the battery upon maintenance<ref name=":2">{{Cite web |last=@tinfever |title=(Unofficial) Firmware Upgrade for Dyson V6/V7 Vacuum Battery Management System |url=https://github.com/tinfever/FW-Dyson-BMS |url-status=live |archive-url=https://web.archive.org/web/20250912021607/https://github.com/tinfever/FW-Dyson-BMS |archive-date=2025-09-12 |access-date=25 Mar 2025 |website=GitHub}}</ref>.

===Power tools===
Power tool manufacturers such as Ryobi and Makita are known to lock battery backs, causing good ones to fail and ended up in repair centers, or worse, landfills<ref>https://www.youtube.com/watch?v=NQ_lyDyzEHY</ref>. Repair technicians who know how to "unbrick" the BMS are capable of reviving these units with perfect condition, reducing e-waste.

===Electric vehicles===
Tesla cuts the range of some Model S and Model X by up to 20% by an OTA update. Some of the batteries became totally unusable, showing a "BMS_u029" error. Some users are able to reverse the change by flashing an older firmware, other users are forced to replace the entire battery pack, costing over $15,000<ref name=":0">{{Cite web |last=Crandall |first=Christine |date=2023-05-18 |title=How Tesla’s New OTA Software Update Cut EV Range By A Massive 20%, Owners Move To Sue |url=https://www.hotcars.com/tesla-software-update-cut-ev-range-owners-move-to-sue/ |archive-url=https://web.archive.org/web/20250413101832/https://www.hotcars.com/tesla-software-update-cut-ev-range-owners-move-to-sue/ |archive-date=2025-04-13 |access-date=2025-09-13 |website=Hotcars}}</ref>.

==Consumer reactions==
Although some consumers rationalize such behavior of increasing safety or avoiding liability. Many of them condemn such practices and describing it as planned obsolescence.

There are ways of tackling battery firmware lockout:

*Replacing the battery pack: This is the simplest way of "repairing" a "bricked" battery. However doing so is costly, increases e-waste production and further fuels planned obsolescence of said manufacturers.
*Extracting the BMS code: Certain logic analyzers can extract the code from communications to and from the BMS chip. Users or repair technicians can use this way to extract the "unseal" password, then reset the "permanent fail" flag and recalibrate the battery's capacity.
*Acquiring the unlock password: Some of the battery models' BMS code has been leaked, some of them are publicized<ref>{{Cite web |last=@davext |date=25 Jun 2024 |title=unbrick-dji |url=https://github.com/davext/unbrick-dji/blob/main/src/main.cpp |url-status=live |archive-url=https://web.archive.org/web/20250914163205/https://github.com/davext/unbrick-dji/blob/main/src/main.cpp |archive-date=14 Sep 2025 |access-date=14 Sep 2025 |website=[Github]}}</ref>. For others, it might be possible to purchase it in the grey market, however, there's a risk of scam as some of the passwords can be as expensive as the pack itself, and there's no guarantee of working.
*Resetting the BMS: Some specialized hardware and software can be used to clear the PF flag, reviving the battery without the need of knowing the battery's parameters. Most of the users won't modify the battery pack after repairing<ref>{{Cite web |date=2019-08-15 |title=Reset-BQ20xx |url=https://github.com/otofoto/Reset-BQ20xx |url-status=live |archive-url=https://web.archive.org/web/20220923061011/https://github.com/otofoto/Reset-BQ20xx |archive-date=2022-09-23 |access-date=2025-09-13 |website=[[Github]]}}</ref>.
*Install a custom (or OEM) BMS chip: Buying a brand new BMS chip and write own program. The main challenge is the knowledge of the working mechanism of the battery and its BMS. Different battery chemistries have different voltage and current characteristics, using the wrong data may cause incorrect capacity reading at best, or battery/device malfunction at worst.

==Lawsuits==
Four plaintiffs are suing Tesla over an automatic over-the-air (OTA) software update that they say reduced the driving range of their vehicles by 20 percent. Forced updates by Tesla may violate California's Computer Fraud and Abuse Act and the Unfair Competition Law<ref name=":0" />.

==References==
{{reflist}}

[[Category:Common terms]]