@gabri3l:

I did as you suggested. The Event Log contained the warning messages telling me that "C:\Documents and Settings\All Users\Start Menu\..." was not available. Then I copied the Component Id, installed ORCA.MSI from the PlatformSDK, opened the installation MSI and found the Component Id in the component section. But the KeyPath is an empty value. I can't delete anything from it since there is nothing in it. I guess this is since the shortcuts are not already packed into the MSI, but only created at installation time.

Then I tried to remove the whole row. The MSI gave me an internal error when I started it. I searched for other occurences of the Component Id, but I didn't find it anywhere else.

Then I searched for the names of the Start Menu entries and found them in the Shortcuts category. I deleted them all and saved the MSI file and installed the software again. This time I had no shortcuts in my Start Menu. I created a shortcut on my own and started the software. This time I was in an endless loop of "repairing" the "damaged" software. Which I only could stop by "burning" them with LordPE, since my Task manager didn't allow me to terminate the processes.

Then I tried to find some occurences of the files the shortcuts pointed to, but I didn't find anything which I would classify as "this is it" (I don't know much about MSI).

How does the auto-repair feature of MSI file work anyway? If I execute "TEST.EXE", does Windows check if it is a MSI installed application and launch the installer to check it or must "TEST.EXE" call some MSI APIs itself to check if it needs to be repaired?

I bet disabling this would decrease startup time of MSI installed software.