• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 482
  • Last Modified:

ALL Windows shortcuts (LNK) hang, direct EXE files work fine

Whenever you double click on any shortcut file (.lnk) explorer hangs/freezes for 10-20 seconds.  Current running applications do not freeze, just explorer.  Note that during this time if you show task manager, everything is normal - no spikes in CPU utilization etc.

However, if I navigate say, into program files and open the same application from it's executable, it responds as it should- instantaneously.  

I'm talking about new out of the box computers that were just built (7 of them) with 2GB of RAM and Pentium D processors.  

Here's the REALLY weird thing:  If you disable the LAN in network connections in Control Panel, all the .lnk files start working fine.  Again, replicatable on 7 machines.  And none of the shortcuts point to network locations!

Now, I'm pretty sure I know what caused this:  Our company has a financial application that is delivered through the Novell application launcher window- after installing the files necessary to be able to run it, the same issue appeared on all computers.

The remaining 21 workstations that have not had this application installed are fine.  The problem is, the application has been in use for 5 years, has not caused any issues - and  is NECESSARY.  There is no option to not-install it at this time.  

I don't even know where to start on this. Uninstalling the financial application does not fix the problem (probably because the uninstaller is garbage)

Mind you, it's my job to fix the computers, but this by far has got me stumped.

Notes:  I've tried running Regmon to see if the finance app had modified keys and that was what was causing the hanging - but I make heads or tails.  

While I can always run apps from their direct exe file, these financial folks won't be able to wait 20 seconds every time they double click on an application...
0
vincentlocke
Asked:
vincentlocke
1 Solution
 
administradoresCommented:
Make sure you have the latest version of NAL and also the latest NIC drivers, looks like that.

It could be an issue with NAL and the APP, and as a workarround you can create bacth files as if they were shortcuts, so the users don't have to browse by now.
0
 
Alan Huseyin KayahanCommented:
  Hi vincentlocke
      *Click Start, click Run, then type gpedit.msc. Press ENTER
      *Under User Configuration expand Administrative Templates, and then expand Start Menu and Taskbar.
      *Double-click Do not use the search-based method when resolving shell shortcuts, and then click Enable.
      *Double-click Do not use the tracking-based method when resolving shell shortcuts, and then click Enable.
     *Expand User Configuration, expand Administrative Templates, expand Windows Components, expand Windows Explorer, double-click Do not track Shell shortcuts while roaming, and then click Enable

Regards
0
 
vincentlockeAuthor Commented:
MrHusy-

Thanks for the advice, but that didn't change anything.  Note that the shortcut files don't bring up any window looking for the target;  they kind of just hang.

administradores-

I am going to try uninstalling Novell, then uninstalling the NIC drivers and reinstalling both - and hope that the App continues to function.

Thanks for your suggestions, will post more after I try uninstalling and reinstalling NIC drivers...
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
vincentlockeAuthor Commented:
Uninstalling Novell client (which by the way is configured for IP only) / uninstalling network drivers and reinstalling both made the problem go away for about 1 minute, now its the same old again.
0
 
administradoresCommented:


Can you post the properties of these links, right clicking over the link and properties, and selecting second tab.
0
 
administradoresCommented:
Need to know were they start.
0
 
vincentlockeAuthor Commented:
I found the solution.

apparently, after reading about a simliar problem except with network paths - I was able to see using FILEMON from sysinternals that Explorer.exe after double clicking on anything that was NOT an .exe file would attempt to load wshenu.dll about 50 times.  During these attempts the system would lag.

Downloaded and installed Windows Script 5.7 - which corrects the issue, because wshenu.dll doesn't even exist, so the new version makes these calls just not happen.

Not sure why the calls started happening to begin with, but they don't appear on our other computers which don't run this App.

Thanks all for your time.

Can someone close this?
0
 
administradoresCommented:
Nice you solved.


Aks for a refund on the next link.

http://www.experts-exchange.com/Community_Support/General/#browseZones
0
 
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now