Skip to content

Learn how to fix "These files might be harmful to your computer" warning while copying files from local shares/sites to Windows 10/8/7, in this post.

While accessing or copying files from local home server, network share or site, you might receive following warning:

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?

FIX These Files Might Be Harmful To Your Computer In Windows 10

If you’re pretty sure that the share from which you’re getting file(s) is trustworthy but still you see this warning, you need to fix it. On local servers this warning is actually meaningless because the servers or shares are yours. The warning seems legitimate only for third-party shares/servers. So you can turn off this annoying warning for local intranet zone. Here’s how:

FIX: ‘These Files Might Be Harmful To Your Computer’ In Windows 10/8.1/8/7

FIX 1 – Via Internet Properties

1. Press W8K + R and type inetcpl.cpl in the Run dialog box, to open Internet Properties.

Internet Explorer Properties

2. In Internet Properties window, switch to Security tab. Select Local intranet and click Sites button.

FIX These Files Might Be Harmful To Your Computer In Windows 10

3. Next, click Advanced in Local intranet window.

FIX These Files Might Be Harmful To Your Computer In Windows 10

4. Finally, add your local sites, share’s IP address to the zone list. You can add a wildcard entry as well, for example, share 192.168.1.* should cover 192.168.1.101192.168.102 and so on. Click Close, once you’re done.

FIX These Files Might Be Harmful To Your Computer In Windows 10

Exit Internet Properties. You would no longer face the warning now.

FIX 2 – Via Group Policy

FYI: GPO snap-in is not available in Windows 10 Home editions. If you’re on Windows 10 Home and want to use Group Policy, go here and upgrade to Pro edition.

1. Press W8K + R and put gpedit.msc in Run dialog box to open Local Group Policy Editor. Click OK.

Local Group Policy Editor

2. Next, in the GPO snap-in window, navigate here:

User Configuration > Administrative Templates > Internet Explorer > Internet Control Panel > Security Page

FIX These Files Might Be Harmful To Your Computer In Windows 10

3. In the right pane of Security Page, look for the policy setting named Intranet Zone Template. The policy is Not Configured by default. Double click on it to to modify its status:

FIX These Files Might Be Harmful To Your Computer In Windows 10

4. Set the policy status to Enabled and under Options, set Intranet drop-down to Low. Click Apply followed by OK. Now again in right pane of Security Page, look for the policy setting named Site to Zone Assignment List. Double click on it to to modify its status:

FIX These Files Might Be Harmful To Your Computer In Windows 10

5. Set the policy status to Enabled. Under Options, click Show button.

FIX These Files Might Be Harmful To Your Computer In Windows 10

6. Finally, in Show Contents, type the share’s IP address or site name with which you’re getting title warning. Wildcard entries are accepted here as well. Click OK, Apply, OK.

FIX These Files Might Be Harmful To Your Computer In Windows 10

Exit Group Policy Object snap-in. Reboot your system to make changes effective. After restart, you’ll no longer see the warning.

Check following video to illustrate this fix:

Hope this helps!


Facebook Google+ Twitter

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Comments

  • CasiBK : I tried all of these methods as well. I have a blank SystemData folde...

    5 hours ago

  • Leslie : Thanks, Kapil, but I'm locked out and unable to access the start menu ...

    10 hours ago

  • Leslie : Thanks, Kapil. But since my screen login doesn't recognize my password...

    10 hours ago

  • Kapil Arya : ^^ Please refer this fix: https://www.kapilarya.com/the-user-profile-s...

    11 hours ago

  • Kapil Arya : ^^ The NETPLWIZ method is not supposed to work for Microsoft account. ...

    12 hours ago