The data is a set of device identifiers, which matches those identifiers reported to the system by the devices themselves. The default value for this entry consists of products identified by Microsoft testing as being unable to support AutoRun. This entry should not be altered from its default. Editing Group Policy[ edit ] AutoRun may be suppressed on particular drives and drive types by using the methods described in the Group Policy section. However, the Group Policy Editor is not available on Home versions of Windows XP  and does not provide any fine-grained drive selection facilities.
|Published (Last):||6 August 2005|
|PDF File Size:||10.15 Mb|
|ePub File Size:||3.68 Mb|
|Price:||Free* [*Free Regsitration Required]|
The data is a set of device identifiers, which matches those identifiers reported to the system by the devices themselves.
The default value for this entry consists of products identified by Microsoft testing as being unable to support AutoRun. This entry should not be altered from its default. Editing Group Policy[ edit ] AutoRun may be suppressed on particular drives and drive types by using the methods described in the Group Policy section.
However, the Group Policy Editor is not available on Home versions of Windows XP  and does not provide any fine-grained drive selection facilities. Registry files[ edit ] A Registry setting file can be created that, when executed, makes the desired changes in the Registry. Windows Registry Editor Version 5.
This is not optional. This example would need to be run as Administrator and a reboot would be needed for the setting to take complete effect. Initialization file mapping[ edit ] Windows Vista and later versions of Windows have a policy setting, "Default behavior for AutoRun", that can be set to disallow the reading of an autorun.
This avoids certain scenarios where malware leverages autorun. Previous versions of Windows do not have this policy setting but the use of initialisation file mapping is an effective workaround. The following Registry file illustrates the workaround, where all autorun.
It is important to note that this applies to any autorun. Since either the policy setting or this workaround disable autorun, installation of software from an autorunning install CD or DVD will obviously no longer be automatic. When AutoRun is disabled, Windows should not proceed further through the activation sequence than the Registry check. However, it parses any autorun. This leaves the user open to attack from malware which uses the autorun. Double clicking the drive icon will infect the machine.
Right Clicking and selecting the "Explore" or "Open" options from the context menu is not a workaround as these menu items can be coopted by the appropriate autorun. This bug was fixed in a number of security updates, detailed in Microsoft Knowledge Base article This is not a bug. Some programs may deliberately change AutoRun Registry settings. Early versions of CD burning software like Roxio have been known to change settings in this way.
Creating an AutoRun-Enabled Application
This topic uses CD-ROM as an example it was the first medium to implement this technology but today there are many different media types that can use it. To enable AutoRun in your application, you simply include two essential files: An Autorun. If it does, the system searches for a file named Autorun. This file specifies a setup application that will be run, along with a variety of optional settings. The startup application typically installs, uninstalls, configures, and perhaps runs the application. Creating an Autorun. The Autorun.
The value can be expressed as either text or as a resource stored in a binary. An action command in the Autorun. The string displayed in the Autoplay dialog is constructed by combining the text specified in the action entry with hard-coded text naming the provider, provided by the Shell. The icon is displayed next to it. This entry always appears as the first option in the Autoplay dialog and is selected by default. The Always do the selected action option is not available in this situation.
AUTORUN.INF SHELLEXECUTE PDF
INF file. If no path is specified, Windows looks for the file in the root directory of the media. Specify a relative path no drive letters! The file name specified with this command must be located in the same directory as the file name specified by the open command. You can also specify a. EXE, or.