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
Jun 02, 2020marceldk 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.
marceldk
Jun 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
- marceldkJun 03, 2020Copper Contributor
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.
- Henno_KeersJun 03, 2020Steel Contributor
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?