Mixed Reality Portal / Keyboard Input methods

Status
Not open for further replies.

evgenij

New Member
Hello, I'm still struggling with the finalization of my image and three things don't want to go the way I want:
  1. I cannot complete the mixed reality portal setup. After I install the app from the store (can it be installed with operating system?) and start the setup of my Reverb G2, the portal closes after I have to center my headset without any error messages.Screenshot 2023-06-07 074034.png
  2. I use the US-ANSI keyboard with the US-International layout to be able to write German characters like "üäß". but i have trouble setting it up correctly in the unattended file. Either I end up with two different input methods (e.g. english-gb, english-us int) or I have a german iso input method after installation. I want to end up with single en-us intl. keyboard layout with the german regional settings for date/time or if possible en-us intl. + russian input methods and german regional settings. What/how do I have to set this? Which of the four language settings affects what?
Screenshot 2023-06-07 075136.png


Tanks a lot for your help, I've attached my latest preset.
 
Last edited by a moderator:
Thanks for the report.
Will see if I can test the portal without the headset, or I'll need some extra feedback.
At first glance, I would not remove Sensors, but please wait until fully reviewed to see what else could it be.

Also will check the keyboard thing.

You can integrate apps as updates, download here with the app web link, then latest MSIX file.
A bit messy as Microsoft doesn't provide the app links or integration certificates for the non-inbox apps.
So the integration will work only for the apps already present in the image, and not removed.
We can cover that later, let's first see about the dependency.
 
I couldn't sit idle, so I enabled Sensors and reinstalled the OS. :)
Unfortunately, no change to the error. Unfortunately, there is no error message at all.
Please let me know how I can help to isolate the problem

PS: I don't think you can reproduce the problem/behavior without having a VR headset plugged in.

PPS: found this error in my event manager but have no idea how to fix
Code:
Application pop-up: MixedRealityPortal.exe - System Error : The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
 
Last edited:
VR is dependent on Remote Desktop, because that's how it can render a separate desktop. Try restoring:
Code:
                <c>rdpserver 'Remote Desktop Server'</c>
                <c>rdpserverlic 'Remote Desktop Licensing'</c>
                <c>remotefx</c>
 
VR is dependent on Remote Desktop, because that's how it can render a separate desktop. Try restoring:
Code:
                <c>rdpserver 'Remote Desktop Server'</c>
                <c>rdpserverlic 'Remote Desktop Licensing'</c>
                <c>remotefx</c>
Thanks for this tip, unfortunately it didn't changed anything for me, so I went a different way:

The preset I use is based on ntlite gaming AND privacy preset with some modifications, so I tried to use only the privacy preset to see if the problem is caused by gaming or privacy preset. And it looks like I was looking for the problem in the wrong place - the privacy preset produces exactly this behavior.

Next I will do a reinstall with gaming preset + mixed reality portal to see if it fixes the error.
 
Try restoring Device Experience. The presets are cumulative:
Gaming is Privacy + more removals​
Lite is Gaming + more removals​
 
Yesterday I made several attempts but unfortunately all without luck. It's a bit disappointing and frustrating. Neither the customized gaming nor the customized privacy preset let me complete the setup. I had hopes of creating my own lightweight Windows 11 image and picked up ntlite. I'm afraid I'll end up with standard image + ooshutup or similar and then I can throw the ntlite license out the window.
 
The problem is very few NTLite users have a VR headset, due to cost. Therefore it's hard to test the app setup. Most users are happy using the included presets on a normal desktop. But I can understand your disappointment.
 
OK, did the tracing test of the initial preset, without the hardware to confirm, and these are the main suspects:

Components:
Remote Desktop Server
Sensors
Battery
Infrared devices
DirectX WARP
- that is directly needed for Virtual reality, stated in the description
Device Experience
Natural Authentication
Face Recognition
Text Prediction
Tablet PC
On-screen keyboards


Kept also a lot more in the upcoming suggested preset, but keep these while doing subsequent tests, do these last.

Services:
don't change any Service start state for now (reset that page after loading the preset)

Regs:
Also we don't know what's in the integrated REG files, skip those as well while testing, to reduce constant untested factors.

Drivers:
Try without integrating imported drivers, just in case there is no app issue where it skips some deployment portion because of it.

Yesterday I made several attempts but unfortunately all without luck. It's a bit disappointing and frustrating. Neither the customized gaming nor the customized privacy preset let me complete the setup.
Gaming template includes the Privacy template as it removes more, which means the issue is most probably in the green-labeled components, which explains why it's always there.
So load your preferred preset from the start, then re-check (keep) all the green components as the next test.

Btw you can passthrough USB devices to a virtual machine, making testing faster and simpler.
For example VMWare Player.
Install Windows, run NTLite on it just to activate, snapshot the VM.
Now remove all in preset you want except green ones, try installing the VR.
If it works, snapshot again, if it fails, revert and store the preset as failed, then rinse and repeat.

Please have some more patience, should be doable, I would do it for you if I had the hardware at hand. Will eventually get the VR headset, especially as it becomes the norm.
Then we'll have a VR compatibility option to lock only needed components.

Sending you an edited preset as the first test, when you find the time. Then build on top of it, in any direction (remove more if works, remove less green ones if it doesn't).
Not attaching here as it might have your private data in unattended.

Let us know how it goes.
 
OK, did the tracing test of the initial preset, without the hardware to confirm, and these are the main suspects:

Components:
Remote Desktop Server
Sensors
Battery
Infrared devices
DirectX WARP
- that is directly needed for Virtual reality, stated in the description
Device Experience
Natural Authentication
Face Recognition
Text Prediction
Tablet PC
On-screen keyboards


Kept also a lot more in the upcoming suggested preset, but keep these while doing subsequent tests, do these last.

Services:
don't change any Service start state for now (reset that page after loading the preset)

Regs:
Also we don't know what's in the integrated REG files, skip those as well while testing, to reduce constant untested factors.

Drivers:
Try without integrating imported drivers, just in case there is no app issue where it skips some deployment portion because of it.


Gaming template includes the Privacy template as it removes more, which means the issue is most probably in the green-labeled components, which explains why it's always there.
So load your preferred preset from the start, then re-check (keep) all the green components as the next test.

Btw you can passthrough USB devices to a virtual machine, making testing faster and simpler.
For example VMWare Player.
Install Windows, run NTLite on it just to activate, snapshot the VM.
Now remove all in preset you want except green ones, try installing the VR.
If it works, snapshot again, if it fails, revert and store the preset as failed, then rinse and repeat.

Please have some more patience, should be doable, I would do it for you if I had the hardware at hand. Will eventually get the VR headset, especially as it becomes the norm.
Then we'll have a VR compatibility option to lock only needed components.

Sending you an edited preset as the first test, when you find the time. Then build on top of it, in any direction (remove more if works, remove less green ones if it doesn't).
Not attaching here as it might have your private data in unattended.

Let us know how it goes.
Thanks for your help, that gives me hope.
I was not aware that the gaming preset contains the settings from the privacy preset until yesterday. But the tests I did showed that the problems are already in the privacy preset.

I will do the tests this afternoon, because unfortunately the real hardware is needed. I used Virtualbox for all tests except VR headset. To test VR headset in VMWare/Virtualbox I would have to mess with USB and PCIe passthrough as hardware compatibility is checked during setup.
 
The installation with the preset you provided is complete, but the problem is still the same: the Mixed Reality Portal window disappears/collapses as soon as I click on "Center".

Here is Logevent I've found:
Code:
 System

  - Provider

   [ Name]  Application Popup
   [ Guid]  {47bfa2b7-bd54-4fac-b70b-29021084ca8f}
 
   EventID 26
 
   Version 0
 
   Level 4
 
   Task 0
 
   Opcode 0
 
   Keywords 0x8000000000000000
 
  - TimeCreated

   [ SystemTime]  2023-06-08T14:45:47.4242102Z
 
   EventRecordID 869
 
   Correlation
 
  - Execution

   [ ProcessID]  1116
   [ ThreadID]  1132
 
   Channel System
 
   Computer DESKTOP01
 
  - Security

   [ UserID]  S-1-5-18
 

- EventData

  Caption Mixed Reality Portal: MixedRealityPortal.exe - System Error
  Message The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
 
My Reverb G2 need a lot of microsoft stuff.
For example mixed reality portal not starting when removed Cortana or QuickAssist.

And You must have windows Home, Pro, Business, or Education.
Note: Not supported on N versions or Windows 10 Pro in S Mode.
 
MRP requires Cortana and QuickAssist? Ohmann, things I didn't really want in my system xD


nuhi I've recorded a shot video so that you can see and better understand of what the issue is.

https://drive.google.com/file/d/1QacEbbY01jzVFeZcdoJQXaaKbGNE05YL/view?usp=drive_link

Additionally I've found HP-Reverb driver errors:

Code:
The device HP Reverb Virtual Reality Headset G2 (location 0003.0000.0002.003.002.001.000.000.000) is offline due to a user-mode driver crash.  Windows will attempt to restart the device 5 more times.  Please contact the device manufacturer for more information about this problem.
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated.  This may temporarily interrupt your ability to access the devices.

and also an error possibly related to it, it occurred immediately before the driver error:
Code:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
 and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
My Reverb G2 need a lot of microsoft stuff.
For example mixed reality portal not starting when removed Cortana or QuickAssist.

And You must have windows Home, Pro, Business, or Education.
Note: Not supported on N versions or Windows 10 Pro in S Mode.
I really appreciate this tip. After I re-enable Cortana and Quick Assistant, it goes one step further and tries to complete the setup, but after a while it still crashes with an error code: "Something went wrong. We're not sure what's going on, but the error code should help: 15-13". Lol, I'm not sure what's going on either. :)
 
Try other com ports. Set default desktop resolution to 1080p 60 hz


But why should I do that? The same configuration/setup works fine with the default Windows 11 Pro image. So it must be an image and not a connection/desktop resolution issue.

Now it looks driver related for me:
Code:
The description for Event ID 2 from source AMD_ANR_BG_PROC cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

AMD_ANR_BG_PROC
Function: GET_OUTPUT_DEVICES called.

The message resource is present but the message was not found in the message table

However, the latest AMD driver is installed and works fine on a standard Win11pro installation. And also reinstalling the ntlite image does not solve the problem.

Probably one or two components/services are still missing or they are stopped/disabled.

PS: 1080p doesn't really look good on a UWQHD display.
 
Yes, I have read that too. For some, reinstalling the OS has helped, for others reinstalling the drivers, for third replacing the cable. But as I mentioned earlier, the same setup with the stock Windows image and the same cable/USB port works without problems. So in my opinion it can't be the cable/port or the resolution. And I also have already reinstalled drivers and the operating system. So it must be something with the preset. Imho.
 
The same configuration/setup works fine with the default Windows 11 Pro image.
Ok. Now I understand the problem is in system.
For me also looks like drivers problem.

-----------------------
Yes i know 1080p is not cool on monitor, but when i put higher resolution like 2560p for example, then my Reverb get error (or when i set more then 60hz for desktop). I have nvidia card.

Try also install OpenXr
https://apps.microsoft.com/store/de...ows-mixed-reality/9N5CVVL23QBT?hl=en-us&gl=us
 
Last edited:
To help rule out driver issues from the preset check this out (link), and see if manually installing the latest VR drivers (on your live install of a custom image) allows the app to open without crashing. The article states that if access to Windows Update is blocked then it cannot pull the latest driver, so in theory this could produce a crash if the app is coded to only proceed after the driver is checked/updated.

I don't think you have to use Microsoft's steps for the install either, just extract the folder, right-click on the 3 .inf files and "install" them, then reboot and test to see if the app works. Try their steps too if that doesn't work, just to be sure.
 
Status
Not open for further replies.
Back
Top