Changing config.nt

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I can't seem to save changes to c:\windows\system32\config.nt

The file's attributes do not show read only, yet it will not let me save
changes.

How can I make a change to the file?

I am logged on as an administrator.
 
Well, it's basically a startup file for MSDOS - it shouldn't really need to
be changed in Vista, but you might want to check the permissions on the file
to make it "write" and "read" by your user.

--
Zack Whittaker
» ZackNET Enterprises: www.zacknet.co.uk
» MSBlog on ResDev: www.msblog.org
» Vista Knowledge Base: www.vistabase.co.uk
» This mailing is provided "as is" with no warranties, and confers no
rights. All opinions expressed are those of myself unless stated so, and not
of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared
that up!

--: Original message follows :--
 
Sounds like you a UAC problem. Have you tried loggin on as the local
administrator account?

You will need to enable the account in compmgmt.msc then
1.. From the Start menu, go to "All Programs", "Accessories"
2.. Right-click on "Command Prompt" and choose "Run as Administrator"
3.. Click "Allow" from the ConsentUI prompt
4.. In the resulting Command window, enter "regedit" and press enter
5.. In regedit, browse to HKLM\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon
6.. Add a new key at that level called SpecialAccounts
7.. In the SpecialAccounts key, create a sub-key called UserList
8.. At this point the path is: HKLM\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon\SpecialAccounts\UserList
9.. In the UserList key, create a new value of type DWORD (32 bit) called
Administrator and set the value to 1.
Josh
http://windowsconnected.com
 
Zack,

Thanks for the reply. It turns out that my application does require me to
change the Files=40 line to a higher number to execute properly.

Your suggestion to change the premissions for all users did fix the problem;
however, the correct solution was discovered after reading Josh's reply.

Even though the user I was logged in as is an administrator, apparently I do
not have administrator rights when I run a command prompt unless I right
click on the "Command Prompt" and choose "Run as Administrator".
 
Josh,

Thanks for the reply.

You helped me to realize that even though the user I was logged in as is an
administrator, apparently I do not have administrator rights when I run a
command prompt unless I right click on the "Command Prompt" and choose "Run
as Administrator".
 
Back
Top