C# Registry

Question

1.00/5 (1 vote)

See more:

Hello friends,

I am new to c#.

I am trying to make a program that can store my software related information in the system registry.
When I am trying to write the registry with c# code, it gives permission error; unable to write the registry.

Please give me a solution.

I am using this code with windows 7 and VS 2010.

Thank you in advance.

Posted 5-Sep-10 22:10pm

darora85

Updated 28-Nov-18 10:02am

Dalek Dave

v2

Add a Solution

Comments

Dalek Dave 6-Sep-10 4:23am

Edited for Readability and Grammar.

Richard MacCutchan 6-Sep-10 5:18am

Which key are you trying to update? Please show your code and the exact key that you are attempting to write.

2 solutions

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2010-09-05T22:14:00

Solution 1

The registry is protected space so your application needs to run with administrator privilege. Right click your app and select "Run as administrator".

Posted 5-Sep-10 22:14pm

Richard MacCutchan

Comments

darora85 6-Sep-10 4:22am

friend,
i am already running with the admin privilege, but it is not allowing to write the registry.Can this work be done by c# code also(getting admin privilege).

CPallini 6-Sep-10 4:28am

I believe your statement is valid just for some parts of the registry, like HKLM.

Dr_armin_R 29-May-11 2:36am

Yes, So true.
I tried to write on "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" but I couldn't ! Once I changed to HKCU there was no problem. It seems there exists some kind of Proxy.

daddy356 · Answer 2 · 2018-11-28T10:03:00

Solution 2

Hello,
Open the registry editor, click the start key and select run.
then type regedit and click ok.
When thr registry is open right click on the HKLM and choose permissions.
when the window comes up if you see Administrators click on it and then check
the box under allow, full control.

then that should do the trick

Posted 28-Nov-18 10:03am

daddy356

Comments

Dave Kreskowiak 28-Nov-18 16:31pm

That's a really bad "solution" to an 8 year old question. This "solution" isn't a solution at all and will prevent apps demanding this "solution" from being used in an enterprise environment.

Modifying security to get around a poor design practice is never a good idea.

C# Registry

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0

C# Registry

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0

Existing Members

...or Join us