backtop

Ooops! The article you requested could not be found, please navigate our site to locate the article you requested


Comments     Threshold


This article is over a month old, voting and posting comments is disabled

The wait..
By GoodBytes on 2/16/2008 2:53:09 PM , Rating: 5
This is why I wait until SP1 is officially out, before upgrading. Until SP1 is official out for the consumers, everything related to SP1 good and bad, should be taking at a grain of salt.




RE: The wait..
By wolfwood on 2/16/2008 2:57:10 PM , Rating: 2
I agree, however the version they put out is suppose to be the RTM version so they might have to yank it back and put a fix in. Or at least they should.


RE: The wait..
By anotherdude on 2/16/2008 3:03:58 PM , Rating: 3
I raed through most of the posts at that link (MS Technet) and made a few observations;

- this is stil, technically, the RC, as the widespread release has yet to come down - supposedly so some last minute driver updates could be effected. Perhaps, I say perhaps, this is the reason the SP has failed for this handfull of users who reported in to technet.

- I was also a littler unsure if some of these botches were due to pre-sp fixes or due to the SP itself.

I could have installed the same SP they got but prudence suggested I be more patient.


RE: The wait..
By KamiXkaze on 2/16/2008 3:21:35 PM , Rating: 1
Agreed same here till most of the bugs are gone I will wait before I upgrade to Vista.

KxK


Vista
By Duwelon on 2/16/2008 3:47:38 PM , Rating: 2
Vista SP1 will rape your women, pillage your villages and set all your hopes and dreams ablaze...




RE: Vista
By Duwelon on 2/16/2008 3:51:27 PM , Rating: 3
I've never been critical of Daily tech before, but come on. Millions of users use Vista by now and you put a story up over 10 users? What purpose other than to create FUD over Microsoft does this serve? At least wait until there's some knowledge of the cause...


RE: Vista
By James Holden on 2/16/2008 4:45:38 PM , Rating: 2
This same topic was reported by CNET, Engadget, Gizmodo, and about 1000 other blogs. If there's a pretty large topic on technet about it *before* the thing ends up on the actual Windows Update, then you can be pretty sure this is going to turn up again in the final release.


RE: Vista
By ShadowZERO on 2/16/2008 4:43:12 PM , Rating: 2
I remember the same type of problems happening to some with both sp1 and sp2 for XP. Just seems like another cycle of history repeating to me.
I've learned to slipstream my service pack installations onto a freshly formatted hard drive. Wouldn't get a SP from any type of internet connection unless I absolutely had to.


First the iBrick, now the PC brick?
By jhinoz on 2/16/2008 2:17:34 PM , Rating: 2
at least this isn't intentional. But seriously, not enough QA testing happening. Bugs always get through but surely this would get picked up?

Never had anything similar with MS office ... at least they're bringing the fixer over from office to OS.




By fake01 on 2/16/2008 2:29:01 PM , Rating: 2
I had a similar problem when I installed SP2 on XP. It would get slightly past halfway installing than it would freeze. I would leave it for a few hours and come back to find it in the exact same place as I left it. I try to exit it and I can't. I am forced to do a hard restart where I either got a BSOD or a message saying windows wasn't installed correctly and when it tries to revert back it screws itself up and I had to format my PC.

I eventually got it installed. There was nothing wrong with my PC or the software I was using, just a crappy version of SP2.


Not Very Common
By Flunk on 2/16/2008 3:29:41 PM , Rating: 3
I have been testing the SP1 upgrade on many different PCs to ensure that it functions properly and I haven't run into this issue. I don't think that this is any reason not to update to SP1, this is unlikely to happen (10 reports is incredibly low) and if you follow proper procedures (back up your data before running the update) even if it does happen it is a quick fix.

P.S. If anyone misuses the term "bricked" again I am fully willing to brick their computer properly. Either by flashing a corrupt BIOS or literally smashing it with a brick. Your choice.




Misuse of "bricked"
By dancingwllamas on 2/16/2008 2:24:45 PM , Rating: 2
This sucks, but the system isn't bricked if you can still reinstall the OS.




whew
By Bonesdad on 2/16/2008 2:33:10 PM , Rating: 2
Oh man, glad I'm still on XP...I almost upgraded, but decided to wait for SP1. Still, sounds like it's only an unfortunate few




Killed mine
By FujiT on 2/16/2008 3:02:05 PM , Rating: 2
It killed my pc. It kept on rebooting so i'm on 2003 EE R2 and it's faster, more stable although some software doesn't work on it (like logitech setpoint)




No problems here.
By Shawn on 2/16/2008 4:06:33 PM , Rating: 2
But even if I did I would just roll back the system to a previous state. I had a problem with one of the previous betas and I rolled back windows to a pre-sp1 beta state with no issues whatsoever. I am still using that Windows install and have since upgraded it to SP1 RTM with no problems.




Was the copy of the SP intact?
By BigToque on 2/16/2008 4:14:57 PM , Rating: 2
I'm just curious if maybe this is the result of some people installing a service pack when the hash of the file doesn't match the original.

The file might still run, and then hang when one or more of the files inside is corrupt.




Let me guess who wrote this "article".
By Domicinator on 2/16/08, Rating: -1
By amanojaku on 2/16/2008 3:14:09 PM , Rating: 5
quote:
I knew when I saw the completely exaggerated title of this article claiming that peoples' computers are being "killed" and the ridiculous picture of Ballmer that this was by Mick.


I would say that a computer that doesn't boot to a usable desktop is effectively killed. Not everyone who uses a computer is a genius capable of using the restore utility, assuming it even works. Some people can barely turn a computer on!

BTW, EVERY picture of Ballmer I've seen was ridiculous.


RE: Let me guess who wrote this "article".
By TomZ on 2/16/2008 3:16:30 PM , Rating: 1
I agree, this article is pretty poor. Talk about making a mountain out of a molehill.

The final paragraph is complete crap. Going back to a previous restore point doesn't affect user data at all. It's only purpose is to save the (operating) system state, e.g,. drivers, configuration, etc. - NOT USER DATA.


RE: Let me guess who wrote this "article".
By James Holden on 2/16/2008 4:32:51 PM , Rating: 2
Sure, now try explaining that to someone who doesn't read Dailytech every day and wants to file their taxes today.


By darkpaw on 2/16/2008 4:51:01 PM , Rating: 2
The people that have TechNet/MSDN subscriptions would *hopefully* be smart enough to understand how to recover a failed system.

The only people that legitimately have SP1 right now are subscribers, beta testers, and certain volume license customers.

Anyone else trying to install SP1 atm is using a pirated copy, and if it screws up their system, I say too bad for them.

I could have SP1 through MSDN right now, but I'm going to wait until I have enough time to do a clean install.


RE: Let me guess who wrote this "article".
By SavagePotato on 2/16/2008 3:21:12 PM , Rating: 3
But over TEN users on the Microsoft forum have reported having this issue.

EPIDEMIC!! Run for the hills.


RE: Let me guess who wrote this "article".
By Highbuzz on 2/16/2008 3:56:40 PM , Rating: 2
IT'S OVER 90---- Oh wait, no, it's not...


By James Holden on 2/16/2008 4:39:06 PM , Rating: 3
10 of the MSDN subscribers posted* on technet about it. Now I'm not a genius in statistical sampling or anything, but if SP1 went out on Tuesday worldwide you can sure bet there'd be a few people reporting this.


By Nekrik on 2/16/2008 3:39:01 PM , Rating: 2
Agreed, I had avoided his articles this week but tried this one hoping they would have encouraged him to use a little discretion by now. I feel bad even discussing it as I feel it encourages them to endorse his sensationalistic style simply because it creates traffic. I wish they'd opt to be a more reputable site than they seem to be working for now.

At the very least you'd think they'd wait to know what the source of the problem is before posting this article.


"It looks like the iPhone 4 might be their Vista, and I'm okay with that." -- Microsoft COO Kevin Turner











botimage
Copyright 2012 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki