"franknark" <> wrote in message
news:19AF2653-1BCF-4487-B4D6-...
> A Vista SP1 Home Premium problem - 9 live icons covering 9 dead icons:
>
> Several days ago I had a desktop with 9 live, working icons at the bottom
> of
> the desktop. ie: recycle bin, computer, network, control panel, etc.
> The
> 9th icon was a folder called 'powershell'.
>
> Several days ago I deleted the 'powershell' folder, and, underneath that
> folder, was surprised to find a dead copy of the 'powershell' folder.
> The
> deleted 'powershell' folder was in the recycle bin, and an undeleted dead
> copy on the desktop.
>
> This dead copy cannot be accessed with selection, left-click, or
> right-click
> operations - so the 'Properties' info cannot be displayed.
>
> Left, right, up, down arrow keys cannot move an icon selection area to
> this
> dead icon.
>
> A desktop refresh has no affect - a restart has no affect.
>
> The C:\Users\frank\Desktop directory list does not show the dead folder.
>
> Creating a new desktop folder with the same name 'powershell' does not
> upset
> vista. This can be done either on top of the dead folder or somewhere
> else
> on the desktop. Deleting the live 'powershell' has no affect on the dead
> 'powershell' folder.
>
> It turns out that all 9 live icons were covering 9 dead icons. When a
> selection area is drawn around the 9 icons, and the area with 9 icons
> moved
> up to the middle of the screen, the 9 dead icons remain. None of them can
> be
> accessed or deleted.
>
> Any suggestions about getting rid of the dead icons?
>
> Thanks in advance.
Hi--
I reread and some or all of your icons are what are called "system" icons.
In that case, they aren't going to be simply shift+deletable. To mod or get
rid of them, you might be able to use some of the delete undeletable file
free apps or even Doug's method, but often to change them **you need to go
to the registry**. You may have to google "delete system icons." The
hacks for deleting these icons definitely involve registry subkey mods.
In earlier versions of Windows like Win 9x, you removed icons like the ones
you had by removing registry subkeys from the key called NameSpace. It
often caused instability when some were removed like the one for Network
Neighborhood.
Go to regedit in the run box (windows key + r for red at the same time) or
just type regedit in the search box above windows start button . Thanks to
Jerry Honeycutt's book for this info:
These should be removable by editing HKLM or HKCU in the branch
SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer . What you do is to right
click that subkey, and click Add in the right click context menu, and choose
Add a RegDWORD value and type in the box the name for the value which is
HideMyComputerIcons. You also might try adding the value HideDesktopIcons
which has worked.
The specific name might have to be the class ID of the particular icon you
want to hide. You've already named them so for example it could be
HidePowershellIcons or HideRecycleBinIcons and yes the plural of icons gets
used for some reason although you can try singular.
This gets more complicated than I have room for, and I refer you to Jerry
Honeycut's fantastic Windows Registry Guide p. 88 and others (MSFT Press)
where I pulled this info. Jerry's instructions are really critical to
getting this done. I just wanted to give you an idea of what might be
involved. You really should read Jerry's book to appreciate the scope of
what is involved here, because I scratched the surface in the space/time I
had.
http://www.honeycutt.com/
http://www.honeycutt.com/About/tabid/75/Default.aspx
The reason I'm hemming and hawing on this is because you don't know and we
don't know the genesis of this curious phenomenon. I wish you tube had been
around when I had about 30 ifile icons on my desktop in ME and every time I
deleted all of them another layer smacked me in the face. It would have
made a great You Tube and I would also have emailed it to Redmond. To this
day, I'm not sure what it was but if it happened now I think I'd be better
at rooting out the cause--possibly some type of spyware/mild trojan hybrid.
It was so funny it was worth having the problem.
CH