Yeah, I was just about to do a clean install this morning till I saw the posts about the update being removed. Even though I have the ISO's prior to them being pulled, I think I'll now wait and see what's going on.
No news here that a large group of entitled people with shinny profile tags gank upon individuals with different opinions than theirs. Even when it's about facts.
Then when even their software god proves them wrong, you only hear silence.
But there was no need to feel targeted by my slight-off-topic rant. Sometimes I overreact to what I perceive as lynching over the internet, must be because I've grow up on the eastern block. Such is life
Back on topic, I too used the now removed builds to clean install on two PCs, and did not find any issues.
But on my main PC that I've upgraded, I did find lots of stuff not working properly and a sensible degrade in real-time performance.
Now that I've re-applied some of my tweaks, things look back in shape.
If they have pulled it does that mean that those of us that are not having any troubles, when they re issues it again mean we have to put the whole lot back in or just the fix they will add.
I would think , based upon a lot of different reports, that there are under lying issues here...
Not Bugs, per say..
Just my thoughts...
I can see several circumstances linked to the troubles updating Windows. As I said in other post on anothr thread, multiple situations are on the scene. Almost as many situations as users can exist. But, although Microsoft is not the one to blame 100% about this errors, it's its responsability to make clear points and advices before going into an upgrade or major update, and to me those can be the likes of:
- Take care if you're under a non legal copy. Anyhing can happen.
- Take care if you're an obsessed instal-every-cleaning-app-in-the-market user. Of course, they are supposed to work well with Windows, but a lot of times, they just make it crash, f***ing around with important files and registry keys. In this point, Microsoft should be more clear with the users, and not being afraid to "offend" those third parties companies. If an app can be dangerous for your system, you should say it to your users on a clearly way, not only under the "use it under your responsability" point.
- Check if your actual OS is 100% free of errors. If you're having troubles when doing the sfc test, you can expect a mess or another when you upgrade your system.
- Microsoft just have to be less afraid with the system requirements. I mean, when all the Vista thing happened back in the day, it was clear that manufactureres were providing mid-obsolete machines, and that Microsoft was provided an unnecesary charged interface. Let's go to achieve an intermediate point, better. That's what MS has been trying since W7, and it has been achieved as they have been able to provide an OS which is able to run in very old machines. But... is this a good thing? I mean, the asier requirements you provide, the bigger range of users are you pointing, some of them running very old systems, able to provide awesome errors.