Though the details aren’t terribly specific, MS has provided an inkling of when Copilot+ PCs running Intel and AMD CPUs should ship. In an item about a new incremental update technique dated July 15, MS provides the snippet depicted in the lead-in graphic above. This states that “Windows 11, version 24H2 will be available as a traditional feature update to all devices later this year.” Thus, I call this an MS Intel/AMD Copilot+ PC date drop — of sorts, at least.

What Does This MS Intel/AMD Copilot+ PC Date Drop Mean?

I confess: I’m reading somewhat between the lines as I interpret this. But I’m not alone: you’ll find stories at WindowsLatest, TechRadar, Windows Central, and elsewhere that draw the same conclusions I do. Of course, the words “later this year” could occur any time between now and December 31, 2024, so that stipulation is far from precise or narrowly targeted.

That said, I’m in accord with most industry watchers — including the afore-linked stories — in believing that 24H2 is likely to drop some time in Q4 2024. My best guess would be “after Thanksgiving, but before Christmas” to give room to steer around major end-of-year holidays and associated time off for breaks. But it could happen earlier, to get 24H2 out of the way before the holiday season kicks off in late November. Only time will tell…

Further Points of Possible Confirmation

Intel’s May 20 press release for its Lunar Lake CPUs reads “Starting Q3 2024 in time for the holiday season, Intel’s upcoming client processors … will power more than 80 new laptop designs across more than 20 [OEMs]…” A June 2 press release from AMD steers clear of dates for its Ryzen AI 300 Series CPUs, but does mention partnerships with ” Acer, ASUS, HP, Lenovo and MSI” that will surely ship at or about the time time that Intel’s OEM partners offer up their competing laptops and so forth.

Could it be that interesting options for end-of-year gifting might include snazzy new technology toys? MIght you or I want one? For sure!

There’s a new KB in circulation that claims to extend the reach of Copilot in Windows 10. That would be KB5033372, released December 12. But alas: on the lone eligible  physical PC and various Windows VMs here at Chez Tittel, Windows 10 Copilot remains elusive. It runs fine inside Edge, but will not show up as a Taskbar or Start menu item on any of their desktops. Sigh.

Why Windows 10 Copilot Remains Elusive

A quick visit to the KB announcement (link in preceding paragraph) gives me an excellent idea why my PC isn’t getting Copilot. Because some multi-monitor set-ups are subject to “mysterious icon migration” across or among desktops, MS has blocked it for such configs. Here’s what they say:

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration.

And wouildn’t you know it: my Windows 10 PC runs with dual Dell UltraSharp 2717 monitors. That definitely accounts for my physical PC’s lack of Copilot. But I’m not so sure about the VMs. It may stem from my typical mode of access to them (using one of the two just-mentioned monitors) or it may be something else.

A Ray of Hope?

In the same KB announcement already cited MS also says that they’re “working on a solution and will provide an update in an upcoming release.” Here’s hoping that release is upcoming sooner rather than later!

And once again, I’m a Johnny-come-lately among all those already in the vanguard. But hey: that exactly the way that things go here in Windows-World. Once more with feeling, I guess!!

Dang! I’d have to call my desktop experience “a swing and a miss.” I jumped on the KB5023378 Preview update, expecting to get Copilot out of that amendment. Wrong! Among the first words in the afore-linked update Support note, key Windows 10 Copilot limitations emerge. This includes this scoping statment: “This [Copilot addition] only applies to devices that run Home or Pro editions…” (emphasis mine). As you can see from the lead-in graphic for reasons that are too long and tedious to explain, this PC is running Windows 10 Enterprise. Sigh.

Bitten By Windows 10 Copilot Limitations

Sigh. It just goes to show that my personal dark cloud hasn’t quit hovering in the vicinity. I’ve often observed that if MS slides an update out as a gradual release, my PCs are invariably in the rear guard. This is something of a spin on this all-too-familiar situation, but nontheless an amusing one.

Fortunately, my physical desktop is not the only Windows 10 image I can run. I just jumped over to the ThinkPad P16 Mobile Workstation where I have a couple of Win10 images from which to choose. My cleanest one (installed last week for an AskWoody column) is installing same right now. When it reboots, I expect to see a Copilot icon in the Taskbar. Here goes…

Overall, install time on a 4GB Gen2 VM was quick. The whole thing took under 3 minutes to download, install, then cycle through post-reboot update processing. Good stuff. But did I see Copilot on the Taskbar when it was all done? Nope.

I had to turn on and relaunch the VM to come back from the update reboot. And another reboot didn’t bring it up, either. Nor did a right-click in the Taskbar show a Copilot control. No Copilot item under Settings → Personalization, either. Very interesting. I’m obviously going to have to learn more to get Copilot working on my Windows 10 Pro VMs. Should be fun: stay tuned!

That Old Familiar Sensation

I see in the Windows Latest coverage (Mayank Pamar) that “Microsoft has also warned that the feature may not be available on devices with compatibility issues, including devices with an incompatible app.” Why do I get the feeling that includes either my ThinkPad P16 Mobile Workstation or its Hyper-V runtime environment for my 2 Windows 10 VMs on that machine?

Note Added December 6: Maybe I should be grateful none of my Win10 PCs got Copilot? I’m seeing numerous reports that MS has put updates for both 10 and 11 on hold because of Copilot issues. I guess waiting is better than troubleshooting problems of Microsoft’s making. Isn’t that just the way things go here in Windows-World?