Notes on comments.
Welcome to our blog dedicated to the engineering of Microsoft Windows 7
Back in January we released the Beta and updated you on our overall engineering process that will get us from Beta to the Release Candidate. Today, downloading of the Release Candidate started and we’re already seeing a lot of installations and a lot of excitement. On behalf of the team, I want to extend a thank you for all of the millions of people who have been running and testing the Beta who have helped to make the Release Candidate possible. The feedback we have received, through all the mechanisms we have blogged about, has been an incredibly valuable part of Engineering Windows 7. We continue to be humbled by the response to Windows 7. Thank you!
This post is about the path from RC to what we call RTM, release to manufacturing. RTM is not one point in time but a “process” as from RTM we enable the PC manufacturers to begin their processes of building Windows 7 images for new PCs, readying downloads for existing machines, and preparing the full supply chain to deliver Windows 7 to customers. Thus RTM is the final stage in our engineering of Windows 7, but the engineering continues from RTM until you can purchase Windows 7 and Windows 7 PCs in stores at General Availability, or GA.
The path to RTM starts with downloads of the RC. The RC is “done” and what we are doing is validating this against the breadth of the ecosystem and with partners. It means, from our perspective, we have run many tests many times and are working to understand the quality of the release in a breadth sense. We’re all familiar with this as we have done this same thing as we went from pre-Beta to Beta and from Beta to RC. The primary difference with the RC is that we will not be changing the functionality or features of the product at this point—that’s the sort of thing we’ll save for a future release. We’ve gotten tons of feedback on design and features and shown how we have digested and acted on this feedback throughout many posts on this blog. We know we did not do everything that was asked, and we have also seen that we’ve been asked to do things that are tricky to reconcile. We hoped through the dialog on this blog that we’ve shown our commitment to listening and balancing a wide variety of inputs, and how we have thought about the evolution of Windows.
What sort of feedback are we looking for in the RC? We are primarily focused on monitoring the behavior of the product through the telemetry, and of course making sure we did not introduce any regressions in any dimension from Beta quality. One of the things we have done since Beta has continued to beef up telemetry—we’ve put in additional monitoring points in many systems. We’re particularly interested in seeing what devices are installed, drivers that are required, and overall system performance. We have telemetry points that monitor the UI responsiveness of the Start Menu, Internet Explorer (recently posted), Boot, Shutdown, Resume, and across all subsystems. Of course in the final product, this telemetry is optional and opt-in, and it is always private.
There are a series of specific types of reports that we are keeping an eye out for that would constitute changes we would make to the code between now and RTM. Some of these might include:
All of the feedback will be evaluated and whether the issue is with Windows itself or with hardware, software, or OEM partner code we will work closely across the entire ecosystem to do what is necessary to deliver excellent fully integrated PCs. This goal is more important than anything else at this point. The depth of this work is new for the team in terms of spending engineer to engineer time across a broad range of partners to make sure everyone is ready together to deliver a great PC experience.
Overall, while many have said that the quality of the Beta was on par with past RCs (remember how some even suggested we release it as final!), we are working to do an even better job with Windows 7. We think we have the tools in place to do that.
While the RC itself was compiled about 2 weeks ago, it takes a bit of time to go through the mechanics of validating all the ISOs and images that are released. In the meantime we continue doing daily builds of the product. The daily builds are incorporating code changes to address the above types of issues that impact enough customers that on balance the code change is more valuable than the potential of a regression. Throughout this process, every change to the code is looked at by many people across development and test, and across many different teams. We have a lot of engineers changing a very little bit of code. We often say that shipping a major product means “slowing everything down”. Right now we’re being very deliberate with every change we make.
The RTM milestone is not a date, but a process. As that process concludes, we are done changing the code and are officially “servicing” Windows 7. That means any subsequent changes are delivered as fixes (KB articles) or banked for the first service pack. Obviously our ability to deliver fixes via Windows Update has substantially changed the way we RTM and so it is not unreasonable to expect updates soon after the product is complete as we have done for both Windows XP and Windows Vista.
Between now and the RTM milestone we will make changes to the code in response the above inputs. We are decelerating and will do so “gracefully” and not abruptly. We do not have a “deadline” we are aiming to meet and the quality (in all dimensions) of the product and a smooth finish are the most important criteria for Windows 7. In addition, we have a lot of work going on behind the scenes to build Windows 7 in nearly 100 languages around the world and to make sure all the supporting materials such as our Windows web site, SDK, resource kits, and so on are ready and available in a timely manner.
Once we have entered the RTM phase, our partners will begin to make their final images and manufacture PCs, and hardware and software vendors will ready their Windows 7 support and new products. We will also begin to manufacture retail boxes for shipment around the world. We will continue to work with our enterprise customers as well and based on the RTM process the volume license products will be available as well.
Delivering the highest quality Windows 7 is the most important criteria for us at this point—quality in every dimension. The RTM process is designed to be deliberate and maintain the overall engineering integrity of the system. Many are pushing us to release the product sooner rather than later, but our focus remains on a high quality release.
Ultimately our partners will determine when their PCs are available in market. If the feedback and telemetry on Windows 7 match our expectations then we will enter the final phases of the RTM process in about 3 months. If we are successful in that, then we tracking to our shared goal of having PCs with Windows 7 available this Holiday season.
--Steven and Jon
I have been working with the Windows 7 beta and just recently the Windows 7 Release Candidate. One thing I did not see mentioned going into the RTM build is that of working on increasing the performance of the Windows 7 with the RTM build. Are we to assume that the RC performance is what we will expect on the RTM build?
I am very excited for the Windows 7 GA and hope you continue to make great strides with this OS.
I just have one comment.
Thanks Steven! :)
I have a CanoScan 5600f scanner and if I leave it on and plugged in (via USB) when Windows 7 RC goes into sleep mode I cannot come back out of sleep mode. If I turn it off and go into sleep mode the computer will wake as expected.
Just thought I'd share :-)
I should also mention that Windows 7 is fantastic. I haven't been this excited about a new OS since Windows 2000!
Congratulations to all members of Win7 team! The OS feels really snappy and stable, and I hope the RTM is to become a great success. It also would be appreciated if you could enlarge the experience given by the Microsoft Connect website as I think that the best products are made when all parties concerned are present and can throw in their ideas.
BTW, I have some restore from hibernation problems that I haven't had with Beta and Pre-Beta, but I suppose telemetry has already notified you of that :)
1. set UAC level to highest one
2. go into Computer Management
3. set Startup Type for Application Information service to Disabled
4. restart system
5. many system actions (requiring UAC prompts) will simply not work, you can't easy fix it. you have to reinstall everything...
I understand, that it will need access to computer. But selling system to customers with such functionality "by design" won't be too honest and professional.
Second example: like zdnet.com notified, system by default hides files extensions. How many non-technical users will understand, that file "document.txt" in Explorer is "document.txt.exe" ?
Third: http://www.pretentiousname.com/misc/win7_uac_whitelist2.html (I haven't checked, but I believe, that it can be the truth)
1. system+patches installed on VMWare (1,5GB of RAM, 20 GB HDD), nothing changed after installation
CPU stays at 100% (majority is used by NT kernel & system process).
If you so think about quality, how will you fix it ? or will you ignore this ?
Steven it looks promising but, as per http://www.pretentiousname.com/misc/win7_uac_whitelist2.html, has UAC security actually been fixed? I mean if there is a whitelist of trusted apps and arbitrary code can elevate, why even have non-admin vs admin accounts? Why waste every developer and users time?
I am running Windows 7 RC, and unfortunately it doesn't fix the problems that occurred with the beta. In the Beta release I could not hibernate with more than a couple of applications open. It would simply blue screen rather than turning off. I'm quite concerned that this problem still exists in the release candidate.
During the beta I was just putting my machine into sleep overnight. Unfortunately in the release candidate, restoring from sleep simply reboots the machine.
I'm sure you're receiving telemetry data about this but it is of grave concern to me that so close to release such major problem still exists.
It's not clear to me if fixes for this sort of problem will be delivered via Windows update before the release candidate goes to manufacturing, so that we can confirm the problem would exist with the released product.
I'm surprised that nobody mentioned this but the fade in/out animation when you open/close ANY program is very choppy for me in the RC.
It was perfect (like Vista) in the public Beta. I hope this gets fixed as it is very distracting.
WMP does not play favorite radio
32bit 7100 build (clean install)
8800GT 512MB with 185.85 drivers from Nvidia
Feel free to run dxdiag, save the output to a text file, and mail it to me.
This is likely related to your specific configuration since we do lots of standby/resume testing.
If you have any utilities, a/v, firewall, etc. running then let me know as well.
I commented on a previous blog entry that support for the tab character in tool-tip shell extensions was broken in the beta. I can confirm it has been fixed in the release candidate. Thanks guys!
I like many others am wondering what the impact of the silent elevation flaw in UAC is:
Is this website a hoax, or is this a legitimate problem with UAC? I think this is much worse than the older problem in the beta where UAC setting could be changed via a script that emulated keystrokes. Based on what the author wrote it sounds like this flaw would completely eliminate the value of having applications prompt for elevation, since malware could avoid the prompts.
I would be very interested to see a blog post refuting this claim if it does not actually pose a risk. In the meantime I have changed my UAC settings to the highest level just like Vista.
I've noticed a bug in the RC.
When I'm moving the taskbar from left to top, to right, sometimes there' is left with a blurry artifact on previous docked position. To remove this, I have to drag the taskbar back down to the bottom of the screen.
Another quirk which I know won't be fixable in RC stages, is the progress bar in the taskbar, perhaps in the future releases, you can make that progress bar target the total progress for all instances of the applications, and have the hover over menu/thumbnails display the individual progress bar's showing individual progress state.
I really like the hover state of the start button, but the Windows flag image seems to differ to the the normal start button state, perhaps making that image on the default button state as well?
I've also noticed, for the new login screen design, the Shutdown, Restarting text, which has a drop shadow on it, seems to be a bit strange, I think the new blue-bird background is a little too bright maybe?
Other than that, I think this is one of the most stable releases of Windows I've ever used.
Just an issue that I and at least one other Acer Aspire One user has experienced: When booting, boot fails, Windows 7 initiates startup repair, but cannot repair. I had to reinstall again. The other user, who's forum entry I read had performed a hard reset by holding down the power button (as I seem to recall I may have done too). Obviously that's not a great way to shutdown a system, but I guess in both our cases, the system had locked up and it was the only way out. Not too bad for me, on a machine I use for playing with, but if it had been my main machine it would have been extremely annoying. I can try to replicate the problem if you'd like.
Other than that, it looks great. The AAO flies, much quicker than the beta.
hi. there is only one thing that i found lacking in win7. the biometric devices support still does not work. the correct drivers are installed automatically but when you try to register a fingerprint, the application crashes. i don't know if it is a driver problem or a win7 problem but you may want to look into biometric support a bit.