Although my Windows 11 Pro is upgraded on unsupported hardware, I don’t think that has anything to do with these minor hiccups. I’ve been running it since October 4.
I was expecting this:
The other issue was particular to my setup, I have the Windows Recovery Environment in its own separate partition on a different SSD from the Windows installation. The upgrade had pulled 530MB from the end of my Windows installation partition and setup the Windows RE there. I re-established my preferred Windows RE, reclaimed the 530MB, and while I was at it, I upgraded it to the newer version of winre.wim.
After getting that re-sorted, the first hiccup I noticed was that I had to reinstall Audacity. Once reinstalled, it runs normally. A couple of days later I noticed an issue with Adobe Reader. The hiccup was with Adobe Acrobat Reader DC not being able to open in protected mode. I uninstalled it using Revo Uninstaller Pro. Then I opened Task Manager and closed both Microsoft Office Click-to-Run and Microsoft OneDrive. Next I installed AcroRdrDC1901020099_en_US (because it allows choosing the installation folder), then upgraded it through the Reader. That proved to be successful, and after a reboot to re-enable Office and OneDrive, the Reader opens in protected mode once again. And today (Sunday), I noticed this again:
When checking my drive images created via Task Scheduler by Image for Windows, I noticed immediately that the image file sizes were unusual. Using TBI Mount I checked them out, and they weren’t the correct partitions … I opened Image for Windows, ran the setup for a drive image and checked the partition ID against my Batch file partition ID, and the partition numbers were correct, but the drive numbers were different. I corrected all the drive ID numbers in my Batch files, deleted the incorrect image files and re-created fresh images. After that was completed, I checked Disk Management against a screenshot from a couple of months ago, and found that: Disk 0 has become Disk 5 Disk 1 has become Disk 0 Disk 2 has become Disk 1 Disk 3 has become Disk 2 Disk 4 has become Disk 3 Disk 5 has become Disk 4 Everything else is copacetic, and only Image for Windows let me know that 21H1 Disk Management had re-ordered the SSD ID numbers.
Like the upgrade to 21H1, the drive numbers (I have 6) were bumped up by one in rotation. 5 to 0, 0 to 1, 1 to 2, 2 to 3, 3 to 4, and 4 to 5. It’s a minor thing because all my apps and programs (scattered around different drives/partitions) are still working, all the drive letters in File Explorer and Disk Management stay the same. It just affects my scheduled tasks for IFW, and that only takes editing the drive numbers.
The current numbering actually matches the SATA port numbers to the drive numbers. My OS partitions (dual boot) are on an mSATA SSD, which is SATA port 5. That isn’t really very important, since GPT partitions are identified by GUID’s instead of port numbers. The GUID’s stay the same through the upgrade, there’s just some tiny quirk that tics the drive numbers up by one.
That’s it so far, but I’m still looking. I’ve tried just about every app/program that I run, and haven’t found (other than Audacity and Adobe Reader) any that don’t operate correctly.
I’ll update the list of hiccups if that becomes necessary. StartAllBack has eliminated my reluctance to upgrade, making the most visible cringe factors of Windows 11 non-issues.
