Windows 7: Anyone else kind of disappointed?

I really wish MS would've added new featured from the RC to RTM timeframe. A lot of icons are left unchanged from Vista's, plus the taskbar could've been reworked a lot.

The point of an RC is not to add new features, it is to basically provide a feature-locked OS and only change showstopper-type bugs.

I'm not surprised at all. The point of a release candidate is a final check to ensure on real computers with real people that everything is working as it should. Only problems that were discovered and fixed should be implemented between RC and RTM.

"Anyone else kind of disappointed?"

No. Not at all.

+1

Never enjoyed any OS more than Windows 7.

I have to agree with the OP. I am completely bummed that my $300 version doesn't contain any untested and potentially dangerous features.

Overall I am very happy with this os.

One thing I am unsure about is the fact it attempts to install drivers during the installation without asking the user, so we end up not knowing exactly what was installed and what hasn't. I don't know, I just expected it to be a bit smarter, to advice users better on drivers. A lot of people might get inferior performance due to thinking they have all right drivers installed.

Nope. I'm actually surprised how clean it works and looks.

The only thing that didn't go as planed was with my new HDD. Neither XP nor the Windows 7 disc were able to create the propper partition for Windows 7 installation, but a simple, maybe even scratched, XP disc.

Yes I am still disappointed

I am still having bug and freeze problems on all of the computers that I have been testing on since the first release in November.

I am currently testing both x64 and x86 versions on 4 of my PC's and still having minor bug issues, and the major freeze problem.

I do not Just use my PC's for e-mails, browsing the web and gaming. I primarily use them for Engineering Design Work and they need lots of resources to operate efficiently. My primary Base unit is the one I do most of my work on and the Most efficient Operating system on it is Windows XP x64 (sp2) and customized. (Not the Basic install of services and registry sets).

The freeze issue is random and it happens when my PC's go into sleep mode. Some times the will wake up normally, but way to often they will not wake at all, I have to force re-boot. And no error logs related to sleep mode issues, only the E-ID 41 (forced re-boot). This has happened on all the releases from 7000 to 7127, and now 7600, the releases from 7137 to 7229 never had this problem. And this has happened on all my test PC's including Laptops and Desktops.

I have tried many changes in settings for Power Settings (Advanced), Network Adapter Settings, Monitor settings.

Ideally I want my Network Adapter to stay Active on my main box so I can access files from my other computers any time I need them, I want my HDD's to go to sleep when not in use so they will live for a while. and My Monitors to shut down when not in use.
All computers are Multi-Boot

Any one have any Ideas??

Here are some Hardware details.
Main System
Windows 7 7600 RTM x64 Ultimate
Gigabyte GA-965P-DS3, Intel C2Q 6600 64Bit
Marvell Yukon 88E8053 PCI Gigabit
8 Gig Ram
Dual nVidia 9400 GT (PCI-e and PCI)
7 HDD's @ 5.5 TByts (SATA II and IDE)
4 Monitors 3-LCD Hanns G, 1-AOC

2nd Test System
Windows 7 7600 RTM x64 Pro
Gigabyte GA-G31M-ES2L, Intel C2D E6450 64Bit
Realtek RTL8111C (PCI) Gigabit
4 Gig, nVidia 7200 GS (PCI-e)
5 HDD's @ 1.75 TByts (SATA II and IDE)
2 Monitors, 1 LCD-Hanns-G, 1 CRT-Samtron

3rd Test Laptop
Windows 7 7600 RTM x86 Home Premium
Lenovo 3000 N100, Intel C2D T2060 32Bit
Intel Pro Wireless3945ABG
2 Gig, Mobile Intel 945 Graphics Chip Set
1 HDD - (SATA II)

4th Test Netbook
Windows 7 7600 RTM x86 Home Basic
Acer AspireONE, Intel C2-ATOM N270
Atheros AR5007EG Wireless, Realtek RTL8102E PCI - NIC
1.5 Gig RAM, Mobile Intel 945 Graphics Chip Set
1 HDD, WD 120 SATA II

Because the issue propogates across platforms and OS builds, it is reasonable to conclude that the cause is not in the hardware or the OS build.

Are you applying a setting at any level that is drawn from your legacy bag of tricks?

For more than a year, I dealt with XP booting to svchost running at 50%/100% due to a customized network setting on my slipstream CDs. I knew it was somewhere in those settings because I finally solved the problem by installing from a slipstream that used default network settings. I burned an entire pack of CDs testing different slipstream configs. I still do not know what the actual setting was that caused the problem.

Something I "learned" and applied caused a major XP "bug". It spanned XP, XP SP1 and XP SP2 on every machine I ever installed it on.