Engineering Windows 7

Welcome to our blog dedicated to the engineering of Microsoft Windows 7

Beta to RC Changes – Turning Windows Features On or Off

Beta to RC Changes – Turning Windows Features On or Off

The theme of “choice and control” has been applied in many aspects of how we have designed Windows 7. We’ve certainly received lots of positive feedback about the theme and about the choices we’ve made in the design, and we’ve also received a few suggestions for how we might continue to implement this theme in the future. We’ve received feedback for features that should be even more customizable (such as Explorer or the logon screen) or features that should be added to Windows (such as a PDF format reader, security tools, or disk utilities). And we’ve received feedback that some users might prefer to run Windows without certain features. This post is about a point of choice and control in the Windows 7 control panel called “Windows Features” which is where you can choose to turn various features of Windows on or off. This continues our discussion of changes we have made based on feedback from the Beta as we progress to the Release Candidate. This post is by Jack Mayo who is the group program manager for our Documents and Printing team and also worked on Internet Explorer 8. --Steven

“Turning Windows Features On or Off” has a long history in Windows, going back to the earliest days of the 32-bit code base. We’ve received a lot of suggestions about features that you would like to turn on or off using your own criteria for choice. For Windows 7 we’ve engineered a more significant list of features and worked to balance that list in light of the needs of the broad Windows platform as well. We want to provide choice while also making sure we do not compromise on compatibility by removing APIs provided for developers. We also want to strike the right balance for consumers in providing choice and balancing compatibility with applications and providing a consistent Windows experience.

We know many have specific ideas of what constitutes a “feature” or a “program” in Windows and what constitutes an identifiable “part” of the operating system, and yet we also know different people can have different points of view, often strongly held. Some might take an end-user approach and identify a feature based on a window or start menu shortcut. Some might take an approach based on one perspective of architectural subsystems, such as storage or security. Some might take an approach based on what to some are alternate choices to some similar functionality. All of these are valid in some context, but would not result in consistently identifying “features” considering these varied points of view. As engineers we know that no software system can be decomposed into an arbitrary set of layers or parts and any decomposition is likely to change over time.

We don’t want the discussion about this feature or these choices to digress into a philosophical discussion about the definition of an operating system, which is ultimately a challenging exercise (judging by the revision history on the community page), but we do want to improve a feature centered on helping to meet the feedback expressed by some over the summer when this blog started.

In the Release Candidate for Windows 7 we have extended the control panel called “Windows Features” which is available from the standard “Programs and Features” control panel (we often call this ARP, for the original name of Add/Remove Programs). This location is unchanged from Vista and XP, though the wording has been clarified. In Windows 7 if you bring up the Windows Features control panel by clicking on “Turn Windows Features on or off” (or just typing “Windows features” in the start menu) you will see the following in the Release Candidate (by default the hierarchy is not fully expanded, but in this screen shot I’ve expanded some elements for additional information):

Windows Features control panel

For those familiar with the Vista version or the Beta version of this dialog you will notice the list has grown. Let’s talk about what we’ve added and briefly how it works.

If a feature is deselected, it is not available for use.  This means the files (binaries and data) are not loaded by the operating system (for security-conscious customers) and not available to users on the computer. These same files are staged so that the features can easily be added back to the running OS without additional media. This staging is important feedback we have received from customers who definitely do not like to dig up the installation DVD.

For any of the features listed you can change the state to enable it or disable it. The Vista and Windows 7 beta control panel lists a wide range of features. Some are targeted towards Developers working on a client workstation (IIS, MSMQ, etc.), others are utilities for network administrators and enthusiasts (RSM, SNMP, Telnet, etc.), and some are features customers have asked us to make optional (Games, Fax and Scan, Tablet PC components).

In Windows 7 we are expanding the number of features you have control over in this regard, giving customers more control, flexibility and choice in managing the features available in this version of Windows.  In addition to the features that were already available to turn on or off in Windows Vista, we’ve added the following features to the list in Windows 7:

  • Windows Media Player
  • Windows Media Center
  • Windows DVD Maker
  • Internet Explorer 8
  • Windows Search
  • Handwriting Recognition (through the Tablet PC Components option)
  • Windows Gadget Platform
  • Fax and Scan
  • XPS Viewer and Services (including the Virtual Print Driver)

It is worth describing the details of “remove” since this too is a place where there are engineering and customer decisions to be made. We’ve already seen one decision which is to make sure we keep the features staged for future use so that a DVD is not required. A second decision is that we also continue to support the APIs available for features where these APIs are necessary to the functionality of Windows or where there are APIs that are used by developers that can be viewed as independent of the component. As many of you know these are often referred to as “dependencies” and with Windows the dependencies can run both internal to Windows and external for ISVs.

It should be no surprise, but when we develop new features in Windows we tend to use the underlying infrastructure and associated APIs rather than duplicate code which would create extra working set, slow performance, and increase the surface area that needs to be secured, etc. We all know code reuse is a good engineering practice. As a platform, Windows tends to emphasize the creation of APIs for many systems, even when those subsystems are viewed as part of a larger system. When we have APIs that are used, we faced the choice of breaking software that just expected those APIs to be there or to continue to support the API. When we continued to support the API our approach was to remove a feature by making sure that an end-user could not invoke the feature via traditional end-user mechanisms. These are often difficult decisions as we work to balance the expectations of developers, the shared desire to deliver a robust release of Windows 7, and to maintain the goals set out by the feature “Turn Windows Features On or Off”. Because there are so many combinations of dependencies just represented in this list, selecting some options might provide you with some explanation as to the challenges in selecting a combination (for example Windows Media Player and Windows Media Center share a lot of code so turning one off might introduce a pretty complex situation for the average end-user).

Finally, we know some have suggested that this set of choices be a “setup option”. Some operating systems do provide this type of setup experience. As we balanced feedback, the vast majority of feedback we have received was to streamline setup and to reduce the amount of potential complexity in getting a PC running. We chose to focus this feature on the post-setup experience for Windows 7.

--Jack

Leave a Comment
  • Please add 8 and 6 and type the answer here:
  • Post
  • This shouldn't be given much priority, cos it aint too important imo.

  • The boot animation blog actually exposed that somewhat unwittingly when it revealed that the Vista startup process essentially sat around wasting the End User's time for a large period (in computing terms) just so that it could show off a fancy animation (that wasn't even very impressive). Windows 7 has seen this and changed it - this is a fundamental change of ethos that can only be good for the OS as a whole, if it is applied all over.

  • For someone it might not be important but i find it very useful post because i like to chose which features i like to to keep and which i like to turn off. Not everything is for everyone. So before giving your opinion think benefits of others as well.

  • That’s a great info. Thanks for the info. Looking forward to the future discussion about these points…

    -------------

    <a href="http://www.gencsohbetci.net" title="sohbet">sohbet</a> - <a href="http://www.oyunportali.net" title="çocuk oyunları">çocuk oyunları</a>

  • Thanks for help, you do a great job.

  • I just wonder why there is no option to remove input methods (NOT keyboards) build in the system. Even I never use Korean, also the stupid Chinese (Traditional) ones.

    Instead, I have hacked the Registry. Make the MS Pinyin IME 2007 which really just categories in Chinese (PRC) acts like the one of Chinese (Taiwan). I could do this easily in XP, but difficult in Vista or 7, unless I install MS Pinyin IME 2007 separately.

  • You most definitely need to add a complete removal option. Also add a prompt warning the user that by removing the selected features they can cause depending software to stop working correctly.

    Services have dependency tab, you can add the same functionality to features and be able to inform the user what is it that they could potentially break if they remove the particular module.

  • Thank you for letting us turn off IE, at least a little bit.  I still think someone deserves to go to jail for forcing that security hazard on us, but now I can make sure no one I know accidently runs it.

  • This is a ridiculously GOOD feature. I can't believe Microsoft didn't include this in Vista. Letting people turn off features they don't use is a great way to save CPU resources

  • Interesting post. I normally comment AFTER reading the posts I visit. If I am ona interesting blog, but, do not like the post, or do not find it worthy to comment on, I refrain from doing so. Thanks for sharing.

  • I’m very excited for Windows 7, hope (and doubt) they put this kind of TLC into Windows Mobile 7 (or crazier yet, make Windows Mobile 7 a version of Windows 7, so all your big boy apps still work).

  • I just wonder why there is no option to remove input methods (NOT keyboards) build in the system. Even I never use Korean, also the stupid Chinese (Traditional) ones.

    Instead, I have hacked the Registry. Make the MS Pinyin IME 2007 which really just categories in Chinese (PRC) acts like the one of Chinese (Taiwan). I could do this easily in XP, but difficult in Vista or 7, unless I install MS Pinyin IME 2007 separately.

  • Although you can if you really want to, you should not turn off Windows Firewall unless you have another firewall enabled.

  • Windows 7 now ships with UAC configured to hide prompts when users change Windows settings. While this mode still ensures normal applications can’t overwrite your entire registry hive, Microsoft made a boo-boo in allowing users to change any Windows setting without any prompts. Yes, you can even change UAC settings, allow applications free reign in elevated mode (after the required restart).

  • The point is not merely that these features take up space ... (Although that is a valid issue for some people ) .

    The point is, it is my computer and I should have the choice whether to have a program installed or not . I am forced to use windows because there are lots of programs that run only in windows (Eg: almost all games) .

    It's like since I need windows , I also have to tolerate a whole lot of other "applets" and "features" on my computer .

    The security , performance and modularity aside what about ethics ???

    I say don't decide things for me .

    Some ppl b4 me have argued that this is justified becoz some lazy developers choose to cut corners .... I don't think that needs a counter-arguement.

    And I do agree with the need for simplicity of end-users (Some of whom need help to find "help" in windows). But there is no reason for choice to be sacrificed for the sake of simplicity . Maybe give dumbed-down versions for end-users and power-user versions.(same cost but more choice)

    I know a lot of noobs downloading stripped down versions of Xp and Vista on torrents just so they can get more performance .

    But great work on win 7 guys ... It's miles above vista . I love the revamped UAC . But I would've liked a more powerful control panel .

    One thing I would like to see in win 8 is a  Visual automation system somewhat like autoit or silkuli .But with more support and functionality added.

Page 8 of 9 (133 items) «56789