Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.3.0a7
Issue ID
960093
Regression
No
Building as local system user fails on windows
To reproduce:
1) Download attached project
2) Download PsTools (notably, PsExec) - https://docs.microsoft.com/en-us/sysinternals/downloads/psexec
3) Run cmd in administrators mode
4) Run the PsExec like this - "psexec -i -s cmd.exe"
5) Run your Unity in batchmode like this (you can use 'cd' to move to the folder and add logging message if you want it to be more conveniently placed):
<pathtounity>\Unity\Editor\Unity.exe -batchmode -buildWindowsPlayer tmp\test.exe -projectPath <path-to-repro-project> -quit
Expected: It builds normally (it does so when built from editor ran explicitly)
Actual: Compiler errors are found
Reproduced in 2017.2.0f3, 2017.3.0b6, 2018.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment