What you need to know
- The Lenovo ThinkPad X1 Carbon with a 10th Gen Intel CPU is now available.
- The only variant on Lenovo's website with a 10th Gen processor is the Intel Core i7 variant.
- The Intel Core i7 variant with a 10th Gen CPU costs $2,609.
Lenovo's ThinkPad X1 Carbon is now available with an Intel 10th Gen processor. The new processor comes with a significant performance boost and new features when compared to the Intel 8th Gen processors that ship with other variants of the ThinkPad X1 Carbon. The only variant of the device that has an Intel 10th Gen processor is the Intel Core i7 version that costs $2,609 (opens in new tab).
Intel's 10th generation of chips increase performance over previous generations and also add support for Thunderbolt 3 and Wi-Fi 6 (802.11ax).
The Intel Core i7 version that runs on an Intel 10th Gen processor comes with 16GB of LPDDR3 memory, a 256GB SSD M.2 PCIe-NVME, and Integrated Intel UHD graphics.
The ThinkPad X1 Carbon features a woven carbon fiber finish, a thin body (14.95mm), and weighs 2.5 pounds. It also has a four-speaker sound system with support for Dolby Atmos.
While Lenovo's website only lists the Intel 10th Gen processor with the Intel Core i7, more versions running the latest processors are expected in the future.
The trusty powerful workhorse
The Carbon doesn't scream about specifications unless you bring up portability and LTE in the conversation. Still, it's a powerful notebook that can be relied upon to handle video editing and other intensive applications. It's now available with a 10th Gen Intel processor.
Sean Endicott brings nearly a decade of experience covering Microsoft and Windows news to Windows Central. He joined our team in 2017 as an app reviewer and now heads up our day-to-day news coverage. If you have a news tip or an app to review, hit him up at email@example.com (opens in new tab).
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.