The problem might have some to do with how windows finds these shortcuts.
Any reasonable person might expect that they store the shortcut data in the registry, the registry resides in ram, and they put everything else in there :-)
Instead the Key shorcuts for .INK and .URL are inside the shortcut itself.
As you can see in the picture , after trying to trace down where it was in the registry (its not), I found the change in the Shortcut own data itself.
There are 2 major locations where this data is scanned from, anywhere in all of the start menu, and via the desktop folder.
When people find that removing some program, or some web program, "fixes" the problem, mabey it has to do with items , or mappings, or some unapproved stuff in the start menu or the desktop?
After realising the method used, it was easy enough to take the advice of using another method other than windows, to do the same things.
The notepad shortcut method used, is going to add microbes of delay also. A shortcut to a text file itself, that will eventually open a notepad, will get to go through a fun process. Find the class bounce around in the registry, find the associated program, open that program, and pass in that parameter.
Most program shortcuts can have quoted whole paths "C:\Windows\Notepad" , instead of using environment variables to eventually locate the program, in the many environment variable paths. . Many programs like to stuff thier program path into the enviroment variable path, they have even broken the "search path" there by making the line to long.
Most Program shortcuts can also have quoted parmeters placed after the quoted program path "d:\documents\todo.txt". this has the computer finding the file direct without searching or guessing, and passing the file to it imediataly. (the quotes only nessisary when there are spaces)
If you want to see speed, try it as "C:\Windows\Notepad" "d:\documents\todo.txt" And cut out the middleman. Create the shortcut for the program instead (notepad), and add a parameter for the txt file into the program shortcut. Ok its like DOS now :-) But faster.
To check the enviroment variables (which is only for specific issues) Go to "System", and in the "System Properties", in "Advanced" bring up the "Enviroment Variables" and look at the mess in the PATH variable.