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(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)
I've been trying to get WebXR running on my HoloLens 2 now for a while, but it's not working.
I've got a project running on 8th Wall that I would like to test ( note that it works fine on Quest 3 browser )
As it wasn't working, I looked for basic test links, the first two WebXR Sample links on the Immersive Web site seem to be ones that should just work. On my HoloLens 2, they don't.
Here's the steps I take...
If I check the developer console, I see these two messages...
Could not create a session because something went wrong initialising the session in the runtime,
and...
XRSession creation failed: The specified session configuration is not supported
In edge://flags, search for XR - all 3 were set to default. I also set them to Enabled, OpenXR, Enabled.
When I click on the Lock icon beside the website URL, I see...
Permissions for this site: Augmented Reality: Allow
I had Windows Updated to the latest version.
I then Reset the device, which didn't help.
I then joined the Windows Insider program, selecting the Beta Channel.
I then got into that loop where you press Restart by clicking on your icon, it shows Update/Restart update/Shutdown, but it got stuck in a loop,.
I was able to then Reset the device again. When I reset, it showed up that I'm in Windows Insider, and Windows Update doesn't show any updates.
Under About / Windows Specifications...
Edition: Windows Holographic for Business
OS Build: 22621.1324
Activation Status: Windows is activated
If anyone has any suggestions, I'd be grateful! I'm keen to just see one example of WebXR running on the device.
It would be great to get it running on Edge of course, but if anyone has tried WebXR on Hololens using a different browser, I'm up for trying that too.
Thanks in advance for any help...
Mal
![](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(3.2, 52%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERC%3C/text%3E%3C/svg%3E)
Hi @MalDuffin,
Q&A isn't a bug reporting or feedback site. Please report HoloLens issues through the Feedback Hub on your device. For Edge on HoloLens, there's a Feedback Hub link in Edge.
Somebody else has reported this, so it is being looked into.
If you wish to talk to somebody directly you can open a support ticket at https://aka.ms/hldevsupport .
--Rob
Thanks for replying Rob - I've opened a support ticket like you suggested.
Somebody else has reported this, so it is being looked into.
Was there a workaround for the other person, like installing an older version of Windows where WebXR works in Edge?
I'm keen to use this device as part of an art installation, and the content works on a different Hololens 2 device that another remote developer kindly tested for me.
Their HoloLens 2 info...
Windows version 22621.1266.arm64fre.ni_release_svc_sydney_rel_prod.240304-1501
Edge version: 121.0.2277.128
I don't mind factory resetting, or installing another browser, as long as I can get WebGL working.
I'm looking forward to doing some development work on the Hololens 2 when I get over this initial hurdle.
![](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(25.6, 76%, 12%)' 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)
We had this issue as well - one thing we noticed was openXR was at a newer version 1.13 - we reverted to 1.12 and webxr started working again.
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.
In my answer I wrote...
"so that, if something goes wrong before the demo I'm running, I can fix it"
I tempted Murphy lol
The night before I went to do an on-site check, everything was working on the HoloLens 2 - the only thing I had changed was that I took of the requirement to enter the PIN when starting up. I'm not sure if that allowed the device to update in the background, or if it just updated itself somehow.
When I went to do a quick check to see if it was working the next morning, it of course didn't. I did a quick check with even the basic XR demos, and they didn't work either.
I didn't have time to check what version of OpenXR etc was running, I just ran through the steps that I listed ( re-install v22621.1266, and then do a software update to v22621.1272 ) which takes just over half an hour.
After that process, the Hololens 2 was up and running WebXR again!
Just a final update, and a question.
I had borrowed a 2nd Hololens for an on-site test ( two Hololens 2, three Quest 3s ), and had them all working the night before. One Hololens then updated something overnight ( no update was asked for ), and of course then didn't work when I got to the site ( luckily, once again, I knew the steps to fix - but had to take 40 mins out to set it up ). This is a situation which would make a lot of devs just not use the Hololens 2 as part of future projects. I'm keen to keep using it if another opportunity appears ( which it might in a few months time ), but only if WebXR is seen to be an important part of the Hololens 2 package, and gets proper testing and development and isn't left broken for a long time.
The other Hololens 2 worked great with no issues, the three Quest 3's always worked without issue.
A quick question - is there a way to see if the internal developers dealing with OpenXR and WebXR know about this issue, so that with the next update, the issue is fixed ( or more like reverted, as it really worked well when it was set up in the way I outlined )
I want to make as much effort as I can to make sure the next WebXR developers can run content on the Hololens 2 with the next updates, without having to go through all of the issues I found and have it just work out of the box.
I got it working! Firstly, many thanks to two developers for reaching out to me letting me know they got it working - I was able to run a few different combinations to get it working. I then broke it again on purpose ( by updating OpenXR ), and then re-installed using the steps below to get it working again ( so that, if something goes wrong before the demo I'm running, I can fix it )
I needed to use the Advanced Recovery Companion* to install a downloaded version of v22621.1266, and then do a software update to v22621.1272* ( * links at bottom of post )
If I did the install of v22621.1272 directly, it doesn't work!!!
I also tried various older versions, including...
v22621.1133
v22621.1252
A few key things...
Here's an 8th Wall link where you can test if it's working or not.
If WebXR is set up correctly ( as it is if you follow the instructions at the top ), you will get the Enter AR prompt and enter the immersive 3D space, and see the 3D basketball in front of you.
If it doesn't work, you'll just see the basketball in the floating browser window, as if it's running in normal desktop mode.
Hope this helps someone who runs into the same issues, and gives the developers some links to test out and help get it working for a future update for everyone to benefit from - this was a bit of a nightmare to figure out, and a real time sink in terms of waiting around to install different versions / re-logging in etc.
Download OS
https://aka.ms/hololens2download/10.0.22621.1266
Download Advanced Recovery Companion
https://apps.microsoft.com/detail/9p74z35sfrs8?hl=en-US&gl=US
Just as a quick update - this A-frame WebXR hand tracking example on Quest 3 just works - touch the 3D floating buttons to interact, pinch the 3D slider and drag it to scale the object. It's a basic example, but it feels very intuitive to use when inside the VR space.
https://aframe.io/examples/showcase/handtracking/
On HoloLens 2, none of the touch interactions work. This demo here would be a great one for the MS devs working on WebXR to get working, as it covers a lot of the basics that many developers will want to use out of the box when creating an experience - as a bonus, the Hololens will be more compatible with established WebXR standards.
![](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(291.2, 40%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Thanks for all your efforts, it saved me a lot of time! For me it's ok to stay on 1266 and prevent Windows updates for the time it will take.
However, even on a 1266 Edge seems to be unusable after updating to 124. When I now try to start an AR session, I see the turning spheres animation endlessly. Nothing more is going to happen... does anyone know how to prevent Edge from updating on HoloLens? On a 2nd device, I'm on Edge 121 when updating ran into an error which luckily seems to stop updating permanently. But how can I stop auto-update on my 1st device, keeping Edge 121 and OS 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(80, 5%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Thank you. It seems the issue (at least, this time) is not with the operating system per se, but with the Edge browser. Even after reverting back to the 1266 version of the OS, and blocking Windows Update, Edge updated itself without my consent and break the WebXR immersive mode again.
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