--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?Microsoft Edge - Welcome screen vs. don't show policy
Hi, We have a GPO that disables the Edge welcome screen (sets the SOFTWARE\Policies\Microsoft\Edge key's HideFirstRunExperience variable to 1). On some of our PC's when the user try to run Edge, they get a blank page with invalidurl error. This white page can not be closed, only way to dismiss if you stop edge processes with the taskmanager. If you set the registry value to 0, then it can reach the welcome screen and you have to do the first steps. This policy should disable the welcome screen and not just hrowing an error. how could we avoid this screen to appear? Is there any setting that let Edge think it was already started and omits this screen completely? Why did this bug appeared in the first place? This policy was working for years now, and only show this bug randomly. Edge - stable, latest version; Windows10 22H2;
Edge error RESULT_CODE_MISSING_DATA or RESULT_CODE_KILLED_BAD_MESSAGE even in the settings menu.
After the KB5050021 (Windows 11 (23H2)) update, Edge stopped working. The same error appears on all tabs and even in the settings: Error code: RESULT_CODE_MISSING_DATA. I deleted the update, but Edge still didn't work. Edge only partially worked in compatibility mode with Windows 8. Does anyone know what the problem could be? Without compatibility, the error is either RESULT_CODE_MISSING_DATA or RESULT_CODE_KILLED_BAD_MESSAGE, and on any tabs and even in the settings menu. Edge Version 134.0.3124.93 (Official Build) (64-bit) DEV/BETA/CAN also don't work with the same errors. UDP. After the KB5053602 (Windows 11 (23H2)) update, Edge still not working. Is there a solution to this problem?
Edge 130.0.2849.46 (Official build) (64-bit) Broke Extension(s) - Ublock Origin in this case.
Hello, I know very well that Edge is also moving to MV3. But, there isn't any announcement about complete removal of MV2 yet. Since Edge updated to v130, it broke popular extension like Ublock Origin, for many people. We've reported the issue to extension devs, it but seems that while there are many people who are affected, there still be many that have extension working fine as expected. https://github.com/uBlockOrigin/uBlock-issues/issues/3419 Many people've reported this issue not only on github, but also on reddit as well. The extension was working fine before v130, so we suspect that the cause is Edge update itself. - Issue: The extension loads but cannot run, and its dashboard page cannot load, is completely empty. Turn on/off does not work. Removing/Reinstalling from MSEdge Store also does not work. The only "workaround" for this is setting up a completely new blank local profile, but that will cost all the synced settings and extensions data. Please help us looking into this issue, Thank you. --------------------------------- Browser: Edge 130.0.2849.46 (Official build) (64-bit) Extension: Ublock Origin v1.60.0 Extension source: MSEdge Store System: Windows 10 22H2 19045.5011 (I don't think system info matters because there're people who're on Win11 and have this issue as well)
Inconsistency of window's new Date() function returns invalid date in Microsoft Edge
We are facing some browser problem while using React as frontend for initialize new Date() object such that new Date().toLocaleString() gives empty string. As this is not the case with Chrome so raising it here. Looking forward to get a permanent solution as of now we have added retries for initialize new Date() object for work around.
