Repairing Equipment With Embedded Software: The Limits On Temporary Copies

Modern equipment often cannot even start, diagnose itself, or complete a repair cycle without loading embedded software into memory. That creates a practical copyright question for manufacturers, equipment owners, lessors, and repair businesses: when a maintenance task causes a temporary software copy to be made, is that copy allowed under federal law? The answer can be yes, but only in a narrow set of circumstances.

Under section 117(c) of the Copyright Act, an owner or lessee of a machine may make or authorize a copy of a computer program when that copy is created solely because the machine is activated for maintenance or repair. That narrow rule is useful, but it is not a blank check. The machine must lawfully contain an authorized program copy, the copy must be used only for that maintenance or repair, and it must be destroyed immediately after the job is completed. This article is general information only and is not legal advice.

For small businesses, the real challenge is operational. A routine restart needed to test a machine may fit the statute better than downloading a spare installer, keeping a reusable image, or using software from one machine to service another. Good records can help you define the repair scope, document who authorized the work, and reduce the chance that a routine job turns into a copyright dispute.

When Does Federal Copyright Law Allow A Temporary Software Copy During Equipment Repair?

Title 17 section 117(c) is a specific exception for machine maintenance and repair. It says the owner or lessee of a machine may make or authorize the making of a copy of a computer program if that copy is made solely by virtue of activating a machine that lawfully contains an authorized copy of the program.

That wording matters. The copy must arise because the machine is turned on or otherwise activated. The rule is aimed at the temporary copying that naturally happens when software-controlled equipment boots up, runs diagnostics, or loads code needed to test whether the machine works.

The exception is also limited by purpose. The activation must be for maintenance or repair of that same machine, not for a broader software project, product development exercise, or unrelated access to embedded code.

In practical terms, a service technician may be in a better position if the job involves starting the customer's lawfully configured machine to identify a fault, replace a failed component, and confirm that the machine now works as intended. The position is weaker if the technician copies software out of the machine for later reuse, explores nonessential software modules, or uses the process to build a library of installers for future jobs.

Section 117(c) does not say every repair is permitted. It addresses a narrow copyright issue about temporary copies made through machine activation. Other legal and contract questions may still need separate review.

Why The Conditions In Section 117(c) Matter So Much

Businesses often read the first half of the rule and stop too early. The later conditions are what make the exception narrow.

First, the machine must lawfully contain an authorized copy of the computer program. If the installed software itself is unauthorized, section 117(c) does not solve that problem.

Second, the new copy must be used in no other manner. That means the temporary copy created by machine activation cannot become a general business asset, reference image, backup pool, or training tool.

Third, the new copy must be destroyed immediately after the maintenance or repair is completed. That is a stricter timing point than many businesses expect. The statute does not describe a delayed deletion window for convenience, later troubleshooting, or future jobs.

Fourth, any computer program, or part of a program, that is not necessary for the machine to be activated must not be accessed or used other than to make the new copy by virtue of activation. In other words, if a program or part of a program is not necessary for the machine to be activated, section 117(c) does not permit access or use beyond making the activation copy. A separate repair purpose does not remove that condition.

This is why the facts of the job matter. A standard restart needed to test whether a machine powers up, loads required code, and reaches normal operating status may look very different from opening unrelated software modules, pulling out files for analysis unrelated to the repair, or preserving an image for another customer's machine.

What Counts As "Maintenance" And "Repair" Under Section 117(d)?

Section 117(d) gives the key definitions.

For this rule, maintenance means servicing the machine so it works in accordance with its original specifications and any specification changes authorized for that machine. Repair means restoring the machine to that same working state.

Those definitions help separate genuine maintenance work from projects that go further. If a machine originally shipped with certain software behavior, and later received manufacturer-authorized specification changes for that particular machine, work directed at keeping or restoring that approved state is closer to the statutory language.

By contrast, adding a new capability, enabling an unauthorized feature set, or changing the machine to perform beyond its original or authorized specifications is harder to characterize as maintenance or repair under section 117(d). The same caution applies to broad retrofits framed as service calls when they effectively create a different software environment than the machine was authorized to use.

This does not mean every upgrade is unlawful. It means section 117(c) is not the right provision to rely on just because the machine is open for service. If the job includes software changes that go beyond restoration or servicing to the machine's original or authorized state, you may be asking a different copyright or contract question entirely.

Who Can Rely On The Rule, And What Can A Repair Business Actually Do?

The statute speaks about the owner or lessee of the machine. That person or business may make the copy or authorize the making of the copy. For a repair company, this matters because customer instructions alone are not proof that every legal condition has been met.

A service provider should think separately about at least three issues.

One is machine status. Is the customer truly the owner or lessee of the machine being serviced? A reseller, contractor, or operator may use equipment without having the legal status described in the statute.

The second is software status. Does the machine lawfully contain an authorized copy of the program? A customer may assume so, but the repair business should avoid making promises or assumptions if the installed software history is unclear.

The third is job scope. Is the copy created solely because the machine is activated for maintenance or repair of that machine? If the work plan includes side uses, software extraction, or retaining a reusable image, the job may move outside section 117(c).

It also helps to separate section 117(c) from section 117(a) and section 117(b). Section 117(a) addresses the owner of a copy of a computer program, a different question from owning or leasing the machine. It concerns another copy or adaptation made as an essential step in using the program, or for archival purposes, subject to its own conditions. Section 117(b) addresses transfer of certain exact copies or adaptations under limited conditions. Those provisions are not a substitute for the immediate destruction rule that appears in section 117(c).

For repair businesses, the safest operational lesson is simple: do not treat "the customer told us to" as the full legal analysis. Authorization from the machine owner or lessee is part of the picture, but it does not by itself satisfy the statutory conditions.

Examples That Show Where The Boundary Usually Sits

Consider a hypothetical packaging machine that will not complete its startup checks after a sensor replacement. The customer owns the machine, the machine lawfully contains its authorized embedded software, and the technician restarts the unit so the software loads into working memory, runs required diagnostics, and confirms the machine is back to approved operating condition. If the temporary copy exists only because of that activation and is not retained after the job, that fact pattern is closer to the narrow section 117(c) scenario.

Now compare that with downloading a spare installer from the machine to a workshop laptop so the technician can keep a reusable copy for future service calls. That is a different activity. The copied software is no longer just a temporary result of activating the customer's machine for that customer's maintenance or repair.

The same concern applies if a repair shop creates a standard image from one machine and later uses it to service another machine, even if the models are identical. Section 117(c) is tied to activation of a machine that lawfully contains an authorized copy, for maintenance or repair of that machine.

Another risky example is unrelated access. If a machine must boot to allow a mechanical repair, that does not justify opening software modules that are unnecessary for activation under section 117(c). The statute specifically restricts access to program parts that are not necessary to activate the machine.

Adding new functionality is also different from restoring existing authorized functionality. If a technician uses the repair session to unlock an upgraded feature package, alter limits, or enable capabilities outside the machine's original or authorized specifications, section 117(c) may not be the right basis for the work.

None of these examples guarantees a legal outcome. The details matter, including the machine setup, the software authorization history, the service agreement, and what the technician actually did during the job.

A Practical Job Record For Maintenance Copy Issues

Section 117(c) does not specify a mandatory form, certificate, or fixed record-retention period. Even so, a short and consistent job record can help a business define what happened and what did not happen.

A suggested operational record could include:

• the machine identity, serial number, location, and customer details
• whether the customer is acting as machine owner or lessee
• the service authorization given for that specific machine
• the software environment the machine was already authorized to contain, as far as reasonably known from records, labels, or the customer's documentation
• the maintenance or repair objective, such as restoring operation after a failed part or servicing the machine to original or authorized specifications
• the activation step that caused any temporary copy to occur, such as a standard restart, diagnostic boot, or calibration startup
• which programs or program parts were required for activation and which were not needed for the task
• whether any software was copied, extracted, stored, transferred, or reused outside the activation process
• confirmation that any temporary copy created through activation was not used in another manner and was destroyed immediately after completion of the maintenance or repair, if applicable to the system architecture
• the completion time, technician notes, and any customer signoff on the machine being returned to its original or authorized working state

This kind of record does not prove compliance on its own. It does, however, help show that the business treated temporary-copy issues as part of job scoping rather than as an afterthought.

What Section 117(c) Does Not Give You

Businesses should be careful not to overread this provision. Section 117(c) is not general permission to bypass access controls, ignore license or service-contract terms, share installers, distribute software, or undertake every type of repair involving software-controlled equipment.

Those issues may involve other parts of copyright law, contract law, or other rules entirely. They require separate review based on the equipment, software license agreement terms, and business model involved.

That matters for both owners and service providers. A company may believe that because it can lawfully activate its own machine for repair, it can also keep a local bank of software images, share service media across affiliated entities, or override technical restrictions wherever repair would be convenient. Section 117(c) does not clearly say that.

Likewise, a repair business should not assume that every customer request creates a federal defense for every software-handling step in the workshop. The statute is focused on machine activation, necessary temporary copying, limited use, and immediate destruction after the maintenance or repair is complete.

If a job could involve a dispute over ownership status, authorization status, access controls, license limits, distribution of installers, or software modifications beyond restoration to original or authorized specifications, that is the point to get independent qualified US counsel involved for the specific facts.

How Small Businesses Can Reduce Risk Before The Job Starts

Most disputes are easier to prevent at intake than to explain later. A short repair intake process can help define whether the planned work is a narrow maintenance or repair task, or something broader.

Start by identifying the exact machine and asking whether the customer is the owner or lessee. Then pin down the operational problem being fixed. A work order that says "repair software issue" is usually too vague to manage section 117(c) risk well.

Next, map the technical steps you expect to use. Will the machine simply be restarted or booted into a standard diagnostic mode, or does the team expect to download, store, or move software outside the machine? If the answer is the latter, the business should pause and review the basis for that step rather than assuming it fits the maintenance-copy rule.

It is also sensible to separate required programs from unnecessary ones. For programs or program parts unnecessary to activation, section 117(c) allows no access or use beyond making the activation copy. If the planned repair needs other access, review the separate basis for it rather than treating the repair objective as permission.

Finally, make sure your technicians know the difference between restoring approved operation and adding features. The legal boundary may turn on that difference.

FAQ

Does Section 117(c) Let A Repair Shop Keep A Reusable Software Image?

Not on the facts described by the statute alone. The rule is limited to a copy made solely by virtue of activating a machine that lawfully contains an authorized program copy, for maintenance or repair of that machine, with no other use and immediate destruction after the job.

Can A Business Use Software From One Machine To Repair Another Identical Machine?

That is risky under section 117(c). The provision is tied to activation of the particular machine being maintained or repaired, not to creating a general service library for other machines.

Does A Customer's Permission Automatically Make The Copy Legal?

No. Authorization from the machine owner or lessee is relevant, but it does not replace the other statutory conditions, including lawful authorized software, limited purpose, restricted access to unnecessary program parts, and immediate destruction of the new copy.

Does This Rule Cover Software Changes That Add New Features?

Not comfortably. Section 117(d) frames maintenance and repair around keeping or restoring the machine to its original specifications and authorized changes for that machine. New capabilities may raise a different question.

Key Takeaways

• Section 117(c) is a narrow federal copyright rule for temporary copies created solely by activating a machine for maintenance or repair.
• The machine must lawfully contain an authorized program copy, and the temporary copy cannot be used for any other purpose.
• Any new copy covered by section 117(c) must be destroyed immediately after the maintenance or repair is completed.
• Programs or program parts not needed to activate the machine should not be accessed or used beyond what activation itself requires.
• Maintenance and repair under section 117(d) focus on making the machine work to its original specifications and authorized changes, not adding new functionality.
• Repair businesses should use clear work orders and job records covering machine identity, owner or lessee authorization, software status, activation steps, and any deletion of temporary copies.
• Section 117(c) does not itself answer separate issues such as access controls, software sharing, installer distribution, or broader contract terms.

For help preparing repair-scope documents, service terms and workshop records through the Sprintlaw platform, contact the team on (888) 449-8437 or team@sprintlaw.com. For exact entitlement questions or disputes about a particular machine, software copy, or service workflow, seek advice from independent qualified US counsel.