What causes this, the Smartscreen Filter? As I was installing Windows 10, I opted to not use Smartscreen Filter. I've had it block the installer for CCleaner and other things (at one point or other). I feel it is a little bit over-aggressive in what it blocks so I have opted to not use it in my Win 7 and 8 machines, and on this one. But I was given the choice to not use it at all which was kind of surprising seeing as how MS foists and forces other features upon you, like automatic-bootloop-causing-updates.
The only PC I have Smartscreen running on, is an XP machine I use for Pro Tools LE 6.4, I have to rebuild that machine 3 times a year so Smartscreen as it is there actually helps. But in XP it is limited to running within the IE environment, from Vista up they extended it to run through the whole OS.
Windows SmartScreen helps keep your PC safe by checking downloaded files and web content within apps to help protect you from malicious software and potentially unsafe web content. Before an unknown or potentially unsafe downloaded file is opened, Windows will display a warning. If SmartScreen detects potentially unsafe web content in an app, Windows will display a warning in place of the content.
Windows SmartScreen Settings - Change in Windows 10 - Windows 10 Forums
I have just upgraded from Win 7 to Win 10 and the majority of the JPG files I already had saved on my PC (from the internet) are now afflicted with this security message when I try to open them from Windows Explorer. I have tried running your Option 5, using PowerShell to unblock all files within a folder but I'm finding that a lot of files still come up with the security warning when I try to open them, as if the unblock command hasn't worked on all of them. I have to admit that some of my folders are pretty large and can have 1500 or more JPGs in them - is there a limit to how many files the unblock function can handle at a time?
Hello shalebing, and welcome to Ten Forums.
There's no limit for the command. It'll just take a bit longer for the command to finish when there's a ton of files in the folder.
Please go ahead and post a screenshot showing the security message you still get to see what the issue may be.
Screenshots and Files - Upload and Post in Ten Forums
Are these folders located on external or removable drives? If so, then that would be why since the file is still being opened from an external source.
Many thanks for the reply Brink. I have tried this routine again on a folder that has over 3000 JPGs (sorry, looks like my previous guess at 1500 was way off the mark!). The process starts OK but seems to finish too quickly and when I try to open a few random files, a few will open but most are still affected by the security pop-up. I have attached a screenshot of the security message. I can confirm that the files in question are all stored on an external USB drive.
The command I am typing in to PowerShell is:
get-childitem "f:\bsspi_sys\blah" | unblock-file -confirm and I am responding to the confirmation with 'A' for
Last edited by Brink; 2016-06-09 at 10:29. Reason: attached your uploaded image
Since the source is from an external USB, you will always see that message by default.
If you like, you could use an option in the tutorial below to disable the "Open File - Security Warning" message for the file types you want.
Open File Security Warning - Enable or Disable - Windows 7 Help Forums
Thanks. I have already created the new zone REG_DWORD option in the Associations registry to stop any future downloads being affected. That's a real bummer though that files I try to load from the USB drive will flag up the security message. That didn't happen when I was using Windows 7 - is this peculiar to Win 10? The strange thing is that some files on the USB drive will open fine with no message while others (well most to be honest) are affected.
Yeah, it is odd how some will and some will not open with it from the external drive. I believe that image files were not affected by this in Windows 7, but does appear to be now in Windows 10. It used to be mostly executable and document type files that mostly got this message.
It is annoying - I can fully understand the need for it with .exe files etc. but with .jpg files (which I use a lot) it is a major frustration.