Talk:AutoRun

message: I'm hesitant to alter the article as I've never edited before, but: I don't feel disabling Autorun by setting <CODE>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\CDRom</CODE> to 0 is the best idea. In Windows 2000/NT/XP this also disables Media Change Notification (MCN) so Windows won't display the disk label or update displayed content when the disk in the drive is changed. (See newsgroup posts and my responses here.) 
I'd recommend instead using NoDriveTypeAutoRun under the key: <CODE>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer</CODE>, as explained in this Microsoft TechNet article: NoDriveTypeAutoRun
and leaving the <CODE>Services\CDRom entry</CODE> set to 1. You can then disable AutoRun\Play selectively on certain drives or by setting it to <CODE>0xFF</CODE> (decimal 255) on all drives, without the unwanted side-effects.
Comments welcome!
--Nowl 15:09, 27 April 2007 (UTC)
thread_title:  A better way? 

message: This article lacks information about autorun.inf commands, some (but not all) of which is available at http://support.microsoft.com/kb/818804.  Information about commands 'action' and 'label' (and perhaps others) is absent even from there, probably due to the age of the page (Last Review: July 12, 2004).  Such information's inclusion here would either encourage MS to update their article or beat them at describing their own product.  Thanks!--Jesdisciple (talk) 05:09, 7 December 2007 (UTC)
thread_title:  Beat the Home Team! 

message: Sorry I just dumped a bunch of bold-italicized text into the middle of the article in a couple places.  I just don't have time to rewrite things correctly and am hoping someone else can pick up the pieces.  There is a lot of confusion over what AutoRun and AutoPlay means.  I think a lot of people might be coming here for information on how to totally kill this insane feature.  I know I did because we got infected by a virus jumping around on a memory stick.  None of the standard ways that Microsoft offers actually stops AutoPlay from running when the user naturally double clicks on CD-ROM or USB stick drive icons.  I only found that one article about the non-standard way of killing AUTORUN.INF files permanently.  And it works perfectly. By itself, it prevents code on media from ever running without the user actually clicking directly on the executable itself.  So I wanted to get this important info out there.  --207.154.79.131 (talk) 01:42, 4 March 2008 (UTC)
replies: text: What is up with this article? The bold/italicized stuff should just be worked into the content instead of pointing out errors with the article. I don't have time to edit this, but someone fix it-- it's just dumb. --63.226.239.213 (talk) 18:25, 5 March 2008 (UTC)
thread_title:  Bold and italicized comments should be worked into the article 

message: Previously there was only one technical registry table, but I can confirm Windows XP uses another table, which I detailed. However, I have no idea which OS the editor of the previous table had in mind, so I just assumed they meant older Windows than XP. Also, can someone confirm if Vista uses XP's blocking methods or something entirely new? -Lwc4life (talk) 10:06, 29 June 2008 (UTC)
thread_title:  Can someone confirm the different (Windows) OSes? 

message: Is there a source out there that officially states how much time should the  key be held down in order to disable a specific autorun for sure? -Lwc4life (talk) 10:09, 29 June 2008 (UTC)
thread_title:  How long should Shift be pressed? 

message: Arguments for keeping this section: 
1. The bulk of info is direct from Microsoft (authoritative), and is relevant to the article. 
2. It explicitly instructs the reader how to use gpedit, which is only alluded to in the next section. If the wiki article can contain explicit .ini code, then the level of detail I added is reasonable.  
Additionally, it does prevent Explorer's double-click open invocation of autorun.ini for CDrom/DVD's (restoring normal Explorer open of drive).  This is valuable information.  I looked long and hard throughout the web for how to do this, and an explicit note in this Wiki article would have saved me much trouble.   
3. The section has several valid references (including link to Microsoft for Autoplay repair). Again, valuable and relevant information.
(Exlex) Before removing this section please explain why it doesn't belong. My edit only added info to the aticle.  You provided no rationale for deleting, which is unacceptable unless addition is vandalism.  —Preceding unsigned comment added by Sulewasi (talk • contribs) 23:59, 12 September 2008 (UTC)
thread_title:  GPedit section 

message: Are AutoRun and AutoPlay synonymous, or are they different features?  After reading the article, I still don't know.  Spiel496 (talk) 16:41, 2 October 2008 (UTC)
thread_title:  AutoPlay vs AutoRun 

message: I hate to put it this way, but the problem with this page is that it is missing a LOT of AUTORUN.INF file information.
I'm not so good at putting info on pages, but...
http://www.autoruntools.com/autorun-inf.php
has a lot of info that this page doesn't.  can someone put this on the page?  Your own words, of course.
Tangmeisterjr (talk) 20:36, 5 October 2008 (UTC)
thread_title:  A LOT OF MISSING INFORMATION ON THIS PAGE!!! 

message: I've typed up a significant amount of text already on autorun, specifically on autorun.inf and the technical details surrounding autorun. I'll update this wiki entry with what I have and try and integrate all the items on this talk page into it.
I cannot just copy swathes of text from msdn without entering the realm of copyright so I'm avoiding that pitfall (which takes a bit of time and rewriting).
I feel it's very important to mention microsoft knowledge base articles KB950582, which fixes the very very long standing problem of disabling autorun correctly and KB953252 which references that fix. These are recent (Sep 2008) fixes which primarily change Double Click, Contextual Menu and AutoPlay functionality. I'd consider them top-rated security patches against autorun worms.
I'll have to take screenshots and images of the AutoPlay popups and right click dialogs from Windows screenshots. I believe that qualifies as fair use under Wikipedia guidelines.
Carveone (talk) 15:21, 11 December 2008 (UTC)
thread_title:  I'll do it 

message: Before I commit, I just want to put my intentions up on the Talk Page. First I've done a complete rewrite and it's loooong. 75KB of raw text + images. I want to change the page name slightly to AutoRun and do a redirect from Autorun. The different capitilisation seems pedantic but is much more common and seems to be official. I have to look up a lot of wikipedia edit how-tos before I finally make the change. I'm wondering can I just make the change or should I put up an example page first... If I do, it'll be soon and at User:Carveone/Sandbox...
Carveone (talk) 12:12, 22 December 2008 (UTC)
thread_title:  Changes 

message: Move Parsecboy (talk) 01:24, 12 January 2009 (UTC)
replies: text: I did a little bit of research on the naming thing and it seems that Microsoft uses "Autorun" and "AutoRun" interchangeably when discussing the feature.  The Windows Vista help, e.g., uses "Autorun", the API documentation uses "AutoRun", and other technical articles, as well as non-Microsoft sources, do both.  Tricky... I think the rename is fine, but if it doesn't go through, don't fret too much about it being "wrong".  Chances are pretty good that not even Microsoft knows for sure.  Warren -talk- 18:25, 6 January 2009 (UTC)
replies: text: As I was reading technical documentation primarily when writing the article I guess I would come to a certain conclusion. That and I fret about inconsistencies! I believe that when AutoPlay was introduced, Microsoft docs reflected the CamelCase tendencies everywhere. Of course, it's fashionable now too. MySpace, BlackBerry, SpongeBob SquarePants! Carveone (talk) 18:39, 6 January 2009 (UTC)
replies: text: I also did a bit of research and for me it seems that "AutoRun" is used more often in official Microsoft documents. The CamelCase capitalisation also seems much more logical to me, considering Microsoft's long history of CamelCase names, e.g. AutoPlay, ActiveSync, ClickOnce, ClearType, ReadyBoost, BitLocker, DoubleSpace, ActiveMovie, DirectPlay, DirectDraw etc. Ghettoblaster (talk) 19:52, 6 January 2009 (UTC)
thread_title: Requested move

message: The article would be improved by incorporating some discussion around stuxnet. Regards, Ben Aveling 01:05, 11 October 2010 (UTC)
thread_title:  stuxnet 

message: Please see 
http://www.geek.com/articles/news/microsoft-kills-autorun-for-security-reasons-in-new-critical-update-2011029/
somebody that is much more knowledgable than i should update this wiki based on the recent microsoft updates.
69.68.126.157 (talk) 14:54, 10 February 2011 (UTC)
replies: text: Thank you. That's very pertinent to the AutoRun page. I want to update both autorun and autoplay with Windows 7 appropriate info so I'll take a look and get on it! Carveone  —Preceding unsigned comment added by 137.43.144.169 (talk) 16:35, 12 February 2011 (UTC)
thread_title:  Microsoft kills Autorun 

message: The article currently states: "Disabling AutoRun may force a user to double click the drive icon to get a contents list, thus actually increasing the chance of malware infiltration." This is a somewhat odd claim, not obviously true, and is unsourced. Why would double clicking the drive icon increase the chance of malware? And, using standard Windows Explorer folder view, drive contents can be accessed with a single click on the drive, no need to potentially launch something...
-71.174.181.150 (talk) 21:54, 4 March 2011 (UTC)
thread_title:  "chance of malware infiltration"? 

message: Is it possible to disable AutoRun but keep AutoPlay?  How?
AutoRun is dangerous, and should generally be disabled. But, it would be convenient to still be able to automatically play inserted audio CDs and video DVDs. Is this possible?
There is a registry trick to kill autorun.inf processing, credited to Nick Brown:
 REGEDIT4
 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
      NT\CurrentVersion\IniFileMapping\Autorun.inf] @="@SYS:DoesNotExist"
* nickbrown-france.blogspot.com/2007/10/memory-stick-worms.html
* blogs.computerworld.com/the_best_way_to_disable_autorun_to_be_protected_from_infected_usb_flash_drives
* antivirus.about.com/od/securitytips/ht/autorun.htm
Basic AutoPlay seems to keep functioning in XP after this registry tweak. This change completely inhibits the ability to run autorun.inf files, so installing some software then requires the ability to view and understand such files, to find the .exe file that needs to be installed.-96.233.20.116 (talk) 20:28, 11 June 2012 (UTC)
thread_title:  AutoRun vs. AutoPlay 

message: Hello fellow Wikipedians,
I have just modified  on AutoRun. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20061006000535/http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx to http://www.microsoft.com/windowsxp/Downloads/powertoys/Xppowertoys.mspx
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—InternetArchiveBot (Report bug) 04:59, 22 October 2016 (UTC)
thread_title:  External links modified