Don't Judge Your New Laptop on Day One
Our first experience with a new Snapdragon PC almost gave us the wrong answer. Here's what happened - and why your first few hours with a new Windows laptop may not tell you the whole story.
An early CheckMyARM test system almost failed its own test.
It was a new Snapdragon X Elite laptop, chosen in large part for exactly the things these machines are supposed to be particularly good at: long battery life, cool operation, quiet operation, and plenty of performance for everyday work.
For the first couple of days, it wasn't delivering them.
The fans ran far more often than expected. The machine was warmer than expected. Background CPU activity stubbornly refused to settle into what we'd consider a normal idle state. And most concerning, battery life looked nowhere near what we'd expected from the machine - or what professional reviews suggested we should expect.
Nothing was obviously broken. Performance was generally fine. The computer was completely usable.
It just wasn't behaving like the computer we thought we'd bought.
Then something changed.
Not all at once, and not because of some magic setting we discovered. Windows simply seemed to finish doing whatever it had been doing.
Background CPU activity dropped dramatically. Fan noise became very uncommon, rather than routine. The laptop became cool and quiet. Battery behavior improved substantially - and the already-impressive performance got a modest uptick as well.
The machine we'd expected finally showed up.
So we started wondering:
What exactly had we been testing for the first few days?
Windows was doing its homework
A just because you've reached the desktop.
Windows deliberately gets you to a usable computer relatively quickly, then continues a surprising amount of work in the background: installing updates and drivers, updating applications, indexing files for search, scanning content for security, synchronizing cloud data, performing maintenance, and more.
On Copilot+ PCs, Windows also performs . Microsoft specifically recommends keeping a Copilot+ PC plugged in while its initial search indexing completes.[1]
None of this is particularly mysterious. And none of it is necessarily a problem.
In fact, Microsoft's own procedures for testing Windows battery life tell us quite a lot about how much this background work matters.
Before Microsoft considers a PC ready for meaningful battery testing, its published methodology calls for completing Windows and application updates, installing current drivers, running a full antivirus scan, allowing to finish, rebooting, and then allowing the . It tells testers to verify that OneDrive synchronization and other cloud-connected background activity aren't still running during measurements. Microsoft even notes that Automatic Maintenance on a device that has just completed OOBE may take more than 1.5 hours.[2]
In other words, Microsoft doesn't judge battery life while Windows is still doing its homework either.
And the homework can create more homework
This is where a real user's new computer can look quite different from a clean test machine.
Our CheckMyARM system wasn't simply turned on and left pristine. It was being turned into someone's actual computer.
That included connecting it to a substantial OneDrive library.
Now consider what happens as a large collection of files arrives on a new PC.
OneDrive has work to do synchronizing them. Windows Search has new content to index. A Copilot+ PC may have additional semantic indexing to perform.[1] Depending on the files and configuration, security software may have additional inspection work to do. Windows and applications may generate metadata, thumbnails, caches, and other derived information.
We shouldn't pretend every file travels through some neat, predictable assembly line of background processes. Windows is much more complicated than that.
But the important point is simple:
So the effect of several simultaneous setup activities isn't necessarily just additive.
And the amount of work can vary enormously from one person to another.
Someone setting up a mostly cloud-based machine with a handful of applications may reach a quiet state fairly quickly. Someone restoring substantial synchronized libraries, installing a large software collection, and configuring years' worth of accumulated data may give Windows considerably more to digest.
That's one reason we don't think there's a useful answer to the question:
"How many hours does a new PC take to settle?"
Our system took unusually long - nearly three days before we were satisfied that its behavior had truly stabilized. We suspect the amount of synchronized data contributed substantially to that.
That's an observation from one system, not a recommendation to put every new laptop on a three-day timer.
The computer is usable. That's kind of the point.
It would be easy to frame all of this as a Windows flaw:
Why doesn't Microsoft just finish setting up the computer before letting me use it?
Because you probably wouldn't like the alternative.
Imagine finishing Windows setup only to be greeted by:
YOUR PC IS STILL BEING PREPARED
Please wait while we install updates, synchronize your files, scan
them, index them, optimize applications, and perform maintenance.
Depending on how much data and software you're bringing with you, that could be a very long wait.
Instead, Windows lets you use your computer.
And it really is usable.
Microsoft's own maintenance and testing guidance reflects the tradeoff: background work is expected, while deliberately waits for a quiet, settled system.[2][3]
That's a reasonable engineering tradeoff.
It also creates an interesting side effect.
Windows can be busy enough to consume meaningful energy without being busy enough to make your foreground experience feel obviously bad.
So instead of thinking "Wow, my computer is still doing a ton of setup work," you may think:
"Why is my brand-new laptop warm?"
"Why did the fan come on?"
Or, most dangerously:
"Why is the battery life so disappointing?"
Some background work waits for a quiet moment
There's another wrinkle.
Some Windows maintenance activity deliberately waits for appropriate opportunities rather than competing aggressively with foreground work. Microsoft's testing guidance also calls for rebooting and leaving systems idle before testing, and for ensuring battery tests begin from a .[2][4]
That means enthusiastically putting your new laptop through its paces isn't wrong, but it can reduce the opportunities Windows has to finish some work it's politely trying not to perform while you're busy.
There's a little irony there:
The harder you test the new computer, the longer you may remain in the period you're trying to test your way out of.
Again, that doesn't mean don't use it.
Quite the opposite.
Use your new computer
Take it off the charger.
Sit on the couch with it. Take it to work. Bring it to a coffee shop. Install the applications you actually use. Connect the services you actually depend on.
That's how a new computer becomes your computer.
We're not saying don't test the battery.
We're saying:
Don't declare the verdict yet.
If your brand-new laptop consumes 35% of its battery during an afternoon of setup, synchronization, updating, indexing, scanning, installing, and experimenting, that's a perfectly valid observation.
Concluding from it that the laptop will always consume 35% of its battery during a comparable number of hours is something different.
Observe freely.
Conclude carefully.
Why the professional reviewers may be getting a different answer
Professional battery tests can produce dramatically better results than some owner reports.
It's tempting to decide that one side must be wrong.
Maybe the professional test is artificial. Maybe the disappointed owner doesn't know what they're doing.
We think there's a better possibility:
They're both right. They're just measuring different things.
Professional reviewers need repeatability. [5]
That's appropriate.
A professional battery test is trying to answer:
How efficient is this machine under a known, reproducible workload?
The owner who unboxed a laptop this morning may be answering:
What happened when I used this machine during its first six hours in my house?
Those aren't the same question.
One is testing the house after construction is finished.
The other is checking the electric bill while the movers are still carrying furniture upstairs.
Both bills are real.
Context determines what they mean.
And then there are the reviews we all read
Spend enough time reading owner discussions of new laptops - particularly Snapdragon X systems - and a familiar contradiction starts to appear.
One person reports extraordinary battery life. Another says theirs lasts only a handful of hours and wonders what all the hype was about. Professional testing may show something dramatically better still.
Some of those differences have perfectly ordinary explanations: screen brightness and refresh rate, workload, battery health, applications, external displays, firmware, drivers, and plain old defective hardware all matter.
But there's another variable that's easy to miss:
When was the machine tested?
A new owner is understandably eager to find out whether the laptop they just bought lives up to its promises. So they unplug it, watch the battery gauge, listen for the fan, and start forming an opinion - often while Windows is still updating, synchronizing, scanning, indexing, and turning a factory-fresh installation into their computer.
That pattern shows up in real owner discussions.[6] It also shows up in independent reporting: PCWorld has specifically noted that first-day Snapdragon X battery life can be surprisingly low while a user is installing applications and running updates, then improve after setup.[7] Paul Thurrott documented a similar progression across two Snapdragon systems: disappointing early battery behavior followed by materially better results as the machines moved beyond initial setup.[8][9]
If an owner reports what they experienced, their review isn't wrong.
They really did get disappointing battery life that day.
The problem comes when a temporary observation becomes a permanent conclusion:
"This laptop gets terrible battery life."
That's one reason apparently contradictory reviews don't necessarily require somebody to be wrong. They may simply be describing the same kind of machine at very different moments in its life.
Is this actually an ARM problem?
Probably not.
And that's important.
Windows Update, Defender, Search, OneDrive, application updates, maintenance, and cloud synchronization don't exist because you bought an ARM processor. Intel- and AMD-powered Windows PCs perform background work too. The same question arises around Intel-powered Windows PCs. In one technically detailed Framework community discussion, users explicitly considered fresh-install Windows maintenance, updates, and indexing while investigating unexpectedly high power consumption.[10]
Apple even acknowledges a similar phenomenon.
Current versions of iOS and iPadOS can explicitly show Ongoing iOS Update or Ongoing Device Setup insights when background activity is temporarily affecting battery life and thermal performance. Apple advises users who notice worse battery life after an update to wait a few days and check again.[11]
So this isn't uniquely a Windows problem.
And it isn't uniquely an ARM problem.
But we think Windows on ARM creates an unusually good environment for misunderstanding it.
People buy Snapdragon laptops specifically because they've heard about exceptional battery life, cool operation, and quiet operation.
What do you do after buying one?
You look at the battery. You touch the chassis. You listen for the fan. You may even open Task Manager.
In other words, you're paying unusually close attention to exactly the characteristics temporary background work can distort.
That's not an excuse for bad battery life. It's a reason to make sure you're measuring the thing you think you're measuring.
So how do I know when it's done?
We wish Windows made this easier.
There isn't currently one big indicator that says:
Congratulations! Your computer has finished becoming your computer.
So don't watch a stopwatch. Watch the machine.
A few useful signs:
- Windows Update no longer has significant work pending.
- Microsoft Store application updates have completed.
- OneDrive reports that synchronization is up to date.
- Search indexing has substantially completed; Windows exposes indexing status under Settings > Privacy & security > Searching Windows.[1]
- Reboots requested by updates have been performed.
- When you're doing nothing, Task Manager repeatedly returns to genuinely low CPU, disk, and network activity rather than simply switching from one busy background process to another.
- Fan, temperature, and battery behavior become more consistent from session to session.
You don't need to obsess over every process.
You're looking for a pattern:
The computer repeatedly becomes boring when you aren't asking it to do anything.
That's probably a better than any number of hours we could give you.
Can I help it along?
Yes - mostly by letting Windows finish rather than trying to make Windows stop.
Finish
Install Windows, Store, driver, and application updates. Reboot when requested. Let cloud synchronization complete.
Facilitate
Keep the computer plugged in when convenient - Microsoft specifically recommends AC power while a Copilot+ PC completes its initial Search indexing.[1] Give it some powered-on, awake, idle time when you don't need it.
Observe
Watch Update state, OneDrive status, Search indexing status, and Task Manager until the machine repeatedly returns to a quiet baseline.
What we wouldn't recommend is frantically disabling Search, Defender, synchronization, Windows Update, or other services simply because Task Manager says they're using resources.
A painkiller can make you feel better.
It doesn't necessarily make you heal faster.
Suppressing the symptom may simply postpone work your computer needs to finish.
Help it finish.
But don't wait forever
There's an equally important other side to this advice.
Not every hot laptop is "still settling." Not every battery problem is Windows Search. Not every noisy fan deserves another day.
Display configuration, applications, drivers, firmware, peripherals, emulation, power settings, bugs, battery health, and the hardware itself can all affect the experience.
And sometimes a particular computer simply isn't right for you.
We're not suggesting you rationalize genuinely bad behavior until your return window closes.
We're suggesting something much narrower:
Give a new machine a fair opportunity to reach its normal operating state before deciding what that normal state is.
Then judge it.
That's what CheckMyARM is here to help you do.
Microsoft, give us the progress bar
There's one part of this experience we'd love to see improved.
Windows already knows a great deal about what it's doing.
It knows when updates are underway. Search knows when it's indexing. OneDrive knows when it's synchronizing. Defender knows when it's scanning. The individual pieces already know much of their own state.
Apple has already demonstrated the value of telling users when ongoing setup activity may temporarily affect battery and thermal behavior.[11]
Why not put the pieces together?
Something as simple as:
Your new PC is still settling in.
Windows is completing setup, updates, synchronization, indexing, and other background work. Battery life, heat, and fan activity may not yet represent normal use.
Keep using your PC. Keep it plugged in when convenient. We'll let you know when things quiet down.
We'd much rather have Windows tell someone "I'm still working" than have that person conclude "this new computer has terrible battery life."
Until then, we'll keep watching Task Manager.
Or maybe somebody needs to build that utility.
Hmm.
Don't judge it too quickly.
We almost did.
Sources & Further Reading
[1] Microsoft Support - Search indexing in Windows. Documents
traditional and semantic indexing on Copilot+ PCs, recommends plugging
in a Copilot+ PC for initial indexing, and explains where to view
indexing status.
https://support.microsoft.com/en-US/Windows/Experience/performance-optimization/search-indexing-in-windows
[2] Microsoft Learn - Device under test setup for battery-life
measurements. Windows 11 battery-test preparation guidance: complete
updates and drivers, update Store apps, run a full antivirus scan,
complete Automatic Maintenance, verify cloud activity such as OneDrive
isn't active, reboot, and "allow the system to settle before testing."
Notes that Automatic Maintenance immediately after OOBE may take more
than 1.5 hours.
https://learn.microsoft.com/en-us/windows-hardware/test/assessments/device-under-test-setup-for-battery-life
[3] Microsoft Learn - Automatic Maintenance. Background
maintenance architecture and scheduling guidance.
https://learn.microsoft.com/en-us/windows/compatibility/automatic-maintenance
[4] Microsoft Learn - Windows Performance Lab testing methodology.
Calls for completing Windows/Store updates, running a full antivirus
scan, rebooting, and leaving the system idle before testing.
https://learn.microsoft.com/en-us/windows/deployment/performance-lab/testing-methodology
[5] Tom's Guide - How we test laptops, tablets and PCs. Describes
controlled system preparation, updated drivers, testing with other
applications closed, and a repeatable web-browsing workload run until
the battery is exhausted.
https://www.tomsguide.com/computing/how-we-test-laptops-tablets-pcs
[6] Reddit / r/Surface - "Surface Laptop 7 - battery drains fast?"
A new Snapdragon Surface owner reports unexpectedly rapid battery loss;
discussion raises new-PC updates/setup activity among possible
contributors. See the community-source note below.
https://www.reddit.com/r/Surface/comments/1kf6awo/surface_laptop_7_battery_drains_fast/
[7] PCWorld - "10 ways Snapdragon AI PCs are just like
Chromebooks." Chris Hoffman notes that Snapdragon X battery life can
be surprisingly low on the first day during updates/app installation and
improve after setup.
https://www.pcworld.com/article/2405342/10-ways-a-snapdragon-x-elite-pc-is-just-like-a-chromebook.html
[8] Thurrott.com - "Snapdragon X Copilot+ PC: Early Thoughts on
Battery Life." Documents an initially disappointing first day while
installing updates/apps and treats setup activity as a likely factor.
https://www.thurrott.com/mobile/copilot-pc/304779/snapdragon-x-copilot-pc-early-thoughts-on-battery-life
[9] Thurrott.com - "Snapdragon X Copilot+ PC: More Thoughts on
Battery Life." Follow-up documenting substantially improved battery
results and a similar early-to-improving pattern on another newly
configured Snapdragon system.
https://www.thurrott.com/mobile/copilot-pc/304932/snapdragon-x-copilot-pc-more-thoughts-on-battery-life
[10] Framework Community - "Full day battery life on Framework 13
(Windows)." A technically detailed discussion in which users consider
fresh-install Windows maintenance, updates, and indexing while
investigating unexpectedly high power consumption on Intel-powered
Windows PCs. See the community-source note below.
https://community.frame.work/t/full-day-battery-life-on-framework-13-windows/37001/4
[11] Apple Support - If the battery in your iPhone or iPad drains
too quickly. Documents "Ongoing iOS Update" and "Ongoing Device Setup"
Battery Insights and explains that background update/setup activity can
temporarily affect battery life and thermal performance.
https://support.apple.com/en-us/120745
About community sources
We occasionally reference firsthand reports from forums and other communities because they can be valuable evidence of what real users are experiencing. We treat them as observations, not authoritative technical documentation, and don't use individual reports to establish prevalence or causation.