Forum Discussion
marceldk
May 27, 2020Copper Contributor
Smartscreen not working / delay in downloading files
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 ...
bhkumar007
Microsoft
May 29, 2020marceldk 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
marceldk
Jun 02, 2020Copper Contributor
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 ...
- bhkumar007Jun 02, 2020
Microsoft
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.
- marceldkJun 03, 2020Copper Contributor
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"- bhkumar007Jun 03, 2020
Microsoft
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