Forum Discussion
Smartscreen not working after Update to 103.0.1264.49
- Hello all. Thank you for your patience. I'm the Product Manager for Smartscreen in Microsoft Edge and I want to provide a quick update. We've developed a fix to address this issue, and we're in the final stages of testing and validation before shipping to all customers. The fix will be available starting edge v104 and on later releases.
The NewSmartScreenLibrary policy is still available and will remain available until we're confident the issue has been resolved. The plan as of now is to deprecate it in v107. More details to come later on. https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#newsmartscreenlibraryenabled
Ricky_S thanks for your hint and sorry for my late response. My coworker was on vacation and I had much other things to do.
Did SmartScreen realy work for you on Server 2016 without HKLM\SOFTWARE\Policies\Microsoft\Edge\NewSmartScreenLibraryEnabled or NewSmartScreenLibraryEnabled = 1?
I can't get it to work. No way for me.
There are also no messages on our proxy.
For testing, I setup three systems (Win 10 21H2, Server 2016 and Server 2022):
- separate VLAN
- no domain
- Edge 106.0.1370.42
- Sophos AV
- Proxy (user and system) are in place
- Systems are up-to-date
Server 2022 and Windows 10 21H2 are working as expected, but Server 2016 doesn't. There are no warning when testing on demo.smartscreen.msft.net.
Sadly, with Edge 106.0.1370.34 the Policy NewSmartScreenLibraryEnabled got deprecated, so I have no way to make SmartScreen work on Server 2016 anymore.
Today is patch day but I have to stick with Edge 105 because of this issue.
If someone had an idea, please share.
MicrosoftKrinto1100 Hello! I see that the team is aware of an issue affecting Server 2016 specifically and they were working on the fix. I reached out to them to get more information. Or like Ricky_S mentioned you can open a Support request and they can investigate your specific scenario. Thanks!
-Kelly
- Now everything is clear.
Many thanks to you and the team! - Kelly_Y
Krinto1100 Once the team finalizes the fix, you will not need to use the parameter. They plan to release the fix in v107. Thanks for testing it out!
-Kelly
Kelly_Y thank you.
Does this mean that I always have to start Edge with the parameter -enable-features=msSmartScreenUseEdgeNetworking or will it work without the parameter in the future?
If the paramter is still needed, is there a way to set this centrally (GPO, Regstriy)?
- Kelly_Y
Krinto1100 The latest information that I've heard from the team is the NewSmartScreenLibraryEnabled policy is deprecated but it will continue to work through v107, so you should not have any issues.
Also, they plan to release the -enable-features=msSmartScreenUseEdgeNetworking fix in v107.
Thanks!
-Kelly
Kelly_Y thank you very much!
I have installed and tested Edge Canary on different systems. Once -enable-features=msSmartScreenUseEdgeNetworking is used, the error no longer occurs and SmartScreen works.Can the GPO NewSmartScreenLibraryEnabled please remain active until the error is fixed? Otherwise SmartScreen will not work on my RDS farm when 107 is released.
- Kelly_Y
Krinto1100 Quick update from the team, they are experimenting with the fix. You can test it out using the latest MS Edge Canary channel with feature flag --enable-features=msSmartScreenUseEdgeNetworking. Let us know if that resolves your issue.
-Kelly