A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Separate names with a comma.
Discussion in '2021.2 Beta' started by ProGameDevUser, Jun 27, 2021.
i am downding the 2022.1.beta... but the issue tracker doesn't fix... so maybe we must wait
yep still crash..2021.2.6 and 2022.1.beta.. so maybe i should check the issue checker every day
I can confirm that my fix for the startup crash is working, thank you everyone who helped testing it.
is this bug fix ?
This is it https://issuetracker.unity3d.com/is...ndows-machines-when-tbb12-dot-dll-gets-loaded
still crashing on my win7, seems crash when loading tbbmalloc.dll
when can https://issuetracker.unity3d.com/is...ntreferencesinternal-when-opening-the-project this bug fix ? i really need the new feature in my project
Clean install windows 7 SP1 x64 English, just drivers and Cpp redists, on new SSD.
2022.1.0b2 -- Crashes.
2021.2.7f1 -- Crashes
And now hub doesn't even offer to install 2021.1.28... this is really sad.
Anything after 2020.3 LTS immediately crashes for me also on Windows 7.
The fix has landed in trunk now, the back ports are in progress... I don't have an ETA yet, stay tuned and thank you for your patience.
this bug state has been set to Active, hope the new version can be release
I had this problem, I found out that the issue is the Windows user folder name that contain non alphabetic characters.
Ended up creating a new user using only alphabetic characters and been able to open the editor now.
This is not the reason, my username ever is "user" and have the problem.
But it is awful if "creating a new user" is the only way to solve this problem
We are working on the fix. I think that the username is a red herring, it has nothing to do with issues discussed in this thread. @unity_K8ik7EaSJd1UyA was running into a different issue I believe.
Does anybody have this ntdll.dll crash on fully updated licensed Windows 7? My idea is that the problem may be in unlicensed Win7, where some critical updates not installed.
I have a message "the update is not applicable to this computer" when I run it. Some latest updates in Windows Update are also failed to install due to errors.
Все новые версии Unity у меня не работала до 2022.1.0a15, возможно эта версия будет работать так же у вас, я скачал ее из архива бета https://unity3d.com/beta/2022.1b
I think that is the message I got when I tried to run the KB2533623, which was suggested by the Hub, when I already had KB2758857 which supercedes it. This is a licensed copy of Windows 7 64-bit. And I'm also not seeing any log file in C:/Users/UserName/AppData\Local\Temp\Unity\Editor\Crashes.
I just tried 2021.2 9f1 (the current version) on a second (very old) Windows 7 SP1 machine that hasn't had any updates since 2018, and it worked fine.
It crashes on freshly-installed Windows7 x64, fully-updated-freshly-installed Windows7 x64. No matter. Does not even matter activated or not (I tried installing Win7 enterprise, which I don't have key for, and Win7 pro, which I do have key for. Nothing changed.)
Machine is intel core i3 8gb ram 512gb SSD.
It may be hardware-related, since it does NOT crash on notebook (core i7, 16gb ram, 480gb SSD).
Finally I had to wipe my SSD and install Win10.
Now 2021.2 works, but all buttons/icons are empty
wtf with Unity?
Some good news, all affected releases are now patched:
The fix for 2022.2 landed in the 2022.2.0a1 alpha release.
The fix for 2022.1 landed in the 2022.1.0b8 beta release.
The fix for 2021.2 landed in the 2021.2.12f1 patch release.
This is great news! Thank you for the work done! We hope that there will be no more such errors
2022.1.0b8 : still crashes on launch. Windows 7 x64 with all updates. Machine is 8gb RAM, 512gb SSD
2021.2.11f1 : does the same.
Can you share the dump file from 2022.1.0b8?
but... 2022.1.0a15.223 <...> (version provided by KEngelstoft) - already works
And All the UI icons (disappeared earlier) - was in their places!
(but forum now - don't let me attach pics
ok, let it be forum post link: #98)
The fix for 2021.2 landed in the 2021.2.12f1 patch release so this is not surprising. Can you please try the 2021.2.12f1 patch release?
It is not yet visible in Hub...
Wow, you are right. That one works for me too. Other versions after 2020.3, including the latest 2022.1.0b8, I get this:
There is no dump file - it crashes instantly.
WELL, FINALLY! It remains to wait for this version in the Hub, because now there are only 11.
Hey guys, those who are still getting a crash on 2022.1.0b8, can you please send me a crash dump from it? Instructions can be found here.
I did have some (mini) dump files after all. Search results led me to look in the wrong directory. The correct path for Unity crash dumps is: %LOCALAPPDATA%\CrashDumps (just paste that into Windows Explorer address bar)
The instructions to get a full dump file at Tautvydas-Zilys' link can be confusing if you aren't used to registry edits. REG_EXPAND_SZ = Expandable String Value, for example. This picture of the completed edit may help someone:
Installing vcredist linked above fixed it for me!
Though, GUI is not rendering correctly.
Another user above, after their unity started working, complained that the User Interface is missing.
These are exactly the same buttons, now having issues rendering on my pc.
I'm on Windows 11 - English Version. I'm having issues with Unity 2021.2.11f1
My case looked a little different ...
forum post #33
I think we just had a breakthrough. I noticed that in the dump that somebody sent to me last night, the version of msvcp120.dll used is different than the one on my machine (the version on the crashing machine was 12.0.40660, whereas on my machine it's 12.0.21005.1). After a bit of looking on the internet, I found this support article from Microsoft: https://support.microsoft.com/en-us...-package-5b2ac5ab-4139-8acc-08e2-9578ec9b2cf1
It seems that it's an optional VC++ 2013 update that doesn't get installed automatically (hence none of our machines could reproduce it). Upon installing it on a Windows 7 VM, the editor started crashing identically. After I uninstalled it, and installed one from the official VC++ 2013 download page (https://www.microsoft.com/en-us/download/details.aspx?id=40784), the crashing stopped.
Now that we can reproduce it, I think we will be able to better investigate it. Furthermore, I think this is a valid workaround for anyone running into this issue:
1. Open "Add or remove programs"
2. Find all instances of "Microsoft Visual C++ 2013 Redistributable (x64)" and uninstall them (only x64 and 2013 ones! Don't touch others);
4. Re-install it from https://www.microsoft.com/en-us/download/details.aspx?id=40784
5. Try to run Unity
I just do not have enough words to tell how I am grateful to You!!!
Aaaaand.... they start now, BUT!
I guess the crash with NTdll is really caught... BUT! That does not solve problems for me, sadly...
Version 2021.1.xx does not use compress_bc7e.dll, so it works for now.
But I think I'll need to open another issue, since it probably is not related to this one?
It seems I have the same problem. 2021.1 now works for me also.
What CPU are you running? 0xC000001D is STATUS_ILLEGAL_INSTRUCTION, I wonder if that DLL is using instructions your CPU does not support.
And yes, please open a bug report from the computer this is happening on. It will send the information about your system config.
CoreQuad Q9650 (I know it's an old CPU, but it still works finely. Will test it on core i7 machine later, but it has win10 installed, so -- not fully relevant test.)
Will do tomorrow. I really wonder if case is CPU being slighly ancient.
I think it's likely the DLL is accidentally using AVX instructions which that CPU does not support. If you can report a bug and attach a crash dump, we can take it from there.
You might also be able to work around it by changing BC7 texture compressor from "bc7e" to "ISPC (legacy)" in editor preferences.
Hey! Windows 10 got similar issue as well.
- 2021.2.12f1 doesn't work for me.
- Reinstall Microsoft Visual C++ 2013 Redistributable (x64) doesn't work.
- Downgrade to 2021.1.28f1 works.
Here is the editor.log and crash.dmp
Update: Ryzen 7 3700X
I'm on a Ryzen 7 so that's not it for me.
Anyway, I got 2021.2.12f1 working thanks to Tautvydas-Zilys. Check the version of msvcp120.dll you have in C:\Windows\System32. The version I now have that's working is 12.0.21005.1. The problem it seems is that the linked VC 2013 Redistributable 12.0.30501 did not change the msvcp120.dll file version, so I still had the crashing 12.0.40664 version.
Once I downgraded to VC 2013 Redistributable 12.0.21005.1, and ensured I had the corresponding msvcp120.dll of the same version, Unity no longer crashed. To try to understand what was going on I again went through the steps to uninstall/reinstall the linked version 12.0.30501, and saw that now it kept me on the working 12.0.21005.1 version of msvcp120.dll.
Speculation aside, here's what I did exactly...
I got the VC 2013 Redistributable 12.0.21005.1 from an old nVidia driver package: version 359.06. The installer unzips it to C:\NVIDIA\DisplayDriver\359.06\Win8_WinVista_Win7_64\International\MSVCRT by default. Before installing it, I first uninstalled my current VC 2013 and deleted msvcp120.dll. Deleting the file is tricky because it is likely to be currently in use. Restarting the computer and immediately closing Logitech Gaming Framework allowed me to delete it. Then it was necessary to restart again after deleting it (otherwise the installer would end up restoring the file somehow). Upon rebooting I got an error that a program couldn't start because msvcp120.dll is missing - great! Then the installer gave me 12.0.21005.1 showing in both Programs and Features and for msvcp120.dll. At this point Unity worked.
The link you provided is version 12.0.30501. Once I installed it, Unity did start working, but the buttons are glitching out.
The error still appears
I can no longer reproduce the bug.
I had to dismantle that older PC yesterday due to hardware malfunction.
So we will never know, but I guess it really is because of unsupported instruction on that old machine.
Anyway, on core i7 16gb win10 (notebook) and on core i5 16gb win10 (desktop) I can reproduce the bug win MSVC redist -- if I install latest available, it crashes, if I install one you recommend, it starts perfectly well.
MSVCpp2013x64- 12.0.30501 works as well. Only 12.0.40660 crashes on launch.
I've been sent here by Tautvydas-Zilys from a post I've made about what turned out to be the same issue.
I'll add the little extra I found out in the past days.
It's not just version 12.0.40660, but also version 12.0.40664, which is the latest available from Microsoft here:
Another thing I've noticed is that version 12.0.40664 will install itself alongside the one already installed by Unity, instead of updating/replacing it.
Unity 2020, 2021, and 2022 all install the same version, 12.0.30501.
If you have both of them installed, and you just uninstall version 12.0.40664, Unity will still not work.
You have to install any "non-bugged" version again for Unity to start working again.
Unity 2020 is not affected and, according to an early post by Nomex in this topic, it seems that the issue started with 2021.2.0b16.
It's not help at all.