I admit it: I got tired of waiting for Windows Update to include my lone holdout PC in the April Upgrade to Version 1703. Given that it was officially let go on April 5, and today is June 28 (12 weeks to the day), I hope this doesn’t come across as over-eager. I don’t think it is, at any rate. Here’s the deal: I decided to leave my wife’s PC on the previous version (1607) in April after upgrading my other 7 machines here at home. But after waiting … and waiting … and waiting some more, I decided this morning to bite the bullet and upgrade. It’s based on a 2013 vintage JetWay JNF9G-QM77 mobo with a mobile i7 quad-core CPU, 16 GB RAM, and a Samsung EVO 840 250 GB SATA SSD. So now, at last, I’m done waiting for Win10 Version 1703 on that machine.
How Is It I’m Done Waiting for Win10 Version 1703?
That part is easy. Having decided to wait no longer for Windows Update to push the update, I simply turned to the Windows 10 Update Assistant instead. Actually, that meant clicking the “Update Now” button on the Download Windows 10 web page, as shown here:
Click the “Update Now” button on a PC running an older Win10 version, and the updater does the rest automagically.
The Upgrade Proves Eminently Survivable
The whole process took about 15 minutes. In fact, the post-upgrade clean-up took somewhat longer than that. Given that MS decided to hold off on upgrading the machine itself, no doubt based on something about its hardware configuration, I was a little antsy that this might not work. But the faithful little mini-ITX box chugged through the download, powered through the reboots at the 30% and 75% marks, and went on to complete with nary a hitch.
The Windows Update MiniTool (WUMT) did find some missing drivers after all was said and done (mostly Intel chipset stuff) but the post-install cleanup also went quite well. When instructed to clean up system files, Disk Cleanup removed about 22 GB of old OS files from the system. PatchCleaner found about 4.5 GB of orphaned files, which I dutifully copied over to the backup/external drive before removing from the SSD as well. I was able to trim the SSD to just over 60 GB of on-board content when all was said and done, which put it within 1 GB of the original disk size of just under 60 GB before applying the upgrade.
Now that I’ve got this behind me, I’d love to better understand the criteria MS uses to withhold upgrades to some PCs and advance them to others. To me, it looks like they’re being pretty conservative about what goes ahead and what stays behind. In this case, I’m glad they may have been over-cautious. Let’s hope other holdouts fare equally well when their upgrades finally come through.