This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 57.00000000000001%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
I'm developing a WebXR app with three.js for HoloLens 2 and at this point the project has different functional stages. While developing a non functional version of it, I reversed the code to a safe, tested and functional branch only to find that it no longer worked. The issue: ARButton for XRSession specifies that AR is not supported (it formerly did in this app version).
After some frustrating debugging process, we've tried to launch a minimal version of the app just with the button. Same result.
Then we started digging in the different Edge updates in order to find if it was related. Even if it's not stated in the logs, we've found that there have been some updates in the past weeks.
Following this browser hypothesis, we've tried to open the app in our cellphones both in chrome and edge. Chrome did indeed allow us to launch the XRSession through the ARButton but in Edge we found the same issues that above.
Finally, in order to discriminate if it was our codes issue, we tried to open all the webxr examples at https://threejs.org/examples/?q=webxr . The behaviour was the previous one, both in the Hololens and our mobile devices.
Both this final steps were tested in different edge an three versions through the different devices, but for the record the Hololens2 Edge current version is 113.0.1774.42 in our headset device.
Is there any known issue about this or any kind of fix?
Thanks in advance.
Reproduction steps
It's unclear which would be the best place to aware MSFT about this issue, as the GitHub repo of Edge is quite chaotic or somehow abandoned.
Thx in advance
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 1%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZW%3C/text%3E%3C/svg%3E)
Hello, Welcome to Microsoft Q&A,
We did some testing and Microsoft Edge on HoloLens shows AR support not detected. This looks like a bug, please feel free to file a bug via Help and feedback -> Send feedback in Microsoft Edge from HoloLens device - Introducing the new Microsoft Edge | Microsoft Learn.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 39%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
I've been having (almost) this same problem for a few months now. I'm using VR on a VIVE Pro though, not AR on a HoloLens. WebXR support has stopped being detected in Edge. Chrome too. Support is still detected in FireFox, but the session never actually shows up in SteamVR when I try to launch it from the browser.
Did all the browser teams just give up on supporting WebXR and forget to tell everyone or something?! Or is this an OS-level problem? VR runs fine, I just can't get any web-based VR stuff to work. It's maddening, because I'll search for fixes to the problem, and all the fixes I find mention browser flags and settings that literally don't exist anymore.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 71%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
Same issue, trying to create a webapp for HoloLens 2 and desktop. Working with Babylon.js and thus WebXR but it seems that every Chromium based browser have discarded the WebXR API. Cannot get into immersive-ar on Edge since an update and I'm just hoping for a fix at this point.
Hi @Randowitz , as the Tip said, Q&A is a site for support not for tracking bugs. For this bug, please feel free to submit it via Help and feedback -> Send feedback in Microsoft Edge from the HoloLens device.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 89%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPY%3C/text%3E%3C/svg%3E)
Same issue happened here https://learn.microsoft.com/en-us/answers/questions/1303227/seeking-help-with-webxr-issues-entering-3d-webxr-s. Do you work around the issue till now?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 67%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHD%3C/text%3E%3C/svg%3E)
Hi! I have this same issue, as a workaround I'm using immersive-vr for now, but that doesn't have all the features immersive-ar has. I've submitted the issue in the help and feedback in May, but it still seems broken.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 56.00000000000001%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
I have tried to get the WebXR AR support running on the HoloLens 2 as well and encountered the same issue.
A rather unsightly workaround I found for this is to downgrade the HoloLens2 OS to 22H1 (10.0.20348.1501), which for me came with the Edge on version 98.0.1108.43. There, I could start the immersive AR and run the hit test sample from the WebXR samples. However, Edge instantly started downloading the update and applied it after I restarted the browser. With the now updated version of Edge (144.0.1823.55), the WebXR AR was broken again. I have not yet found a way to stop the auto update of the Edge, so short of never closing the Edge to prevent the update to apply, there is not much to do for now I think.
If anyone knows how to prevent the automatic windows update on HoloLens or automatic Edge update, please let me know I would greatly appreciate it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 78%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
Hello,
Having the same issue, I also submitted a feeback through the Help and feedback -> Send feedback
10 days ago, I never got any anwser. Seem like i'm not the only one.
Any progress on that, it's been more than a month now. Our clients are getting impatient to have their application running again !
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 54%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
Thank you for the feedback and submissions. A change is in flight internally to resolve. Will post once we have further information, we are getting close.
Good news, we are tracking to a public release.
To help get to that date, we have a fix that is in the latest in-flight builds of HoloLens OS. If you have access to a test HoloLens device, you can get the latest build here that has the fix:
Insider preview for Microsoft HoloLens | Microsoft Learn
If anyone does go to insider preview to help test and works, please let me know here. If any issues, can hit up too.
Hi @Nathan Manis - MSFT great to hear that a fix is on the way! I only have one HoloLens device and I'd rather not put the insider preview on there, but thanks for letting us know a fix coming!
Dear @Nathan Manis - MSFT
I've successfully deployed the preview on my HL2. WebXR immersive AR is back ! Great job !
I get a weird behavior on the hit test API though: some walls/objects are registered, some aren't and the hit result is behind them.
However, I am not certain this wasn't the case earlier, it may be something wrong on my end.
Edit: Nevermind the hit test issue. It's on my side, I just forgot to take into account that I could get multiple hit results for a single test, so I was only using the last and further away one.
M. Courgeon
Nevermind the hit test issue. It's on my side, I just forgot to take into account that I could get multiple hit results for a single test, so I was only using the last and further away one.
Great news on this thread, the HL2 latest September update has the changes now from the preview insider ring. Thanks everyone for the testing & getting the confirmations flowing to get this into the released channel.
Great news to report back to this thread.
After the successful testing in the insider channel, the fix is now public in the September 2023 HL2 OS release:
Thanks everyone for testing the builds with us in the insider ring of HoloLens OS & getting the confirmations flowing to get this into the released channel.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 51%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
https://immersive-web.github.io/webxr-samples/ were working until I did the last update of Windows Holographic 23H2 of March 2024:
https://learn.microsoft.com/en-us/hololens/hololens-release-notes#windows-holographic-version-23h2---march-2024-update
I do not update that often so it may have been broken in an earlier update but certainly betwwen the september 2023 one you mentioned and the March 2024 one.
May you please confirm webxr is broken on latest Windows Holographic 23H2 update please?
Without any solution so far, I'll try to move back to a previous Windows Holographic version with Advanced REcovery Companion : https://learn.microsoft.com/en-us/hololens/hololens-recovery
It allows me to move back to the November 2023 version, while it seems possible to download others versions packages from https://aka.ms/hololens2download/10.0.22621.1133 whre 10.022621.1133 is the full version number of the release of September 2023
I confirm the https://immersive-web.github.io/webxr-samples/immersive-ar-session.html sample works with the november 2023 version 22621.1252 but does not work with the lastest March 2023 version 22621.1266
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 2%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
Hi, my Hololens 2 is using the insider preview version 22621.1318, with edge 121, immersive AR is supported. Maybe there is hope that the next version will fix this problem. best
Hi @Matthieu Courgeon , the latest update of Windows Holographic is Build 22621.1266 from March 2024. Where did you get a Build 22621.1318 please?
As I mentioned, I'm using the insider preview build. I don't remember precisely how I got it enabled but I was closely interacting with the Microsoft teams during the WebXR break of last summer, they somehow made me activate it. Since then, I still have the preview builds.
it's the link right under the "Hololens 2 release notes": Insider preview for Microsoft HoloLens
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 28.999999999999996%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
@Matthieu Courgeon & @Sebastien Perin as Mathieu said it was working on the preview build up to 1318, I did an update yesterday to 1324 and both start AR and VR sessions do not work anymore...
I just updated to 1324 too, weirdly, https://immersive-web.github.io/webxr-samples/ says that the AR and VR are supported, but context creation fails for both immersive AR and VR.
Thanks for the feedback and reporting. This is active here and working to get into Edge update for HoloLens. Nothing to share at this moment but it is under review here and inflight for future.
Will reply back here once it is live and should see something too once addressed in release notes.
@Nathan Manis - MSFT Thanks for that update, great to know it is being worked on. Looking forward to the fix!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 79%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
As it broke again, this might give you a temporary solution until MS fix it at source...
I'm also seeing this behavior again, unfortunately
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more