Windows 7's Default Security?
DY357LX
Playing since day 1. Still can't Comm.England Join Date: 2002-10-27 Member: 1651Members, Constellation
in Off-Topic
<div class="IPBDescription">Couple of oddities installing stuff.</div>A friend of mine recently picked up a nice new gaming rig. It has Windows 7 installed (and up-to-date).
But last week I tried to install Minecraft for her, it said "omg java iz required nub" so I headed off to the Java site and downloaded it. Only for the installer to fail at around 97% claiming it couldn't retrieve the remaining files.
A quick Google revealed that it was probably the default Windows Firewall being difficult. Not wanting to mess with someone else's Firewall I instead installed Minecraft on her laptop and all was good.
But today, she's launched WoW to try out the new patch, only to be told that the patching process failed (at 100% of checking patch files) because the "Logs" folder is read-only.
Fair enough, I altered the folder attributes and unchecked Read-Only. Still fails. (Untick, "APPLY" - "OKAY".)
I then altered the attributes of the entire WoW folder and unchecked the Read-Only for there as well. Still no go.
Tried a attrib -R in CMD but alas, no joy.
The weird thing is, this WoW installation is exactly the same as mine (on a Win7 machine) because I copied it to my external HDD and took it round to her house so she wouldn't have to download 17 gig. (Maybe this is where the problem lies?)
Browsing the WoW forums results in 2 solutions:
Untick the read-only box. - Tried it.
Delete WoW and re-download it. - That's a last resort as it's now 24 gig.
Anyone have any idea's? UAC is OFF and I'm outta idea's. (It's looking like the external HDD will have to save the day.)
Thanks.
Oh, one last thing, any Windows 7 Users that can tell me the DEFAULT installation path for WoW?
(Does it insist on going in a Public\Games folder or is Program Files (x86) fine?)
But last week I tried to install Minecraft for her, it said "omg java iz required nub" so I headed off to the Java site and downloaded it. Only for the installer to fail at around 97% claiming it couldn't retrieve the remaining files.
A quick Google revealed that it was probably the default Windows Firewall being difficult. Not wanting to mess with someone else's Firewall I instead installed Minecraft on her laptop and all was good.
But today, she's launched WoW to try out the new patch, only to be told that the patching process failed (at 100% of checking patch files) because the "Logs" folder is read-only.
Fair enough, I altered the folder attributes and unchecked Read-Only. Still fails. (Untick, "APPLY" - "OKAY".)
I then altered the attributes of the entire WoW folder and unchecked the Read-Only for there as well. Still no go.
Tried a attrib -R in CMD but alas, no joy.
The weird thing is, this WoW installation is exactly the same as mine (on a Win7 machine) because I copied it to my external HDD and took it round to her house so she wouldn't have to download 17 gig. (Maybe this is where the problem lies?)
Browsing the WoW forums results in 2 solutions:
Untick the read-only box. - Tried it.
Delete WoW and re-download it. - That's a last resort as it's now 24 gig.
Anyone have any idea's? UAC is OFF and I'm outta idea's. (It's looking like the external HDD will have to save the day.)
Thanks.
Oh, one last thing, any Windows 7 Users that can tell me the DEFAULT installation path for WoW?
(Does it insist on going in a Public\Games folder or is Program Files (x86) fine?)
Comments
- Are you installing with an administrator account?
- Is the UAC enabled?
- If the UAC is enabled did you remember to run run the installer with administrator privileges?
- File permissions are usually a non issue, unless you have modified those by hand before.
- Windows firewlal is also a non issue, cause it only blocks incoming packets, that do not have a corresponding socket. So as long as communication is initiated from you machine, the firewall does not interfere.
EDIT:
Being unable to modify a specific folders properties is most likely because that folder inherits it's properties from an parent folder.
Your best bet would be to make the whole folder structure read only and then remove the read only attribute.
However if you copied the files over a serious of NTFS volumes ACLs are going to be intact. So you should make your friend owner of the whole structure first, before removing the read only attribute.