2
I know how to do this in Windows XP, as explained in this answer, but it seems that LocalizedString in HKLM\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D} is locked in Windows 7. Every time I try to edit it, I get the following error, Cannot edit LocalizedString: Error writing the value's new contents
Does anyone know how I can edit this to show the computer name on the desktop’s "Computer" icon?
Jason
Posted 2012-02-27T02:33:10.747
Reputation: 131
1
@Synetech, thanks a lot for pointing me to the not so obvious, I probably would have never seen it had not been for your help (upvoted your answer), and yes I was already running as admin, I have UAC set to elevate without prompt for admins (also tried running "as administrator", running from cmd prompt started as admin, etc, etc, but nothing worked) but didn't work
Fix: Turns out, that key is stupidly configured (imho), neither System, nor Administrators had write access to that key, I had to take ownership of the key then give administrators write access to be able to modify it.
Jason
Posted 2012-02-27T02:33:10.747
Reputation: 131
4
That key is protected. To write to it, you need to give yourself write permission to it.
Synetech
Posted 2012-02-27T02:33:10.747
Reputation: 63 242
Hmm, curious that somebody decided to rescind an up-vote today after almost a year without explanation. I can’t address any problems or provide help if no comment is left. sigh – Synetech – 2012-12-05T15:52:51.370
1
Open regedit with the Sysinternals command line utility PsExec with -i -d -s switches:
Example: "C:\Program Files\Sysinternals Suite\PsExec.exe" -i -d -s C:\Windows\regedit.exe
(This works even with the «Legacy» registry entries for example...)
PsExec: http://technet.microsoft.com/en-us/sysinternals/bb897553
Hope this help. Let us know.
climenole
Posted 2012-02-27T02:33:10.747
Reputation: 3 180
I tried simmilar approach psexec -i -s cmd then ran regedit from there, but didn't work, as I stated in my own answer, I found out that neither administrators nor system had write access to this key – Jason – 2012-02-27T15:00:32.533
May be the wrong switches... – climenole – 2012-02-27T15:01:48.937
wrong switches? – Jason – 2012-02-27T15:02:36.993
l instead of i ... (I do it the 1st time I used PsExec... :-S ) – climenole – 2012-02-27T17:30:00.550
got you, I guess I'm old school, having the console there before I launch that and other commands and perhaps see if I get some error make me feel warm and fuzzy :) – Jason – 2012-02-27T19:04:17.277
Finally you find it! Good news :) – climenole – 2012-02-27T15:10:32.187
Turns out, that key is stupidly configured (imho), neither System, nor Administrators had write access to that key, I had to take ownership of the key then give administrators write access to be able to modify it.Um, yes, that’s what I said. – Synetech – 2012-12-05T15:53:54.380@Synetech actually, that's what you said after I figured it out the hard way, thanks to hints from both you and climenole (and upvoted both answers), but whatever – Jason – 2012-12-06T22:01:34.993
Okay; I don’t know what happens behind the scenes, I can only see the timestamps. Cheers. – Synetech – 2012-12-07T02:11:30.690