Thanks, I'll look into the VB scripting since putting the admin password out there unencrypted is not an option. The overall problem, and the reason I need to load this registry key everytime a user logs on traces back to Symantec AntiVirus. My corp. is running 10.0 and everyone was receiving DoScan.exe errors. We tried running the Symantec service on all of the machines as admin, but it kept dropping the logon priveledges for the service and knew that shouldn't be the final fix. So I found out Symantec has a RemoveStartScan.reg file that can be run to stop the scans at startup, but it has to be run everytime a user logs on. This got rid of the DoScan.exe errors, but introduced the registry merge popup I stated above. I heard 10.1 fixes this solution, but that costs $$ The RemoveStartScan.reg changes HKCU settings.