Category Archives: Insider stuff

Cloud File Service Update Secrets

If you read my Windows musings with any frequency, you know that I’m constantly patrolling my PCs to check for updates, patches and fixes. One thing I’ve been noticing lately is that updates for cloud based file services can be tricky. In response, I’ve been cataloging cloud file service update secrets. Let me explain…

What Makes Cloud File Service Update Secrets Useful?

In working with numerous law firms, publishers, and software companies, I find myself using various file services to exchange large chunks of digital stuff. These are usually ZIP files bigger than 25MB (the top end on email attachment size in many SMTP servers). Simply put, they provide a way to move lots of project files around. Most also offer enhanced authentication and security capabilities.

The following table addresses the various cloud file services I use, with some additional information. I’ll walk through things below.

Provider Name Trick
Google Google Drive No
Box Box Drive Yes
Dropbox Dropbox Yes
Microsoft  OneDrive Yes

Column 1 identifies the maker, 2 names the cloud file service, and 3 indicates if an update trick is required (Yes) or not (No). Notice that 3 of my 4 all require “tricks” for update. That mostly has to do with how often they update their software, and how often they push those updates to users.

Updating Box

Box itself describes the whole drill in detail at its support article entitled “Installing and Updating Box Drive.” The Windows TLDR version is: Right-click the Box icon in the TaskBar notification area; if an Update entry appears in that menu, click same. The following notification appears:

Click Update Box Drive and you’re done. If this doesn’t work, you must uninstall Box, visit the Box Download page, click the download button, then reinstall. Then you’ll be caught up. Easey-peasey, pretty much. But I’ve had to intervene with remove-replace manuevers several times over the past couple of years.

Updating Dropbox

The support article here is entitled “Update to the latest version…” As with Box, right-click the Dropbox icon in the Taskbar notification area. Check notifications. If an update is pending that hasn’t yet been applied, you’ll find an update button there. If you don’t see such a button, this is where things get interesting. You may not find the latest version at the download page. Here’s the trick: you need to visit the Dropbox Client Releases page instead, where you’ll want to grab the one near the top labeled “Stable Build” with the highest release number. You can simply install this without having to uninstall beforehand (this installer is smart enough to update an existing install if it recognizes one).

Updating OneDrive

Most of the time, OneDrive updates itself automatically as part of a Windows OS install and/or Office install/365 subscription. Some-times, you may have to intervene to get it working. This Business Insider article takes you through those steps in detail. Right-click the OneDrive icon in the Taskbar notification area, click Settings, then About. The OneDrive version entry comes up as a link. Click that link and you’ll open the MS OneDrive release notes page. Download and install the link at the intersection of Latest release build (left) and Production ring (above) and you’ll be good to go. As with Dropbox, the OneDrive installer is smart enough to update an existing installation if it finds one.

No More Secrets?

I have no more update secrets to share for cloud file services. That’s because these are the only ones I’m using. I’m sure, were I using more, I would have more secrets to share. But looking for the maker’s “how to update” support page is a good place to start, after which third party sources may shed additional light. Good luck with your own update secrets in that regard. Cheers!

 

Facebooklinkedin
Facebooklinkedin

AI Support Shows Up in Task Manager

After recent updates to Office on Windows 10 and 11, AI support shows up in Task Manager. It’s in a process named “ai.exe” of which you can see four instances in the lead-in graphic. That comes from my Windows 10 production desktop, but you can also see this running in Windows 11 versions as well.

That said, this facility comes from Office, not OS, upgrades. That means it won’t show up on PCs that aren’t running Office 365 or newer standalone versions. Nevertheless, I find it interesting that MS is moving AI into its own processing environment away from the executables for individual office components (e.g. Word, PowerPoint, Excel, Outlook, Teams and so forth). In fact, I’m guessing that the reason I see four instances in Task Manager reflect recent use of all four of those components recently on this very PC.

What AI Support Shows Up in Task Manager Says…

It tells me that MS is really getting serious about supporting AI throughout its application stack. I have to presume that support in the OS itself won’t be too far behind. Yesterday’s announcement that new Surface devices will support Neural Processing Units (NPUs) to speed AI workloads therefore comes as additional confirmation. To me,  this represents a shift in the kinds of things that OSes and apps can do, and handle, as part of normal operations. AI is here, and it’s not going away.

Read more about what’s going on here in this Windows Latest story dated April 10. It’s got much more detail about the processes, folders, and executables that have recently popped up in Windows 10 and 11. Personally, I find it fascinating, and hope to see tangible impacts in my work with Office apps soon. So far, after a six-day stretch during which I’ve worked in Word all day long (8 hrs +) I haven’t really noticed anything… But here’s hopin’, right?

Facebooklinkedin
Facebooklinkedin

Weird Windows 10 Winget Timeout Error

OK, I’m mystified by this one. Running through the usual update checks this morning, I noticed Winget was taking longer than usual to complete on my Windows 11 PCs. And when I checked my production PC, I got the weird Windows 10 Winget timeout error you see in the lead-in graphic. In fact, I ran it twice and got the same error both times. So I jumped over to my sole remaining other Windows 10 PC. While it also took longer than usual to complete, it did so successfully. What gives?

Weird Windows 10 Winget Timeout Error Is Opaque

What’s interesting — to me, anyway — is that I can’t find any useful information on how to fix this error. My most productive search string is “winget upgrade timeout.” Even so, I don’t see anything useful about this error nor how to fix it. Ditto for a search on “winget upgrade failed when searching source.” Interesting!

I just ran it again on the production PC and got some output (the manifest progress bar showed, then went blank, and the timeout error popped up again). I suspect some issue involving communication with the MS Store is also involved because “msstore” is identified as the source. That said, I access the Store app and update there without difficulty (though it, too, took longer than usual).

I just filed a Feedback Hub item. I’ll be interested to see if this gets a response. And that’s how things go in Windows-World sometimes. Stay tuned: this one might fix itself…

Note Added Early Afternoon

After noodling about on this for a bit, I found a PowerShell script at GitHub to install Winget afresh. I ran it, it reported success. But there’s no change to the timeout error. Resolution may have to come from elsewhere. We’ll see…

Note Added April 23 AM

OK then: winget is working once again, on all machines. As Pink Floyd once put it: It was apparently just “A Momentary Lapse of Reason.” Glad to have things working again. Wish I knew why they broke in the first place. But these things happen, here in Windows-World.

Facebooklinkedin
Facebooklinkedin

PowerShell Update Oddity Version Confusion

I’m flummoxed. I just upgraded PowerShell from version 7.3.3.0 to 7.3.4.0. It’s the latest stable version, as you can plainly see at GitHub. But even after updating, that preceding version still shows up using winget list powershell. An explicit uninstall request reports “No installed package found matching input criteria.” Hmm; WTF? I can only call this a PowerShell update oddity version confusion problem!

If you look at the left-hand tab in the lead-in graphic, you’ll see two versions of Powershell, one numbered 7.3.3.0 and the other 7.3.4.0. But when I try to uninstall the older one, winget can’t find it. And indeed when I try to open it in the right-hand tab, it comes up at the current (latest) version. I’ve seen something like this before, so I start thinking about causes and workarounds. Read on to see how I resolved this one…

Resolving PowerShell Update Oddity Version Confusion

I’m of the school that says if you can’t do it one way in Windows, you can almost always find another. If I poke around in my file system searching on “pwsh.exe” (the name of the powershell executable file), I see an app-based instance of the 7.3.3.0 version in ProgramFiles\WindowsApps. And sure enough, inside Settings → Apps, I find three (count ’em) versions of PowerShell. Here’s a snap:
AFAIK, I only need the middle one, so I right-click to uninstall the other two. When I’m done, I check Windows Terminal, and it tells me I need to reset my default profile. I do, and choose version 7.3.4.0. When I open a new Terminal window and run winget list powershell again, it shows only a single (and correct) version. Problem solved!

Now, all I have to do is figure out why the winget uninstall didn’t work, but a manual uninstall inside the Apps widget in Settings did the trick. I’m gonna have to think about that for a while… Stay tuned!

Facebooklinkedin
Facebooklinkedin

No Windows 11 Presence Sensing Here

I read, with some amusement and a sense of inevitability this morning  about a new Windows 11 feature. The latest Windows 11 Beta release (Build 22624.1610) supports presence sensing. Of course, special PC hardware augments are required. Apparently I have no PC new or advanced enough for this. Alas, no Windows 11 presence sensing for me!

What No Windows 11 Presence Sensing Means

If I remember correctly the notion of “presence” comes from computer telephony. It means the user is present and in front of the device (PC, in this case). Presence data helps guide whether or not requests and data go to users who’ve registered for specific conferences, events, and so forth. If they’re present, they’re included; if not, they’re not. And also, presence detection can work with Windows Hello (via IR camera sensing) to determine if a user is in front of the PC, to handle login and access.

My Lenovo P16 Mobile Workstation is pretty good at visual recognition. It’s also a mid-to-late 2021 vintage PC. Thus, I’m surprised that it apparently does not support Windows Presence. How do I know? There’s no “Presence sensing” entry in Settings → Privacy & Security → entry on that PC (or any of my other machines). Sigh. Why is that when MS announces a new Windows feature, I either don’t have it in the build, or it’s not supported on my PC? I guess it’s just a consistent turn of (ill) fate for yours truly.

I’ll see if I can remember to ask Lenovo to make sure this feature is present (pun intended) on my next eval unit. If so, I can check it out. If not, I don’t think it will kill me.

And so it sometimes (or often) goes, here in Windows-World. Stay tuned for news about other new stuff I don’t (or can’t) have. I’ll keep you posted.

 

Facebooklinkedin
Facebooklinkedin

Installing Updates Silently (or Not)

In dealing with the never-ending story of Windows OS and app/application updates, I sometimes marvel at the obvious and visible role that certain installers play in that process. Fortunately, some tools — like PatchMyPc — make a virtue out of “silently installing” such things, too. The arrival of a new Intel Bluetooth driver this morning on some of my PCs prompted the observation that installing updates silently (or not) has real value. For me, at least… (see lead-in graphic for my inspiration).

Why Installing Updates Silently (or Not) Matters

It’s all about the user interactions. Some installers demand that users respond to their requests for permission and acknowledgement before they’ll proceed. This morning’s Bluetooth item, for example, required no less than four mouse clicks to go through its paces.

This matters because it makes life interesting for admins who have to automate updates via scripting and automation. It also explains the broad appeal of a product like RoboTask and AutoHotKey (see this Windows Report story for some useful coverage of this topic). Capturing mouse movement and clicks and replaying them becomes a vital ingredient in turning something done “by user, by hand” into something that can run as part of a general scheduled update process. But in general, such things are best avoided if possible.

Going Down the Rabbit Hole…

Switching over to silent updates can be challenging, though. Take a look at this Spiceworks forum thread that walks readers through the requirements involved in working with Chrome templates and Group Policy Objects (GPOs). It’s kind of scary, but also pretty fascinating. There’s a lot of research and, sometimes, effort involved in putting complete update packages together for automated deployment. That’s the kind of stuff I like to observe, and learn from, when I have the chance.

 

 

Facebooklinkedin
Facebooklinkedin

Winget Discord Update Trick

I’ve got a new PC waiting in the wings to take over for my aging production PC. Right now, it’s ensconced in my son’s bedroom, where I use it as a test machine. He also games on it when he comes around. As a Discord user, he checks in on that app daily when he’s here. One of his tools pinned that app, so Winget can’t upgrade it through normal means (e.g. Winget upgrade –all or some equivalent). But I’ve discovered a Winget Discord update trick that works nonetheless.

Pinning Requires Winget Discord Update Trick

For some time now (as described in this July 2020 GitHub thread) users and programs can “pin” packages for Winget. This explicitly holds Discord to some specific version (or range of version numbers). It also means that unless Winget upgrade is targeted with a specific Discord version, it doesn’t perform the upgrade.

The trick to a successful upgrade is to use the –version parameter with Winget upgrade to explicitly specify the upgrade target. For example, I successfully upgraded the upstairs PC with this command:

winget upgrade Discord.Discord –version 1.0.9012

Note: I had to use the “full package name” for the Discord app (“Discord.Discord”). I also had to provide the complete version number (1.0.9012) following the –version parameter. After jumping through those hoops, the pinned version allowed the update. One presumes that the same approach will work for other pinned apps and applications with Winget as well.

It may take some squinting, but you can see Discord’s version info in the lead-in graphic at the far right. It reads “Host 1.0.9012 (30921).” To the left is a Terminal window that shows a successful targeted upgrade (update, actually) of the Discord app itself. It’s easy — if you know how. Those are the deets! And now, it’s all good…

Facebooklinkedin
Facebooklinkedin

Windows 10 PowerToys Registry Preview Issue

I’m not sure if what I’m seeing is general to Windows 10, or specific to my two remaining Windows 10 installs. But I’m seeing a Windows 10 PowerToys Registry Preview issue here at Chez Tittel. Don’t take it wrong — the tool works just fine. But you can’t use its built-in “Open file” button, nor the “Ctrl-O” key combo to open a registry (.reg) file. Instead, only a right-click on a .reg file in Explorer (or equivalent, such as VoidTools Everything) will do the trick.

What’s with the Windows 10 PowerToys Registry Preview Issue?

I wish I knew. Everything works as it oughter on Windows 11. As far as I can tell, the issue applies only to Windows 10. Given that there’s a relatively easy workaround, I’m guessing there’s some kind of simple gotcha preventing the Explorer hook-up in Windows 10 for Registry Preview “File Open” from working.

I’ve already tweeted @ClintRutkas, fearless team leader for PowerToys about this. Hopefully, that will help spur corrective action. But it reminds me that it’s always interesting to take new software facilities for a spin. Despite internal testing’s best efforts, stuff like this often pops up when more general releases occur.

Don’t Stop Your Own PowerToys Investigations

Please note that the issue — and Registry Preview itself, in fact — pops up only in the latest version. And, as you can see below that version number still starts with a leading zero. By convention, that means this is still a pre-release version out on extended beta test. These things happen with such software, for sure. But it’s fun to find one yourself now and then — just be sure to report in with your findings. Cheers!

Windows 10 PowerToys Registry Preview Issue.version-info

Facebooklinkedin
Facebooklinkedin

Reboot Releases Macrium Backup Volumes

If you’ve been reading this blog lately, you know I experienced a drive crash earlier this week (see “Bye-Bye Seagate…” for details). In the wake of that failure, I had to recover the very data volume that failed from a Macrium Reflect backup. That went off without a hitch. But I hit a snag when I attempted to unmount the volume, which normally requires only right-click menu navigation. Eventually I figured out — and confirmed — that a Windows reboot releases Macrium backup volumes.

An example of a mounted backed-up volume appears above; the normal menus below.

Normally, a two-step cascade provides easy access to unmount a Macrium backup volume. Not that time!
[Click Image for Full-Sized View.]

I’m Glad Reboot Releases Macrium Backup Volumes

After I’d finished grabbing the two folders I really needed from that backup I tried to unmount the volume and drive letter Reflect created to grant me access to its contents. No dice. When I right-clicked the Macrium Reflect entry, the all-important next-level “Unmount Macrium image” item shown above did not appear.

Geek that I am, I attempted to unmount it at the command line. But I couldn’t get PowerShell or Command Prompt to give me the details I needed to make that happen. (I simply couldn’t figure out how to get a GUID or other key drive ID details.)

I reasoned to myself: “Because Reflect mounted the volume, it must surely get unmounted if I reboot the PC.” And indeed, that’s exactly what happened. When I rebooted the PC, the volume that Reflect had mounted appeared no more.

As you can see from the preceding screenshots, it was just a momentary glitch. I mounted a different volume to shoot those images. This time, the right-click menu worked perfectly to dismount from the second image what shows up mounted (boxed in red) in the first image. Go figure!

Facebooklinkedin
Facebooklinkedin

Intel DSA Repair Lets Scan Complete

This morning, I read about a new Intel graphics driver over at Neowin. With 6  or more PCs likely to need an update, I starting using the Intel Driver & Support Assistant (DSA) to check things out. On one of my two Lenovo ThinkPad X380 Yoga PCs (8th gen Intel CPUs, 16 GB RAM, 1 TB SSD), the spinning balls for the system scan kept spinning … and spinning … and spinning … In looking for a way to fix things, I turned to an Intel Support note. That led me indirectly to learn that an Intel DSA repair lets scan complete.

How Intel DSA Repair Lets Scan Complete

I followed Intel’s advice to uninstall, then reinstall, the DSA app. Along the way, the installer offered a “Repair Installation” option( via Revo Uninstaller). “Hmmmm,” I thought to myself “Why not try this option first and see if it helps?” I did, after which the system informed me a reboot was needed to complete the process.

So I did that, too. And when the PC rebooted the next time around, the DSA system scan completed nearly instantly. After watching it grind for nearly two minutes earlier this morning, that came as a great relief. As irony would have it, DSA did NOT find new graphics drivers for me to install on that PC, either. Here’s what it told me instead:

Intel DSA Repair Lets Scan Complete.scan-complete

Despite Neowin’s alert, DSA finds no need for a new graphics driver.

The Installer Will Show “Repair” When Available

This did remind me that many application installers include a “Repair installation” option as part of the installer’s bag of tricks. This time, repair was in the bag — and thankfully, it worked. Problem solved. And the old “remove & replace” operation proves its value yet again as a strategy for fixing application and update issues, but with an interesting twist. Cheers!

Impatient? Direct Driver Link for 31.0.101.2121

If you don’t want to wait for Intel to bring you these drivers via DSA (it’s now early afternoon on release day and they’re still not showing up there), you can grab them from the Intel Drivers & Software downloads page: Intel 6th-10th Gen Processor Graphics — Windows. As for me and my curiosity, I’m content to wait for now…

Facebooklinkedin
Facebooklinkedin