Wait For Windows 7 SP1, Support Firm Warns Users
CWmike writes "Users should wait for Microsoft to work out the bugs in Windows 7 before jumping on the new OS, computer support company Rescuecom said on Friday. 'From the calls we're getting, as well as our own experience in the past with all Microsoft's operating systems, we're recommending that people stick with their time-tested OS and wait for the dust to settle,' said Josh Kaplan, president of Rescuecom. Citing a litany of reasons, ranging from the risk of losing data during an upgrade to tough economic times, Kaplan urged Windows users to put off upgrading to Windows 7 or buying a new PC with the operating system pre-installed. 'There are some compelling reasons for both businesses and home users to move to Windows 7,' Kaplan said, 'so we're saying "just wait for a bit."' Upgrading an existing machine — whether it's running the eight-year-old Windows XP or the much newer Vista — is particularly risky, he added, especially if users haven't taken time to make a full backup before they migrate their machines. Some users have found that out first hand. Among the top subjects on Microsoft's support forum is one that has put some PCs into an endless reboot loop when their owners tried to upgrade from Vista to Windows 7. Microsoft has not yet come up with a solution that works for all the users who have reported the problem, sparking frustration."
Trust me.
Help stamp out iliturcy.
Wait... Windows 7 is the vista service pack.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
I say get Windows 7 now, if you have a reason. If you have a new computer get it with 7 for sure. Get it for an old computer if there's a reason you want it (like DirectX 10/11 support or something) and your computer is reasonable (at least a dual core with 2GB RAM).
We have been deploying it here at work and it works great. It is a solid and fast OS. App compatibility is extremely good, even with our squirelly engineering apps.
But then seriously, how is this guy's story "news for nerds" any more than my anecdote? I would think nerds would be capable enough of doing testing to determine if 7 is right for their environment and then deploying it if appropriate.
What's new? This is always the recommendation. It has never not been the recommendation to jump on a Windows product as soon as it's been released by a support firm. Is it just posted here to give Slashdot readers a space to vent their Windows 7 thoughts on?
Beware: In C++, your friends can see your privates!
While no initial release is perfect (and nor is any currently deployed system), this seems like FUD to me. Win7 is small enough of a difference from Vista (and that's a good thing) that there's relatively few surprises switching to it. There's no major driver model change and real world app compatibility testing has been in progress for almost a year now.
I hear this every time a new version of Windows comes out. While it may be good policy for businesses to buy time to test the OS, develop training materials, and fix any application problems, it isn't as big of a deal for consumers, and articles like this come off as anti-Microsoft FUD.
There is always risk in upgrading to a new operating system, especially if you don't have much experience with it. That shouldn't stop you from waiting for the service pack.
My Sysadmin Blog
Especially since it seems most of the complaints are centered around people trying an upgrade install from Vista. Ok well:
1) Don't. Seriously, upgrade installs on OSes are bad news over all. Can they work? Sure I know people who've done upgrades that have gone off without a hitch. I also know people who have hosed their system that way. Windows, Linux, all the same, a reinstall is the way to go.
2) This doesn't matter for new systems. They are shipping with a fresh OS. As such saying to wait on a new system because of this is silly.
3) Seriously, don't do a fucking upgrade install!
While this bug should be fixed, that doesn't mean you shouldn't get the OS if you want it. Also, what makes them think it'll be fixed in SP1? If it is something real difficult and/or rare they may just recommend a clean install and be done with it. The more time that passes, the less people will care about the upgrade process.
But then you should have that anyhow. If you data matters, it needs to be backed up. How much it matters depends on how well you back it up. Reinstalls aren't the time to make backups, every single day is the time to make backups.
I'll be the first to admit that, in the past, this is exactly the recommendation I follow. However, I've used the beta, the RC, and I'm typing this on RTM, with an official install disk and license sitting next to me waiting until I have time to reinstall everything. Win7 has been rock-solid stable for me (aside from Creative's shite XFi drivers) through every version I've tried. If you are aware of any incompatible software that you need to run, then by all means wait (or run a VM), but otherwise, I have yet to see any reason to wait for a service pack on this one. If someone could provide some concrete reasons to wait, I'd take this article seriously, but otherwise, FUD.
As to upgrading, when has it ever been a good idea to perform a Windows upgrade installation? If you've been running any old version of Windows for 6 months or more, a fresh install is probably indicated anyway (although, I have been running RC on my home system since the day it came out, and I haven't had any Windows Rot yet, still runs as well as when I installed it). Backup your data, wipe the drive, and start from scratch. Bit of a pain in the ass, but that's pretty much a fact of life with Windows.
While Windows 7 is stable, how you can say it's more stable than XP?
I haven't seen XP crash in years.
Gone!
Because the is a Knowledge Base article (KB975253) about this problem?
The real "Libtards" are the Libertarians!
"has put some PCs into an endless reboot loop when their owners tried to upgrade from Vista to Windows 7. Microsoft has not yet come up with a solution that works for all the users who have reported the problem,"
Download and boot a linux live cd, mount your NTFS partitions, copy all your data, install linux or reinstall windows
The only problems I've had, and I only use my Windows box for games and keep my data on a server anyway, are
1: Quake 2 and derivatives do not run
2: My Turtle Beach surround sound USB headphones make Windows 7 bluescreen.
Otherwise everything I've tried on it works as well as it did under XP. I'm not happy with the new interface, but I remember not liking Windows XP when it first came out.
Boobies never hurt anyone. - Sherry Glaser.
1.) SQL 2005 and SQL 2008 both have known compatibility issues. SQL 2005 will ALWAYS fail an upgrade to SP3 under Win 7 without a reg hack.
I have been able to install SP3 for SQL 2005 on exactly one (of 5) Windows 2003/2003R2 servers. That one success was a clean, fresh install that had nothing else on it. Every other system STILL fails to install SP3, after the 3rd (or 4th?) release of SP3. I don't blame that on the OS, I blame it on the patch. Or maybe on SQL 2005 itself, I don't know. But it isn't specific to Win7, at any rate.
Poor means hoping the toothache goes away.
WIndows 7 uses the same drivers that Vista does... there isn't anything to wait for.
Do what thou wilt shall be the whole of the Law
While I hate "Me too" posts as much as the next guy, I have to agree that this article is FUD for the management types. I installed 7 RTM as soon as it was available from TechNet, and haven't had problem one yet.
Well, I have one problem - it doesn't seem to connect to Windows 2000 Server shares, and it doesn't like my (very outdated) Samba network. Apparently it requires Samba 3.3 or higher. However, that aside, I have to say my existing PCs (original P4 3ghz, 3gb or 4gb memory) are noticeably snappier than they were with XP - granted, some of that may have been the accumulation of crud that happens with any windows installation. Clean installs are always speed-boosters.
Speaking of which - yeah, don't bother with an upgrade. With as cheap as USB drives (even USB HDs, not just flash) are these days, you have no real excuse for not doing a clean install. I'll be deploying Windows 7 starting in April to the 500+ workstations at my company, and every install will be a wipe & reinstall using Acronis TrueImage with a nice sysprep'ed image. All of the testing I've done so far has made me a happy camper and Win7 evangelist.
Prior releases... yeah, waiting for SP1 was always a good idea. Hell, we waited for XP SP2 before deploying it. I really think they've finally gotten this thing right.
But of course, I could be wrong.
Poor means hoping the toothache goes away.
I thought that info was olds, not news? For at least the past 10 years, anyone who upgrades to a new windos version before the first big patchset is done is roughly on the same risk level as someone going to vacation in Afghanistan. As a woman. In a bikini. Together with your lesbian girlfriend. Who has an "I love USA" tattoo.
Assorted stuff I do sometimes: Lemuria.org
*11 step process of uninstalling drivers and software, upgrading operating system, reinstalling drivers and software
If you're going through all the effort of uninstalling, and reinstalling stuff, by the time you're done it'd be just as easy to backup (which you're doing anyway), wipe, install new OS, install applications, restore user data from backup. Then you reduce the chances of any cruft being carried over.
AUMHA Discussion: Should I Use a Registry Cleaner?
[excerpt]
Mark Russinovich wrote:
No, even if the registry was massively bloated there would be little
impact on the performance of anything other than exhaustive
searches (ed. of the registry itself).
On Win2K Terminal Server systems, however, there is a limit on the
total amount of Registry data that can be loaded and so large
profile hives can limit the number of users that can be logged on
simultaneously.
I haven't and never will implement a Registry cleaner since
it's of little practical use on anything other than Win2K
terminal servers and developing one that's both safe and
effective requires a huge amount of application-specific
knowledge.
[/excerpt]
It's a very interesting read, that's just one of the many security
and computer experts that chimed in on the issue.Overall, the
consensus is No, you should not use a registry cleaner. Period.
A few end-users howl contrary.
I'll go with the expert's advice that aren't trying to sell or promote crapware.