Update 1 -- You have thirty (30) days to test Windows 10 and still roll-back the Windows 10 installation to your previous operating system. Since the fixes to Window's 10 start button, explore feature, Cortana, and drag-and-drop functionality were unlikely to be fixed soon, I decided to implement the roll-back as a test. (Normally I would have simply restored the entire disk image using my backup software.) It worked fairly fast (as compared to the install) and appears to have worked well with one or two exceptions.
I had to re-enter my network security key and refresh my IP address.
All of my email appeared to be unread. Quickly and easily fixed by selecting the folder and using control-alternate-a (the character "a") to mark all messages in the folder as being read.
Original post ...
One of the Microsoft’s most touted features, the Start Button, does not work on my computer. And, judging from the comments in the community, this is an intermittent, long-standing problem with no known fix at this point in time. Oh Joy! Oh Joy!
Like the pinheads that have reviewed the features of Windows 10 on a clean machine with a fresh install, I thought that I would play “stupid boy” – a term used in computer test labs – and do an in-place upgrade over my existing Windows 7 installation. And, test it using my normal workflow.
Of course, I am not one for playing Russian Roulette with my daily routine, so I was sure to do a full system backup using my trusty Acronis True Image software, making sure that I had the latest version that would support Windows 10 and backing up to an external hard drive. I loaded the image onto a second machine and once again verified the image. So I have minimized my risk of losing anything but my time and temper.
The install went well and the system appeared to function normally, albeit a little more slowly than I wanted. While I could have trashed the old installation under “Windows.old” and removed some of the superfluous setup files, I decided to leave them in place in case I wanted to experiment.
All was well until that first voluntary re-boot. Then the Start Button and the Explore feature went South. Attempting to fix the issue, I looked through the techie forums and was presented with a number of suggestions ranging from a clean install (DUH!), a repair install that would leave my data files intact, but force me to reload my other applications; tweak the registry, or run a piece of PowerShell code (didn’t work), or do any one of a number of things. After hours of fiddling, nothing worked. So I gave it a rest.
I have all of the functionality needed to engage in my daily workflow and will continue on until Microsoft presents a solution or a workaround.
Bottom line …
The saga continues and I will be updating this post when a fix is available. Meanwhile, I would hold off doing an in-place upgrade unless you are full backed-up and have a secondary machine available. I would also hold off on doing a clean install unless you can recover and continue your normal daily activities.
Two things are apparent with Windows 10. One, it appears Microsoft is forcing people toward cloud solutions and storage; controlled by them, of course. And, while Microsoft may have improved security to keep you safe from outsiders, they certainly have enabled (by default) their access to your system and data. More on protecting your system in a future post.
Best of luck for now.
"The object in life is not to be on the side of the majority, but to escape finding oneself in the ranks of the insane." -- Marcus Aurelius