Windows 10: Favorites folder flagged by NTFS after latest cumlative update

After the update to 14393.187 all the url files in my favorites folder have the popup "File Download - Security Warning". It only does it when I open them from my toolbar or favorites folder. If I open Edge first then access my favorites they open fine. I have a lot of url files and I really like using the toolbar, is there a way around this new security?

:)

 

Upgrade to Windows 10 1511 10586 has failed after preparations of updates was finished.

Cumlative update for Windows 10 (KB3116869) does not fix this issue, but it's something better because it's more files and folders inside SoftwareDistribution folder than before this update. I think
I have to wait to Redstone update because it will be new ISO.

 

Something is Repeatedly adding links to the IE and EDGE Favorites Bar

I removed the items flagged in the Adwcleaner but after a week or so the items are back in my favorites folder. Is there a way to track what/when these items are being added and what processes are running when to identify what is the culprit?

 

There have been several users [including me] affected by this. There is a workaround in A warning popup when opening any .url file in “Favorites”. Why? [this thread also contains links to the other MSA threads on the same subject]. Some people have used a workaround with icacls to alter url file properties [but this has to be repeated for all new urls you make]. I just uninstalled the latest Windows 10 cumulative update as a quick fix in the hope that the next cumulative update will not cause this problem [note that other users uninstalled other recent updates to fix the problem - the common factor has yet to be identified].

Denis

 

Thanks for the confirmation Denis, another workaround I found.

 

Yes, that thread goes into detail about why using icacls to change the integrity level is relevant but it assumes that Windows is functioning correctly and therefore does not address the question of why it should suddenly treat [some] urls differently. I understand the OP's frustration at this part of the question being glossed over.

In our case, we know that the integrity level is correct already because
1 Windows treated the urls correctly before the offending update
2 Windows treats the urls correctly if the offending update is removed

If only there was some consistency to the identity of the offending update. I removed the problem by uninstalling one particular update, Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3176938), but other users have removed the problem by uninstalling other updates.

We are really just left to await the next update and hope it has been fixed. It's taking a bit longer than usual, but it should be ready soon.

Denis

 

https://support.microsoft.com/en-us/kb/3199375 is a hotfix for Windows 7 & 8. It provides a link to a new cumulative update for Windows 10 version 1511. There is no information about Windows 10 version 1607 [the anniversary update] and no new cumulative update has been issued for this version.

Denis