Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
3
Found in
2019.3.0a8
Issue ID
1166764
Regression
Yes
Windows Standalone builds with IL2CPP scripting backend don't start on Windows 7
Workaround. Open "<UNITY_INSTALL_DIR>\Editor\Data\il2cpp\libil2cpp\os\Win32\File.cpp" and apply this diff:
diff --git a/libil2cpp/os/Win32/File.cpp b/libil2cpp/os/Win32/File.cpp
index 3d7f48279..1b928f663 100644
--- a/libil2cpp/os/Win32/File.cpp
+++ b/libil2cpp/os/Win32/File.cpp
@@ -503,7 +503,11 @@ namespace os
{
success = TRUE;
// The async write succeeded. Now get the number of bytes written.
+#if IL2CPP_TARGET_WINDOWS_DESKTOP
+ if (GetOverlappedResult((HANDLE)handle, &overlapped, (LPDWORD)&written, TRUE) == 0)
+#else
if (GetOverlappedResultEx((HANDLE)handle, &overlapped, (LPDWORD)&written, INFINITE, FALSE) == 0)
+#endif
{
// Oops, we could not get the number of bytes writen, so return an error.
*error = GetLastError();
See https://forum.unity.com/threads/2019-1-8f1-failed-to-load-il2cpp-unity-on-windows-7-machines.701273/ for more information.
Reproduced in 2019.3.0a8, 2019.2.0b8, 2019.1.8f1 and 2018.4.3f1.
Not reproducible in 2019.3.0a7, 2019.2.0b7, 2019.1.7f1 and 2018.4.2f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment