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!

Before I got turned in the right direction with APC PowerChute software yesterday, I’d already installed two different versions (see post). Each of them runs as a systray app. That means it’s set up as a startup task, and keeps one or more Windows processes running constantly. It turns out that neither app was exactly what I wanted, so I needed to uninstall them. Alas, the developers didn’t — and still don’t — include an exit option in the right-click menus for these beasts (see lead-in graphic). Thus, I found myself first undoing systray entanglements before Revo or built-in uninstallers would work. Let me explain…

What’s Involved in Undoing Systray Entanglements?

Revo Uninstaller gave me a good clue when I tried to uninstall either version of the PowerChute software. It flashed a warning that told me the software was running. I should try uninstall again when it was turned off. What, exactly, does that entail? Good question!

I had to open Task Manager, find all related processes and kill them. For the old PowerChute, that was easy: I just killed its one and only process. For the new PowerChute Serial Shutdown (PCSS) utility, I had to kill once process named pcss-systray.exe, and another named pcss-agent.exe. Indeed, to be on the safe side, I chose the right-click “End process tree” option in case there was anything else related also running under the PCSS umbrella.

It worked! After killing those items, I was able to successfully uninstall both PowerChute versions. Then, when Schneider tech support (APC’s parent company) furnished me a different version of the new executable, I was able to install and use it. It’s running right now, in fact.

This Story’s Moral Is…

If you find yourself needing to uninstall a systray app of some kind, and uninstallers won’t run, check Task Manager for related processes. If you end those tasks (or their process trees) you should be able to proceed. At least, that worked for me. Here in Windows-World, such esoterica occasionally comes in handy. Keep it in mind!

Whoa! I’d forgotten how time-consuming and intricate the built-in Window disk checker can be. My pithy summation, as I prep the old drives on my soon-to-be-retired i7 Skylake PC is: CHKDSK follies follow drive prep. And with 9 disk drives to prep and clean up to make that move, that’s more than enough folly for anybody, including me. For the record, I’m using the CHKDSK /f /x command.

What CHKDSK Follies Follow Drive Prep Means

As the lead-in graphic illustrates — it shows 5.25 hours to grind the fix and clean operation to completion — it takes real time to make all this happen. I left it running when I left my desk last night, and the time info was waiting for me when I logged back in this morning. Only 8 drives left to go!

The 5 stages of CHKDSK run as follows:

1. Examining basic file system structure
2. Checking file name linkage
3. Examining security descriptors
4. Looking for bad clusters in user data file
5. Looking for bad, free clusters

Now that I’m on my second of 9 drives it looks like CHKDSK spends most of its time on the two final stages. It took 5.22 hours for Stage 4 on the first drive. The second, now underway, is estimating about the same amount of time for stage 5. I’ll follow up with more numbers later.

Isn’t that just the way things go in Windows-World sometimes? The job has to get done. Then the waiting begins. It can take a while, as these numbers already intimate (and may later show: I’ll keep track).

Total Times (Follow-Up 5 hrs later)

Looks like the CHKDSK stuff is actually all over the place. I had two drives take less than 1 second (!) to complete, most others came in at or around 1 minute (72 seconds, anyway). The first two drives I tried had trouble in need of repairing, and that skewed my impressions. Go figure! All cleaned up now, though.