Closed zackwang closed 8 months ago
I have the same issue.
I reconfigured VS Restart computer untenable antivirus protection
but Can't start it.
.NEt Runtime 5.0.27(x64) Unity Version 2020.3.21f1
@zackwang & @Kijimu7,
Can you look in the
Also, please try terminating the process in Task Manager and try running it again.
This is not a common issue, so it would be very helpful to gather as much information as possible.
EDIT: I was able to start the MizedRealityFeatureTool.exe file! I reinstall and it worked this time!
@davidkline-ms I checked if there is a folder but I don't have the MizedRealityFeatureTool folder in my directory. I also checked the Microsoft folder as well. In my case, I don't see the MixedRealityFeatureTool in the task manager.
@davidkline-ms I hit this issue when installing the feature tool on a new computer as well. Had to install the specific version of .NET in the other thread (5.0.13) to get the app to start. Can we make this work with a wider range of .NET installations?
@Kijimu7 How were you able to get it to work?
I reinstalled the toolkit file multiple times and it worked.
In case you still have problems, it appears that the MRFT don't handle VPN tunnel. If you want to open it, you have to disable it.
If you go to your event manager and see something like that, I'm pretty sure the problem is related.
@Kijimu7 How did you reinstall the toolkit file? I'm only able to directly click on the MixedRealityFeatureTool.exe and it shows up in the task manager but it doesn't open.
I am still having the same problem. it worked in my previous windows installation but not in this one. I installed all the .NET runtimes from top to bottom still nothing. I get these though: Application: MixedRealityFeatureTool.exe CoreCLR Version: 5.0.1722.21314 .NET Version: 5.0.17 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.IOException: The process cannot access the file 'C:\Users\Farhad\AppData\Local\MixedRealityFeatureTool\MixedRealityFeatureTool.log' because it is being used by another process. at System.IO.FileStream.ValidateFileHandle(SafeFileHandle fileHandle) at System.IO.FileStream.CreateFileOpenHandle(FileMode mode, FileShare share, FileOptions options) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access) at Microsoft.MixedReality.FeatureTool.Core.Log.RegisterFile(FileInfo file) at Microsoft.MixedReality.FeatureTool.App.LoadAppState() at Microsoft.MixedReality.FeatureTool.App.Initialize(Object sender, StartupEventArgs e) at System.Windows.Application.OnStartup(StartupEventArgs e) at System.Windows.Application.<.ctor>b__1_0(Object unused) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state) at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame) at System.Windows.Threading.Dispatcher.Run() at System.Windows.Application.RunDispatcher(Object ignore) at System.Windows.Application.RunInternal(Window window) at System.Windows.Application.Run() at Microsoft.MixedReality.FeatureTool.App.Main()
Faulting application name: MixedRealityFeatureTool.exe, version: 1.0.2206.0, time stamp: 0x62577b55 Faulting module name: KERNELBASE.dll, version: 10.0.19041.1826, time stamp: 0x299341e8 Exception code: 0xe0434352 Fault offset: 0x0000000000034fd9 Faulting process id: 0x2a04 Faulting application start time: 0x01d8bd10ff5e0c88 Faulting application path: C:\assd\MixedRealityFeatureTool.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 505d0ca8-c03f-4eaa-a74d-55b564a4b227 Faulting package full name: Faulting package-relative application ID:
We are in the process of updating the Mixed Reality Feature Tool to .NET 6. At the same time, we are planning on releasing a single-binary version which will contain the .NET runtime as well as the assorted DLLs that comprise the tool. We are doing some testing on this new configuration and will advise once it is available.
Thank you for your patience.
Hey, I just let this try by a community member on an M2. He was kind enough to show the error he encountered: https://gist.github.com/JanDeDobbeleer/c9229ac80fe865d8eb371f1fb319cedd
@davidkline-ms I hit this issue when installing the feature tool on a new computer as well. Had to install the specific version of .NET in the other thread (5.0.13) to get the app to start. Can we make this work with a wider range of .NET installations?
Thank you. It worked for me on my Macbook Air M2 with Parallels desktop. I installed the .NET (5.0.13 runtime and 5.0.404 SDK for arm64) and restarted windows. Working now. Hope that Microsoft will update the .NET dependency issue in the next release of the tool.
We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visithttps://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!
I encounter the same issue again with the latest Mixed Reality Feature Tool v1.0.2209.0. I'm using a MacBook M3 with Windows 11 Enterprise on parallel Desktop. I tried the latest .NET6 (6.0.421 in ARM64) as well an older version (6.0.20 in ARM64). None of it works. Could you kindly suggest?
I encountered the problem of Mixed Reality Feature Tool not responding (the Start button does light up) on the lastest Mixed Reality Feature Tool v1.0.22.09.0 on my MacBook Air M2 and parallel desktop. I tried installing the specific versions of .NET (5.0.13 runtime and 5.0.404 SDK for arm64) and it worked. However, it is not stable. When I try again sometime later, the same problem reappears.
It would work sometime after I reinstall the .NET SDK and runtimes, but it was rather unpredictable whether the tool will work this time.
@davidkline-ms I hit this issue when installing the feature tool on a new computer as well. Had to install the specific version of .NET in the other thread (5.0.13) to get the app to start. Can we make this work with a wider range of .NET installations?
Thank you. It worked for me on my Macbook Air M2 with Parallels desktop. I installed the .NET (5.0.13 runtime and 5.0.404 SDK for arm64) and restarted windows. Working now. Hope that Microsoft will update the .NET dependency issue in the next release of the tool.
Describe the bug
I dowloaded the MixedRealityFeatureTool and double clicked to run it but nothing happens. I checked the task manager and it looks like the MixedRealityFeatureTool is running with a some CPU usage but it does not start
To reproduce
I'm running a windows 11 on Mac using Parallels Desktop. To reproduce
Expected behavior
I'm suppose to see some UI
Screenshots
Here is the log file in
C:\Users\zack\AppData\Local\MixedRealityFeatureTool
Task manager shows MixedRealityFeatureTool is running with some CPU usage
I check the event viewer and it shows this error
Your setup
Target platform
Additional context
I tried the same process as bug https://github.com/microsoft/MixedRealityToolkit-Unity/issues/10420 by installing .NET Runtime 5.0.17 (windows x64) and .NET Desktop Runtime 5.0.17 (windows x64) but it still doest not work