Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
Hafeman v. Google & Microsoft — Computer Recovery Patent Appeal | PatSnap
Patent Litigation

Hafeman v. Google & Microsoft: Federal Circuit Dismisses in Part, Affirms in Part

Individual inventor Carolyn W. Hafeman appealed against Google LLC and Microsoft Corporation at the Federal Circuit, asserting three patents covering computer recovery and return technology. After 801 days, the court issued a split ruling — dismissing part of the appeal and affirming part — leaving the patentability challenge partially resolved.

Resolution time
801days
801 days from filing to close — a substantial Federal Circuit appeal timeline
Patents asserted
3
US9892287B2, US10789393B2, and US10325122B2 — computer recovery or return technology
Outcome
Appeal Dismissed in Part
Appeal dismissed in part; lower decision affirmed in part — split Federal Circuit outcome
Cost ruling
Not recorded
No cost or fee ruling is recorded in the available case data
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Three computer recovery patents, two tech giants, one split Federal Circuit ruling

Carolyn W. Hafeman, an individual inventor, filed this appeal at the Court of Appeals for the Federal Circuit on 26 March 2024, bringing patentability challenges concerning three US patents — US9892287B2, US10789393B2, and US10325122B2 — all directed to computer recovery or return technology. The defendants are Google LLC and Microsoft Corporation, represented by Smith Baluch LLP. The underlying verdict cause is recorded as an invalidity/cancellation action.

The Federal Circuit closed the case on 5 June 2026, issuing an order that the appeal be 'dismissed in part, affirmed in part.' The recorded basis of termination is 'Appeal Dismissed in Part.' The docket order states the cause was considered and adjudged as dismissed-in-part and affirmed-in-part, meaning some aspects of the appeal did not proceed on the merits while others were upheld at the appellate level. The specific terms and scope of each part are not further detailed in the available record.

The 801-day duration is consistent with a substantive Federal Circuit appeal involving multiple patents and two major technology defendants. What drove the partial dismissal — whether procedural standing issues, jurisdictional defects, or voluntary withdrawal on certain claims — is not disclosed in the public record. The specific patents or issues corresponding to the dismissed portion versus the affirmed portion are not identified in the available case data.

See Complete Case & Patent Analysis →
Case at a glance
Case no.24-1604
DefendantGoogle, LLC
CourtCourt of Appeals for the Federal Circuit
JudgeN/A
FiledMarch 26, 2024
ClosedJune 5, 2026
Duration801 days
OutcomeAppeal Dismissed in Part
Verdict causePatentability
BasisAppeal Dismissed in Part
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Court of Appeals for the Federal Circuit via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Appeal Dismissed in Part in 801 days

801 days from filing to close — a substantial Federal Circuit appeal timeline

Case timeline: Appeal filed MAR 26 2024 — 801 days total Horizontal timeline showing the three key events in Carolyn W. Hafeman v Google, LLC from filing to resolution. Source: PACER, Court of Appeals for the Federal Circuit. MAR 26 2024 Appeal filed Pre-trial proceedings JUN 5 2026 Appeal Dismissed in Part 801 DAYS TOTAL
Patent at issue

US9892287B2, US10789393B2 & US10325122B2 — Computer Recovery or Return Technology

Publication No.US9892287B2
Application No.US15/601645
Patent details
Productcomputer recovery or return system — US9892287B2
Cited in actionMarch 26, 2024

Publication No.US10789393B2
Application No.US16/377768
Patent details
Productcomputer recovery or return method — US10789393B2
Cited in actionMarch 26, 2024

Publication No.US10325122B2
Application No.US15/864749
Patent details
Productcomputer recovery or return technology — US10325122B2
Cited in actionMarch 26, 2024
Technical brief · sourced from PatSnap patent database
Patent figurePatent figure
Representative claim (1 of 3 independent)
1. A method for displaying information to assist with returning a computer comprising the steps of: activating a processor to display on a display screen on the computer which displays information concerning return information for returning the computer to an owner from data stored in a memory of the computer, the screen displaying recovery information, to facilitate return of the computer so the return information is visible to anyone viewing the display screen; initiating or changing return information which appears on the display through remote communication without assistance by a user with the computer, wher…
Technical background
CROSS-REFERENCE TO RELATED APPLICATIONS This is a continuation of U.S. patent application Ser. No. 15/199,316 filed Jun. 30, 2016, now U.S. Pat. No. 9,672,388 which is a continuation of U.S. patent application Ser. No. 14/691,222 filed Apr. 20, 2015, now U.S. Pat. No. 9,390,296 issued Jul. 12, 2016, which is a continuation of U.S. patent application Ser. No. 14/087,866 filed Nov. 22, 2013, now U.S. Pat. No. 9,021,610 issued Apr. 28, 2015, which is a continuation of U.S. patent application Ser. No. 10/945,332 filed…
Patent family
22 family members across 6 jurisdictions (US, EP, IT, AT, DE, WO)
PatSnap Eureka · FTO Search Agent
Should you run an FTO against US9892287B2, US10789393B2, and US10325122B2?

Any company developing computer recovery, remote device management, asset return, or data wipe functionality should treat this patent family as a live FTO consideration. The partial Federal Circuit affirmance confirms that at least some patentability findings stand — but the scope of surviving claims is not fully determinable from the public record alone. Product teams deploying cloud-based recovery, lost-device return workflows, or enterprise device management platforms should assess exposure before scaling.

Run FTO in Eureka
Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Official verdict

Official order — verbatim text

THIS CAUSE having been considered, it is ORDERED AND ADJUDGED: DISMISSED-IN-PART, AFFIRMED-IN-PART
Source: PACER Docket, Case 24-1604, Court of Appeals for the Federal Circuit

The Federal Circuit's order — 'dismissed-in-part, affirmed-in-part' — reflects a split disposition in which at least one portion of Hafeman's appeal was not adjudicated on the merits (dismissed) while at least one portion received substantive appellate review and the lower tribunal's decision was upheld (affirmed). The affirmance standard at the Federal Circuit requires that no reversible error be found in the decision below; the dismissal component indicates a separate, non-merits barrier to review on those issues. The precise allocation between the three patents is not specified in the available record.

PACER case 24-1604 · Public docket record Explore in Eureka ↗
Court ruling

Federal Circuit split ruling: what dismissed-in-part, affirmed-in-part means

Legal mechanism

What 'dismissed in part, affirmed in part' means at the Federal Circuit

A split Federal Circuit disposition means the court declined to reach the merits on at least one portion of the appeal — dismissing it for procedural, jurisdictional, or standing reasons — while separately affirming a lower tribunal's decision on at least one other portion, finding no reversible error there. The two parts of the ruling operate independently. The specific allocation of dismissed versus affirmed issues is not detailed in the available record.

Split appellate disposition
Patent holder outcome

Hafeman's position after a partial affirmance

For the portion of the appeal that was affirmed, the lower tribunal's decision stands against Hafeman — suggesting at least some patentability findings adverse to the patent holder were upheld. The dismissed portion means the Federal Circuit did not adjudicate those issues on the merits, leaving the underlying status of those specific claims or patents uncertain from the public record alone. The specific patents or claims affected by each part are not disclosed.

Partial adverse outcome for appellant
Defendant outcome

Google and Microsoft secure at least a partial appellate win

The affirmance component of the ruling is consistent with a favorable result for Google LLC and Microsoft Corporation on at least part of the patentability challenge — the lower decision in their favour was not disturbed on those issues. The dismissed portion does not constitute a merits win or loss for either defendant. The overall effect on enforceability of the three asserted patents against these defendants is not fully determinable from the available record.

Partial appellate win for defendants
Commercial implications

Computer recovery IP: what a split ruling signals for the sector

A split Federal Circuit ruling on computer recovery and return patents suggests the asserted technology touches on legally contested ground — some claims or proceedings survived appellate scrutiny while others did not reach a merits ruling. Companies developing or commercialising device recovery, remote wipe, or return-technology products should monitor the specific claim scope of US9892287B2, US10789393B2, and US10325122B2 in light of this outcome and any subsequent proceedings.

Contested computer recovery IP
Legal analysis based on PACER docket records for case 24-1604 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffCarolyn W. HafemanIndividual/Search in Eureka ↗
DefendantGoogle, LLCCompany/Search in Eureka ↗
Co-DefendantMicrosoft CorporationCompanySearch in Eureka ↗
Plaintiff counselStephen UnderwoodAttorneyCounsel for Carolyn W. HafemanSearch in Eureka ↗
Plaintiff law firmGlaser Weil Fink Howard Jordan & Shapiro LLPLaw FirmRepresenting Carolyn W. HafemanSearch in Eureka ↗
Defendant counselMatthew A. SmithAttorneyCounsel for Google, LLCSearch in Eureka ↗
Defendant law firmSmith Baluch LLPLaw FirmRepresenting Google, LLCSearch in Eureka ↗
Presiding judgeJudge N/AJudgeCourt of Appeals for the Federal CircuitSearch in Eureka ↗
R&D signals

R&D signals in the computer recovery and device management patent space

Forward-looking patent and R&D intelligence derived from the Hafeman v. Google & Microsoft dispute — covering portfolio activity, filing trends, and white-space opportunities in device recovery technology.

Patent portfolio

Hafeman's computer recovery patent family: continuation depth and filing strategy

The three asserted patents share sequential application numbers suggesting a deliberate continuation filing strategy around core computer recovery inventions. Understanding the full depth of Hafeman's portfolio — including any pending continuations, divisionals, or related applications — is critical for competitors and licensees assessing long-term exposure in the device recovery space.

Continuation family depth
Technology landscape

Filing trends in computer recovery, remote wipe, and device return technology

The computer recovery and device return domain is attracting filings from a range of players as enterprise device management and BYOD policies scale globally. Tracking claim-level filing trends in remote recovery, asset identification, and return-workflow patents can surface competitive positioning signals and highlight areas where the patent landscape is densifying or opening up.

Device recovery filing trends
Competitor IP posture

Google and Microsoft's own IP in device recovery and management

Google LLC and Microsoft Corporation both maintain substantial patent portfolios in device management, security, and recovery workflows. Analysing their own filings in this space — and how those filings relate to the claimed inventions in the Hafeman family — can reveal defensive patent strategies, potential cross-licensing leverage, and areas where their proprietary approaches diverge from the asserted claims.

Big Tech defensive IP
White-space opportunity

Adjacent innovation opportunities near computer recovery IP

The contested claim space around computer recovery and return technology — particularly following a split Federal Circuit ruling — may create white-space opportunities in adjacent areas such as hardware-assisted recovery, blockchain-based device identity, or AI-driven asset return workflows. These adjacent domains may offer innovation runway with reduced freedom-to-operate friction relative to the core disputed claims.

Adjacent R&D white space
Related litigation

Similar Federal Circuit patentability appeals in computer recovery and device management IP

Explore Federal Circuit appeals involving patentability challenges to computer recovery, device management, and remote access patents — cases with comparable invalidity/cancellation postures.

🔍
Access 40+ similar cases in PatSnap Eureka
Carolyn W. Hafeman patent enforcement history, Court of Appeals for the Federal Circuit case history, Carolyn W. Hafeman's full IP portfolio, and comparable case analysis
Related device recovery appealsGoogle patent validity casesMicrosoft invalidity Fed CircuitIndividual inventor vs Big Tech
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the computer recovery patent IP landscape

A split Federal Circuit ruling across three patents and two major defendants highlights the complexity of enforcing device recovery IP at the appellate level.

Individual inventors face structural challenges appealing against large tech defendants

Hafeman's position as an individual inventor asserting three patents against Google and Microsoft at the Federal Circuit is resource-intensive. The split outcome — with part of the appeal dismissed without a merits ruling — suggests procedural or standing hurdles that smaller patentees should anticipate when pursuing invalidity or enforcement appeals against well-resourced defendants.

Computer recovery patents remain an active battleground at the Federal Circuit

The patentability challenge across three related computer recovery patents in a single appeal signals that this technology cluster is under sustained scrutiny. Teams building device management, remote recovery, or asset return platforms should assess whether their own implementations or patent portfolios overlap with the US9892287, US10789393, and US10325122 family before engaging in this space.

🔒
Full strategic analysis in PatSnap Eureka
Unlock deeper Federal Circuit appeal intelligence for computer recovery patent disputes — portfolio risk, claim mapping, and sector filing trends.
Standing analysis signalsContinuation family risk mapCompetitor filing trends
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

Hafeman v Google — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Track computer recovery patent risk before your next product launch

The Hafeman family remains active IP in a contested space. Run an FTO against US9892287B2, US10789393B2, and US10325122B2 in PatSnap Eureka to map your exposure and monitor any continuation filings.

Disclaimer

This page is compiled from public court dockets and third-party patent and litigation data via PatSnap Eureka, and is provided for general informational purposes only. The information shown — including party names, patent and application numbers, dates, case status, outcomes, and any analysis — may be incomplete, may not reflect the most recent filings or legal status, and may contain errors or omissions. Verify all details against official court records (for example, PACER) and the relevant patent office before relying on them.

Nothing on this page constitutes legal advice or a legal opinion on the validity, infringement, enforceability, or scope of any patent or case, and no attorney‑client relationship is created by its use. Any description of an outcome (such as a dismissal, settlement, or consent judgment) is a general summary, not a legal determination. All patents, trademarks, and company or law‑firm names are the property of their respective owners. PatSnap makes no warranty as to the accuracy or completeness of this content and disclaims, to the fullest extent permitted by law, all liability for reliance on it. For advice on a specific matter, consult qualified legal counsel.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.