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
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
Add comment