I performed a Windows 10 upgrade for free and wanted to know how to go back to my previous version. I waited a couple days after working with the new Windows 10, then I found the option that said I had 28 days remaining before the necessary files would be removed from my system. I decided to rollback. I know I had 28 days, but I was too comfortable with my Windows 7 Ultimat. Well, the rollback failed. The message said that the files needed were no longer on my computer. I knew the folder that had my previous installation and that folder was still there. But there must be a file or files that integrate with the rollback procedure to access the data and restore it to it's original state. I figured I was the recipient of bad luck. I did have my data backed up. I got my original Windows back with everything in tact bvut I wanted to figuere out why this even happened. Let me tell you the story, it might be interesting to some...
I upgraded again. This time I did not wait and I performed the rollback after I finished the installation. Rollback worked fine. Just a random glitch the first time? Due to my incessant paranoia, I couldn't accept that. So I started to experiment. I figured I would install, upgrade, re-install, and restore several times. This was gonna take a while so I put the coffee on. 3rd time, I installed, and once everything was complete, I decided to play around. I was able to start rollback and I cancelled before letting it actually restore my previous Windows. But I was able to see it was going to work. I also noticed after a while that automatic updates was disabled. I enabled it. Ppdates immediately begin to download and install. I had an idea that perhaps there was an update that may have caused my rollback to stop working. Boy was I on the right track. I rebooted, and the updates were still finishing so the reboot did not take place immediately. Once I got the system back up I tried the rollback again. BAM! Right in my face!. It failed. Files needed were no longer on my system. Was my reboot responsible for this? Was it the Windows updates and the reboot? I was not entireley sure I isolated this conpletely yet. So, I restored Windows 7 and did the Windows 10 upgrade yet again.
OK, now, this was the one that I think showed me what was happening. After installing Windows 10 upgrade, I tried rollback, it started but again I stopped it before actually going through with the restore. I did the windows updates and let them complete. I did not perform a reboot. Biut I let the updates finish. I was supposed to reboot, but I did not at this time. I tried rollback first. It failed. I have now pinned it down to rollback failing after the first set of Windows updates. Nothing to do with rebooting. I did not have a good idea of how many updates actually took place or which one caused it. But, before those updates, rollback was working. After theose updates, rollback was NOT working.
OK, I replicated the problem at least 3 times. The question I have now is WHY? I had already tried to question Microsoft. There was a specific tech support message board on the Microsoft site specifically designated for those with issue using rollback. But, all the questions just seemed fabricated. As if it were a path being laid out for people to follow and gather some instructions that applied to each individual's situation. Some questions ask about how to perform rollback. Others are asking if there is a way to restore the previous Windows installation. Just not a message board with alot of people complaining about issues. And every answer to every question was from the same guy. He was a tech from Microsoft on this forum. I tried to reply to a few of the messages since I had issues with rollback and this was a message board for that purpose. Every time I replied to another person's question or problem, my response never got posted. There is something very strage about this. Because I even posted my own question with details and it would have probably been one of the only questions that talked about an actual situation experienced by a real person. Well, my message was said to be getting reviewed by a moderator. It never made it to the board. I posted this question again and even asked a couple other questions. Never got posted. It seems the moderator is being selective and posting only the messages that would make him and/or microsoft appear to be handling all relative issues concerning rollback. But they were not. They were only building a message board by taking bits and pieces of info that were not likely from actual people's situations. It just seems like it is fabricated. Questions & Answers. Made to look like a place to get help but it looked like it was only an instructional type of message board and not a bunch of real people at all. And now I am really wondering why. There is even more...........
Why is rollback a problem? Why is the tech support message board looking as if it is fabricated? What's the deal. I have a very unusual but creative suspicion that I think some may find is a very logical and possible scenario.
I think rollback was deliberately made to fail through a set of updates that are performed after Windows 10 uopgrade is installed. But why? The success of Windows 8/8.1 was an abomination. There are stats that monitor how many systems were actually using Windows 8/8.1 vs those using XP/Vists/Win 7/etc.....The number of systems said to be using Windows 8/8.1 before Windows 10 was released was so low that Microsoft could not afford to screw up with Windows 10. Only about 16% of the systems out there were using Windows 8/8.1 and the rest were spread out over the other OS platforms with Windows 7 being the top dog with near 58-60% or so. Now, if you offer a major uopgrade like Windows 10 for FREE and people don't want it, I would say investors will likely throw in the towel. This was a make it or break it chance for Microsoft. And the key to the success was predicated on how well they do within the first 30 days. And that is why the 30 day time frame for those of us who want to keep Windows 10. The rollback option was a clear indicator of the success of Windows 10. I mean, they were giving this away for free to all Windows 7 users, which dominated the Windows based OS market, and Windows 8/8.1 users, which were the only sure thing they likely had since thiose people would likely accept Windows 10 if they were content keeping the dreaded Windows 8/8.1. SO they could count on 16% but need to win the other 58060% or most of them, if possible. So, what do you do if you see that a few weeks into the campaign, Microsoft is not seeing the results they hoped?
Well, each user has 30 days once they upgrade. So depending on how many upgrades were being done daily, weekly, monthly, versus how many rollbackss took place is gonna give the true rate of success. But, if the number of people wanting to perform rollbacks begins to rise, I believe there was a plan B. And that was an update designed to complicate the rollback process. And complicated it was. The over-all success could now be masked. Because all those people who now had to resolve restoring their old OS and data by using backups or re-installing our previous version of Windows are now off the grid. If there are investors or people that are predicating their involvement with Microsoft on the success of WIndows 10, they now have hidden alot of rollbacks from view. And just as I said, since we did not rollback using the option provided, we are no longer part of the statical data that they may be using to prove the rate of their success with Windows 10.
I admit, this might be a stretch, but not beyond the realms of reality. And I actually think the tech support message board I was dealing with is all fabrication. And as I was dealing with all of these things, the trail I was following is what brought about these conclusions. And ironically, I actually like Windows 10. And rollback time limits have probably come and gone fro alot of people by now. And alot of those who had problems like this may never be part of the statistical data that validates the true success of Windows 10. Something to think about