An early defect is a manufacturing fault that was in the machine when it left the factory. It didn’t develop. You just hadn’t run into it yet.
That distinction is the whole thing. The fault existed on day one; your chance to act on it cheaply expires on day fourteen or thirty. So the useful question isn’t “is my laptop broken” but “how do I find out in time.”
What this guide settles is whether a given symptom is a defect at all, and who has to honour it if it is. The mechanics either side sit elsewhere.
- What to check, and when → what to check on a new laptop
- Turning a symptom into evidence (photos, repro steps, dates) → the detailed check for a device you just bought
Defect, or just unfamiliar?
A surprising share of “faults” in the first week are the machine working as designed on hardware you haven’t used before. Before escalating anything, rule these out:
- A fan that spins up for the first few days. Indexing, updates, and preinstalled software are all running. This settles.
- A screen that looks colder or warmer than your old one. Different panel, different calibration. Not a fault.
- A trackpad that feels wrong. Sensitivity and gesture defaults differ enormously between manufacturers.
- Battery life below the advertised figure. The advertised figure comes from a specific benchmark at a specific brightness. Real use never matches it (more).
- A key that doesn’t respond. Check the layout first. The key may not be where you think it is, or a modifier may be latched.
None of these are defects. Reporting them as defects costs you credibility on the one that turns out to be real.
Three shapes of failure
Real faults tend to fall into one of three patterns, and the pattern tells you how hard it will be to catch.
Dead on arrival. The port never worked, the speaker channel is silent, the pixel is black. Present from the first minute, findable in ten. These are the ones a browser check catches: a flat-color screen pass, a left/right speaker pass, a keyboard pass. Nothing subtle about them once you actually look.
Intermittent. Works most of the time. A key that misses one press in fifty, Wi-Fi that drops every few hours, a display that flickers on wake. These are the expensive ones, because they’re easy to dismiss as your own mistake and hard to demonstrate to support.
Drift. Gets worse over time: a hinge loosening, a battery dropping capacity faster than it should, a fan developing a rattle. Often not visible inside the return window at all, which pushes these into warranty territory.
Knowing which shape you’re dealing with tells you where to spend effort. Dead-on-arrival needs ten minutes of looking. Intermittent needs a log. Drift needs a baseline recorded early so you can prove the change later.
Making an intermittent fault reproducible
Support cannot act on “it sometimes does a weird thing.” Reproducibility is what turns a complaint into a replacement, and you build it by narrowing three variables:
When. Note the time each occurrence. Patterns emerge fast: only after sleep, only when warm, only on battery, only after an hour.
Under what. What was running, was it plugged in, was an external display connected, how long had it been on.
How often. Three times in two days is a fact. “Quite often” is not.
Then find the shortest sequence that triggers it and write that down as steps. You are done once you can get it down to close the lid, wait thirty seconds, open it, flicker appears. That sentence is worth more than any amount of describing.
Video helps disproportionately, especially for anything visual or audible. Phone footage is fine.
Some faults collapse into a single image.
Where a tool leaves its result on screen, as the keyboard check does, that screen is the evidence. “F7 doesn’t work” and a picture of the position that never filled in start the conversation in different places.
Who covers what
Three different things can apply, and they don’t overlap the way people assume.
The retailer’s return policy is the widest and the shortest. Inside the window, most retailers accept a return for any reason. You don’t have to prove a defect at all, which is exactly why finding anything early matters so much. You don’t need to win an argument, only to be inside the window.
The manufacturer’s warranty is longer but narrower. It covers defects only, and it usually means shipping the machine for repair rather than swapping it.
Consumer law sits underneath both, and it’s the part most people don’t use. In the UK, the Consumer Rights Act gives a short right to reject faulty goods outright, plus longer rights afterwards. Across the EU, the legal guarantee runs for two years. In the US it varies by state, with implied warranties and the Magnuson-Moss Act in the background. None of this replaces the return window. It’s what you fall back on when the window has closed and the manufacturer is being difficult.
The “within spec” conversation
At some point you may be told that what you found is within specification. Often that’s true, particularly for pixel defects and backlight bleed, where manufacturers publish thresholds.
Two things to remember. First, “within spec” is a manufacturer’s judgment about a warranty claim, and it says nothing about your retailer’s return policy, which usually doesn’t care why you’re returning it. Second, the threshold is theirs to set and varies wildly between brands, so a number quoted on a forum tells you nothing about your machine.
Inside the window, “within spec” is rarely worth arguing with. You have a simpler option.
The habit that matters
Check on day one so the obvious things surface immediately. Check again after a few days, once the machine has stopped doing new-computer things and started doing normal ones. Check once more before the deadline, with your notes rather than your memory.
That’s three short sessions. Nearly everything that gets discovered too late would have been caught by the second one.
Once you’ve found something, the detailed check for a device you just bought covers how to record it so it holds up.