PlanetSide 2 – Launch TrailerCheck out the launch trailer for the newly released PlanetSide 2 title. This massively multiplayer online game is available now on Microsoft Windows platform. Watch the trailer after the break.
Home » Posts filed under Windows
Per-User (Non-Admin) ActiveX
Running IE8 in Windows Vista, a standard user may install ActiveX controls in their own user profile without requiring administrative privileges. This improvement makes it easier for an organization to realize the full benefit of User Account Control by enabling standard users to install ActiveX controls used in their day-to-day browsing.
If a user happens to install a malicious ActiveX control, the overall system will be unaffected, as the control was installed only under the user’s account. Since installations can be restricted to a user profile, the risk and cost of compromise (and, in turn, the total cost of administering users on a machine) will be lowered significantly.
Per-User ActiveX was designed with compatibility in mind—most existing ActiveX controls will not have to be rewritten to benefit from this feature; the only change will be repackaging. As in Internet Explorer 7, when a webpage attempts to install a control, an Information Bar is displayed to the user.
By clicking on the information bar, users can choose to either install the control machine-wide, or install it only for their own user account. The options in this menu will vary depending on the packaging of the control and the rights of the user.
The available options depend on Group Policy settings for per-user ActiveX installations and whether or not the control has been packaged to allow per-user installation.
While this feature offers the possibility of lowering total cost of ownership, IT Administrators running managed environments may elect to disable this feature via Group Policy. For more information regarding Per-User ActiveX, please refer to the Non-Admin ActiveX Controls article in MSDN’s IE8 Beta 1 Whitepapers.
Recognizing that any binary extensibility mechanism increases attack surface, ActiveX Opt-In was introduced with Internet Explorer 7.
By default, ActiveX Opt-In disables most controls on a user's machine. When the user encounters a Web page with a disabled ActiveX control, they will see an Information bar with the following text: "This website wants to run the following add-on "ABC Control" from "XYZ Publisher". If you trust the website and the add-on and want to allow it to run, click here …" The user can then choose to enable the ActiveX control from this Information bar.
ActiveX Opt-In allows some controls to run by default:
For more information on ActiveX Opt-In, please refer to the MSDN Article Best Practices for ActiveX.
When a user navigates to a Web site containing an ActiveX control, IE8 performs a number of checks, including a determination of where a control is permitted to run. This check is referred to as Per-Site ActiveX, a defense mechanism to help prevent malicious repurposing of controls. If a control is installed, but is not permitted to run on a specific website, an Information Bar appears asking the user whether or not the control should be permitted to run on the current website.
Users can use the Information bar to allow the control for a specific Web site or allow the control for all Web sites.
IT Professionals administering a system of computers running Internet Explorer 8 may choose to preset allowed controls and their associated domains. Such settings can be configured using Group Policy.
For more information regarding Per-Site ActiveX, please refer to the Per-Site ActiveX article in MSDN’s IE8 Beta 1 Whitepapers.
Enforcing Per-Site with ATL SiteLock Technology
If your ActiveX control is designed for use only on your web site, then locking it to the domain of that Web site will make it harder for other sites to repurpose the control in a malicious manner. See Developing Safer ActiveX Controls Using the Sitelock Template for more information.
Reducing Exploit Risk with DEP/NX, “Killbits,” and Servicing
Working with your processor and Windows, IE8 helps reduce the exploitation of vulnerable controls through Data Execution Prevention. See the previous post in this series, IE8 Security Part I: DEP/NX Memory Protection, for more information on how to ensure that your ActiveX controls are DEP/NX compatible, as well as information on how to opt-in to other available protections.
If a vulnerable control has been exploited, IE has included a poison-pill option—the “killbit”— to block usage of specific controls within the browser. Vendors who are aware of a vulnerability in their control should contact Microsoft to setup a killbit for a future software update package. For more information, please refer to Knowledge Base article 240797, How to stop an ActiveX control from running in Internet Explorer.
As with standard desktop software, it is important to keep controls up-to-date to ensure compatibility with newer systems and lower the risk of compromise through evolving security threats. For more information on updating ActiveX controls, please refer to the IE Blog entry Good Practices for ActiveX Updates.
Working with Users through Manage Add-Ons
While most end users aren’t aware of the inner-workings of ActiveX controls or their enterprise policy on them (if applicable), users are able to find out information about the controls installed for use in Internet Explorer through Manage Add-Ons. It is important for developers to ensure that their controls are not only performant and secure, but also open in the information they provide.
Controls are identified by Name, Publisher, Version, and Class ID within the Manage Add-Ons interface. Given this, control developers are encouraged to include this metadata in release builds of their controls.
For more information on making sure that your ActiveX control properly conveys information about itself to users, please refer to Christopher Vaughan’s post Add-on Management Improvements in Internet Explorer 8 as well as the MSDN Article Best Practices for ActiveX.
Thanks for your help in ensuring your ActiveX controls are secure!
Windows XP SP3 contains some new updates, and a number of bug fixes and security improvements. You can learn more about XPSP3 features by reading the white paper located here. We expect XPSP3 will be publicly available shortly and want you to have this information prior to its final release to the web.
Internet Explorer 6 Users
XPSP3 will continue to ship with IE6 and contains a roll-up of the latest security updates for IE6. If you are still running Internet Explorer 6, then XPSP3 will be offered to you via Windows Update as a high priority update. You can safely install XPSP3 and will have an updated version of IE6 with all your personal preferences, such as home pages and favorites, still intact.
If you are currently running IE7 or IE8 on Windows XP SP2 (XPSP2) and you are thinking of upgrading to XPSP3, read on.
Internet Explorer 7 Users
If you are currently running IE7 on XPSP2, Windows Update will offer you XPSP3 as a high priority update. If you choose to install XPSP3, Internet Explorer 7 will remain on your system after the install is complete. Your preferences will be retained. However, you will no longer be able to uninstall IE7. If you go to Control Panel->Add/Remove Programs, the Remove option will be grayed out.
This behavior is by design and here is why. When we install IE7 on Windows XP SP2, we backup the existing IE6 files in an uninstall directory. Those IE6 files are the ones that shipped on XPSP2 plus all the security updates you’ve installed while using IE6. Windows XP SP3 contains a newer version of the Internet Explorer 6 files. If you have XPSP3 on your system and uninstall IE7, your system would revert to the backed up (older) version of the IE6 files rather than the newer XPSP3 version. You would end up in a mixed file state in Windows where most files would be the upgraded XPSP3, except for the IE6 files restored when uninstalling IE7. This state is not supported and is very bug prone. To ensure a reliable user experience, we prevent this broken state by disabling the ability to uninstall Internet Explorer 7.
If you must uninstall IE7 after you have upgraded to XPSP3, then you have to first uninstall XPSP3, and then uninstall IE7. After this series of uninstalls, you will be reverted back to a XPSP2, and a stable version of IE6, so feel free to upgrade to XPSP3 again.
If you install IE7 after you install XPSP3, then you will be able to uninstall IE7 at any point and be reverted to the newer IE6 version that ships in XPSP3. The restriction on uninstalling only applies to when you install a Windows Service Pack release on top of a standalone IE release.
Keeping this in mind, you might want to uninstall IE7, upgrade to XPSP3 and then install IE7 again so you can uninstall IE7 in the future if need be.
Internet Explorer 8 Beta 1 Users
Installing IE8 Beta1 on Windows XP SP3 is fully supported, so go ahead and upgrade your computers to XPSP3 and then install IE8 Beta 1 to try out our new features. You will be able to uninstall IE8 Beta 1 at any point to revert back to either IE7 or IE6 depending on what you were using before.
However, if you already have IE8 Beta 1 installed on XPSP2, Windows XP SP3 will not be offered to you via Windows Update. This is because after you update your system to XPSP3, you will no longer be able to uninstall IE8 Beta 1 and the Remove option will be grayed out under the Add/Remove programs in Control Panel. The reason is the same as in IE7 case described above. Since people are more likely to uninstall beta software, we strongly recommend uninstalling IE8 Beta 1 prior to upgrading to Windows XP SP3 to eliminate any deployment issues and install IE8 Beta 1 after XPSP3 is on your machine.
Microsoft Windows XP Service Pack 3 fixes a range of bugs in Windows XP. It doesn't matter what XP updates you have previously applied to your system, SP3 will update any unpatched, partially patched or completely updated system (it includes all previously released patches and updates). XP SP3 fixes the security holes so you won't get attacked.
Microsoft periodically combines updates, fixes, and other improvements into a single package - Service Pack. Microsoft develops updates, fixes, and other improvements that address issues reported by the company's customers and partners. To make it easier for customers to get these updates and enhancements, Microsoft periodically combines them into a single package, and makes that package available for all Windows customers.
These packages are called service packs", Microsoft revealed in the introduction of the Overview of Windows XP Service Pack 3. With the Release Candidates of Vista SP1 and Windows Server 2008 heading to increased testing pools the past week, and with Microsoft cooking the first public build of the first refresh for its latest Windows client, the official overview for XP SP3 is the only crumb from the service pack fiesta over at the Redmond company. The Release Candidate of XP SP3 in a pre-final stage has already shipped to MSDN and TechNet subscribers.FILE: WindowsXP-KB936929-SP3-x86-ENU.exe
BUILD: 2600.xpsp.080413-2111 : Service Pack 3, v.5512
CRC 32: C411A9DA
Download ALL FOUR PARTS
Right click on the file with name WindowsXP-KB936929-SP3-x86-ENU.7z.001, and click open archive under 7-Zip context menu. OR open the same file with 7-Zip File Manager.
Check to ensure the CRC 32 Checksum to be C411A9DA or MD5 Checksum to be BB25707C919DD835A9D9706B5725AF58.
Right Click on the single file that you see, and extract to any location.
Install by clicking on WindowsXP-KB936929-SP3-x86-ENU.exe file
Enjoy =)Below are the install notes for XP SP3 taken from MSDN
This document provides information about installing Windows XP Service Pack 3 (SP3). Both this document and the installation screens will guide you through the installation process.
To install SP3, your computer must meet the hardware and operating system requirements listed below. In addition, your computer must at least be running Windows XP with Service Pack 1 installed.
We recommended that you have Service Pack 2 installed before installing SP3. You can download Service Pack 2 at the Windows XP Service Pack 2 website.
To install SP3 on a single computer, your computer must have a CD-ROM drive and at least the following:
Operating system requirements
You can use SP3 to update the following operating systems:
Note: the following operating systems cannot be updated using SP3:
Before You Install Service Pack 3
To prepare for your installation of Service Pack 3
Installing Service Pack 3
You can install SP3 either from the Service Pack 3 CD or from the Windows XP Service Pack 3 website (Link available only after SP3 launched officially on Windows Update). The website provides a link to Windows Update, where you can install SP3.
To install Service Pack 3
Removing Service Pack 3
You can use Add or Remove Programs to remove SP3 and restore your computer to its previous state.
To remove Service Pack 3 by using Add or Remove Programs
Post by addiehf on Saturday, March 15, 2008 Label: Windows
Here is some additional information that you might find useful when installing IE8.
Which platforms can I install IE8 on?
IE8 is supported on the following operating systems:
IE8 is not supported on pre-release versions of Vista SP1 and XP SP3. When installing on earlier builds of Vista SP1, IE8 just won’t install and you will see this error “The installation does not support your operating system’s current Service Pack version.” When installing on earlier builds of XP SP3, the wizard will proceed but your system will be missing KB946501 which is required for IE8, and hence, your installation will be terminated.
What Operating System languages can IE8 be installed on?
The IE8 beta is currently available in English only. You can install it on any supported localized operating system. For example, if you are running German Windows Vista, you can install IE8. When you switch between languages in the Windows Vista UI, IE8 will continue to appear in English.
How can I tell if I successfully installed IE8?
After IE8 installation is complete, the final screen of the Install Wizard indicates that Internet Explorer installation completed successfully.
After you restart your computer and launch Internet Explorer, you can open the Help->About Internet Explorer dialog to see the version number 8.0.6001.17184
How do I uninstall IE8?
On Windows XP or Windows Server 2003 Platforms:
On Vista or Windows Server 2008 Platforms:
Are there any required updates for IE8?
There are 2 required updates for IE8:
If this update is not on your computer when you try to launch IE8, you will be prompted to manually install this KB.
If this update fails to install or you unselect the checkbox, you will not be able to install IE8 until this update is on the computer.
You can find out more about updates that get installed during IE8 setup from knowledge base article KB94856.
What do I do when I run into issues installing IE8?
Check out the knowledge base article on Troubleshooting IE8 installation. If after trying the recommended workarounds you still can’t install IE8, go to the IE Beta Newsgroup to see if there are any known solutions available. Microsoft MVPs and IE Team members are monitoring this newsgroup and they will help address your issues.
Some of the first things users may notice in the Beta 1 release of Internet Explorer 8 are new features such as Activities and WebSlice. We recognize that the technology behind Activities and Webslice relies on innovations that have come out of the community, which of course has had a critical role in the development of the Internet. We also appreciate the community’s deep commitment to permissive IP licensing and to ensuring the continued ability to innovate.
So with these new features and other initiatives we’re launching in Internet Explorer 8 Beta 1, we want to highlight the ways in which we’re using new approaches to licensing the various intellectual property components involved. We carefully chose these new licensing models because they are the models, or facilitate the kinds of free and open uses, that the relevant communities have adopted for themselves. While we will still evaluate the most appropriate way to make specifications and test cases available on a case-by-case basis, here we concluded that the Public Domain, Creative Commons and BSD licenses (for copyrights) and the Microsoft Open Specification Promise (for patents) are the best vehicles for making these technologies available.
In this post I’ll briefly describe how these are all being used, and also point you to links where you can find additional information about them.
Creative Commons and Public Domain for Copyrights in the Specifications
For the OpenService Format and WebSlice Format specs, we’re using two separate Creative Commons vehicles to allow developers to freely use and build on our work. We’re licensing our copyright in the OpenService Format Specification under the Creative Commons Attribution-Share Alike License. This license lets others copy, distribute, modify and build upon the specification, even for commercial uses, as long as they simply give credit to Microsoft and license their own changes under the same terms. This license is also consistent with the license adopted by the OpenSearch community, whose work relates to the OpenService Format spec.
We’re setting a new precedent with the WebSlice Format Specification by dedicating our copyright in it to the public domain using the Creative Commons Public Domain Dedication, the first time we’ve used a public domain dedication in connection with one of our specs. This allows anyone to freely copy, distribute, modify and build upon the specification for any purpose, without any additional conditions or obligations whatsoever. In this case, our public domain dedication is in keeping with the expectations of the hAtom Microformats community.
Our use of Creative Commons solutions in connection with these two specs continues our many years of support for and collaboration with that important organization. In addition to using Creative Commons licenses in conjunction with other other specs (including one used in conjunction with Internet Explorer 7) and on websites, Microsoft and Creative Commons have partnered on the creation of an add-in for Microsoft Office that automates the inclusion of Creative Commons licenses into Word, Excel and PowerPoint documents. We’re happy to continue our enthusiastic engagement with Creative Commons with the release of these specs today. For more information about Creative Commons, including how you can use Creative Commons licenses on your own works, please visit http://creativecommons.org.
Microsoft Open Specification Promise for Implementations of the Specifications
Microsoft has developed the Open Specification Promise (“OSP”) to provide a simple and clear patent promise to reassure the broad audience of developers and customers that a given specification can be used for free, easily, now and forever. The OSP was developed with feedback from customers and the open source community, and we’re happy to be making both the OpenService Format and WebSlice Format specifications available under the OSP. The use of the OSP confirms that that these two specifications can be implemented for free. Please refer to this page for complete information and details concerning the OSP.
BSD License for Copyright in the Cascading Style Sheets 2.1 Test Suite
Finally, in connection with the Beta 1 release of Internet Explorer 8, we’re also posting a set of tests to validate our interpretation and implementation of the Cascading Style Sheets (“CSS”) 2.1 Specification. In this case, we hope to get feedback from web designers and developers on the tests we’ve submitted to the W3C for inclusion in the W3C’s CSS Working Group Test Suite. We’re licensing this test suite under the BSD License, which allows redistribution and modification of the tests in source and binary forms, subject to a familiar three-paragraph set of conditions. The BSD License is the license the W3C CSS Working Group has proposed using for the rest of its test cases, thus we’re using it here so that our tests can seamlessly transition over to the W3C CSS Working Group.