Software Deployment

You havn't given us much details to go with.

Was one of the deleted files they target of the shortcut?
Check the verbose log what gets repaired during self-healing.
What does the Shortcut table entry look like?
Is it a 16-bit executable?
What operating system?

Sorry I didn't provide the complete information.

My application is having only one feature , under this all the files and registries are there.
My application shortcut is pointing to that feature and it is advertised.
I have taken verbose log file but in this it has shown " The configuration completed successfully".
Here I am using XP OS.

there must be few junk entries or any entries related to the build in your application.try cleaning it up and check.

Besides deleting junk entries also check if there is any HKCU data in your application and it is not getting populated when you login in standard user and launch the shortcut, you may get tht error then use Active setup

Check the Event Viewer. That will identify which component triggered the repair and you can work from there.

Hi All,

I have checked the packge. My package doesn't have junk entries and No HKCU entries.

But still it is showing the my computer window.

I checked in the event viewer, It is showing the application related shorcut component as warning. My application i s having 25 shortcuts. In this 10 are advertised. For all the advertised shortcuts EventVeiwer is showing the related componenet as the warning. So how should I proceed with this. As this is a setup capture it is having only one feature. Please help me.

Have you validated the package?

Yes, I validated the package

So there are no warnings or errors in the package then?

I have 33,03,09,47 warnings are there . And ICE 43,57 errrors are there which are related to non advertised shortcuts.

Maybe you should fix these before doing anything else... particulary the ICE57's which may relate to the cause of your problem.

After resolving this ICE 57 error also it is not working.

Steps I would follow

Fix all possible ICE warnings/errors - this should be standard practice I'm surprised you dont already do this?
Verify a log generated from the repair that all components are being repaired correctly - wilogutil.exe will help you

Recreate the offending shortcut(s) / component(s)