Re: broken Administrative Tools links

More follow-up on this item. I do not think the problem is file
association related any more. All files with a .LNK extension that do
NOT have a specific target are affected. The most common examples of
this are the Administrative Tools, but Adobe is another link so
affected.

Again, these .LNK files do not have a specific target (right click
Active Directory Users and Computers under Administrative Tools to see
what I mean).

Nero (Ahead Inc) has no clue so far. They finally responded to my
second support request, but their cleaning tool did NOT fix the issue.

Anyone have some suggestions?


On Mon, 20 Feb 2006 10:44:26 -0500, Joe Granto <Joe.Granto@xxxxxxxxxx>
wrote:

I bought the newest version of Nero (v7). I installed with the default
options, which means Nero PhotoSnap installed. When file types got
modified to point to PhotoSnap, I noticed a problem.

All my Administrative Tools MMC shortcuts now that the PhotoSnap icon
instead of the correct icon. Things like ADUC, Terminal Services
Manager, etc.

These shortcuts, when you get properties, they have no true "target";
the target is grayed out, and they say "Windows Server 2003
Administration Tools Pack", so I have no idea what extention caused
the foul-up. Similarly, because there is no target to the link, there
is no "Change Icon" button.

I tried reinstalling the AdminPak = no joy
I tried uninstalling Nero = no joy
I have tried repairing icons = no joy

Anyone have any ideas of what extension I need to revert back to
defaults to get my icons back? I am still assuming it is the an
extension issue, since these files all show the PhotoSnap icon. The
MSC file type association is NOT the issue, I have checked. The
shortcuts in the Administrative Tools are not standard shortcuts, and
do not point the MSC files. Of course, I guess it may NOT be a file
association issue, so all ideas will be entertained.

This is really freakin' annoying. And yes, I have written Nero
support... no replies yet, and when they do reply, I am sure it will
be with a nonsensical answer (please reinstall Windows XP Pro). This
problem is repeatable (that is, I can recreate the issue on any XP Pro
system, at will).



Please replace the "NoSpam" with "Verizon" in my email address in order
to reply.
-------------------------------------------------------------------------
Joe Granto Joe.Granto@xxxxxxxxxx
Senior Engineer Intel Engineering,Verizon


Please replace the "NoSpam" with "Verizon" in my email address in order
to reply.
-------------------------------------------------------------------------
Joe Granto Joe.Granto@xxxxxxxxxx
Senior Engineer Intel Engineering,Verizon
.