Autoplay

Hi All,

This works to turn off Autoplay:

https://www.liberiangeek.net/2012/05...dia-insertion/

But, I would also like to do it from the registry. Anyone
have a link? (All my old stuff doesn't work anymore.)

Many thanks,
-T

T on 2016/12/09 wrote:

Hi All,

This works to turn off Autoplay:

https://www.liberiangeek.net/2012/05...dia-insertion/

But, I would also like to do it from the registry. Anyone
have a link? (All my old stuff doesn't work anymore.)

https://support.microsoft.com/en-us/kb/967715

Looks like AutoPlay is initiated by AutoRun. Here's some mo

https://support.microsoft.com/en-us/kb/2328787
http://www.samlogic.net/articles/aut...ypeautorun.htm

which says the policy (all of which are registry entries) is under:

(HKLM|HKCU)\Software\Microsoft\Windows\CurrentVers ion\Polices\Explorer\

The samlogic article gives you the bitmask on how to select which device
types to disable AutoRun (which will then not initiate AutoPlay). But
that seems oriented to the device type, not to a particular device or to
the media type. I found more registry settings at:

https://smulpuru.wordpress.com/2012/...stry-settings/

On 12/09/2016 01:08 PM, VanguardLH wrote:
T on 2016/12/09 wrote:

Hi All,

This works to turn off Autoplay:

https://www.liberiangeek.net/2012/05...dia-insertion/

But, I would also like to do it from the registry. Anyone
have a link? (All my old stuff doesn't work anymore.)

https://support.microsoft.com/en-us/kb/967715

Looks like AutoPlay is initiated by AutoRun. Here's some mo

https://support.microsoft.com/en-us/kb/2328787
http://www.samlogic.net/articles/aut...ypeautorun.htm

which says the policy (all of which are registry entries) is under:

(HKLM|HKCU)\Software\Microsoft\Windows\CurrentVers ion\Polices\Explorer\

The samlogic article gives you the bitmask on how to select which device
types to disable AutoRun (which will then not initiate AutoPlay). But
that seems oriented to the device type, not to a particular device or to
the media type. I found more registry settings at:

https://smulpuru.wordpress.com/2012/...stry-settings/


Great link. Thank you!

On Fri, 9 Dec 2016 11:34:50 -0800, T wrote:

This works to turn off Autoplay:

https://www.liberiangeek.net/2012/05...dia-insertion/

But, I would also like to do it from the registry. Anyone
have a link? (All my old stuff doesn't work anymore.)

Why? In my experience, the Windows article is enough.

--
s|b

On 12/10/2016 07:02 AM, s|b wrote:
On Fri, 9 Dec 2016 11:34:50 -0800, T wrote:

This works to turn off Autoplay:

https://www.liberiangeek.net/2012/05...dia-insertion/

But, I would also like to do it from the registry. Anyone
have a link? (All my old stuff doesn't work anymore.)

Why? In my experience, the Windows article is enough.


It is quicker to just click on a .reg file.

T on 2016/12/10 wrote:

s|b wrote:

T wrote:

This works to turn off Autoplay:

https://www.liberiangeek.net/2012/05...dia-insertion/

But, I would also like to do it from the registry. Anyone
have a link? (All my old stuff doesn't work anymore.)

Why? In my experience, the Windows article is enough.

It is quicker to just click on a .reg file.

Or even add as a startup item (regedit.exe /s file.reg).

One trick would be to use a tool that takes a snapshot of the registry,
you make the change using the Control Panel applet, and then take
another registry snapshot and do a compare of before and after
snapshots. That would tell you what got changed in the registry during
that span of time between snapshots, including the autoplay option you
changed.

Just be sure to use a registry snapshot tool that supports x64 if that's
the bitwidth of the OS. I've seen those that only capture the 32-bit
sections of the registry when ran on a 64-bit OS. Long ago, I used a
registry snapshot tool (InstallWatch) to help do remnant cleanup after
uninstall a program but it was 32-bit only. It's been so long since I
used that tool that I don't recall its name. There are several registry
snapshotters, like RegShot (https://sourceforge.net/projects/regshot/,
not [yet] used it).

A clumsy but non-3rd party way to do the same snapshotting would be to
run reg.exe and export the registry before you make the change(s), make
the change(s), use reg.exe again to export the registry, and then use
fc.exe (file compare) in a command shell to compare the before and after
exports of the registry. Might be a lot to output so maybe you should
pipe the output of fc.exe into a .txt file and then load the .txt file
into Notepad, like:

fc.exe before.reg after.reg diff.txt & notepad.exe diff.txt

On Sat, 10 Dec 2016 11:14:51 -0800, T wrote:

It is quicker to just click on a .reg file.

Not if you have to check it first (which is advised).

--
s|b

s|b on 2016/12/10 wrote:

On Sat, 10 Dec 2016 11:14:51 -0800, T wrote:

It is quicker to just click on a .reg file.

Not if you have to check it first (which is advised).

Current state is unimportant. The .reg file could be ran as a startup
item, an event in Task Scheduler (on login, Windows startup, etc), or
even on demand via shortcut. You don't need to know if the setting is
which value because you don't care. You are setting to a specific value
whether that value is currently different or the same.

In message , VanguardLH
writes:
s|b on 2016/12/10 wrote:

On Sat, 10 Dec 2016 11:14:51 -0800, T wrote:

It is quicker to just click on a .reg file.

Not if you have to check it first (which is advised).

Current state is unimportant. The .reg file could be ran as a startup
item, an event in Task Scheduler (on login, Windows startup, etc), or
even on demand via shortcut. You don't need to know if the setting is
which value because you don't care. You are setting to a specific value
whether that value is currently different or the same.

s|b wasn't talking about checking the _registry_ first, but the .reg
file - in other words, don't use a .reg file you find on the 'net
without checking what's in it first.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

The web is a blank slate; you can't design technology that is 'good'. You can't
design paper that you can only write good things on. There are no good or evil
tools. You can put an engine in an ambulance or a tank. - Sir Tim Berners-Lee,
Radio Times 2009-Jan-30 to -Feb-5.

"J. P. Gilliver (John)" on 2016/12/10 wrote:

VanguardLH WROTE:

s|b wrote:

T wrote:

It is quicker to just click on a .reg file.

Not if you have to check it first (which is advised).

Current state is unimportant. The .reg file could be ran as a startup
item, an event in Task Scheduler (on login, Windows startup, etc), or
even on demand via shortcut. You don't need to know if the setting is
which value because you don't care. You are setting to a specific value
whether that value is currently different or the same.

s|b wasn't talking about checking the _registry_ first, but the .reg
file - in other words, don't use a .reg file you find on the 'net
without checking what's in it first.

Ah, I see. I figured T would create his own .reg file.

On Sat, 10 Dec 2016 18:43:15 -0600, VanguardLH wrote:

s|b wasn't talking about checking the _registry_ first, but the .reg
file - in other words, don't use a .reg file you find on the 'net
without checking what's in it first.

That /is/ what I meant.

Ah, I see. I figured T would create his own .reg file.

Then it would take even longer than simply unchecking the option in
Control Panel AutoPlay.

--
s|b

s|b on 2016/12/11 wrote:

On Sat, 10 Dec 2016 18:43:15 -0600, VanguardLH wrote:

s|b wasn't talking about checking the _registry_ first, but the .reg
file - in other words, don't use a .reg file you find on the 'net
without checking what's in it first.

That /is/ what I meant.

Ah, I see. I figured T would create his own .reg file.

Then it would take even longer than simply unchecking the option in
Control Panel AutoPlay.

It takes longer to program the code to eject a CD tray, too, then to
just hit the button but almost every backup or burner program has that
code as well as Windows Explorer.

T doesn't want to change the registry entries just once, twice, or a few
times. Looks like he needs to do it often to fix a change he did not
want or to ensure the behavior is how he wants. Nobody takes the time
to write code, a script, or create a .reg file if it only gets used once
(which would've been performed anyway during the generation of the code,
script, or .reg file). Obviously T wants to perform the registry fix
many times. He might even want a .reg file to run it on Windows startup
or on login to ensure the behavior he wants exhibited all the time.

The point of scripts, or even .reg files, is NOT having to perform the
*repetitive* manual tasks. I bet you have shortcuts in your Start menu
and on your desktop. Why do that when you could use Windows Explorer or
DOS commands in a shell to navigate to the folder and start the .exe
yourself? Convenience obviously. I've not see a single Windows (or
Linux) user that doesn't have shortcuts to programs. I've not seen one
screenshot that shows a completely empty desktop and a completely empty
Start menu.

Shortcuts, scripts, .reg files, or any other convenience designed to
perform repetitive tasks are superfluous if each task is performed only
once. If T wanted the .reg file to perform that task only once, yes,
you would be correct that it would be easier to just use the Control
Panel applet to make the change (once he drilled through the wizards
trying to figure out where to make that setting change). He wouldn't
need a .reg file to do that ONCE. That he wants a .reg file evidences
that he wants to do that many times.

--- Example ---

I could use services.msc to stop and disable the BITS and WU services
everytime to ensure I don't get any Windows updates when I'm not
checking for them. I could do the manual enable and start of each
service, perform a WU check, and then manually stop and disable the
services. I could do that every time that I decide to check for Windows
updates. Much easier to have a batch file do the enable/start before WU
check and stop/disable after WU check. So I could:

- Click on Start and select Run.
- Load services.msc.
- Double-click the BITS service.
- Enable the BITS service.
- Click Okay.
- Double-click the WU service.
- Enable the WU service.
- Start the WU service.
- Click okay.
- Exit services.msc.
- Click on Start and select Run.
- Load %windir%\system32\wuapp.exe startmenu
- Use the WU client: check for updates, research each one, apply those
that I choose, and exit the WU client.
- Click on Start and select Run.
- Load services.msc.
- Double-click on the WU service.
- Stop the WU service.
- Disable the WU service.
- Click Okay.
- Double-click the BITS service.
- Disable the BITS service.
- Click Okay.
- Exit the services.msc app.

Or I could:

- Double-click on a shortcut to a .bat file to enable & start services.
- Double-click on a shortcut to load the WU client.
- Use the WU client: check for updates, research each one, apply those
that I choose, and exit the WU client.
- Double-click on a shortcut to a .bat file to stop & disable services.

In future, I might change this by having the batch file wait until the
WU client exits to continue running more commands, so I do just do:

- Double-click on a shortcut to a .bat file that by itself:
o Enable & start services.
o Load the WU client (where I go through my update process).
o On exiting the WU client, stops & disables services.

You go ahead and enjoy the much more lengthy process in the first
procedure along with having to remember order. For me, I prefer the
much easier second procedure and might go to the 3rd procedure to make
the process even easier. Yes, I had to take the time to write .bat
files and create shortcuts to them along with a shortcut to the WU
client. I still prefer the much easier and simplified procedure.

On 12/10/2016 04:43 PM, VanguardLH wrote:
Ah, I see. I figured T would create his own .reg file.

Yup!

On 12/11/2016 10:19 AM, VanguardLH wrote:
Obviously T wants to perform the registry fix
many times.

Over and over and over. It is part of security
hardening for credit cards. And is a good idea
in general for everyone.