1. Error 1921 Service Mcafee Agent Common Services Could Not Be Stopped

Techyv is one of the leading solution providers covering different aspects of Computers and Information Technology. We have a hardworking team of professionals in different areas that can provide you with guaranteed solutions to a blend of your problems. Could not delete key on uninstall, could not write value(s) during install. Win7Pro 64-bit. By blankslate, October 13, 2014 in ESET Internet Security & ESET Smart Security Premium. In the Permissions dialog box, make sure that the Administrator group has Full Control.Now again right-click the registry key and in the popup menu, select Delete.Click Yes on the confirmation prompt. Other Uninstall Errors. If the PC configuration has not changed, you can also try reinstalling the problematic software, and then uninstall it.

I'm trying to delete some registry keys (startup items) via the commandline and while I can delete from HKCUSOFTWAREMicrosoftWindowsCurrentVersionRun just fine I cannot delete anything from HKLMSOFTWAREMicrosoftWindowsCurrentVersionRun.

I even created some temporary keys there through regedit.exe, but even those are undeletable via the commandline.So I searched through similar threads here and obviously googled it. Usually this happens because:

1. Command prompt is not run as administrator. That's not the case here as I definitely have administrator rights within the launched cmd window.
2. Registry permissions are blocking deletion. Again, this is not the case here. I manually changed permission through regedit.exe and I'm now the owner of HKLMSOFTWAREMicrosoftWindowsCurrentVersionRun along with full control for my account.

The specific error message given by commandline is:

Yet the key definitely exists in the location where I'm trying to delete it from and even regedit shows its there. I can also delete it with regedit without a problem.

Anyone have any clues as what to check?

OK, so while writing this post I stumbled upon something really bizarre. It would appear that there are two versions of HKLMSOFTWAREMicrosoftWindowsCurrentVersionRun.

Error 1921 Service Mcafee Agent Common Services Could Not Be Stopped

I have no idea hows this even possible, but when I copy the key name in regedit they are both identical and yet they display different items. The first one is OK and it seems reg.exe is trying to find and delete the key in this location and that's why it errors out. The second one is the problematic one where the key exists that I need to delete via the commandline.

However when I add an identical key to HKLMSOFTWAREMicrosoftWindowsCurrentVersionRun it gets written to the 'correct' location, and I can also delete it via commandline.

OK, I think I know what the problem is now. The 'correct' location is displayed when I run a native 64-bit version of regedit, and the problematic one is only displayed when I run a 32-bit version of regedit.

SOLUTION:

Use %windir%SysWOW64reg.exe to manipulate 32-bit registry entries and %windir%System32reg.exe to manipulate 64-bit registry entries. I'm going to have a stern talk with the program authors though about why they shove their startup key into the 32-bit reqistry on a 64-bit system.

Peter MortensenTMRWTMRW

1 Answer

SOLUTION: Use %windir%SysWOW64reg.exe to manipulate 32-bit registry entries and %windir%System32reg.exe to manipulate 64-bit registry entries.

I'm going to have a stern talk with the program authors though about why they shove their startup key into the 32-bit reqistry on a 64-bit system.

Peter MortensenTMRWTMRW

Not the answer you're looking for? Browse other questions tagged windows-7command-linewindows-registry or ask your own question.