Search Issue Tracker
Fixed in 2019.3.X
Votes
1
Found in
2019.3.0a8
Issue ID
1167678
Regression
Yes
[Win7] Crash on QueryInterfaces when opening any project with Windows 7
How to reproduce:
1. Create a new project in 2019.3.0a8 while using Windows 7
2. Try to open it
Reproducible with: 2019.3.0a8
Not reproducible with: 2019.3.0a7, 2019.3.0a1, 2019.2.0b9, 2019.1.9f1, 2018.4.3f1, 2017.4.30f1
Workaround: Installing this update (https://support.microsoft.com/en-us/help/2533623/microsoft-security-advisory-insecure-library-loading-could-allow-remot) seem to solve the issue in most cases
-
IsouEU
Jan 02, 2020 09:28
So ?
It's soulvable?
KB2533623 was not applicable to my computer
I still with this problem, I don't want to devilgrade my system to windows 10 -
Peter77
Jul 24, 2019 03:49
Related forum thread:
https://forum.unity.com/threads/2019-3-08a-crashes-before-it-starts-used-to-work.711464 -
nobluff67
Jul 18, 2019 16:43
I have the same issue as @LIGHTNING_A.
-
Lightning_A
Jul 11, 2019 02:32
I installed all the important updates from windows updater and I tried downloading KB2533623, but it said that that update was not applicable to my computer, however KB2533623 doesn't show up on my list of installed updates. It still doesn't work so I don't know what's up.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.0a11