Windows xp turn on usb autoplay

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. I did see a folder 'Explorer', but it was under 'CurrentVersion'. In CurrentVersion, I found a folder named AutoplayHandlers, which had an an encouragingly-named subfolder 'CancelAutoplay', which contained a subfolder 'Files'.

I certainly didn't feel comfortable hacking about in there. Again, I didn't see anything obvious and didn't mess with anything. Considering that this is a freshly-restored and updated installation, with no other software yet installed, I am uncertain as to how things could have gotten corrupted. Is there any way to verify my Windows installation?

What else is left to try? Thank you in advance for your assistance. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.

I have the same question 0. Report abuse. When an event occurs, Windows determines which action to perform based on the intersection of the applications registered on a per-content type basis and the content types found on the volume through sniffing. Figure 2Volume Autoplay Event Prompt If the user did not yet specify any preferences, Windows prompts the user to choose one of the applications, as illustrated in Figure 2. If the user has previously selected a preferred application for the event, Windows automatically launches the preferred application.

Once the user selects a default application, this preference can be changed through the AutoPlay tab in the volume's properties in My Computer see Figure 3. When the user inserts a compact flash card containing Windows Media Audio WMA files compressed music files , Windows sniffs the media and finds the music content.

The first time the user inserts such content in the compact flash reader, Windows prompts the user to choose an appropriate handler from a list of all applications registered for this content type. Other applications can register to be included in this list; more on this later. The prompt also has an "Always do the selected action" checkbox which, when checked, enables the user to set the selection as the default action to perform for the current content type.

Once a preference has been established, the original behavior can be restored by checking the "Prompt me each time to choose an action" checkbox in the device's Autoplay properties see Figure 3. When a volume contains mixed content, the prompt does not offer the "Always perform the selected action" option. In this situation, the dialog contains a list of all applications registered for the type of content found.

The "Always perform the selected action" option is not always provided because there are numerous combinations of content which will cause the mixed content prompt to appear. If the content combination is different the next time around, rendering any fixed preference would be inappropriate.

For example, assume a user inserts mixed content media containing digital images and video. The prompt presented is the mixed content prompt. If the "Always perform the selected action" option was available and the user indicated they always want to use Windows Slide Show as the viewing application for this content type, then later when the user inserts other mixed content media containing digital video and music.

The original preference of using Windows Slide Show is most likely inappropriate for digital video and music. Because of this, users are always prompted to choose an application when mixed content media is inserted into the drive. Autoplay V2 on Non-volume-based Devices The non-volume-based events are events generated by all other non-volume devices. Windows cannot read the content of such devices. It is also possible that such a device does not support the concept of content. Because of these factors, registration of apps for non-volume Autoplay devices is done on a per-device basis rather than a content-type basis.

When one of these devices is connected to the machine, Windows checks to see if an application has been registered for the device. If the user has not yet specified a preference, he is prompted to choose one of the registered Autoplay handlers see Figure 4.

If the user has already picked a preferred application for the event, that application is automatically launched by Windows. Figure 4Non-volume Autoplay Event Prompt Once a default application has been selected, that preference can be changed by clicking a small icon that appears in the taskbar notification area when the device is connected see Figure 5.

This approach is different from the way preferences are changed for volume-based devices. The difference is necessary as many non-volume-based devices do not appear in the My Computer folder.

Thus, there is no place to host the Autoplay property page. Figure 5Icon Autoplay V2 Registration Mechanism Both volume and non-volume Autoplay now support a new registration mechanism for applications interested in responding to media Autoplay events. With this new mechanism, multiple applications may be registered concurrently for events related to the same content type.

This concurrent registration provides a more event-related experience for the user. Autoplay settings are stored in the registry. All settings are rooted on the following key:. Applications register handlers to handle Autoplay events associated with particular media types. Information required of volume and non-volume handlers is described in Figure 6 and Figure 7 , respectively.

Figure 8 shows how the information is reflected in the user interface. Figure 8Handler Values UI Handlers contain the information necessary to launch the associated application along with information used in representing that handler in the Autoplay user interface. A handler does not necessarily have a one-to-one relationship with an application.

In response to an Autoplay event, the handler wraps the application with information specific to the event. For example, assuming that an application registers for both music and video events, it would register two handlers. The first would handle music and its action text would be something like "Play music.

If the application registered for IDropTarget new to Windows XP , then all the files that were sniffed will be passed to the application through the IDataObject interface. The buffer returned contains the Item ID lists for all files enumerated in the first four levels of folders on the volume.

No files are filtered out. The purpose of the buffer is to avoid a second enumeration by the handler. A handler implementation is responsible for filtering out the files that it cannot handle. Figure 9 shows a code extract from Sample 1 that performs the enumeration of the sniffed files.

When a non-volume device generates an event for which an Autoplay handler is registered, Autoplay creates an instance of the component registered through the Autoplay handler. If the executable implementing this component is not already running, the COM infrastructure will launch the application. Among the first things that the launched application should do is register its local server factories with COM.

Figure 10 shows edited code from the Sample 2 project that demonstrates how this can be done. This is done so that subsequent Autoplay events will be handled by the already running executable. Although not mandatory, it is recommended in most cases to avoid launching multiple instances of the same application.

The second parameter is presently reserved and will be either NULL or the address of a zero-length string; it should be ignored. Future versions of Windows might introduce new Event Type values. Since the non-volume handlers are invoked from the Shell Hardware Detection service, additional COM registration must be performed with regard to security.

The component as well as the application to be invoked must each have an AppID value. To disable your drives, you need to open the group policy editor. To do this you can click the start button then run and type gpedit. This is the group policy editor interface. Still on the right pane, double click system again, 1. Scroll down and locate "Turn off Autoplay. Once found, double click it. After doublNow that you have opened the Turn off Autoplay interface, you will find out that the default setting is Not configured.

So lets configure it.