mrv2 won't start on windows 11

[yozba]

Describe the bug
When I start mrv2, it exits without displaying anything. It doesn't even throw up a crash log.

To Reproduce
what I did is:

• double click mrv2.exe and mrv2-v1.3.0.exe
• open cmd and type mrv2.exe and mrv2.exe -log

Please tell me if there is another thing that I can do.

Screenshots

2024-12-11.16-56-34.mp4

Explorer on the right side of the video is a file search in C:\Users\UserNAME\AppData\Local\Temp

Desktop (please complete the following information):

• OS: Windows 11
• Version mrv2 v1.3.0
• GeForce RTX 4060Ti
  • NVIDIA Studio Driver 566.36

Additional context
I'm not certain if this happans because of Windows 11 or not.
I use japanese on Windows, but it probably doesn't matter because it works correctly on another computer which is Windows 10.
The same thing happens with the Portable version of mrv2.

[ggarra13]

Some things to check:

1. Are you using the official v1.3.0 from github or sourceforge?
2. Compatibility of the NVidia Studio Driver with your graphics card. I am using 566.14 without any issues on a RTX 3080 under Windows 11, version 2024-23H2.

[yozba]

1. Yes, downloaded from github and sourceforge. for your information, I have just tested on mrv2 beta v1.3.1 but nothing changed
2. My Windows version is Windows 11 23H2 (OS builds 22631.4602)

[ggarra13]

What does your PATH environment look like. Since you are confortable with cmd.exe, do:

echo %PATH%

There can be issues if your mrv2 path points to, for example, OpenUSD libraries of a DCC application or some older install. The recommendation for mrv2 is to not add mrv2 to your path during the installation when it asks you to.

[yozba]

This is what displayed.
The area in red is the user name (not the multibyte characters).

[ggarra13]

Try:

cd C:\Program Files\mrv2-v1.3.1\bin
set PATH=
.\mrv2

That way we can rule a path conflict.

[yozba]

hmmm... nothing changed unfortunately.

[ggarra13]

Ok. Then it is likely a hardware or driver issue. Not my area of expertise, unfortunately. Let me compile a small version of mrv2 with debugging and some print statements. I'll get back to you.

[ggarra13]

BTW, does:

mrv2 -h

print anything?

[yozba]

No, it doesn't.

[ggarra13]

Ok. Install this beta of v1.3.1 (minimal functionality) and run it from the command-line:

https://mega.nz/file/2fhTULCQ#yIQk0csnFz2pFAkeDAPyYPk5KnYs8TwdGlhw4L6XlBE

If it is not a hardware or driver issue, it should print out something.

[yozba]

still print nothing...

[ggarra13]

Oops! Sorry. I uploaded the wrong version without any print statements. Try this one:

https://mega.nz/file/OH4VXb4K#tjmpx6Zv0jJcI1WuAuASpa6_iBEn3zuGr4je_5GfbJc

[yozba]

I've tried, but this doesn't seem to change either.

[ggarra13]

Oh, well. I've run out of options. It is likely a DLL issue. You can try opening the executable with Dependency Walker to verify what DLLs it uses.

[yozba]

2024-12-13.21-22-37.mp4

I am not sure if I am using it correctly since I am not familiar with Dependency Walker, but here is the result of opening it when I selected mrv2.exe from the menu in the upper left corner.
Japanese sentences says "Specified file not found".

[ggarra13]

Actually, Dependency Walker is an old tool and has some issues showing dependencies. Try with the open source "Dependencies" (I'm new to it myself):

https://github.com/lucasg/Dependencies

Uncompress the zip to a directory, run DependenciesGUI.exe and do a File->Open for mrv2.exe (not the versioned one) in the mrv2-1.3.0/bin directory.

It should show something like this for the full mrv2-1.3.0:

If you see any DLL missing, we may have found the culprit.

[ggarra13]

And here are the dependencies for the (minimal) mrv2-v1.3.1:

[yozba]

it seems... no errors?

v1.3.0

v1.3.1 (minimal)

[ggarra13]

I am afraid this is as far as my Windows knowledge goes. I think something is definitively broken on your Windows 11 (is it Pro? or normal?). You will need to contact Microsoft or try a Repair/Reinstall.

I am leaving mrv2-v1.3.1 (minimal versions with full debug symbols on here which you can share with Microsoft). These rely on the Microsoft debug runtime and will only run if you install the MSVC 2022 compiler. You can also try that if you are adventuruous.

.exe:
https://mega.nz/file/bDZRATQb#9et2W75g1DxNtKGH3W3TOlKD63o5JcHG_fqZd1LVUaI

.zip:
https://mega.nz/file/LSQTRJjR#Z7CmibaLA3yhASO4NESSuL7P3WFgcmwllPiVPy3bIG0

[yozba]

I was thinly and convinced that there was something wrong with my computer environment, but it seems that this is indeed the case.
I am using Normal Windows, not Pro.

Anyway, thanks for all your help!
I'll comment if I find anything else, but I'll leave it up to you to decide if you close this issue or not.