Unity 5.3.2p1 64-bit - blank gray home screen

Hi everyone!
I’ve just upgraded to Unity 5.3.2p1 from 5.1.3f1 and having some troubles. Unity project select screen is not starting properly, all I get is gray screen. I am using 64-bit version of Unity on Windows 10, 64-bit.

“AppData\Roaming\Unity\Packages\node_modules” contents seem to be fine, both “unity-editor-home” and “unityeditor-cloud-hub” directorires are there, and looks okay. I’ve tried deleting “AppData\Roaming\Unity\Packages” to force Unity to regenerate them, but no luck, still blank gray screen.

Editor.log:

LICENSE SYSTEM [2016128 21:3:14] Next license update check is after 2016-01-27T08:01:33

Built from '5.3/patch-release' branch; Version is '5.3.2p1 (82077c0be25b) revision 8521596'; Using compiler version '160040219'
OS: 'Windows 10  (10.0.0) 64bit' Language: 'en' Physical Memory: 12195 MB
BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 1, IsPro: 1
Initialize mono
Mono path[0] = 'G:/PROGRAMMING/Unity/Editor_5.3.2р1/Editor/Data/Managed'
Mono path[1] = 'G:/PROGRAMMING/Unity/Editor_5.3.2р1/Editor/Data/Mono/lib/mono/2.0'
Mono path[2] = 'G:/PROGRAMMING/Unity/Editor_5.3.2р1/Editor/Data/UnityScript'
Mono config path = 'G:/PROGRAMMING/Unity/Editor_5.3.2р1/Editor/Data/Mono/etc'
Using monoOptions --debugger-agent=transport=dt_socket,embedding=1,defer=y,address=0.0.0.0:56924
ListPackages failed, output: {
  "name": "unity-editor",
  "version": "5.3.0",
  "problems": [
    "missing: unity-editor-home@~0.0.7, required by unity-editor@5.3.0",
    "missing: unityeditor-cloud-hub@~0.0.1, required by unity-editor@5.3.0"
  ],
  "dependencies": {
    "unity-editor-home": {
      "required": "~0.0.7",
      "missing": true
    },
    "unityeditor-cloud-hub": {
      "required": "~0.0.1",
      "missing": true
    }
  }
}
npm ERR! missing: unity-editor-home@~0.0.7, required by unity-editor@5.3.0
npm ERR! missing: unityeditor-cloud-hub@~0.0.1, required by unity-editor@5.3.0

It seems Unity is unable to find its nodejs modules, even though they are clearly there. Unity 5.1.3 works fine on the same machine.
So what’s going on here? Any workarounds for this?

1 Like

You happen to have unity on a Windows 7 build as I was able to copy all those files over from that and it seemed to fix the problem. I would have figured after a month plus unity would have this figured out by now. Now you got me worried again on building up a new computer with Windows 10…

I’ve checked, the files are exactly correct. I’ve did tried to copy them anyway. but no result.
I’ve actually just installed 5.3.2f1 (public release, not a patch version) and it works fine. The problem seems to exist only in the patch release 5.3.2p1. For some reason Unity released both 5.3.2f1 and 5.3.2p1 at the same day, and only the latter has this problem.
Definitely not a Windows 10 issue.

Good to know. Thanks for the update.
i have a windows 10 and windows 7 machine and only the w10 been giving me issues.