Recent Discussions
Full Screen PDF Issue when in single-app Windows Kiosk mode
Hello, When Microsoft Edge is in Kiosk mode via a single-app Windows kiosk and you open a PDF and enter full screen mode (see screenshot), there is no way to get back out. ESC key does not work and the grey "X" that show up when you hover over the top middle in a normal Edge session is not present. Also tried F11 and some other combinations with no luck. There seems to be no way to back out or view the Edge toolbar again until the Kiosk session ends.
Why so many MS Edge entries in Open with menu on macOS
Hi everyone. I would like to know why we get so many entries in the Open With menu on macOS? I included a screenshot of my right click - Open With menu. It looks like every new version creates an entry in that menu. This, I think, shouldn't be like that. I tried to removed the entries with lregister in command line, but it came back after rebooting. Any suggestion?
v130 breaks pdf digital signature validation
Hi all, I've noticed an issue seemingly shipped with 130.x. I've tested all other available versions (126.0.2592.102,128.0.2739.107,129.0.2792.79,129.0.2792.89 OK), they all validate the signature as expected: Any 130.x fails to validate the signature: I've tested on the very same system to exclude any other variable. Opening the pdf in Adobe Reader works just fine (just in case there's anything in 130 relating toMicrosoft Edge and Adobe partner to improve the PDF experience). There's nothing really peculiar about these signing certificates (issuing is private CA stored in "Trusted Root CA" win cert. store), except maybe the fact that they have a long validity of 5 years (legal regulation on the document validity). Has anyone experienced something similar, or would have any idea where this change in behaviour might come from? Thank you, ThomasEdge prompts users that it is out of date when a target version is set in Intune
Hello, We are using the target channel override and target version policies in Intune to control when our users receive Edge updates. Our target version is currently 128.0.2739.42. Despite this, Edge is showing an update notification to our users. When they click on it in the menu, they get a message that says "Microsoft Edge couldn't update to the latest version, so you're missing out on new features and security fixes." I looked through the log for Microsoft Edge Update, and at no point did it try to download and install a new Edge version. The only update it performed was for WebView2. I found this thread: Edge UpdatePolicy - Disable automatic updates leads to "Microsoft Edge is out of Date" - Microsoft Community Hub However, this registry value is set to INBX (Inbox, I guess?) in our environment. I couldn't find any documentation about what this means. I tried changing this to GCEU as described in the thread, but this did not change the behavior long term. The message initially goes away after a restart, but comes back some time later. We are intentionally controlling our update rollouts and do not want our users knowing or caring Edge is out of date. Does anyone know how to suppress these warnings? This kind of seems like a bug. Thanks! Andrew
Recent Blogs
- Microsoft Edge to replace built-in PDF engine with Adobe Acrobat PDF engineOct 29, 2024
- 8 MIN READMicrosoft Edge for Business, the new, dedicated work experience for the Microsoft Edge browser, is now available in Microsoft Edge stable version 116. All customers who sign into Edge using Microsoft...Aug 06, 2024
