WMR Tray Tweaker Tool

[zildac]

This looks like an interesting tool from the author of the OTT. Not had a real dig into it as yet but looks useful for setting service and exe priorities plus other potentially useful tweaks.

 

https://apollyonvr.wixsite.com/vrtools/windows-mixed-reality-tray-tweaker

 

Update released, can be grabbed from the authors site above or via the in App update function. Having used it for a bit now I can say I had zero qualms about donating, it's very useful.

 

 

 

 

 

Edited April 23, 2021 by zildac
Version update

[dburne]

9 minutes ago, zildac said:

This looks like an interesting tool from the author of the OTT. Not had a real dig into it as yet but looks useful for setting service and exe priorities plus other potentially useful tweaks.

 

https://apollyonvr.wixsite.com/vrtools/windows-mixed-reality-tray-tweaker

 

 

Excellent news, I loved using his Oculus Tray Tool back when I was using Rift.

[zildac]

15 hours ago, dburne said:

 

Excellent news, I loved using his Oculus Tray Tool back when I was using Rift.

Likewise I'm getting a .NET error on launch unfortunately, so I need to have a rummage to see what the issue is before I can do any real testing. The readme is well worth a look through too.

 

Update: Had an email exchange with the author and the issues I was experiencing now seem resolved. Super quick!

Edited April 23, 2021 by zildac

[javelina1]

nice! thanks for sharing!  I was also a big OTT user when I used my Rift.

[dburne]

This will so be worth it just to be able to use it for disabling those pre-allocated virtual monitors I have to go in and disable in the registry after each WMR update. I always forget where it was and how to disable.

Edited April 22, 2021 by dburne

[ShaunX]

9 hours ago, dburne said:

This will so be worth it just to be able to use it for disabling those pre-allocated virtual monitors I have to go in and disable in the registry after each WMR update. I always forget where it was and how to disable.

 

..I had no idea the pre-allocated virtual monitors were coming back after WMR updates but just tested and sure enough, they're back !

 

Thanks for the tip!

 

..So I just checked in the registry, and I still have the PreallocateVirtualMonitors flag set to 0, but I'm now getting 3 preallocated virtual monitors created when I turn my G2 on, which I definately wasn't getting when I originally set that flag a few months back

 

 

 

am I missing something ?

 

 

Edited April 23, 2021 by ShaunX

[dburne]

8 hours ago, ShaunX said:

..I had no idea the pre-allocated virtual monitors were coming back after WMR updates but just tested and sure enough, they're back !

 

Thanks for the tip!

 

..So I just checked in the registry, and I still have the PreallocateVirtualMonitors flag set to 0, but I'm now getting 3 preallocated virtual monitors created when I turn my G2 on, which I definately wasn't getting when I originally set that flag a few months back

 

 

 

am I missing something ?

 

 

 

 

 

I am not sure, mine had re-enabled so just had to go back in and change it back to 0 which took care of it.

[Tshark]

I checked mine and it had not re-enabled.  Registry entry is still there.

[ShaunX]

Well, I don't appear to be able now to prevent the additional 3 virtual monitors being created when I switch on my G2. Tried deleting the registry entry, rebooting and adding it again. Still 3 additional monitors.

[dburne]

1 hour ago, ShaunX said:

Well, I don't appear to be able now to prevent the additional 3 virtual monitors being created when I switch on my G2. Tried deleting the registry entry, rebooting and adding it again. Still 3 additional monitors.

 

Very strange.

You could always try an uninstall and re-install of WMR, bit of a PITB but does not take too long.

Those virtual monitors always drove me crazy.

Edited April 23, 2021 by dburne

[ShaunX]

Just now, dburne said:

 

Very strange.

You could always try an uninstall and re-install of WMR, bit of a PITB but does not take too long.

Those virtual monitors always drove me crazy.

 

 

Thanks, yeah I guess I'll give that a go in the morning

[Twwhitey]

2 hours ago, ShaunX said:

Well, I don't appear to be able now to prevent the additional 3 virtual monitors being created when I switch on my G2. Tried deleting the registry entry, rebooting and adding it again. Still 3 additional monitors.

 

Interesting I'm seeing this behavior as well.  Registry entry is in there unchanged and toggling back & forth and/or deleting and re-creating doesn't seem to make a difference... those extra monitors keep reappearing.  I guess I'll give the WMR uninstall/reinstall a try <eek>

[zildac]

 
Thanks, yeah I guess I'll give that a go in the morning

I don't see this issue, which is odd. I have uninstalled WMR at least twice I think. And the registry entry remains as is and no extra monitors. I have a single monitor, guess you do too so not a factor?

[Twwhitey]

3 hours ago, ShaunX said:

 

Thanks, yeah I guess I'll give that a go in the morning

 So I fixed it but potentially unhelpful update here as it’s not clear exactly what did the trick.  

• I uninstalled and reinstalled WMR.  (No immediate fix)
• I DDU’d & reinstalled nVidia driver 465.89 (No immediate fix)
• i DDU’d and installed nVidia driver 457.30 (no immediate fix)
• as a last resort I went into updates and applied all outstanding updates there were only 4-5 if I recall.  The odd thing is it looked like the recently publicized KB5001330 update which I uninstalled earlier this week re-applied (and took forever to do so) and once completed the pre-allocated setting once again seemed to suppress the extra monitors.  Note I’m on Win10 Pro 20H2 service pack.   

Doesn’t make a ton of sense but I guess I was successful... good luck 

[DerekSpeare]

Ok, so what is the purpose of this Utility?  (I don't have experience with the Oculus tool)  Does it do something beneficial?

Edited April 24, 2021 by DerekSpeare

[zildac]

Ok, so what is the purpose of this Utility?  (I don't have experience with the Oculus tool)  Does it do something beneficial?

Have a read of the release notes. Gives a good outline of what it offers.

[ShaunX]

On 4/23/2021 at 6:48 PM, dburne said:

 

Very strange.

You could always try an uninstall and re-install of WMR, bit of a PITB but does not take too long.

Those virtual monitors always drove me crazy.

 

 

Tried the following today. I deleted the PreallocateVirtualMonitors registry entry, cleared WMR environmant data, rebooted, uninstalled WMR, rebooted, re-installed WMR, added the registry entry again, rebooted..

 

Still getting the 3 preallocated monitors !!!

 

Not sure where to go from here. I've been putting off the 20H2 upgrade, perhaps I should install and see if that makes the difference.

 

Anyone had problems with 20H2 and DCS ?

 

[zildac]

Been running 20H2 for some time, no noticeable issues for me.

[dburne]

33 minutes ago, zildac said:

Been running 20H2 for some time, no noticeable issues for me.

 

Same here.

[ShaunX]

26 minutes ago, zildac said:

Been running 20H2 for some time, no noticeable issues for me.

 

Thanks, my reluctance is because I've had many week of Windows update problems in which both my Intel and AMD machines fail when trying to implement KB5001330 (which I belive can cause performance problems for some anyway). Tried every troubleshooting method available to no avail. Its failed presence was then causing any other new update to fail to install too, including 20H2.

 

Finally came across this Microsoft utility - https://www.majorgeeks.com/files/details/wushowhide.html which allows you to permanently hide queued updates (Not available direct from MS any more - presumably because they want you to install all their updates!)

 

Ran that, hid KB5001330 on both machines and all other updates ran through nicely.

 

So now I guess no excuse and I'll give 20H2 a go

 

 

[zildac]

2 hours ago, ShaunX said:

 

Thanks, my reluctance is because I've had many week of Windows update problems in which both my Intel and AMD machines fail when trying to implement KB5001330 (which I belive can cause performance problems for some anyway). Tried every troubleshooting method available to no avail. Its failed presence was then causing any other new update to fail to install too, including 20H2.

 

Finally came across this Microsoft utility - https://www.majorgeeks.com/files/details/wushowhide.html which allows you to permanently hide queued updates (Not available direct from MS any more - presumably because they want you to install all their updates!)

 

Ran that, hid KB5001330 on both machines and all other updates ran through nicely.

 

So now I guess no excuse and I'll give 20H2 a go

 

 

Useful tool. Yeah, can't say I noticed any huge issue with that update but given the amount of bad press it got for causing stutters I uninstalled it anyway. I'll give the above a go and hide it for the time being