Four blank errors in each new project

hello,
if you can not update your win7 then you need
its https://www.microsoft.com/de-DE/download/details.aspx?id=53335
and https://www.microsoft.com/en-us/download/details.aspx?id=46817
if you have your update service disabled it wont work, you can unplug your internet activate the service update and then disable it again. one of the two first; also sp1. i think it was the id=46817 then you can run the other; if it says can not update some KB update is missing ...
hope this can help you

 

I am facing exactly same problem of 4 blank spaces in Unity 2018.3.7 and 2018.3.9..

 

wow !!!!!
I started to run in this problem with u2018.
bypassed it by using net 3.5

but now as some packages in u2019 seem to need net 4.x those 4 blank errors become blocking.

I only solved this problem today by installing a µsoft small update located here:
https://support.microsoft.com/en-us...ry-insecure-library-loading-could-allow-remot

this seems to be a good day !!! XD

happy unitying !

 

same problem, i am searching for solution to fix these errors as soon as possible!!!!!

 

@ranjini did you try to install the small windows update ?
it worked perfectly for me

 

I also was getting the 4 blank errors in Unity
I update my Win7 with windows update

the error is gone

 

Doesn't work for me, and I have Windows 10 with all installed updates

 

None of the posted solutions worked for me. I've tried switching to using .NET 3.5, but this only produced errors from TextMesh Pro (which wasn't even in the project, this was tested in an entirely new project) stating that certain features (such as `out variable declaration') could not be used because they were not part of C# 4.0 (?!??!). I'm on Xubuntu 19.04 running Unity 2019.1.6f1. I've also tried Unity 2019.1.0f2, which has worked for me before, but unfortunately it appears this version is also not working. Here are the steps to reproduce:

1. Create a new project.

This is a bit of a roadblock for me when trying to make games.

EDIT: Apparently, Unity relies on libssl 1.0.0, an old version which is no longer available in Ubuntu 19.04 and upwards. More info and the correct package are available from this post.

 

I also got the same error and i just uninstalled unity (2019.1.6f1) and deleted all the folder related to unity in the appdata. i.e,local, locallow and roaming. if you want to keep package that you have download then dont delete unity\Asset Store-5.x folder rest everything you have to delete and install the unity .It work for me used net 4

 

The problem got fixed when I updated windows through the link Thanks
PS: The file is only 2 Mb and it takes like 3 minutes to update so yeah, worth a try

 

I had this problem with Unity 2018 3.6.

I solved it by changing the project setting of scripting runtime version to .NET 3.5 Equivalent (Deprecated).

I use win 7, if that makes any difference.

 

I am using the .Net 3.5 because .Net 4.0 is throwing errors for me. Meanwhile, my friend can use .Net 4.0 without any errors. So we collabed on a project and he ahs to switched to .Net 3.5 because of my problem. Now, when he is trying to to use shader and all, Unity is throwing errors. And now when he switched to .Net 4.0 all errors were now.
Any suggestion?
I can't use 4.0 and he can't use shaders and all without errors in 3.5.

 

I had a problem about the 13,37 I don't know what i have to do

 

worked for me. Thanks!!!

 

Would you please view this issue? https://forum.unity.com/threads/help-with-aot-compilation-with-monopinvokecallback.717917/ Get stuck on that, any idea would be appreciated.

 

I was having this issue of four blank errors with version 2019.1.12f1 on Linux. In my case, changing to .net 3.5 didn't help but installing this version of libssl fixed the problem for me, thank you.

In Fedora this is contained in the package compat-openssl10, which can be installed with

sudo dnf install compat-openssl10

 

Thank you, this solved it for me

 

Is Unity going to fix this win 7 .NET 4.x bug or just drop all support of win 7?

 

I have Windows 10. It seems none of these apply to me. I run Unity 2019.2.0f1. I get 4 blank errors.
This started somewhere after I upgraded to 2019.2 (from 2019.1), and using Google Play Games Services.. I'm guessing it has to do with an outdated API script somewhere, as it also is accompanied by a 'it will compile when the obselete scripts have been fixed' or something. But it's not telling me *which* scripts need to be updated? It also pops up the "I made a backup" dialog on every start. (that was apparently caused by Google Play Games Services)

Edit: Also, it's fine before I build for the first time, then I build the second time, then the 4 blank errors pop up.
Edit Edit: I managed to find a workaround.. So when it does this, I locate VBCSCompiler.exe in task manager, end the task, then reimport a directory that contains scripts. Usually does the trick for me. Just very annoying as this happens every 1-2 builds (even patch and run)..

Also, don't forget to terminate the java executable as well, then reimport something small to trigger a recompile. Some of these things can be pinned to running out of memory.

 

I also have the same problem

 

Read my post ^ if you can. Try ending VBCSCompiler.exe and the java (openjdk) executable from task manager, then reimport something small that triggers a recompile.

 

this worked for me
"
Loading error for hostfxr.dll on Windows
If the Console reports that the hostfxr.dll library was found, but Unity failed to load it from C:\<path_to_app>\hostfxr.dll, you can fix this error on Windows 7 or Windows Server 2008 R2 by installing both KB2999226 and KB2533623 patches.
."
check it here https://docs.unity3d.com/Manual/upm-errors.html

 

Worked for me...(Windows 7)

 

I also have the same probleme how can i remeed to it

 

Getting the same problem. Running on windows 7 with all required updates.
Nothing seems to work in 2019 version, you can no longer use .net 3.5 so no fix available.

 

This solution, for those on Ubuntu 19.10, works with Unity 2019.2.12f1
https://forum.unity.com/threads/empty-log-errors-in-2019-1-0f2.669961/

Similar to what was mentioned by whywhywhy323 above

 

un

WIndows 10 here, this solution worked for me also