The issue is happening because changing the full assembly name (like product name or title) can cause Windows User Account Control (UAC) to treat the program as a new or unknown application.
Below steps can be followed
- Right-click your Visual Studio shortcut → Run as Administrator.
This gives full permission for testing the new assembly name.
2. Check your project’s manifest file: Go to your .csproj or project properties → Application tab → Manifest. Set it to "asInvoker" if it's set to "requireAdministrator".
This prevents asking for admin rights every time.
3.Changing small version parts (e.g., Ver 1.2.1 → 1.3) ,changing the whole name (e.g., Device Manager → Device FW Update Manager) can trigger UAC.
- After changing assembly name, do clean Solution and rebuild Solution
If still blocked, use Windows Defender → Allow app through controlled folder access.