Category Archives: AI

Copilot Amazon Differ on TB5 NVMe Availability

I’m prepping for an AskWoody  story about RAID 1 setups on Windows 11. It had me popping open my half-dozen or so NVMe enclosures yesterday to see what I had at my disposal. Among my inventory, I found two identical NVMes (ideal for a RAID 1 test). I also found a Crucial T705 1TB PCIe x5 drive, which isn’t suited for any of my enclosures. It really needs Thunderbolt 5 or USB4 v2.0 to exceed the 40 Gbps speed limit that TB4/USB4 imposes. Imagine my surprise when Copilot said no such enclosures were available, while Amazon showed me at least half-a-dozen products for sale right now. Hence my claim that Copilot, Amazon differ on TB5 NVMe availability.

If Copilot Amazon Differ on TB5 NVMe Availability, Try Evidence

I work with Copilot near daily, especially on understanding and fixing Windows problems, issues and misconfigurations. Warnings about AI hallucinations are always worth remembering with Copilot. Why? Because it has repeatedly shown itself to be wrong or — as in this case — misinformed.  I reproduce Copilot’s response to my correction in which I provide the simple Amazon search that showed me 6-plus TB5 capable NVMe enclosures for sale at US$190 and up.

One big problem I see with AI information is that it includes no shades of grey. If Copilot and other AI interfaces could include confidence levels or probability of correctness, that might help. But no: Copilot, Google AI, Grok and so forth put forward their information as gospel truth. There’s a huge gap between Copilot’s initial flat statement that no TB5 NVMe enclosures are available, and its later correction to “TB5 NVMe enclosures exist, but most are early‑generation products whose real‑world performance is currently limited by host support and certification status.” Big difference!

As Always, Proceed with AI Cautiously

I don’t use or act on AI provided info unless and until I can confirm it through at least one (preferably, two or more) reliable public sources. This little “No it’s not; Well, yes it is…kinda/sorta” encounter demonstrates pretty well why that’s so. Indeed, for testing purposes I plan to buy one of the very enclosures Copilot told me yesterday didn’t exist. Today, it’s a different story!

Isn’t that just the way things go here in Windows-World sometimes? But at least, I’m going to be able to see if TB5/PCIe x5 Gen5 technology lives up to its billing when the Acasis enclosure shows up. If things work as reported, I’ll have an external USB drive that’s as fast as the internal drive on my production desktop.

Facebooklinkedin
Facebooklinkedin

Copilot: Driver’s Education

If you read yesterday’s blog, you already know that I spent most of the weekend with my Flo6 desktop in UEFI, booting, or at the command line in WinRE/WinPE. On the other PC next to my desk chair, I keep a Lenovo P16 Gen1 Thinkpad. I was running Copilot on that PC, looking for insight into making Secure Boot work on the Flo6. Simply put, you can’t ask for help in Windows when that OS isn’t running. During that process I ended up in class for Copilot: driver’s education became quite a concern as I had difficulty scrolling down to read longish replies to my prompts and queries.

What Copilot Driver’s Education Is About

Turns out my scrolling attempts were misguided. I didn’t really understand how the touchpad on the P16 works. As you can see in the prompt window I’m using in this post for a lead-in graphic, the P16 touchpad is  more oriented to gestures than to driving screen controls.

While I was working over the weekend, I simply popped in a wired mouse — complete with scroll wheel — and used that to speed scrolling while interrogating Copilot on the P16. After I had time to dig in a bit deeper, I learned that a two-finger gesture works for scrolling that touchpad quite nicely (two-finger sweep up to scroll down, down to scroll up — shades of Doc in the movie Cars).

Hah! I’ve been using Copilot since it first showed up over two years ago (June 2023) and didn’t know that this till this weekend. Probably because I still mostly drive with a mouse and not a touchpad. Now I know. Here in Windows-World, it’s the little things that sometimes make a big difference…

Facebooklinkedin
Facebooklinkedin

Secure Boot Pursuit Undone

We’ve been (and still are, I kid you not) snowed in here in Central Texas. With Winter Storm Fern bearing down on us, we started hunkering down here last Friday (1/23). On Saturday we had rain, sleet and snow, and woke up to snowy sights Sunday. Figuring I had time on my hands, I decided to see if I could get Secure Boot working on my Asrock B550 Ryzen 7 5800X Flo6 production desktop. Alas, after much wrestling with hardware and software, I saw my Secure Boot pursuit undone early, early this morning. Let me explain…

Why Is My Secure Boot Pursuit Undone?

Through all kinds of contortions (see list below) I couldn’t get the PC to boot with Secure Boot enabled. Let me enumerate some of them so you can appreciate what I tried and failed to get done this weekend:

  • 2 repair  installs of my current running OS
  • 1 “dirty install” (do not format partitions, but run installer which moves old OS into Windows.old and creates a new one: IDKYDT)
  • At least 2 each dism /restorehealth, sfc /scannow & chkdsk
  • Remove boot/sys drive from its M.2 slot to wipe NVMe config data from UEFI (have to remove GPU to access slot, sigh)
  • Swapped out old, soon-to-be obsolete 1070 Ti for 3070 Ti GPU.
  • spent over 30 hours fiddling with UEFI and Windows configs

After the “dirty install” I realized I’d hosed the primary MSA login on my main work machine. Not acceptable!! This morning, I built a new Macrium Reflect X Rescue disk, extracted the drivers from the Flo6, and restored my most recent backup (Friday afternoon, after I’d reorganized the boot/sys drive partitions).

Back in Business, Back to Work!

I learned a bunch about boot configuration data and related commands. I’m definitely completely up on booting the Flo6 into WinRE, Windows installer media, and the Macrium Rescue Disk. I’m much better acquainted with the Asrock UEFI than I’ve ever been before.

I also learned that my old MS Comfort Curve 4000 keyboard can’t (or won’t) send Fn key data to UEFI. Working on the ThinkPad P16 Gen 1 I soon figured out scrolling Copilot output was MUCH easier with an external mouse with scroll wheel than using the touchpad. Who knew?

And finally, I learned that Copilot will lead you all over the place trying to solve problems, heedless of time involved and consequence entailed. Sure, AI will tell you pretty much anything about Windows you want to know, but I wasn’t happy with the circuitous routes it took me on, and the circles it spun me through. Then it occurred to me: the words mendacious, malicious, utopia, and paradise all include AI, as do the phrases folie a deux and waste of time. Here in snowed-in Windows-World this weekend, I saw all those things play out. It was oddly engaging, but I’m glad it’s over.

Facebooklinkedin
Facebooklinkedin

Catching Up Can Be Hard to Do

I’ll admit it. I’m lazy. When I hooked up the Lenovo ThinkCentre Neo 50q Tiny PC a couple of weeks ago, I cheated. How? By hooking up the power, networking, video, keyboard, mouse and camera that had previously been driving the ThinkStation P3 Ultra Gen 2 mini-PC. Yesterday, I had some free time so I unhooked the former and reconnected to the latter. Given the hiatus a storm of updates followed (as expected). When I checked Reliability Monitor (ReliMon) this morning, I found a couple of unexpected errors for the Lenovo TSSIOMonitor (aka Super IO Monitor). When I asked Copilot for help reading those tea leaves, its response: “Catching up can be hard, especially after a prolonged idle period.”

Why Catching Up Can Be Hard

As I look at ReliMon for yesterday afternoon, I see a steady stream of updates and installs that start at 3:38PM and run through 4:09PM (60 in all). According to Copilot, TSSIOMonitor.exe is a Lenovo executable that’s constantly monitoring hardware. Its job is to throw errors when things don’t look or work correctly.

One potential cause of the error is when sensor data is invalid. Another is when driver data doesn’t match what the monitor expects. That’s precisely what happens when chipset drivers update, ACPI tables get rebuilt, embedded controllers reinitialize, and Super I/O registers may be unstable. Basically, the monitor was  using stale data to analyze a fresh situation, and erroring because of inevitable mismatches. Good to know.

Copilot Offers Insight, But I Must Assess Same

I’m getting used to asking Copilot to opine on system stuff when I need help understanding what’s going on. It certainly has more access to deep Windows arcana that I do, but I do notice occasional hiccups and hallucinations as it recites specific details. Indeed it sometimes goes off on tangents that don’t relate to my specific situation, but do play into the general circumstances and experiences around it.

This time, Copilot’s explanation makes good sense. And it helps me understand why such errors might occur when they did. It’s even comforting for it to tell me what I already knew: that a one-off or two-off error while a bunch of updates are underway isn’t terribly concerning. But we both agree that if it kept on happening (TSSIOmonitor.exe has been quiet ever since updates finished) there would be cause for concern, and possible action.

What Ronald Reagan said about nuclear arms monitoring apparently also provides to ingesting information from Copilot: “Trust, but verify.” Words to live by, here in a brave new AI-informed Windows-World.

Facebooklinkedin
Facebooklinkedin

Notification Reveals RDP Recall Gotcha

Here at Chez Tittel, there are 9 PCs in my office (6 laptops, 3 desktops). I tend to remote into 8 of those 9, working from my primary desktop. It’s running an Asrock B550 Extreme 4 with AMD Ryzen 7 5800X CPU, 128GB RAM, and an NVIDIA 3070Ti GPU. When I remoted into the ASUS Zenbook A14 this morning, a seemingly innocuous notification popped up in the RDP window, lower right. That notification reveals RDP Recall Gotcha that reads “Recall: Sign-in with Windows Hello to resume, no snapshots are being saved.”

When Notification Reveals RDP Recall Gotcha , Then What?

I followed the notification’s instruction: Walked up to the laptop, and let the camera log me in locally via facial recognition. When I fired up the RDP session again, there was no such notification showing. So, I checked Windows Hello status, and it shows that facial recognition is enabled and working for my phiz.

Then I checked Recall settings. It shows two interesting facets to what is apparently a real and present RDP gotcha:

1. For RDP to work, it’s necessary to turn off “Require Windows Hello login” in Sign-in Settings (aka “enhanced sign-in security”). For Recall to work this must be enabled.

2. Lack of enhanced sign-in security apparently makes the RDP session behave as if Windows Hello is neither enabled nor defined on this system.

Can you say “Catch-22?” Looks like if you want to use Recall on a Copilot+ PC, you can only do so through a local login. At least for me, it doesn’t work through RDP. Good to know! Though I can’t say I like this much, it is important to understand the limitations of Recall for users who might wish to take advantage of its capabilities.

Looks like Recall requires local operation. My conclusion: To use Recall (and I presume other AI features) go local, or go home. It’s always something, here in Windows-World.

 

 

Facebooklinkedin
Facebooklinkedin

Copilot sez: Enough, or Too Much

I’ve been excessively busy for the past few days, working on a legal matter. Along the way, I’ve learned a few things about Copilot’s limits. Turns out this tool is extraordinarily adept at running down references and finding sources that document specific quotes. But it’s also inclined to get stuck sometimes if my queries assume too much about what it already knows. That is, echoing William Blake’s Proverbs of Heaven and Hell Copilot sez: Enough, or Too Much?  Thereupon it becomes unresponsive. Yesterday, I had to reboot a machine to bring Copilot back to life. Even ending the task and restarting the app didn’t help. Weird!

When Copilot sez: Enough, or Too Much,
Do This…

So I had to ask Copilot “Why do you choke or become nonresponsive sometimes?” It had 5 answers, at least 3 of which corresponded to yesterday’s circumstances:

1. Overloaded or ambiguous input: Messages (prompts, I would say) are too long, too vague or contain multiple conflicting instructions.

2, Tool or system glitches: Copilot avers it relies on a whole box of tools (it names “search, image generation, memory, etc.”). Should one fail to respond, Copilot has to wait, and may stall while waiting.

3. Safety or Policy Filters: By design, Copilot won’t respond to prompts that violate its safety and policy rules. Good thing, and I hope they’re sufficiently broad and devious enough to foil hackers.

4. Missing Context or References: It’s too easy to assume Copilot remembers and understands what you’ve been asking it recently. TLDR version: not always. Be specific.

5. Complex Reasoning Bottlenecks: Technical, multi-layered tasks require Copilot to find, assemble and structure lots of information. Takes time, enough so that it might seem like forever.

I’m pretty sure yesterday’s hangup was a mix of items 2, 4 and 5. I try very hard not to overload my prompts, and what I work on shouldn’t trigger failsafes — of any kind. But hey, here in Windows-World, hang-up and delays are all part of the daily routine. Yours too, I guess?

Facebooklinkedin
Facebooklinkedin

Give Me Real Agentic AI, Please!

I’ve been using Copilot a lot more these days for all kinds of things, both personal and work related. But I have to say, I wish AI could DO more. That’s why this blog post is entitled “Give me real agentic AI.”

Let me explain what I think “real agentic AI” means. It means when you ask for information, AI goes out and does what it must to obtain that information. For example: yesterday I needed information about a specific patent case on the docket in a US Federal Court. First, I spent 15 minutes to access what I now understand is an old, obsolete docket management system. Then, I learned they’d switched to a different docket management system. Another long sign-up process loomed. Long story short: I opted out because of time and effort for another sign-up.

Why I Say: “Give Me Real Agentic AI!”

I want to be able to ask my AI agent to go out and find stuff for me that requires action — and perhaps even payment. Then, I want it to do that work, especially handling the niggling little details. I don’t want to have to jump a bunch of hurdles to get information I need. I want AI to do that for me.

In fact, handing the details involved in obtaining access is what I think AI is best used for. Let me decide what I need and focus on the results; let AI free me of the mundane details and hurdles necessary to get me those results. Then, we can both knock off and share a beer (I cheerfully confess Bender from Futurama is the inspiration for the — wait for it — AI-generated “agent avatar” that serves as the lead-in graphic for this blog post).

Facebooklinkedin
Facebooklinkedin

Copilot Leads Me Astray

I couldn’t leave it alone. I had to worry at the RDP problem between my old production desktop (i7Skylake) and the new one (Flo6). So I asked Copilot for help. Big mistake! It led me into an account replacement exercise that is still underway, 8 or 9 working hours later. Ordinarily, I wouldn’t ever spend that much time on fixing things. This time, I decided it was OK if Copilot leads me astray. And by gosh and by golly, that’s exactly what it did.

No Sense of Effort, As Copilot Leads Me Astray

I started following Copilot’s advice when we discovered that my user account primary directory differed from my login account name. It led me into deleting a bunch of registry keys and folders, to try to force the login process to restore my primary account. I was OK with all of this because I have a daily image backup to which I can always revert, if things go sideways.

But what I found so interesting was that Copilot had me do a bunch of stuff, without informing me how long it was going to take, and how much work was involved. Copilot may know how to solve technical problems — and I learned some useful stuff about how MSAs and local accounts work in the Registry Hives along the way –but it has no sense of balancing time and effort against the rewards that may or may not come, at the end of the day.

Copilot Offers Good Info, But It’s a Lousy Boss

I learned a valuable lesson. But I spent a lot of time learning it. Here ’tis: Copilot is a good source of info, and can guide you into and through all kinds of technical changes and tweaks to Windows. But it has no sense of how much time things take, nor how much work is involved.

Lesson learned: I can ask Copilot to tell me what needs doing, but I still have do decide if and when I want to do it. Others who let Copilot lead them into the briar patch should bear that in mind, as they lose sight of the clear fields around its edge.

Facebooklinkedin
Facebooklinkedin

Copilot AI-driven Settings Helpful

The first Copilot+ PCs made their debuts about 13 months ago (June18, 2024). I’ve been waiting to see some low-hanging AI fruit from that stock ever since, mostly with only ho-hum results. But lately, it looks like those PCs are gaining some useful capabilities accessible to ordinary mortals (like your humble correspondent). Indeed, I just read an Ashwin story for Ghacks with great interest. Entitled Microsoft rolls out a bunch of AI features for Windows 11, it shows Copilot AI-driven Setting helpful, given the right prompts. You can see some visual evidence in the lead-in graphic. Note: MS has a cool demo video about this on YouTube.

What Makes Copilot AI-driven Settings Helpful?

The impetus here is to ask Settings for help and information to address specific problems or issues. After monkeying with cursor size on one of my Copilot+ test PCs, I realized  I’d made it too big. So I prompted “cursor too big.” You can see what popped up before I hit the Enter key. Pretty helpful, and going in the right direction.

After I hit Enter, things got more focused and even more helpful. Here’s what showed up (including my overlarge cursor positioned at far right).

These are just the controls I needed to see, with the “Size” item the very thing I needed to fix my problem. That got me started on trying problems or issues in settings, to see where AI would take me. In most cases, it took me right where it would do some, and often the most, good. That’s not good, that’s great!

What Else Ya Got?

The afore-linked Ghacks story  provides further discussion of AI-driven facilities in Click-to-Do, Snipping Tool, Copilot Vision, and more. Could be that spending some time digging in might be rewarded. After all the hoopla and hype around AI of late, I’m glad to see something that’s helpful and potentially useful that’s also easy to understand and implement. Good-oh.

I’ll know that AI is really on my side in a constructive way when I can say to it “Examine these files and give me a specific analysis” (where that analysis depends on the contents) and get something useful back right away. AI can do that right now, of course, but it still leaves users responsible for the set-up and framing to put everything in context. When it can handle that part, too, then we’ll really have something.

Vital Thanks and Shout-Outs

First, I’d like to thank Ashwin from Ghacks for sharing his article. It’s what encouraged my to take the AI-driven Settings facility for a spin. Muchos gracias, mi amigo!

Second, I’d like to thank Jeff Witt and Amanda Heater in the Lenovo Reviews org for providing me with ongoing parade of test PCs. It’s been going on for years and years now and has been a great working relationship. Right now I’ve got TWO (2!) Copilot+ PCs for testing: a 2024 ThinkPad T14s Gen 6 (Snapdragon X1E-78-100 CPU) and a 2025 Yoga AIO 32ILL10 (Intel Ultra 7 258V) with a gorgeous 31″ display. They’re giving me the opportunities I need to learn and dig more deeply into Copilot+ features and functions. Thanks, thanks, thanks.

Facebooklinkedin
Facebooklinkedin

MS Updates Phi Silica for Copilot+ PCs

Very interesting. I was checking WU this morning on the peachy-keen Lenovo AIO 9i the company sent last month. Seems there’s an update available for a local NPU focused language model called Phi Silica (see lead-in graphic). Seems it’s focused on handling SLMs (Small Language Models) on behalf of Windows 11. It drives the OS’s new “AI facilities,” such as Recall, Click-to-Do, and so forth. As MS updates Phi Silica for Copilot+ PCs, I decided to dig in and learn more… So I asked Copilot, and it told me a LOT.

After MS Updates Phi Silica for Copilot+ PCs, Then?

Turns out there’s a special Update History section for this kind of thing, as the lead-in graphic shows. it’s called “AI Component Updates” and it indicates that Phi Silica has already been updated twice on this machine.

Phi Silica is a small-language model (aka SLM) purpose built for Copilot+ PCs. It runs as well as it can on such a PC’s Neural Processing Unit (aka NPU). It lets such models execute locally without having to use a cloud-based back end to do the heavy lifting.

Here’s how Copilot itself describes Phi Silica: It’s “a 3.3 billion parameter model, derived from Phi-3-mini, optimized for speed, accuracy and low power usage.” It “runs directly on the Snapdragon X Series NPU” (and obviously also their AMD and Intel counterparts, because the AIO 9i is an Intel PC), ” enabling fast private and offline AI tasks.” Phi Silica is what’s behind Click-to-do, on-device rewrite and summarization in Word and Outlook, and Windows Recall.

What Can Users Do with Phi Silica?

Quite a lot, as it turns out. When I asked Copilot if I could use my source files for the hundreds of books and thousands of articles and stuff I’ve written as the base for my own SLM, it said “Sure.” Then it pointed to the GitHub-based, open-ource Phi Cookbook as a good place for me to get started. I’m not sure I’m ready to go there, but it’s nice to know that door is open on Copilot+ PCs to someone with the time, wit and energy to make such a thing happen.

 

Facebooklinkedin
Facebooklinkedin