Slashdot Mirror
Vista SP1 Update Locks Out Some Users
Echostorm writes with word that Windows Vista SP1, which began rolling out via Automatic Update, has left some users' machines unbootable. The update loops forever on "Configuring updates: Stage 3 of 3 — 0% complete. Do not turn off your computer." "Shutting down"... restart and loop. Echostorm notes having found traces of what sounds like the same bug in early beta releases of SP1. It's unclear how many users are affected. So far there is no word on a fix from Microsoft.
bah! -1 retard for me. I didn't RTFA before I posted. I didn't see the part that it was rolling out via Automatic Update.
I suck.
Seriously, sounds like a version issue. An SCM (Software Configuration Management). Seriously, I worked for smaller companies that were serious about versioning and regression testing. Is it my imagination or does MS seem more and more like a software organization that is out of control?
putting the 'B' in LGBTQ+
That's a dillution of the term "brick", and it's also not true. Except in the case of a really destructive update (as in, corrupts the FS or similar), if an update ever renders my Linux unbootable, I'll just pop in the install CD and use it to roll back the changes.
Certainly not what I'd call an "easy" process -- easy for me, maybe -- but it's by no means a brick.
Don't thank God, thank a doctor!
I think their test setups are entirely Hetero, dude. However, it's rather difficult to have every possible machine configuration represented. I mean, think of the permutations! Why won't anyone think of the permutations?
People like you are just retarded. When Apple, FireFox, whatever has a problem it gets played down. When the slightest hint of a problem comes up with MS it's bla bla bla. You guys can say what you want, but this is why I look at slashdot less and less. I'm interested in news not a bunch of anti-MS stories blown out of proportion. Also, just for the record, I've been using Vista for two months now and haven't had any issues. I really don't understand what is causing all the horror stories since the accounts are either vauge or second/third hand accounts. Why doesn't Tacoboy just make another site called IdiotDot for people to spew nonsense about Microsoft and then we get back to talking about real things here without being interupted all the time?
yeah exactly... its called beta testing. Where you literally give it out to people and say this might not work... and if it doesnt tell us and we'll fix it.
Who modded this Offtopic? The summary says "which began rolling out via Automatic Update", which is just wrong. Admittedly they might want to have caught this a touch earlier, but it's not public yet, nevermind auto updating people's machines. OSS FUD I say...
I work for Microsoft too and am not an Orange card. I avoid running Vista when I can. Period.
Usage: km/h for speed (kilometers per hour); kph for very slow impulses (kilopond hours).
Except for a major difference: unlike the 10.4.11 update, this is NOT a public release and contrary to what the summary is, is NOT available on Windows Update.
Maybe... but when was the last Software update for anything Apple, or Firefox, that got you stuck in a reboot loop... Now how many times has this happened to people updating Windows?
Exactly.
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
Just a few days ago with OS X 10.5.2. Several users were complaining of being stuck at the BDOS during boot, slow booting, etc. It seems that there are quite a few issues with 10.5.2, I myself have noticed apps starting much slower since the update. However, for the most part, it's very usable for me. Others however cannot even run some critical apps and has brought them to a complete halt. Not good at all. From what I have read and the trouble I had with using the Software Update version of the update, they needed to test more. I had to use the combo updater just to get the thing to install at all. Now, mod me over-rated.
45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
Wish I had. I'm trying to fucking retire from the Windows business, not get stuck in further.
I love how the pro-MS trolls are out in force today.
Linux, you magnificent bastard, I read the fucking manual!
Not to be cynical, but everything points to this being a fake post considering how horrendously wrong the summary is.
This is a problem reported on a beta version, and so will likely be fixed in the final. The final is currently 'unreleased' to the public (although it's out there), and the beta version requires registry entries to install. In both cases you need admin rights on the machine. The summary is *completely* wrong in that SP1 is not available on Windows Update yet, and that's even assuming that the problem isn't fixed in the final.
Given all that, it seems like an awfully convienent time, '10 minutes ago' for this to happen to you (and if somehow you are telling the truth, what sort of IT department lets users install service packs themselves, let alone unreleased service packs?)
Maybe it was the reference to "Mak" and "MakOz"? The only thing missing was "Mak f@nboiz SUXRZ!".
"Somebody has to do something. It's just incredibly pathetic it has to be us."
--- Jerry Garcia
Such duplicates is, or can be, good management. It allows decoupling of development, so important bug fixes in one part of the tool chain can be released without waiting for another part of the tool chain which might be under a major rewrite.
Major free software packages like gcc does the same, include their own copy of various utilities and libraries. Doing so provides the best of two worlds, it allows code sharing at the development plane, while avoiding the coupling usually associated with using some other projects code.
There is a tiny price in disk usage for the end user, but a price worth paying for not having to wait an additional year for new features, because release schedules have to get synchronized.
To get the full benefit it is necessary to have established clear ownership of the various components, and have a strong ethics with regard to making sure changes are propagated back "upstream". Such an ethics is evolving in the free software world.
I have no idea if the situation is similar inside Microsoft, but the basic mechanisms favoring decoupling certainly exists within a large company as well.