Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I keep getting this irritating warning when copying files over the network:

These files might be harmful to your computer

These files might be harmful to your computer

Your internet security settings suggest that one or more files may be harmful. Do you want to use it anyway?

I am copying a file from \\\c$ (home server) to my local machine which is at \\

How do I turn off this meaningless "warning"?

share|improve this question

7 Answers 7

up vote 69 down vote accepted

I found a fix by changing "internet options" -- so I guess Windows is detecting the "internet" as my own network.. sigh.

  • Click Start / Control Panel / Internet Options
  • Click Security tab.
  • Click Local Intranet
  • Click Sites button.
  • Click Advanced button.
  • Enter the IP Address of the other machine or server (wildcards are allowed) and click Add
  • Click Close, then OK, then OK again.

Changing Internet Options screenshot

This worked for me, but it's a bummer I have to manually enter IPs here.. it would be nice if Windows could detect this is a local network file copy and skip the irritating (and pointless) warning about "dangerous" files.

share|improve this answer
I'm curious what you network adapter settings are (ipconfig /all) - It should be catching those addresses under "Automatically detect intranet network". –  Darth Android Jun 5 '10 at 8:34
If you use names for the computers (i.e. not IP addresses) then the default rules for local intranet (those three "include..." checkboxes) should apply. –  Richard Jun 5 '10 at 9:51
@Richard They should apply anyways, I have a number of windows system which I just reference by IP address and they copy files just fine. –  Darth Android Jun 5 '10 at 10:09
note @gerbenny answer at the bottom about wildcards in the sites dialog. –  IgalSt Aug 1 '11 at 9:04
Note that if the network share is open while this change is made, it has to be closed and reopened to see the change. –  azdev Sep 25 '12 at 13:14

Using Windows 7, I added my IP address with a wildcard:


Now all the ip's in this range are part of the "Local Intranet".

share|improve this answer
ah, good tip, it is not clear that dialog supports wildcards. –  Jeff Atwood Apr 23 '11 at 10:56

If you want to do this in Group Policy, this quote may be helpful to you.

You can control this with Group Policy, as well. Use gpedit.msc and drill down to

User Configuration → Policies → Administrative Templates → Windows Components → Internet Explorer → Internet Control Panel → Security Page

Enable "Intranet Zone Template" with the Low option.

Then enable "Site to Zone Assignment List" and use the Show button to add your "sites" (servername, servername.domain, ipaddress - the values you enter depend on what name or IP you use to access the share) with a value of 1.

Lastly - and this is the most important step - drill down one folder in gpedit to "Intranet Zone" and enable for "Launching programs and unsafe files", choosing Enable from the drop-down.

Close gpedit, reboot or run gpupdate /force and enjoy no more annoying Windows Security dialogues!

From the bottom of http://social.technet.microsoft.com/Forums/fi-FI/w7itprosecurity/thread/35ca8f9c-5e69-4b7f-a002-0d72fa0dc14b

share|improve this answer
+1 Thanks for sharing! Saved my ass today :) –  Anne Mar 27 '13 at 21:17
This is the best way! –  Jeffrey Kevin Pry May 8 '13 at 16:19
For anyone else following this, I couldn't find the .../Intranet Zone/Launching programs and unsafe files setting in my policies. However just doing the first step with file://*.example.com=1 did the trick. –  Styne666 Jun 28 '14 at 10:30

We recently put in a new server using DFS and I was having this same error. I ended up putting in:

" \\\servername.local.?"

After clicking add, it then showed:


I tried the * verses the ?, but that was not allowed.

share|improve this answer

I believe you wouldn't get the warning if you used the netbios name of your home server instead of the ip address. If you use the ip address or say the fully qualified dns name of the remote computer it doesn't recognize it as being in the intranet zone. the other option as mentioned earlier is to manually add it to the intranet zone list.

share|improve this answer

The other solutions here didn't work for me on Windows 7, but I found one that worked: remove Internet Explorer through Add/Remove Programs and then Adjust Windows Features. Unclick Internet Explorer 8. No more nag dialog!

share|improve this answer

Adding these two lines (without changing the default Local Intranet settings) is a quick fix:


You need to disconnect and reconnect shares for this to work.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.