Why does SQL Browser service get disabled?
The SQL Server Browser Service is installed often in Disabled state (and this is what my SQL Slammer link is about, it gives the history why the Browser service is preffered to be disabled unless required). It is only required for named instances or instances listening on non-default ports. Your application installer should only restart the Browser service if needed, and certainly should check for a disabled service and ask an administrator permission to enable the service (ie. display a confirmation dialog) before messing with it.