May 27 2020 02:26 AM - edited May 27 2020 02:28 AM
Hi,
Not sure if this belongs in the Enterprise section but here goes; we're currently implementing Edge as our new default browser (large healthcare organization) in our VDI environment. Besides this issue, everything is working as intended.
The issue we're facing is that, on our VDI platform, SmartScreen doesn't work:
I've tried different proxy settings (automatic vs fixed server entry), disabled our Trend Micro AV solution but all without any result.
We're not seeing this on our fysical endpoints so there's something goin on in our VDI platform. Is there any logging in Edge regarding SmartScreen that could help us out? We've disable the Windows Defender service because we're using a different AV product but even with the service enabled, there is no change in the observed behaviour.
We're using Edge 81.x but newer versions have the same issue. I've attached a video of the delay when downloading a file.
Note, the platform is still using Windows 7 as the new platform with Windows 10 is not yet ready for production use.
May 27 2020 06:30 AM
May 27 2020 06:36 AM
May 28 2020 09:35 PM
@marceldk Regarding the demo pages not working, you can try checking edge://histograms/Microsoft.SmartScreen.ErrorState
For the download delay, you can try disabling SmartScreen and then download the same file. If it is indeed due to SmartScreen, then Download should start instantaneously this time
In a fresh browser session, perform the repro and then edge://histograms/Microsoft.SmartScreen should give you some data around SmartScreen which can help pinpoint the problem further
or you can use edge://tracing and enable the category 'SmartScreen' which should give more details
Jun 02 2020 12:15 AM
@bhkumar007 thanks for the suggestions, never knew these items were available. I'm not sure what i'm looking at though; what does 0, 1, 2 etc mean with these histogram results (these results are only when clicking a few of the demo items on demo.smartscreen.msft.net).
Histogram: Microsoft.SmartScreen.ErrorState recorded 9 samples, mean = 1.3 (flags = 0x41)
0 ------------------------------------O (3 = 33.3%)
1 O (0 = 0.0%) {33.3%}
2 ------------------------------------------------------------------------O (6 = 66.7%) {33.3%}
3 ...
Histogram: Microsoft.SmartScreen.OnCompleteAsyncNoServiceTime recorded 9 samples, mean = 14034.3 (flags = 0x41)
0 ------------------------------------------------------------O (1 = 11.1%)
1 O (0 = 0.0%) {11.1%}
2 ------------------------------------------------------------O (1 = 11.1%) {11.1%}
3 ...
10 ------------------------------O (1 = 11.1%) {22.2%}
12 ...
10000 ------------------------------------------------------------------------O (6 = 66.7%) {33.3%}
Histogram: Microsoft.SmartScreen.PuaProtectionEnabled recorded 1 samples, mean = 0.0 (flags = 0x41)
0 ------------------------------------------------------------------------O (1 = 100.0%)
1 ...
Histogram: Microsoft.SmartScreen.SetAsyncTime recorded 9 samples, mean = 570515.7 (flags = 0x41)
0 ------------------------------------------------------------------------O (1 = 11.1%)
1000 ...
2005 ------------------------------------------------------------------------O (1 = 11.1%) {11.1%}
2187 ...
3097 ------------------------------------------------------------------------O (1 = 11.1%) {22.2%}
3378 ...
9588 ------------------------------------------------------------------------O (1 = 11.1%) {33.3%}
10458 ------------------------------------------------------------------------O (1 = 11.1%) {44.4%}
11407 O (0 = 0.0%) {55.6%}
12443 ------------------------------------------------------------------------O (1 = 11.1%) {55.6%}
13573 ...
24936 ------------------------------------------------------------------------O (1 = 11.1%) {66.7%}
27200 ...
64858 ------------------------------------------------------------------------O (1 = 11.1%) {77.8%}
70746 ...
5000000 ------------------------------------------------------------------------O (1 = 11.1%) {88.9%}
Histogram: Microsoft.SmartScreen.SmartScreenEnabled recorded 1 samples, mean = 1.0 (flags = 0x41)
0 O (0 = 0.0%)
1 ------------------------------------------------------------------------O (1 = 100.0%) {0.0%}
2 O (0 = 0.0%) {100.0%}
Histogram: Microsoft.SmartScreen.TimeoutState recorded 9 samples, mean = 1.1 (flags = 0x41)
0 O (0 = 0.0%)
1 ------------------------------------------------------------------------O (8 = 88.9%) {0.0%}
2 ---------O (1 = 11.1%) {88.9%}
3 ...
Histogram: Microsoft.SmartScreen.UrlCheckWentAsync recorded 9 samples, mean = 1.0 (flags = 0x41)
0 O (0 = 0.0%)
1 ------------------------------------------------------------------------O (9 = 100.0%) {0.0%}
2 O (0 = 0.0%) {100.0%}
Histogram: Microsoft.SmartScreen.UrlThreatType recorded 9 samples, mean = 0.0 (flags = 0x41)
0 ------------------------------------------------------------------------O (9 = 100.0%)
1 ...
Jun 02 2020 11:31 AM
@marceldk 2 indicates the internal code error in SmartScreen (looks like it is related to environment you are using). Can you run edge://tracing with SmartScreen category? If there is any error message in there, that will help pinpoint the issue.
Jun 02 2020 10:49 PM - edited Jun 03 2020 12:49 AM
@bhkumar007 I've had to capture from start-up (used the info @ https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs) to catch these events.
C:\Program Files (x86)\Microsoft\Edge\Application>msedge.exe demo.smartscreen.msft.net --trace-startup --trace-startup-file=H:\trace_startup.json --trace-startup-duration=5
Title
TelemetryDatapoint::data_name 🔍
Category SmartScreen
User Friendly Category other
Start
339,512 ms
Args
data_name
"message"
event_name
"Microsoft.Defender.SmartScreen.Error"
Title
TelemetryDatapoint::data_value 🔍
Category SmartScreen
User Friendly Category other
Start
339,586 ms
Args
data_value
{code: 22,
call_stack: {frames: [{file: "delay_load.h",
line: 86}]},
context: ["RtlGetDeviceFamilyInfoEnum: Invalid argument"]}
event_name
"Microsoft.Defender.SmartScreen.Error"
Title
TelemetryDatapoint::data_name 🔍
Category SmartScreen
User Friendly Category other
Start
339,593 ms
Args
data_name
"client_version"
event_name
"Microsoft.Defender.SmartScreen.Error"
Title
TelemetryDatapoint::data_value 🔍
Category SmartScreen
User Friendly Category other
Start
339,597 ms
Args
data_value
"1.1.1912.3"
event_name
"Microsoft.Defender.SmartScreen.Error"
The clientversion matches the libsmartscreen.dll version in the C:\Program Files (x86)\Microsoft\Edge\Application\81.0.416.64 folder.
Edit, looks like I skipped over some events, most of them are the same as above but this one is different (and a little later on in the trace):
data_value
{code: 22,
call_stack: {frames: [{file: "delay_load.h",
line: 77}]},
context: ["wldp.dll"]}
event_name
"Microsoft.Defender.SmartScreen.Error"
Jun 03 2020 12:58 AM
@marceldk Thanks for sharing the details. It does give an idea on where the issue lies. Can you share the details on OS version/architecture/sku you are using? I don't see the issue on a regular Win7 machine
Jun 03 2020 01:12 AM - edited Jun 03 2020 01:13 AM
@bhkumar007 this is Windows 7 Enterprise 6.1.7601 SP1, x64. Running on an Intel Xeon CPU E5-2680 v2 with 5GB's of RAM with Dutch language settings.
I've noticed that when I install the Beta build (or Dev) next to the stable 81.x version, SmartScreen does work in that browser. But we've reinstalled this 81.x a few times now but no changes in behaviour. The difference being that the 81.x is installed during our automatic process with ConfigMgr's Task Sequences to build the new VDI images and the Beta/Dev build is installed manually in this case.
Jun 03 2020 07:43 AM
@marceldk from what you are saying it looks more that the user context or installer media from where the install is done during the TS is of influence or the install media.
Are you using the MSI during the TS I presume? What are you using when installing manually? MSI or C2R?
Why not deploy Edge after the TS from SCCM, just select stable channel?
Jun 03 2020 09:50 PM
@Henno_Keers yes, I'm using the MSI to install Edge during TS and I've used the C2R with Beta/Dev. I *think* I've also used the MSI to install Beta/Dev next to Stable but I'm going to try that again.
The reason why we're installing the MSI during the TS is because of the automated image creation; after the TS is ready, the image is captured and used for our VDI platform. One of the final steps is removing the configmgr agent (no use for that in a non-persistant environment) so pushing software after the TS is not an option. For the sake of troubleshooting I can manually install Edge after TS and then capture this image, to see if smartscreen is still broken.
Jun 03 2020 10:55 PM
@marceldk The white elephant in the room is the "IS Not" object. The object that should / could have the deviation, but does not have it.
That platform /object is different to the platform / object that has the deviation. What are de differences?
IS: VDI platform
IS Not: physical machines
Jun 03 2020 10:56 PM
Jun 03 2020 11:02 PM
@marceldk we are already on 83 so I could not reproduce your issue, I saw the posting just to late.
But what is the point in looking back if 83 works? 81 is history.
Jun 03 2020 11:17 PM
Jun 03 2020 11:22 PM - edited Jun 03 2020 11:26 PM
@marceldk Succes with the rollout! Greetings to Ronald van der Plas.
Jun 04 2020 06:22 AM
@Henno_Keers thanks, guess it's a small world after all 😉
Regarding the issue; I've successfully deployed a new non-persistent VDI image with Edge 83.x and Smartscreen is working in that image. Not sure what's wrong with 81.x on that platform but upgrading to the newer release will happen sooner then later anyway.
Thanks for all the help @bhkumar007, @Reza_Ameri-Archived and @Henno_Keers.
Jun 04 2020 06:28 AM
@marceldk welcome, the actual help done with Microsoft Edge engineering teams.
When you run into such incidents make sure share feedback through feedback option in Microsoft Edge.