Jan 04 2023 10:53 AM - last edited on Mar 17 2023 10:44 AM by Joon Chang
1/10/23: Hi Insiders! Thanks for bringing the update issue to our attention. We've released the Dev build 110.0.1587.6 today, which fixes the problem. Thank you again for your help and patience.
Hello Insiders! We are excited to kick off the new year with the release of Dev build 110.0.1587.1 to the Dev channel to all platforms except Mac. Mac users will receive the Dev build at a later date. This build includes a range of fixes, new policies, new API, and new features for Android. For more details on the changes, check out the highlights below. Additionally, we got a new blog post about WebView2 Runtine below.
Delivering Microsoft Edge WebView2 Runtime to managed Windows 10 devices - Microsoft Edge Blog
Added features:
Improved reliability:
Changed behavior:
Thanks again for sending us feedback and helping us improve our Insider builds.
Edited (1/10/23): Updated title and added update.
Jan 05 2023 06:27 PM
Jan 06 2023 01:03 AM - edited Jan 06 2023 01:05 AM
There's a newer build on web Installer page that fixed the reboot issue.
Monday, December 19, 2022 3:03:19 PM
CRC32: 755E05CA
Jan 06 2023 02:46 AM
Jan 06 2023 02:59 AM
@MissyQ Is there going to be an update pushed out that resolves the update loop for everyone? Forcing everyone to uninstall and reinstall seems less than ideal.
Jan 06 2023 04:21 AM
Jan 06 2023 05:10 AM - edited Jan 06 2023 05:11 AM
@Eric_E There are no floating hints on YouTube when hovering over a video title in edge dev starting from 110.0.1556.0.
Current stable MS Edge:
The last edge dev:
Jan 06 2023 08:39 AM - edited Jan 06 2023 04:19 PM
Solution@Ryan Buckwalter To be clear, y'all can just use the browser without updating consistently. It works just fine without the update right now, the issue is simply the browser won't update when you go to update it.
We're still working on pushing out a fix. As stated, we will follow up once we know when the fix is rolled out. Appreciate everyone's patience and diligence keeping us honest! :3
EDIT - 4PM PACIFIC TIME, JAN 6TH: We had hoped we would be able to fix this for y'all by this afternoon, however it is looking like we will roll out the fix on Monday. Again, thanks for everyone's patience!
Missy Quarry (she/they)
Community Manager - Microsoft Edge
Join us on Twitter, or over on Reddit in r/MicrosoftEdge or r/edge
Jan 06 2023 10:11 AM
@dmitrymyl Thanks for reporting this issue. I apologize for the inconvenience, but I am unable to reproduce the issue on my end. In order to help our engineers investigate this issue, please follow the steps below to submit feedback with the necessary diagnostic data.
Eric
Jan 07 2023 12:17 AM
Jan 07 2023 03:53 AM
@Eric_E I have confirmed at Dev Version 110.0.1556.0 which I currently at that all websites are unable to show the tooltip. However, in Canary Version 111.0.1605.0 the tooltips are display properly.
Dev:
Canary:
Jan 07 2023 11:30 AM
Jan 07 2023 07:08 PM
Jan 08 2023 03:49 AM
@Eric_E I solved the update problem by uninstalling Dev and installing the download from the website. All is ok now, I'm on version .1, nothing is lost.
Jan 08 2023 11:34 AM
Thanks for the suggestion, it works as long you don't chick the box to remove Edge data.
Jan 08 2023 11:49 PM
In App folder I had 2 folders - one 110.0.1587.1 and old 110.0.1556.0.
I was able to fix Edge by renaming *1587.1 folder to 110.0.1556.0 and then start Edge - that fixed it to me - I got the new version - 110.0.1587.1, no issues with not updating.
Jan 09 2023 12:09 AM
Jan 09 2023 12:17 AM
Jan 09 2023 04:40 PM - edited Jan 09 2023 04:52 PM
There are no tooltips anywhere in the browser, and it started for me with the 110.x releases as well. Y'all need to figure out what's causing it, before you push 110.x to Beta and to Release.
https://techcommunity.microsoft.com/t5/discussions/tooltips-not-working-on-latest-update/m-p/3691303
Scratch that. Updating to 110.0.1587.1 did actually fix it, I now have working tooltips again, but did not on 1556, just like @Limyx826
Also like everyone else, I had to forcibly close all running msedge.exe processes, and then run MicrosoftEdgeSetupDev.exe manually. I also had both the 110.0.1587.1 and 110.0.1556.0 folders visible in "C:\Program Files (x86)\Microsoft\Edge Dev\Application" with the "msedge.exe" hard link and all the other ones still pointing at the versions in 110.0.1556.0. If running MicrosoftEdgeSetupDev.exe didn't work, I was just going to manually replace them all and delete the 1556 folder.