Windows 7 permission bug.

[agreenbhm]

Might not of explained it 100% but the host file i downloaded is also the same one i uploaded/created so that others could connect to my home server, Its not just some random host file. It was just easier to Re-download it from my rapidshare account than to re-write it. Mainly because it has 3 different IPs that i couldnt remember off the top of my head. internal/external and an Nprotect line.

What i was talking about with home/pro is the max ammount of ram 32 bit reads. i have 8gigs and on xp home it would only read 3,125 of it. XP pro is 64bit and will read 16g of RAM. I had purchased this amount of RAM because i had planned on buying XP pro in the near future (also got a good deal) but trying win7 for now.

As far as a person that should or shouldnt be testing beta software i agree, Im really not "testing" anything for the purpose of providing any usefull feedback. Im really just trying it out for myself to see if i like it.

After this explanation, I take back what I said before. Your initial description sounded vague and noobish, but your follow up shows you seem to know a bit more than it seemed. Hopefully no hard feelings :p .

Perhaps try to delete the HOSTS file and then paste the new file into the folder. Also, what account are you using? An administrative account or the Administrator account? If you're not using the Admin account, open Local Users and Groups using Start -> Run ->"LUSRMGR.MSC" (without the quotes). Right click the Administrator account, click properties, then uncheck where it says "Account is disabled".

Then try to login as the Admin and try doing the HOSTS file from there.

[[DGS]]

Found this thread through googling.

I have the final WINDOWS 7 PROFESSIONAL installed (waiting for my serial number to arrive with the CD from Amazon on Oct 20th) and I have the same problem.

No fix has come up for this problem yet? It's really annoying!

I am using Firefox 3.5.3

[squ1zzy]

Sorry, fix doesn't work. It looks like NOD32 is the problem. Disable it and it works fine.

Edited October 4, 2009 by squ1zzy

[[DGS]]

I disabled being on a spesific workgroup and reverted back to just "WORKGROUP" and the problem disappeared.

I have NOD32 V.4 Antivirus still enabled. Problem disappeared.

[chiphuvOz]

I disabled being on a spesific workgroup and reverted back to just "WORKGROUP" and the problem disappeared.

Sorry... but can you please show me how to do this? Thanks a lot.

[CyberManifest]

Ok, I was encountering this too, until I figured out the problem. See the thing is there's a descrpancy between "An Administrator" and "The Administrator". By default "The Administrator" is disabled; er sorta, when you change security settings or when you use the "Run as Administrator" option, then you are in fact using "The Administrator" account and the permissions get set to only be accessible by "The Administrator" even if you are "An Administrator". Simply enable the Administrator account using "lusrmgr.msc" from the run box and make adjustments on the files in question; or change permission properties back to your own administrator account. You can either do this or other work arounds include using a tweak tool to enable the context menu item "Take Ownership" such as "Windows Ultimate Tweak" or use a 3rd party program like "Unlocker" to make adjustments. If it's a command box option/action you don't have permission for then try "Windows Enabler" (Google It). One such example of a command box without permission is the default profile transfer in the advance settings of the system properties. You can transfer the default profile to exsisting users or new users, but you can't transfer regular user profiles to other regular profiles without the help of "Windows Enabler" ;-) Hope this bit of information helps. It worked for me.

[Linkinfamous]

Ok, I was encountering this too, until I figured out the problem. See the thing is there's a descrpancy between "An Administrator" and "The Administrator". By default "The Administrator" is disabled; er sorta, when you change security settings or when you use the "Run as Administrator" option, then you are in fact using "The Administrator" account and the permissions get set to only be accessible by "The Administrator" even if you are "An Administrator". Simply enable the Administrator account using "lusrmgr.msc" from the run box and make adjustments on the files in question; or change permission properties back to your own administrator account.

That is a pretty incorrect view of how integrity levels in Windows Vista and 7 work. When you launch something as an administrator, you're just launching it as a high-IL process, but it's still you.

[NfoTech]

Uhhh... get the RTM version?

[Digital Rage]

Might not of explained it 100% but the host file i downloaded is also the same one i uploaded/created so that others could connect to my home server, Its not just some random host file. It was just easier to Re-download it from my rapidshare account than to re-write it. Mainly because it has 3 different IPs that i couldnt remember off the top of my head. internal/external and an Nprotect line.

What i was talking about with home/pro is the max ammount of ram 32 bit reads. i have 8gigs and on xp home it would only read 3,125 of it. XP pro is 64bit and will read 16g of RAM. I had purchased this amount of RAM because i had planned on buying XP pro in the near future (also got a good deal) but trying win7 for now.

As far as a person that should or shouldnt be testing beta software i agree, Im really not "testing" anything for the purpose of providing any usefull feedback. Im really just trying it out for myself to see if i like it.

Ok. I think I am going to agree with agreenbhm. I think you should perhaps do a bit more research before you blindly jump into Windows 7. I think you also need to do a bit of research on XP as well. If you buy XP Pro don't assume it's going to see all that 16G of RAM because chances are it won't. Reason... XP Pro comes in 32bit & 64bit versions. If you just walk into a retail store and ask for XP Pro chances are they will just sell you the 32bit version unless you specifically ask for the 64bit. Also going with 64bit XP is sort of a waste of time as there are few programs that support it and I haven't seen too many hardware manufacturers that make drivers for it either. Even Microsoft doesn't really support it as they seem to do the bare minimum for updates with it. For example there is SP3 for 32bit but only SP2 for 64bit (however the Microsoft Technet forums say that patches for Server 2003 x64 are "generally" installable for XP Pro x64). Yeah... Good luck with that. :)

[Sooraj Nadarajan]

Hi All,

I faced the same problem while saving images from Firefox 3.5 on my Win 7 - 64 bit.

I felt it was my anti virus (Nod 32) n i disabled Scan on " File Creation "

It started working fine as before :)

[Nehemoth]

The last Eset version:

ESET Smart Security 4

Microsoft? Windows? 7/Vista/XP/2000

Version: 4.0.474, File size: 35.42 MB,

And changelog from http://www.eset.com/joomla/index.php...=4113&Itemid=5

November 25, 2009 - 4.0.467?4.0.474

ESET Smart Security 4

Fix: Error logs are generated while the personal firewall is disabled after every reboot of the PC

Fix: Problems after PC restart when firewall system integration is in "Only scan application protocols" mode

Fix: Anti-spam boot failure when "Folder Redirection" is set on Windows Server

Fix: Scheduler task is not displaying scan targets

Fix: Graphic User Interface crash when making changes in the exclusions in the spam list

Fix: Slow opening of Office documents from a Windows 2003 server share

Fix: Intermittent error when saving files on Windows 7

Other minor fixes and improvements..

I had that security error and upgraded the latest version. Now no error like that.

Source windows7forums.com

[RealFduch]

Ok, I was encountering this too, until I figured out the problem. See the thing is there's a descrpancy between "An Administrator" and "The Administrator". By default "The Administrator" is disabled; er sorta, when you change security settings or when you use the "Run as Administrator" option, then you are in fact using "The Administrator" account and the permissions get set to only be accessible by "The Administrator" even if you are "An Administrator". Simply enable the Administrator account using "lusrmgr.msc" from the run box and make adjustments on the files in question;

You are plain wrong. Why didn't you just test this crazy hypothesis before posting? Just "Run as Administrator" cmd.exe and type "whoami".

"Run as Administrator" does not run the program as the "Administrator" user.

And stop advicing nonsence like enabling that user.

As for the permissions, just give the required access to the "Administrators" group.