The system that I supported for almost 40 years would not allow any of the above to occur, and would result in the immediate termination of the program(s) attempting such actions. Additionally, any non-OS kernel program should not be allowed to directly access core/main memory (or disk file data) by simply reading/writing via an absolute memory/disk address!. Does your antivirus cant remove the autorun& autorun. Once it detects a new USB drive it scans it for any autorun program on it and executes it thus emulating autorun feature that was disabled on Windows 7 for USB devices for security purposes.

Secondly, the Intel processor design should NEVER allow any (non-OS) software to access memory outside of an array (vector) at either end of the vector. As far as I know, the autorun. Autorun USB Helper sits in the background and monitors the system for all new USB sticks connected to it. ONLY a compiler, OS kernel, or an identified system software utility may change the contents of an object code file. This is ONLY one of many intrinsic security vulnerablities within Microsoft's OS (Windows kernel). Firstly, one should not be able to change a file extent so that you can manipulate a file in a different method (EXE to TXT, etc.)! Once a file's 'type' is established (by its creating software), it should be stored in a hidden location within the file's disk header (MFT), and thus changing its file name extent has NO effect upon how it's to be manipulated. Such restrictions are an outgrowth of their even weaker implementation of general, overall system security which is woefully vulnerable. I find that Microsoft's implementation of Autorun to be overly restrictive. Click the Start and Input 'gpedit.msc' in search box, then click the result to open the gpedit.

Usb autorun windows 7