--js-flags=--noexpose_wasm launch flag causes STATUS_BREAKPOINT
Version 135.0.3179.73 (Official build) (64-bit), Windows 11 Education, also occurs on Windows 10 Education and Windows 10 Pro, been testing this since probably version 129 of Edge. --js-flags=--noexpose_wasm as a launch flag causes STATUS_BREAKPOINT, this is regardless of default configuration and with or without extensions. WASM can be used to discover privileged information about a machine, and this seems to be working in the past according to some users online, but no longer does now. Please can someone advise?Applications not launching with latest AVD update
Hello there fellow users - first time poster. I also have an open ticket with Microsoft with this particular issue. I feel like this is something obvious I'm missing here though and any ideas would certainly be appreciated. My org utilizes AVD for connecting to a AVD pool of terminal servers for end users. Within that pool are application groups and clients assigned to the groups, although application groups by and large have the same clients. Here's our typical workspace: The issue we are currently having, is that with the last 2 or 3 recent versions of Remote Desktop, and only on SOME computers, is that the applications will not launch properly. The application will begin to launch for a second or so, and then stop and disappear. This is the last thing an affected user sees before the launch box disappears (AVD will remain open): As a work around, we've had affected users/workstations remove the latest version and install version 1.2.2688.0 where this behavior does NOT occur. There are no relevant windows event logs from what I can tell. All affected users are using Windows 10. Here are my AVD RDP Properties in Azure: Thank you!
