Earlier this week, I reported on my experiences in performing a repair install on my production PC. To recap: in the wake of installing KB4032188 on that machine, I couldn’t enter a pin or password to login after the reboot. Eventually, I did get that PC started. Because those boot issues kept re-appearing intermittently, I ran an upgrade/repair install to fix them. The good news is that this approach worked. But there have been some consequences, as Win10 post-repair-install issues appear. Let me elaborate…
A repair/upgrade install fixes many Windows ills, but it only mostly leaves the prior install intact. What falls outside the “mostly” can get interesting…
Details When Win10 Post-Repair-Install Issues Appear
The appeal of the upgrade (re)install is that this OS repair leaves an existing Windows installation mostly intact. Over the past couple of days, I’ve been learning what falls outside that “mostly” umbrella. Here’s my list of observed items so far. Future experience may cause me to expand as new items make themselves felt or known:
8GadgetPack: Yeah, I know I’m not supposed to run gadgets any more. But they’re so darned handy I do it anyway. Each time an upgrade runs on a Win10 machine, it disables gadgets. Fortunately, Helmut Buhler’s run-time notices this, and offers a repair shortcut on the desktop. A quick double-click on same and gadgets are back at work.
System Restore disabled by default: upgrades and clean installs start up with restore points disabled, no matter the prior state of the OS beforehand. One must remember to visit the System Properties window to turn restore points back on for the boot/system drive (if they’re wanted).
Windows 7 Games: I’m still hooked on Freecell, Solitaire and Hearts. Something about upgrade or clean install kills the ability to run those old games on new Windows versions. A reinstall turns out to be required, but neither terribly difficult nor time-consuming. Prior to repair, the icons still show up (in generic form) but nothing runs; after repair: game on!
Norton Identity Safe: I use Norton Internet Security on my production PC. Norton Identity Safe is my password store on that machine. Also, a Web-based version lets me use it on any machine with Internet access. Although I disabled Norton during the upgrade process, and re-enabled it afterward, Identity Safe wouldn’t run. I ended up downloading and using the Norton Remove and Reinstall tool to fix this.
People: I don’t use the People feature in Windows 10. (Instead, I use Outlook contacts in various versions of Office 365). People still shows up by default on my Taskbar. Thus, I have to unlock the taskbar, then turn off People in Taskbar settings. Finally, I re-lock the taskbar to keep from changing it by accident.
Nvidia GeForce Experience: the first time I fired it up, post-upgrade, it re-installed itself and informed me I needed a new GeForce driver. Looks like something about the upgrade stymies the operation of and automatic update check here.
That’s it so far. The great joy of Windows is that you often don’t recognize a problem until it hits you over the head. I’ll keep adding to this list of items as they do that to me. Stay tuned! If any new Win10 post-repair-install issues appear, I’ll let you know here.