blank item in startup list

[Guest]

when i run the system config utility, in the startup list there is one item
with no name (blank) and no command (also blank). Location =
SOFTWARE\Microsoft\Windows\currenVersion\Run

Any idea what this is, or how to find out?

Thanks.

 

[Rick \Nutcase\ Rogers]

Hi,

Click start/run, type regedit and click ok. Expand the plus (+) signs to
look at these keys:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Click on the key, then look in the right pane for a string that has the
<blank> entry. Click on it and delete it.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Guest]

Hi Rick, and thanks. Results:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run:
No blank items

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run:
All items have names and Types
One item, WiseFTP Scheduler, has no Data value. Is that the guy?

Also, noticed there is a subfolder to run on Local_Machine called
OptionalComponents, assume this is ok?

 

[Ramesh, MS-MVP]

In addition:

If it's a disabled startup entry, check here:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\MSConfig\startupreg]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\MSConfig\startupfolder]

 

[Rick \Nutcase\ Rogers]

Hi,

Check the keys Ramesh has mentioned.

All items have names and Types
One item, WiseFTP Scheduler, has no Data value. Is that the guy?

Not likely, but click on it, then file/export and save a copy, then delete
it. See what happens. You can put it back by doubleclicking the saved copy.

Also, noticed there is a subfolder to run on Local_Machine called
OptionalComponents, assume this is ok?

Yep, that's normal.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Guest]

Hi Rick and thanks,

Before I saw this I went ahead and deleted the registry key that had no data
value, without backing it up. Then I ran winconfig and the item is gone from
the Startup list.

I did not look at the keys that Ramesh mentoined because it was an "enabled"
startup item.

I have not rebooted.

Should I just cross my fingers and boot up?

thanks.

 

[Rick \Nutcase\ Rogers]

Hi,

Rebooting won't kill anything, the entry wasn't required for normal
operation.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Wesley Vogel]

Apparently, if there is no path, or maybe an incorrect path, in Value Data,
the item shows up blank in msconfig | Startup. Also if Default under Data
is blank (nothing there at all) instead of (value not set).

The entry was a startup orphan.

From PCForrest StartMan\Help

[[An orphan is a startup item that has a non-existent target file.
A target is the file which a startup will run when invoked.

How do Orphans occur?
They primarily occur because you've disabled a startup and then, at a later
date, uninstalled the program that uses it. The uninstaller won't know
about the disabled startup so it gets left behind. And if the uninstaller
deletes the target file then the startup becomes an orphan.

Orphans can also occur if you rename or move the target file elsewhere.
Where an orphan is also enabled you may see missing file reports at startup.
In the case of menu startups (shortcuts), the shell will attempt to resolve
the target by a brute-force search for the file based upon the information
stored in the shortcut.

How do I avoid creating orphans when uninstalling software?
Firstly, before uninstalling any software, ensure all its startups are
enabled with StartMan. This ensures all its startups can be located. Next,
use the program's own options to disable or remove the startups - if that is
an option. Finally, uninstall the software. All things being equal, the
startups should be gone, along with the software that used them. If
not...

How should I deal with orphans?
In most cases the orphan should simply be deleted. However, there are
instances where this might be impractical. For instance, a program that
automatically restores its own startups will continually recreate the
orphan - unless it also re-instates the target. In such cases the best
course of action is to disable the startup via the program that uses it.
But if no option exists then uninstalling the software is the only practical
option. If the software is essential to you, you should consider restoring
the target.

Do I have to delete orphans?
No, you don't have to if you don't want to. If they're disabled they'll
cause no real problems except to confuse you during troubleshooting. But if
they're enabled you should consider removing them. If they're not required,
then they have no business being there at all.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In