Inching toward Flo6 Cutover

OK, then. I’m just about there. But it’s been a much wilder ride than I expected, as I keep inching toward Flo6 cutover. That is, I’m almost ready to put the 5800X Flo6 build where my i7Skylake PC is right now. I’ll also leave the i7Skylake running for a while to pick up missed bits and pieces, as they inevitably come up. Let me tell you what’s happened so far…

Steps Involved in Inching toward Flo6 Cutover

In my July 28 post, I listed remaining steps before I could switch from old production desktop to new production desktop. Those included:

  • MS Solitaire: turns out I had to find and run a recovery utility to figure out to which MSA my stats belonged. Only then could I bring up the right account. Took about half an hour: done.
  • Macrium Reflect: 9AM full backup configured and running. This turned out to be dead easy, compared to the other items. Took all of 5 minutes, then another 10 minutes to fire off daily backups.
  • PaintShop Pro: Turns out 2023 is as new as it gets. I didn’t need to buy a new version, but I had to decommission the install on the i7Skylake before I could install and activate the Flo6. Also took about half an hour, most of which was figuring out how the heck to log in. Eventually, I figured it out and got it done.
  • PDF reader: I couldn’t get Nitro Pro to send me an email to reset my password for love or money. That took half an hour. So I switched to Adobe Acrobat Pro. Murphy struck again! The default Acrobat Pro installer — the one on its primary download page — doesn’t work on Windows 11 (at least not on the Flo6 install). It took me almost an hour to find and use the company’s standalone installer instead. That worked, but sheesh: a PITA!

Ready to Switch…

It’s after 5 PM on July 31 (Thursday), so I’ll unplug everything for both systems, switch their locations, and plug them back in after lunch Friday. Hopefully everything will come up as it should. If not, I’ll report further in an addendum hereto. With finger crossed, I’m hustling through the morning so I can get this handled in the afternoon. Wish me luck!

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

Lenovo IdeaCentre Mini X SFF PC

OK, then. Color me surprised. I’ve been keeping an eye on this stuff, and this one got past me. Looks like Lenovo has been selling a small form-factor (SFF) PC with a Snapdragon X processor since April. It’s the Lenovo IdeaCentre MiniX SFF PC, as depicted in the lead-in graphic (front and rear views at top and bottom). I’d tried signing up for the Qualcom devkit early this year, but it never came through. This looks like a worthy successor, and is available at the Lenovo Store for US$750 or thereabouts.

I like the Lenovo IdeaCentre Mini X SFF PC, But…

The unit is small and reasonably well-endowed: X1P-64-100 ARM Snapdragon X, 32 GB RAM, 512 GB Gen4 NVMe SSD, Intel Wi-Fi7, and more. It’s got 2 10Gbps USB-A and 1 10Gbps USB-C ports on the front (plus an audio minijack). There’s more on the back, including GbE RJ-45, 2x10Gbps USB-A, USB-C 40Gbps (USB4), HDMI 2.1 and DisplayPort 1.4a. In fact, it’s got many more ports than the Qualcom devkit ever offered, and that never materialized.

Why, then, is there a “But…” at the end of the preceding heading? Because of late, low-end Snapdragon X laptops cost less than this SFF. That is, they include a screen and a keyboard,  but cost less. Admittedly, such laptops usually lack RJ-45, HDMI or DP port, and also feature fewer USB ports than you’ll find in this SFF PC. Indeed, even Lenovo offers a lower-priced Snapdragon X unit (the IdeaPad Slim 3X, available at Best Buy for US$550, was discounted another US$100 recently during Prime Days).

All this said, I’ve had good luck with Lenovo SFF PCs, and have asked them to send me one of these for review if they can. But if you’re looking to “go low” on price and are OK with reduced RAM, CPU and storage, you can spend less and get a laptop instead. Hey, it’s your PC, so it’s your call, too. I’m interested, but for many a laptop will be a better choice. Copilot says that Lenovo, Acer and Asus have models under US$600 right now, with more such expected from Dell and HP later this year.

Facebooklinkedin
Facebooklinkedin

MS Support Eases Office 2024 Transfer

I guess it was inevitable. As part of my Microsoft MVP award benefits I get a license for Office 2024 for Home and Business. Turns out it’s a single-use (single device) license. I had installed it on a test machine last year, and returned same without uninstalling that software. When I tried to install it again on my nearly-complete replacement desktop, I couldn’t activate my valid license because it was already in use. I knew what I had to do — put a call into Microsoft. But to my great surprise and delight, MS Support eases Office 2024 transfer. I did it all via online chat, too.

How MS Support Eases Office 2024 Transfer

Here’s how the process went. I followed a license transfer link on the MS Support pages (depicted as the lead-in graphic). Then, I logged into that page using the same MSA tied to that license. Next. I entered “transfer license” into the Need more help? field, and selected the resulting “Transfer your Office license…” at the top of the options list. Then I clicked “Contact Us,” and started an online chat with MS support rep Kath (screen name “Kathleen”).

I’ve been on the phone with MS Support dozens of times in my 3-plus decades of working with Windows and Office. This call went as smooth as glass. Interestingly, Kath sent me an image (.img) file to use as my Office installer (that’s a first for me). But I knew enough to mount that file as I would an ISO and run the installer from there. The install went through without a hitch, and when I fired Word off for a first run, it prompted me for the license key. And this time, because Kath had unbound the license from its previous device, the key was authenticated and activated. I’m in business!

The Vexing Climb to Working Outlook

I futzed around with the Outlook app for a while, but wasn’t able to get it to work. That’s because my email provider uses a non-standard domain name for its outgoing SMTP mail server, not the standard default (smtp.mailchannels.net). The Outlook (classic) client provides the facility to override that default, but I couldn’t figure out how to make that happen in the app.

Long story short: I’ve got nearly everything I need to transition from the old i7Skylake desktop (working on it right now) to the new Flo6 desktop (running an RDP session into it right now). I’ll run both systems in parallel for a while, but switch Flo6 into service on my actual desk Monday, and move i7Skylake to a monitor on the next desk over in my office. That way, as I transition from the old machine to the new, I’ll retain easy access to the old to grab anything I realize I’m missing on the new machine from its predecessor.

This turned out to be a great way to get over the Outlook hump yesteday, in fact. When I couldn’t get the Outlook auto-configure to work, I was able to open the old client, examine its configuration in detail, and see the default-vs-actual domain name issue for outgoing mail. Very handy! I’m sure I’ll be doing that again in the next week, probably  several times.

What’s Left, Transition-Wise?

I’ve still got to set up and customize PowerShell (install OhMyPosh, switch to a compatible font, add bunches of tools and utilities, etc.). I will also check over what’s running on i7Skylake and decide what I want to move from old to new PC. At a minimum that will include MS Solitaire, some kind of PDF client, Amazon Kindle, Audacity, possibly a new Corel PaintShop version, Jabra Direct (for my awesome headset), Powerchute Serial Shutdown, UniGetUI, VS Enterprise, and Zoom workplace.

That should — and probaby will — take a while. I’ve been using my current desktop since 2016 more or less daily, so it’s still going to be something of a shock to switch. Stay tuned. I’ll keep writing about this, as it remains a major preoccupation for me coming up.

Facebooklinkedin
Facebooklinkedin

Microsoft 365 Apps Get EOS Dates

It’s possible I’ve been around the Windows-sphere for too long. I wanted to entitle this blog post “When MS Will Stop Updating Office on Windows 10.” But that’s not what MS calls things anymore. First off, EOS is “End of Support” which means no new feature updates, with security updates continuing through October 20, 2028. Second, Office doesn’t fit the bill: in today’s cloud based subscription model, it’s Microsoft 365 Apps that people use. So, when I say Microsoft 365 Apps get OES dates, I’m preparing to tell you when those apps won’t get new stuff from MS for those running Windows 10. Let me tell you more…

Note: the official end of life date for Windows 10 is October 14, 2025. That’s the basic backdrop against which all of these other dates play. So keep that in mind!

How Microsoft 365 Apps Get EOS Dates

On June 24, MS Learn published an article entitled Windows 10 end of support and Microsoft 365 apps. It’s worth a read-thru, but here are those dates, quoted verbatim (I bolded the dates and associated versions to make that info super-easy to pick out):

Devices running Microsoft 365 Apps on Windows 10 will receive feature updates until Version 2608 is released on the following dates:

  • August 2026 for Current Channel (including all versions for individuals and families)
  • October 13, 2026 for Monthly Enterprise Channel
  • January 12, 2027 for Semi-Annual Enterprise Channel

Devices will remain on Version 2608, receiving only security updates until October 10, 2028.

Customer Supports Gets Constrained, Too

After October 14, 2025, Microsoft 365 Technical support continues to function, but becomes subject to certain limitations (see the Learn item cited earlier for details). Basically, MS Support will try to move affected users to Windows 11 to get in the mainstream. Otherwise, assistance is limited to troubleshooting help, with “technical workarounds…limited or unavailable.” No bug logging or product update requests, either.

The End Is Near, Get Ready for Zombification…

Windows versions sometimes experience a life after death, through Extended Support Updates and related measures. These can keep things in a kind of “living dead” mode. But companies and users who depend on Microsoft 365 should clearly prepare to make the Windows 11 transition if they want to get the best and newest capabilities out of their productivity suite. You may not need to repent because the end is near, but you should get ready to switch over for best outcomes and results.

Here’s a shout-out to Martin Brinkmann at ghacks, whose July 14 story Microsoft reveals when Windows 10 customers won’t get Microsoft 365 Apps updates anymore clued me into the MS Learn pronouncements and their content. Danke schön, lieber Martin.

Facebooklinkedin
Facebooklinkedin

24H2 Install Includes Up-to-date Store Apps

I learned some new Windows-speak this morning, I think. First, I read stories at WindowsLatest and Thurrott.com that mention “inbox” and “in-box” apps respectively. Then, I read the MS Tech Community post that inspired their interesting assertions. Seems that Thurrott’s use of “in-box” is probably the most appropriate nomenclature. What’s under discussion is the update status of MS Store apps as a new install of Windows runs for the first time. Indeed, a new 24H2 install includes up-to-date Store apps, for ISOs and installers (e.g. the Windows 11 Installation Assistant)  dated June, 2025, or later.

Why 24H2 Install Includes Up-to-date Store Apps Matters

In earlier Windows 11 installs, one of the first post-OOBE tasks the OS undertakes is a full-scale update of built-in Store apps. This occurs via the Store’s update facility. WindowsLatest observes this means that up to 36 apps are covered. In turn, that saves time and bandwidth. Under this new regime, apps included in the OS image get newer versions. Here’s what the afore-linked blog post says:

…newer versions of the inbox Microsoft Store apps [come] preinstalled instead of the release-to-manufacturing (RTM) version. This includes updated ISO images, virtual hard disks (VHDs), and Azure Marketplace images.

Basically, this means that MS now provides images with more up-to-date versions of Store apps. My take is that the actual update count depends on when download images got built.  MS replaces them on at least a quarterly schedule. Thus, this means fewer Store updates than in earlier Windows versions (23H2 and lower).

Good news, of a singular and restricted sort, here in Windows-World. I’ll raise a small cheer, and a word of thanks, to the Windows team in response.YAY!

Facebooklinkedin
Facebooklinkedin

BlueScreenView Version Unknown Stymies WinGet

I guess it was predictable. Having worked through various version mismatch errors with WinGet, it seems inevitabled that a package focus might fail to report its version info entirely. That seems to be what’s going on with Nir Sofer’s otherwise excellent tool for inspecting Windows crash dumps. But, as you can see in the lead-in graphic, the program fails to report its own version info. Thus, BlueScreenView version Unknown stymies WinGet updates. Sigh.

Depicting BlueScreenView Version Unknown Stymies WinGet

One standard technique for solving WinGet version info issues is the tried-and-true uninstall-reinstall manuever. That said, its successes depend on the developer fixing version mismatches in the packages that WinGet stores in its database. As you can see in the lead-in graphic, that’s NOT what happens with BlueScreenView.

What you see in that graphic is a sequence of efforts to fix the unknown version info for BlueScreenView (BSV, for brevity):

1:  WinGet upgrade shows that BSV has a version number “that cannot be determined”
2-3: WinGet goes to work to uninstall, then reinstall BSV
4: A repeat of Winget upgrade shows that BSV’s version number remains unknown

Alas, this won’t be fixed until Mr. Sofer does something to address the version information stored in the package data. I’m sending him some feedback to that effect after I finish this blog post.

Let’s see what happens next. It’s always something, here in Windows-World. I enjoy digging into WinGet problems as they come up, so that’s what you often hear about from me. Cheers!

Facebooklinkedin
Facebooklinkedin

NZXT H6 Flow Build Comes Together

Allrighty, then. My “new” primary desktop build is almost completely done. I still have some software to install, and some file transfers from old to new to complete. But the hardware configuration is finished. As this NZXT H6 Flow build comes together, I’ve overcome some interesting hurdles and learned something I probably should have already known. Let me fill you in…

Deets: NZXT H6 Flow Build Comes Together

The case itself is perhaps the roomiest I’ve ever worked with. The split-level design  features the motherboard and plug-in elements above, with PSU, drive cage and cabling below. Very easy to work on, and far fewer cable routing shenanigans than I’ve ever run into before. Over the years — including a lengthy stint of motherboard, RAM and storage reviews for Tom’s Hardware in the early 2000s — I’ve probably built 100+ desktop and SFF PCs. From the perspective of ease and comfort, this one rules. First ever build, in fact, without cutting my fingers on the air cooler’s fins. Good-oh.

Here’s a BOM for the build, excluding the already-mentioned case [for which I paid US$110; other current prices in square brackets]:

  • Motherboard: Asrock B550 Extreme 4 (AM4) [US$185]
  • CPU: AMD Ryzen 7 5800X (8 cores/16 threads, 3.8 to 4.7 GHz, AM4, TDP 105W) [US$170]
  • GPU: NVIDIA 3070 Ti [US$600]
  • RAM: 128GB (4×32) DDR4-2666 [US$146]
  • NVMe: Sabrent Rocket Q 2TB[US$80], Samsung 990 EVO 4TB (2ndary)[US$200]
  • Hard disk: Toshiba DT01AC300 3GiB (2.72 TB in Explorer)[US$77]
  • Total system cost, not including monitors:  US$1,568

My ASUS Thunderbolt5 EX didn’t make the cut, because the B550 lacks a USB4/5 header for the device to plug into. Alas it won’t work without motherboard support. Sigh. I should have known, but there it is.

Issues Encountered and Overcome

The only build issues I ran into were:

  • Remembering how to re-insert the below-deck HDD cage. (A quick trip to YouTube took care of that in a hurry. Turns out to be a drop in, then slide up to lock into position kind of maneuver. Dead easy, once you see somebody else do it. Go YouTube!)
  • Getting the hard disk recognized in Device Manager. (None of my SATA devices showed up in Windows Device Manager or Disk Management. I used a temporary SSD-to-SATA device to ensure it was getting power (it got warm). So I knew it was a software issue. Thus, I was inspired to reload the “Standard SATA AHCI Controller:” right-click  the entry, Update driver, Browse my computer for drivers, Let me pick from a list…, reload the only entry showing. The plugged in SATA drive appeared immediately thereafter. Yay!

No drives appeared until I reloaded the standard SATA AHCI controller driver. Then, they popped right up.

Otherwise, this was a terrific, if time-consuming, experience. Because I must wear reading glasses now for close-in work (cataract surgery last fall), I had to give myself extra light and room for the build. I ended up taking over the island in our kitchen (covered with old towels) for the initial assembly, and then for final cable arrangement and clean-up. Except for the SATA HDD and the lack of USB4 support that knocked out the Thunderbolt5 EX, everything worked on the first try. Amazing!

IMO, things turned out extremely well. I’ll be switching over to this build sometime this week. Stay tuned: I’ll tell you more soon.

Facebooklinkedin
Facebooklinkedin

Microsoft MVP (Windows) 2025 Award

MS canceled the old Windows Insider MVP program as of the end of 2023. I had apply for the Microsoft MVP instead, and got awarded an MVP (Windows) in 2024. I’ve just finally understood — thanks to Copilot — that the cycle runs from July 1 of one year to June 30 of the next. Yesterday, got email saying I’d been awarded the Microsoft MVP (Windows) 2025. I’m pleased and relieved to make the cut for another year. The lead-in graphic sums things up nicely.

Beyond the Microsoft MVP (Windows) 2025 Award

How did qualify for this award? I submitted an application around the start of 2025. It summarized my activities with Windows during  2024. They included:

  • 200-plus blog posts here at edtittel.com. [Average frequency just over 4 days a week, all year long.]
  • 3-plus dozen articles on Windows topics for online publications in 2024. Outlets included ComputerWorld, Tom’s Hardware, AskWoody and TechTarget. [Average frequency just over 3 pieces per month.]
  • Online participation at Tenforums and Eleven Forum
  • Ongoing social media interactions with the WinGet, PowerShell and PowerToys teams
  • Daily posts on Windows topics including blogs, observations, news and administrivia on X, Facebook, LinkedIn, Blue Sky, and Mastodon [Average frequency 10 items daily.]

Frankly, I’m glad the MVP team at Microsoft decided my level of activity was enough to qualify me for another year. I’ve been doing pretty much the same thing since I got the award through an old friend and former WIMVP in 2018. I hope to keep at it for some years yet, until I’m ready to retire “for real.” Indeed I’d be happy to keep at it for another decade or longer. We’ll see: the spirit is willing but I’ll have to see how the flesh holds up.

Learn More About Microsoft MVP

Visit the Microsoft Most Valuable Professional home page for more information about the program, including how to nominate somebody for this award. You can also learn how you yourself might qualify for same. And you can look up profiles for the current crop of MVPs, including yours truly, should you be so inclined. Glad to be a member of this select community, arguably one of the key cornerstones of Windows-World.

 

 

Facebooklinkedin
Facebooklinkedin

Author, Editor, Expert Witness