The FCC's Console-Component Rule Took Effect on October 13 — Not the September 8 Date It Was Reported With

Excerpt: An original LostInConsoles source investigation into the Federal Communications Commission's equipment-authorization rule for consoles, controllers, handhelds and headsets — what actually became effective on October 13, 2026, which parts of the order reach console hardware, and the clause that now governs every certification amendment filed after it.

The short version: The FCC's component-provenance rule for wireless devices — the one that reaches every console, controller, handheld and headset sold in America, because all of them are certified "intentional radiators" — did not take effect on September 8, 2026. The final rule, published in the Federal Register on September 11, 2026 as 91 FR 57798, carries one operative line: "This final rule is effective October 13, 2026." That is the date the prohibition on equipment incorporating covered-list components began to apply. Everything authorized before that date is untouched, and the first authorizations the prohibition can reach are the ones filed on or after it — which is the next-generation hardware now moving through the certification pipeline.

Neither the September date nor the October go-live has been reported by a games-industry outlet we can find. The only trade coverage sits in drone-industry and electronics-compliance publications, where the rule is read as a supply-chain-security story about DJI and Autel rather than a hardware story about consoles — even though the legal instrument is identical for both.

This is a synthesis of primary Federal Register text, the FCC's docket record, the rule's codified definitions and the compliance literature that has grown up around it. We flag final rule against proposal, and we mark the one claim of our own that the final text corrects.

What actually took effect, and on what date

Confidence: HIGH (primary — Federal Register 91 FR 57798 and 91 FR 51139; FCC 26-50, ET Docket 21-232).

The order is the FCC's Third Report and Order in ET Docket 21-232, adopted on July 22, 2026 and released on July 23, 2026. It reached the Federal Register twice, and the difference between the two entries is the story:

• 91 FR 51139, published August 7, 2026 is typed by the Federal Register as a Proposed Rule. It carries no effective date.
• 91 FR 57798, published September 11, 2026 is typed as a Rule. Its DATES block reads: "This final rule is effective October 13, 2026."

The September 8, 2026 date that has circulated since August — including in our own investigation of August 25 — is not the effective date of this rule. The rule states its own effective date in one line, and that line is October 13, 2026.

What the prohibition actually reaches

Confidence: HIGH (primary — rule text, 91 FR 57798).

The Commission closes what it calls a component-part loophole. The order prohibits equipment authorization for "devices that incorporate logic-bearing hardware components produced by an entity identified on the Commission's Covered List, where the device would itself be prohibited from authorization had the Covered List entity produced the entire device."

The definition it adopts is precise enough to matter:

"Any device, system, module, sub-assembly, integrated circuit, or other physical component that generates and uses timing signals or pulses at a rate in excess of 9,000 pulses (cycles) per second and uses digital techniques; inclusive of telephone equipment that uses digital techniques or any device, system, module, sub-assembly, integrated circuit, or other physical component that generates and uses radio frequency energy for the purpose of performing data processing functions, such as electronic computations, operations, transformations, recording, filing, sorting, storage, retrieval, or transfer."

Purely mechanical and passive parts — housings, fasteners, resistors, wiring, plain battery cells — sit outside that boundary. So does anything below the timing threshold.

Two scope limits decide whether this is a console story at all. First, the prohibition is producer-based: it applies to components "produced by entities subject to producer/provider-based Covered List determinations," and — in the rule's own words — it "does not apply to production location-based Covered List entries (e.g., UAS, UAS critical components, or routers produced in a foreign country) unless the producing entity is independently identified on the Covered List." In plain terms: it is about who made the part, not where the machine was assembled. Second, the target set is the Covered List — Huawei, ZTE, Hikvision, Dahua, Hytera and their affiliates — and no mainstream console's SoC or memory is a Covered List part. AMD and NVIDIA design the console silicon; the memory comes from Samsung, Micron and SK hynix.

The order does not ban a PlayStation, an Xbox or a Switch. That is the same conclusion our August investigation reached, and it survives contact with the final text.

The clause that now governs every console revision

Confidence: HIGH (primary — rule text).

The line console hardware people should read twice is the tail of the exemption:

"Applications pending as of the effective date are exempt from the new prohibition unless later amended to add, substitute, or change a logic-bearing hardware component."

Translated: a certification file that was already in the queue on October 13, 2026 keeps its exemption — until somebody changes a part inside it. The Commission then goes further on modifications, and the language is unusually concrete. The prohibitions in 47 CFR 2.932 and 2.1043 apply both to equipment already barred and to "equipment that would become prohibited as a result of the proposed modification," and the Commission names the examples outright: "a shift in production to a Covered List entity or a change that would cause a device to lose 'domestic end product' status."

For a console, a controller, a handheld or a headset, that is a new gate inside an existing gate. Amending a certification file used to be an administrative event. From October 13, a change to a logic-bearing part is an event the rule has an opinion about — and the prohibition itself bites only where a Covered List entity's component is involved. What changed is that the analysis now has to happen at all.

That distinction matters because the industry is entering a hardware cycle in which components are being re-sourced constantly. The desk has tracked the pressure all year: memory pricing, the collapse in console hardware spending, price hikes across PlayStation, Xbox and Switch. Re-sourcing has been an engineering and procurement problem. The FCC has now given it a legal edge.

The marketplace clock, and the retro-console carve-out

Confidence: HIGH (primary — rule text).

The order also strengthens the marketing rules under 47 CFR 2.803. It clarifies that the term "distribution for the purpose of selling" reaches any entity — including online marketplaces — that markets unauthorized equipment, and it requires online marketplaces, with limited exceptions, to display a device's FCC ID at the online point of sale.

The Commission adopted differentiated compliance dates "in recognition of the differing implementation burdens": March 1, 2027 for online marketplaces with physical access to, or title over, the device, and June 1, 2027 for marketplaces relying on third-party seller certifications.

Three exceptions are worth naming, because they map onto how game hardware is actually sold:

• listings for devices that were on the market on the rule's effective date and are not later amended or updated;
• listings by sellers who are not "high-volume third-party sellers" as defined in the INFORM Consumers Act;
• listings for used devices.

That last carve-out is the second-hand and retro console market. The FCC did not extend the disclosure duty to the resale of a used console — which is the channel through which most out-of-print hardware in America moves.

The Commission declined, "at this time," to require FCC ID display on external product packaging, and keeps the record open on that question. So the packaging on the shelf is untouched for now, while the listing page is not.

The quiet change to the Covered List itself

Confidence: HIGH (primary — rule text).

Buried in the same order is a definitional revision that has nothing to do with components and everything to do with which entities can ever be added. Responding to a partial remand from the U.S. Court of Appeals for the D.C. Circuit, the Commission adopted a revised definition of "critical infrastructure" for purposes of the Covered List. It retains the standard from section 1016(e) of the USA PATRIOT Act of 2001 — systems and assets "so vital to the United States that the incapacity or destruction of such systems would have a debilitating impact on security, national economic security, national public health or safety" — and anchors it to the 16 critical-infrastructure sectors identified by the Department of Homeland Security and to the 55 National Critical Functions published by DHS's National Risk Management Center. What the Commission removed is the prior "connected to" language that the D.C. Circuit found "unjustifiably broad."

Read cold, this is housekeeping after a court loss. Read as a supply-chain document, it is the definition that governs how far the Covered List can reach into consumer-electronics supply chains next. The order also corrects two administrative errors in the Commission's rules.

Why the date is not cosmetic

Confidence: HIGH (primary), with one analytical inference flagged.

Because the rule is prospective, the distance between the reported date and the real one is not about enforcement history. It is about which hardware counts as first.

The rule's summary states the mechanism plainly: "The rule is effective 30 days after publication in the Federal Register and applies prospectively to new equipment authorization applications; it does not affect previously authorized equipment." Measured from the August 7 document — the one typed as a proposal — that clock produces a date in early September. Measured from the September 11 final rule, it produces October 13, 2026. The two anchors sit 35 days apart, and that is the full width of the confusion.

What sits inside that gap is a console certification season. Nintendo's October certification cluster — a console revision and a wave of controller filings, all dated October 8, 2026 in FCC records — hit the FCC's database days before the prohibition actually began to apply. Every one of those authorizations is unaffected, on the rule's plain terms. Under the date that has been circulating since August, they would have been new applications filed inside the prohibition rather than exempt ones.

The forward-looking reading is the harder one. The next-generation pipeline — PS6, Xbox's Project Helix, the rumored PlayStation handheld — is moving through the same equipment-authorization system the new text now governs, and the first applications the component prohibition can reach are those filed on or after October 13, 2026. Confidence: MEDIUM-HIGH (analytical). We are not claiming any of those products contains a Covered List component. We are reporting that, from October 13, the question is now part of the certification record rather than an assumption.

Alternative explanation (considered, included): It is reasonable to read the September 8 date as having come from a pre-publication estimate built on the August 7 proposal — in which case it was an estimate that the final rule superseded rather than a misreading. We can verify three things: our own August piece leaned on that date, the Federal Register types the August 7 document as a proposal with no effective date, and the final rule names October 13. On the evidence available, the date that has been in circulation is not the date the rule took effect.

Novelty: N2/N3. We searched the games press, the mainstream tech press and the specialist hardware press for coverage of the actual October 13 effective date and found none. The rule itself was reported on August 25 by this desk; the date it actually took effect, and the provisions that only become operative on that date, were not.

Bottom line

The FCC's rule for wireless consoles, controllers, handhelds and headsets did not take effect in early September. It took effect on October 13, 2026 — one line in the DATES block of a Federal Register entry published on September 11, and a date the games press has never reported. Everything certified before it is untouched. Everything filed after it carries a new question: whether a logic-bearing component inside the device was produced by an entity on the Covered List. The console industry spent the summer being told the rule was already live when it was not, and is now inside it without having been told.

LostInConsoles — Investigating the console hardware industry where other outlets don't.

Sources

• Federal Register — Protecting Against National Security Threats to the Communications Supply Chain Through the Equipment Authorization Program, final rule, 91 FR 57798, published September 11, 2026, effective October 13, 2026: federalregister.gov
• Federal Register — the same rule as a proposed rule, 91 FR 51139, published August 7, 2026, no effective date: federalregister.gov
• Federal Communications Commission — Equipment Authorization Program rulemaking record, ET Docket 21-232: fcc.gov
• Federal Communications Commission — Electronic Comment Filing System, ET Docket 21-232: fcc.gov/ecfs
• Electronic Code of Federal Regulations — 47 CFR 2.903, Prohibition on authorization of covered equipment: ecfr.gov
• Electronic Code of Federal Regulations — 47 CFR Part 15, Subpart C, intentional radiators: ecfr.gov
• Drone Intelligence — From 13 October, the FCC stops approving new devices with covered components: droneintelligence.ai