Автоқосылу және Автоойнату: Windows жүйесіндегі құрылғыларды автоматты іске қосу мүмкіндіктері

AutoRun and the companion feature AutoPlay are components of the Microsoft Windows operating system that dictate what actions the system takes when a drive is mounted. AutoRun was introduced in Windows 95 to ease application installation for non technical users and reduce the cost of software support calls. When an appropriately configured CD ROM is inserted into a CD ROM drive, Windows detects the arrival and checks the contents for a special file containing a set of instructions. For a CD containing software, these instructions normally initiate installation of the software from the CD ROM onto the hard drive. To maximise the likelihood of installation success, AutoRun also acts when the drive is accessed ("double clicked") in Windows Explorer (or "My Computer"). Until the introduction of Windows XP, the terms AutoRun and AutoPlay were used interchangeably, developers often using the former term and end users the latter. This tendency is reflected in Windows Policy settings named AutoPlay that change Windows Registry entries named AutoRun, and in the file which causes "AutoPlay" to be added to drives’ context menus. The terminology was of little importance until the arrival of Windows XP and its addition of a new feature to assist users in selecting appropriate actions when new media and devices were detected. This new feature was called AutoPlay and a differentiation between the two terms was created. AutoRun, a feature of Windows Explorer (actually of the shell32 dll) introduced in Windows 95, enables media and devices to launch programs by use of command listed in a file called , stored in the root directory of the medium. Primarily used on installation CD ROMs, the applications called are usually application installers. The autorun. inf file can also specify an icon which will represent the device visually in Explorer along with other advanced features. Windows calls this a "basic" notification. A top level window is one which is a descendant of the desktop. However, if the device changed is not one of these types an application can use the function to register to receive device notifications. An article on the CodeProject website, "Detecting Hardware Insertion and/or Removal", with clarifications from a blog by Doran Holan is of particular technical interest here. Non volume devices are those devices that do not appear as drive letters in "My Computer". These are not handled by any part of AutoRun any actions taken for these devices are taken either by device specific software or by AutoPlay. See AutoPlay#Devices that are not drives. When Explorer receives notification of a volume change, it performs a number of actions:

Checks to see if AutoRun has been disabled through the Registry. If AutoRun is disabled for that drive or drive type, Explorer does not proceed further. There have been bugs in this area. Checks that the root directory of the inserted media contains an autorun. inf file, which might be read. See below. Sends a message to the foreground window. An application which has registered its interest in receiving this message using can respond to this message to halt AutoRun (and thus AutoPlay) at this point. Any application, foreground or not, can also be notified by using the COM interface available in Windows XP and later. Alters double click and contextual menu behaviours. When a user double clicks on the drive icon in Explorer or right clicks to get a context menu, what happens is fully programmable by settings in the autorun. inf file. Adds an autorun. inf controllable icon and descriptive text to the drive icon. Checks to see if the key is held down. If it is then Windows Vista (and later Windows versions) will invoke the AutoPlay dialog regardless of settings to the contrary. Previous versions of Windows will not continue with the process. This includes DRIVE REMOVABLE, DRIVE FIXED and DRIVE REMOTE drive types. AutoRun will work with network drives (the DRIVE REMOTE drive type) that are mapped to a drive letter. AutoRun will also work with floppy drives that are provided with autorun compatible drivers. Type name value Description DRIVE UNKNOWN 0x00000000 The drive type could not be determined (generic drive) DRIVE NO ROOT DIR 0x00000001 The drive is currently invalid (no mounted volumes) DRIVE REMOVABLE 0x00000002 The drive has removable media (floppy drive, USB flash drive) DRIVE FIXED 0x00000003 The disk cannot be removed from the drive (hard disk/solid state drive) DRIVE REMOTE 0x00000004 The drive is a remote (network) drive DRIVE CDROM 0x00000005 The drive is a CD ROM, DVD ROM or BD ROM drive DRIVE RAMDISK 0x00000006 The drive is a RAM disk DRIVE NOT DETERMINED 0x00000007 The drive has not yet been determined DRIVE NOT FOUND 0x00000008 The drive currently can't be accessed (detached drives) [RESERVED] 0x00000009 This value reserved for future technologies

The Windows Registry is a hierarchical database that stores configuration settings and options for the operating system. The terminology is somewhat misleading so it is briefly summarised here. A Registry key is similar to a folder that, in addition to values, each key can contain subkeys which in turn may contain subkeys, and so on. A Registry value consists of a name data pair. Microsoft documentation commonly uses the term "entry" as an equivalent term. It also uses "value" for "data" when it is obvious what is meant. To avoid confusion, this article always uses the term "entry" when referring to the name data pair. Two Registry keys that are very commonly referred to are which contains per machine settings, and which contains settings for the currently logged on user. These are almost always abbreviated as and respectively. There may be many users of a machine; their settings are stored in , is actually just a link to the appropriate place in .

Registry settings may be changed directly by using the GUI tool or the command line utility. Settings can also be placed in a text file, named with a reg extension type. For example, "". When the file is double clicked, the settings in the file are entered into the Registry, permissions allowing. They can be changed indirectly by using Group Policy, applied locally to a single computer with or to a domain with
It may be necessary to either logout or restart the computer in order for any Registry changes to take effect.

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. However, Group Policy would be the accepted method of disabling AutoRun on an entire Windows domain.