Once upon a time, a long time ago, one could see a start menu; if i remember right, it looked like a subdirectory and listed the programs
that would start up at boot.

Have not seen that since Win7.

I need to see WTH got started behind my back, and maybe how to prevent
that happy horsemanure.
--- Synchronet 3.20a-Win32 NewsLink 1.114

Robert Baer wrote:

Once upon a time, a long time ago, one could see a start menu; if i remember right, it looked like a subdirectory and listed the programs
that would start up at boot.

Have not seen that since Win7.

I need to see WTH got started behind my back, and maybe how to prevent
that happy horsemanure.

Always state explicitly which OS you're running,
where you are observing a problemo.

The Win10 MSConfig isn't all that useful.

https://i.postimg.cc/Kv45Lw3j/msconfig.gif

The Sysinternals.com Autoruns shows Shell Extension launch, for a
number of items at the very bottom of its list. That's what some
of the extra ones are, but the items at the top of the list might
be slightly different than the msconfig-inspired list.

https://i.postimg.cc/QMSBfNR3/autoruns.gif

There can be Startup registry items, and two Startup folders.
As a guess at where the stuff hides. Also, Scheduled Tasks
launches stuff.

Paul
--- Synchronet 3.20a-Win32 NewsLink 1.114

Paul wrote:

Robert Baer wrote:

   Once upon a time, a long time ago, one could see a start menu; if i
remember right, it looked like a subdirectory and listed the programs
that would start up at boot.

  Have not seen that since Win7.

I need to see WTH  got started behind my back, and maybe how to
prevent that happy horsemanure.

Always state explicitly which OS you're running,
where you are observing a problemo.

* It that damn macro scheduler always there.
Since it now does not work, and the forum is worse, i guess i will uninstall it (if possible) and try to forget this one, and hope someone
comes out with something at least half-way useful.

The Win10 MSConfig isn't all that useful.

   https://i.postimg.cc/Kv45Lw3j/msconfig.gif

The Sysinternals.com Autoruns shows Shell Extension launch, for a
number of items at the very bottom of its list. That's what some
of the extra ones are, but the items at the top of the list might
be slightly different than the msconfig-inspired list.

   https://i.postimg.cc/QMSBfNR3/autoruns.gif

There can be Startup registry items, and two Startup folders.
As a guess at where the stuff hides. Also, Scheduled Tasks
launches stuff.

  Paul

--- Synchronet 3.20a-Win32 NewsLink 1.114

Robert Baer wrote:

Paul wrote:

Robert Baer wrote:

Once upon a time, a long time ago, one could see a start menu; if
i remember right, it looked like a subdirectory and listed the
programs that would start up at boot.

Have not seen that since Win7.

I need to see WTH got started behind my back, and maybe how to
prevent that happy horsemanure.

Always state explicitly which OS you're running,
where you are observing a problemo.

* It that damn macro scheduler always there.
Since it now does not work, and the forum is worse, i guess i will uninstall it (if possible) and try to forget this one, and hope someone comes out with something at least half-way useful.

The Win10 MSConfig isn't all that useful.

https://i.postimg.cc/Kv45Lw3j/msconfig.gif

The Sysinternals.com Autoruns shows Shell Extension launch, for a
number of items at the very bottom of its list. That's what some
of the extra ones are, but the items at the top of the list might
be slightly different than the msconfig-inspired list.

https://i.postimg.cc/QMSBfNR3/autoruns.gif

There can be Startup registry items, and two Startup folders.
As a guess at where the stuff hides. Also, Scheduled Tasks
launches stuff.

Paul

For runtime observation, use Process Monitor.

If the OS you're using is too old, it probably won't load.

See what I mean about telling me the OS ?

If this is a WinXP or Win2K setup you're running the
macro recorder/macro language, then the current
Process Monitor likely won't run there. You would
have to go to archive.org and find an older one.

You will see executables being "ReadFile" or "CreateFile" as
they are launched, as evidence of what is going on.

# Event-level tracing [what are they doing to my file system]

https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

# Task Manager "what is running now" [Use Run As Administrator to get max info]

https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer # Task Manager "what is running

Autoruns is for static tracing of "how did these start themselves
on my system after I just booted". If the macro-recorder process
is started on each boot, then the macro-recorder could do
just about anything it wants.

Paul
--- Synchronet 3.20a-Win32 NewsLink 1.114