Window blocked startup programs

LoneStar · External Since: Feb 28, 2007 Posts: 96

"Rock" <Rock RemoveThis @nospam.net> wrote in message
news:OvEun4qfHHA.1252@TK2MSFTNGP04.phx.gbl...
> "Tim" <twentworth RemoveThis @houston.rr.com> wrote
>> "Rock" <Rock RemoveThis @nospam.net> wrote in message
>> news:%234I%23d1lfHHA.4596@TK2MSFTNGP05.phx.gbl...
>>> that changes were made, just like in XP. When that happens, using the
>>> icon in the notification area unblock it allowing msconfig to run, and
>>> then check the box for it to not alert you again. It won't alert until
>>> the next time you make changes with msconfig.

Sigh. Rock, WHERE is this box in Vista's pop-up notification icon that we
need to check? Like Tim, I can't see it, anywhere! I "think" we may all be
discussing different things.

This horse has done been beat dead!

EW

Rock · External Since: Feb 10, 2007 Posts: 2069

"LoneStar" <ewyatt_del_me.DeleteThis@excite.com> wrote

> "Rock" <Rock.DeleteThis@nospam.net> wrote

>> "Tim" <twentworth.DeleteThis@houston.rr.com> wrote

>>> "Rock" <Rock.DeleteThis@nospam.net> wrote

>>>> that changes were made, just like in XP. When that happens, using the
>>>> icon in the notification area unblock it allowing msconfig to run, and
>>>> then check the box for it to not alert you again. It won't alert until
>>>> the next time you make changes with msconfig.

> Sigh. Rock, WHERE is this box in Vista's pop-up notification icon that we
> need to check? Like Tim, I can't see it, anywhere! I "think" we may all
> be discussing different things.
>
> This horse has done been beat dead!
>
> EW
>
>

We may be talking about different things or there is something wrong with
both your setups.

What I was answering is the situation where you make a change in msconfig
and reboot. Msconfig then, as it did in XP, tries to alert you that it is
running in diagnostic mode. But since it needs admin privileges to run and
display this dialog box, it get's blocked until permission is granted. So
you click on the Blocked startup program icon in the notification area,
point to Run blocked program, which will show a list of the block programs,
in this case msconfig, and click on it to run it.

Msconfig then pops up with the message box saying, in effect, it's in
diagnostic mode. There is a check box to tell it not to alert you to this
again. Msconfig closes, and now the next time you reboot (assuming you made
no other changes through msconfig in the interim) it doesn't run. If you
don't check that box, every time the system is rebooted with msconfig in
diagnostic mode it will try to run. If subsequent changes are made in
msconfig, you have to give it permission all over again, and check the box.

The principle of allowing blocked startup programs that ask for admin
privileges when the system starts is the same thing. It can't be disabled
on a program by program basis.

If this isn't the issue, I'm sorry then I don't know and/or understand what
the issue is.
--
Rock [MS-MVP User/Shell]

Rock · External Since: Feb 10, 2007 Posts: 2069

"Rock" <Rock.DeleteThis@nospam.net> wrote in message
news:uVUjNPIgHHA.3676@TK2MSFTNGP05.phx.gbl...
> "LoneStar" <ewyatt_del_me.DeleteThis@excite.com> wrote
>
>> "Rock" <Rock.DeleteThis@nospam.net> wrote
>
>>> "Tim" <twentworth.DeleteThis@houston.rr.com> wrote
>
>>>> "Rock" <Rock.DeleteThis@nospam.net> wrote
>
>>>>> that changes were made, just like in XP. When that happens, using the
>>>>> icon in the notification area unblock it allowing msconfig to run, and
>>>>> then check the box for it to not alert you again. It won't alert
>>>>> until the next time you make changes with msconfig.
>
>> Sigh. Rock, WHERE is this box in Vista's pop-up notification icon that
>> we need to check? Like Tim, I can't see it, anywhere! I "think" we may
>> all be discussing different things.
>>
>> This horse has done been beat dead!
>>
>> EW
>>
>>
>
>
> We may be talking about different things or there is something wrong with
> both your setups.
>
> What I was answering is the situation where you make a change in msconfig
> and reboot. Msconfig then, as it did in XP, tries to alert you that it is
> running in diagnostic mode. But since it needs admin privileges to run
> and display this dialog box, it get's blocked until permission is granted.
> So you click on the Blocked startup program icon in the notification area,
> point to Run blocked program, which will show a list of the block
> programs, in this case msconfig, and click on it to run it.
>
> Msconfig then pops up with the message box saying, in effect, it's in
> diagnostic mode. There is a check box to tell it not to alert you to this
> again. Msconfig closes, and now the next time you reboot (assuming you
> made no other changes through msconfig in the interim) it doesn't run. If
> you don't check that box, every time the system is rebooted with msconfig
> in diagnostic mode it will try to run. If subsequent changes are made in
> msconfig, you have to give it permission all over again, and check the
> box.
>
> The principle of allowing blocked startup programs that ask for admin
> privileges when the system starts is the same thing. It can't be disabled
> on a program by program basis.
>
> If this isn't the issue, I'm sorry then I don't know and/or understand
> what the issue is.
> --
> Rock [MS-MVP User/Shell]

Disregard this message. It was sent too soon. See the following one for
better detail.

--
Rock [MS-MVP User/Shell]

Tim · External Since: Sep 09, 2006 Posts: 76

I think you are accurately describing the general problem, except for one
thing. Even when I have unblocked all startup programs with msconfig (it
says "Normal Startup"), I still get the notification that it's blocking
msconfig upon startup. If I'm using Normal Startup, msconfig shouldn't be
running at startup at all, correct? So why is it trying to start up and
then being blocked? If you look at registry key
HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\MsConfig, you'll see an
entry called NoRebootUI. If I'm not mistaken, a setting of 1 means that
msconfig will not run upon reboot. Mine is set to 1, so it shouldn't be
running. But Defender apparently thinks that it is.

"Rock" <Rock.TakeThisOut@nospam.net> wrote in message
news:eNoWrPIgHHA.4596@TK2MSFTNGP05.phx.gbl...
> "LoneStar" <ewyatt_del_me.TakeThisOut@excite.com> wrote
>
>> "Rock" <Rock.TakeThisOut@nospam.net> wrote
>
>>> "Tim" <twentworth.TakeThisOut@houston.rr.com> wrote
>
>>>> "Rock" <Rock.TakeThisOut@nospam.net> wrote
>
>>>>> that changes were made, just like in XP. When that happens, using the
>>>>> icon in the notification area unblock it allowing msconfig to run, and
>>>>> then check the box for it to not alert you again. It won't alert
>>>>> until
>>>>> the next time you make changes with msconfig.
>
>> Sigh. Rock, WHERE is this box in Vista's pop-up notification icon that
>> we
>> need to check? Like Tim, I can't see it, anywhere! I "think" we may all
>> be discussing different things.
>>
>> This horse has done been beat dead!
>
> You're right, we may be talking about different things or there is
> something
> wrong with
> both your setups.
>
> What I was answering is the situation where you make a change in msconfig
> and reboot. Msconfig then, as it did in XP, tries to alert you that it is
> running in diagnostic mode. But since it needs admin privileges to run
> and
> display this dialog box, it get's blocked until permission is granted.
>
> When the desktop loads an icon appears in the notification area with a
> message box above it stating, in part,
>
> "Windows has blocked some startup programs.....Click to view blocked
> programs"
>
> Clicking on it brings up a menu. One choice is Run blocked program.
> Pointing at that brings up a list of the blocked programs. For msconfig
> it
> will display "System Configuration Utility". Click on that to allow it to
> run. UAC will ask for elevation or permission, and when given the System
> Configuration Dialog box appears. I have attached a .jpg of this dialog
> box.
>
> In it is a check box followed by the text:
>
> "Don't show this message or start System Configuration when Windows
> starts".
>
> Check the box, and the System Configuration dialog box closes. Now the
> next
> time you reboot (assuming you made
> no other changes through msconfig in the interim) msconfig doesn't run.
>
> If you don't check that box, every time the system is rebooted msconfig
> will
> try to run.
>
> If you do check the box but subsequent changes are made in msconfig, you
> have to give it permission all over again, and re-check the box on next
> system start.
>
> How one allows blocked startup programs that ask for admin privileges when
> the system starts is done the same way, but those programs might not have
> a
> checkbox like the System Configuration Utility. It can't be disabled on
> an
> individual program basis. It's triggered because the program is asking to
> run with admin privileges.
>
> If this isn't the issue, then I'm sorry, I don't know and/or understand
> what
> the issue is.
>
> --
> Rock [MS-MVP User/Shell]
>

Rock · External Since: Feb 10, 2007 Posts: 2069

"Tim" <twentworth RemoveThis @houston.rr.com> wrote
>I think you are accurately describing the general problem, except for one
>thing. Even when I have unblocked all startup programs with msconfig (it
>says "Normal Startup"), I still get the notification that it's blocking
>msconfig upon startup. If I'm using Normal Startup, msconfig shouldn't be
>running at startup at all, correct? So why is it trying to start up and
>then being blocked? If you look at registry key
>HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\MsConfig, you'll see an
>entry called NoRebootUI. If I'm not mistaken, a setting of 1 means that
>msconfig will not run upon reboot. Mine is set to 1, so it shouldn't be
>running. But Defender apparently thinks that it is.

> "Rock" <Rock RemoveThis @nospam.net> wrote in message

>> "LoneStar" <ewyatt_del_me RemoveThis @excite.com> wrote
>>
>>> "Rock" <Rock RemoveThis @nospam.net> wrote
>>
>>>> "Tim" <twentworth RemoveThis @houston.rr.com> wrote
>>
>>>>> "Rock" <Rock RemoveThis @nospam.net> wrote
>>
>>>>>> that changes were made, just like in XP. When that happens, using
>>>>>> the
>>>>>> icon in the notification area unblock it allowing msconfig to run,
>>>>>> and
>>>>>> then check the box for it to not alert you again. It won't alert
>>>>>> until
>>>>>> the next time you make changes with msconfig.
>>
>>> Sigh. Rock, WHERE is this box in Vista's pop-up notification icon that
>>> we
>>> need to check? Like Tim, I can't see it, anywhere! I "think" we may
>>> all
>>> be discussing different things.
>>>
>>> This horse has done been beat dead!
>>
>> You're right, we may be talking about different things or there is
>> something
>> wrong with
>> both your setups.
>>
>> What I was answering is the situation where you make a change in msconfig
>> and reboot. Msconfig then, as it did in XP, tries to alert you that it
>> is
>> running in diagnostic mode. But since it needs admin privileges to run
>> and
>> display this dialog box, it get's blocked until permission is granted.
>>
>> When the desktop loads an icon appears in the notification area with a
>> message box above it stating, in part,
>>
>> "Windows has blocked some startup programs.....Click to view blocked
>> programs"
>>
>> Clicking on it brings up a menu. One choice is Run blocked program.
>> Pointing at that brings up a list of the blocked programs. For msconfig
>> it
>> will display "System Configuration Utility". Click on that to allow it
>> to
>> run. UAC will ask for elevation or permission, and when given the System
>> Configuration Dialog box appears. I have attached a .jpg of this dialog
>> box.
>>
>> In it is a check box followed by the text:
>>
>> "Don't show this message or start System Configuration when Windows
>> starts".
>>
>> Check the box, and the System Configuration dialog box closes. Now the
>> next
>> time you reboot (assuming you made
>> no other changes through msconfig in the interim) msconfig doesn't run.
>>
>> If you don't check that box, every time the system is rebooted msconfig
>> will
>> try to run.
>>
>> If you do check the box but subsequent changes are made in msconfig, you
>> have to give it permission all over again, and re-check the box on next
>> system start.
>>
>> How one allows blocked startup programs that ask for admin privileges
>> when
>> the system starts is done the same way, but those programs might not have
>> a
>> checkbox like the System Configuration Utility. It can't be disabled on
>> an
>> individual program basis. It's triggered because the program is asking
>> to
>> run with admin privileges.
>>
>> If this isn't the issue, then I'm sorry, I don't know and/or understand
>> what
>> the issue is.

Ok, yes, if it's in normal startup mode, and no changes were made to set it
to that mode since the last time msconfig was run and the system booted,
then it should not. Or if you tick the box saying don't alert me, even if
not in normal startup mode, it should not alert.

Sorry I don't know why it's doing that on your system. Maybe someone else
will spot this thread now that we seem to have a good explanation of the
problem, and provide some input on it.

On this system, msconfig is in selective startup mode because I recently
unchecked something from on the Start tab. After the first reboot I checked
the box to not alert any more. There have been several boots since then
with it not running at startup.

For that key you mention, the value is set to 0, not 1.

--
Rock [MS-MVP User/Shell]

Ross · External Since: Jun 13, 2006 Posts: 48

I plowed through this whole thing and have at least identified my problem. I
won't know until tomorrow whether I've solved it. First, I didn't use
MSCONFIG to do anything, so I'm innocent in that regard. Second, the problem
occurs on this computer, but not on a notebook sitting next to it. Third,
the offending program (thanks to Rock for showing me how to find it) is Sonic
Record Now program manager. My guess is that this came with an Apricorn DVD
player I recently installed. Since I rarely if ever record anything, I'm
going to disable this from the startup program list. We'll see what happens
tomorrow.
--
Ross

"Olly" wrote:

> Have you been into msconfig ? type msconfig in search click on the file look
> in start
> up programes make sure they are all checked.
>
> "Tim" wrote:
>
> > When I start Vista, I always get a popup that says Windows blocked some
> > startup programs. When I go into Windows Defender to find out what is
> > being blocked, I get the list of programs loaded at startup, and each is
> > either designated "Permitted" or "Not yet classified." Even the "Not yet
> > classified" programs are being loaded. So how do I find out which ones
> > Windows is blocking?
> >
> >

Ross · External Since: Jun 13, 2006 Posts: 48

I've only tested it once, but it seems to have worked like a charm. The
Sonic program is not on my new Dell notebook, so either the Apricorn put it
on this machine or it was already on it and Vista or Apricorn object to it.
FYI 1, I've run MSCONFIG many times in the past, but not since installing
Vista on this machine. FYI 2, I get nearly all my music from XM or my own
CDs, and back up to a Kingston Data Traveler, which is why I don't record to
disks. FYI 3, this procedure is described very succinctly (for once) in
Vista Help under the heading "Run or remove blocked startup programs".
--
Ross

"Ross" wrote:

> I plowed through this whole thing and have at least identified my problem. I
> won't know until tomorrow whether I've solved it. First, I didn't use
> MSCONFIG to do anything, so I'm innocent in that regard. Second, the problem
> occurs on this computer, but not on a notebook sitting next to it. Third,
> the offending program (thanks to Rock for showing me how to find it) is Sonic
> Record Now program manager. My guess is that this came with an Apricorn DVD
> player I recently installed. Since I rarely if ever record anything, I'm
> going to disable this from the startup program list. We'll see what happens
> tomorrow.
> --
> Ross
>
>
> "Olly" wrote:
>
> > Have you been into msconfig ? type msconfig in search click on the file look
> > in start
> > up programes make sure they are all checked.
> >
> > "Tim" wrote:
> >
> > > When I start Vista, I always get a popup that says Windows blocked some
> > > startup programs. When I go into Windows Defender to find out what is
> > > being blocked, I get the list of programs loaded at startup, and each is
> > > either designated "Permitted" or "Not yet classified." Even the "Not yet
> > > classified" programs are being loaded. So how do I find out which ones
> > > Windows is blocking?
> > >
> > >