Forum Discussion
84.0.480.0 (Official build) canary (64-bit) shows error on About screen
- Apr 14, 2020Thanks but it was always an option for everyone at any time, not new to this.
this problem is fixed in the next Canary updates. also the updater works using these methods which is even better than the normal updater since user can set it to check for updates automatically every hour or every minute.
https://techcommunity.microsoft.com/t5/discussions/84-0-480-0-official-build-canary-64-bit-shows-error-on-about/m-p/1304083/highlight/true#M28779
https://techcommunity.microsoft.com/t5/discussions/84-0-480-0-official-build-canary-64-bit-shows-error-on-about/m-p/1303650/highlight/true#M28766
Hi everyone,
Thank you for sharing your experiences with this. One of our program managers had some initial https://twitter.com/OliviaZ73011638/status/1244804479452495872:
"1. Press Win +R, type cmd.exe and press Enter
2. Type “%LOCALAPPDATA%/Microsoft/EdgeUpdate/MicrosoftEdgeUpdate.exe /regserver” and press Enter
3. Reboot the machine and verify if the issue is fixed."
If that doesn't resolve the error, you can also try uninstalling and reinstalling Canary. And to confirm, there are no known performance effects with this error, it just means that you might not see version 84 changes until after we can push the fix in a subsequent build.
Hope this helps, and please let us know if you see anything else come up!
Fawkes (they/them)
Project & Community Manager - Microsoft Edge
- VBartlett1978Apr 11, 2020Copper Contributor
Deleted So I downloaded off the Edge insider website. build has updated, but the problem still remains as you will see from my screenshot.
- Don CuthbertApr 10, 2020Brass Contributor
Deleted
I had not noticed until someone else pointed it out that the .480 build has been updated successfully to .481. However, .481 still displays this same error.
Perhaps the command that you gave us did force a successful update, as I did not see mine updating on-screen within the About page.
Note that this error message did not appear until after the successful update to the .480 build. I don't know that it actually affects the auto-update function at all. Everything else seems fine to me.
- RedBetaApr 10, 2020Iron Contributor
Ok after seeing your post I checked and I was still in 480....the browser has been open since I tried the CMD and the error was there.
I just closed the browser and reopened it and it is on 481....the error is there.
- VBartlett1978Apr 10, 2020Copper Contributor
Deleted I can confirm that I have tried both fixes as well and still the same issue.
- tistouApr 10, 2020Bronze Contributor
Deleted
Tested too and same error
- MichaelCApr 10, 2020Brass Contributor
Deleted
I was waiting for canary to break a little 😉 ah well! Thanks for the update and look forward to the fix!
- AnonymousApr 10, 2020
MichaelC Dennis5mile TheShaunSaw RedBeta HotCakeX Rohit Yadav
Thank you all for the quick testing on this! We are actively in communication with the product team about this right now, and will keep you all updated as they find out more. (It sounds like there may be a secondary bug that's making those troubleshooting steps ineffective.)
We appreciate your help with this!
Fawkes (they/them)
Project & Community Manager - Microsoft Edge- Rohit YadavApr 12, 2020Bronze Contributor
Deleted any update from the team on this issue?
- HotCakeXApr 10, 2020MVP
Deleted
It did not fix it for me.
neither did uninstalling and reinstalling. I fully uninstalled Edge canary yesterday when this problem occurred, then few mins ago installed it again fresh from new installer but the problem was still there, used the method you suggested, rebooted, it's still there 😞
- Rohit YadavApr 10, 2020Bronze ContributorDid this fix resolved the issue for anyone? Did not work for me 😞
- scherniApr 14, 2020Copper Contributor
Rohit YadavNope did not fix for me either.
- TheShaunSawApr 10, 2020Silver Contributor
Deleted
No, both the methods did not fix the issue.
- Dennis5mileApr 10, 2020Silver ContributorNope, not for me either and I tried both 2ice.
Dennis5mile