These commands enable applications to start, start installation programs, or start other routines. In versions of Windows that are earlier than Windows Vista, when media that contains an Autorun command is inserted, the system automatically executes the program without requiring user intervention.
Because code may be executed without user's knowledge or consent, users may want to disable this feature because of security concerns. The configuration settings that are described in this article give Administrators the ability to selectively or completely disable all Autorun capabilities for systems that run Windows , Windows XP, Windows Server , Windows Vista, and Windows Server systems.
The default behavior in Windows Vista and Windows Server is to prompt the user whether an Autorun command is to be run.
Changes to these settings are described later in this article. An Administrator can completely disable Autorun commands or revert to the pre-Windows Vista behavior of automatically executing the Autorun command.
If the feature is configured to disable Autorun capabilities, or if this policy is not configured, Windows Vista and Windows Server will continue to prompt the user whether the Autorun command is to be run. Windows Vista-based and Windows Server based systems must have update Security bulletin MS installed to take advantage of the registry key settings that disable Autorun. Click Start , type Gpedit. If you are prompted for an administrator password or for confirmation, type the password, or click Allow.
In the Details pane, double-click Turn off Autoplay. Click Enabled , and then select All drives in the Turn off Autoplay box to disable Autorun on all drives. Click Enabled , and then select Do not execute any autorun commands in the Default Autorun behavior box to disable Autorun on all drives.
Click Start , click Run , type Gpedit. In the Settings pane, right-click Turn off Autoplay , and then click Properties.
Note In Windows , the policy setting is named Disable Autoplay. ImportantThis section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it.
Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:. In the Value data box, type 0xFF to disable all types of drives. Or, to selectively disable specific drives, use a different value as described in the "How to selectively disable specific Autorun features" section.
To selectively disable specific Autorun features, you must change the NoDriveTypeAutoRun entry in one of the following registry key subkeys:. The value of the NoDriveTypeAutoRun registry entry determines which drive or drives the Autorun functionality will be disabled for.
For example, if you want to disable Autorun for network drives only, you must set the value of NoDriveTypeAutoRun registry entry to 0x If you want to disable Autorun for multiple drives, you must add the corresponding hexadecimal values to the 0x10 value.
For example, if you want to disable Autorun for removable drives and for network drives, you must add 0x4 and 0x10, which is the mathematical addition of 2 hexadecimal values, to determine the value to use. These default values are listed in the following table. All the fixes in the current update for Windows XP and for Windows Server are included in the HonorAutorunSetting registry entry in the following subkey:.
Note For Windows Server and Windows XP, all changes of this update are controlled by the HonorAutorunSetting registry entry so that you can revert to the previous configuration if it is required. The registry key has a default value of 0x1. This value enables the functionality that is present in the current update. Before you install the current update, this registry key is not present in the system.
You can obtain prepackage installation Autorun behavior by manually setting the registry key to 0. To do this, type 0 instead of 1 in step 6 of the following procedures to manually set the registry key. In the Open box, type regedit , and then click OK. In the Value data box, type 1 , click Hexadecimal if it is not already selected, and then click OK. To prevent the Autorun feature from being invoked, and to keep any programs from writing Autoun. Note After you implement this procedure, Autorun features will not be available from network drives.
The following Microsoft Knowledge Base article contains two methods to prevent users from connecting to a USB storage device:. Note After you implement one of these procedures on a system, USB storage devices no longer function on the system. The update does not change the current Autorun settings on your system.
Instead, the update lets users correctly enforce Autorun settings. Include your email address to get a message when this question is answered. The modifications made to the Group Policy will hinge on these two Run Policies.
Helpful 0 Not Helpful 0. However, you need to know that unintended minor changes during the editing process may alter the way certain applications load and run. Hence, you need to totally sure of what you're doing. Submit a Tip All tip submissions are carefully reviewed before being published. You Might Also Like How to. How to. Co-authors: 8. Updated: March 4, Categories: XP Instructions. Thanks to all authors for creating a page that has been read 59, times.
Is this article up to date? Yes No. Cookies make wikiHow better. By continuing to use our site, you agree to our cookie policy. About This Article. Featured Articles How to. Trending Articles How to. As Microsoft introduce new Windows versions, they are introducing new Group Policy settings, e.
I'm seeking some preferably official MS statement of how you update Group Policy editor to work with the new settings. My guess is, you get some? Also, must you or should you create and maintain separate GPOs with the new settings applying these GPO's only to the new clients that can recognize these new settings , or can you safely apply the "new GPO"s to legacy clients that presumably will simply ignore the new settings?
Share Flag. All Comments. Collapse -. Windows update.
0コメント