exe building makes small file

[Florian.Ludwig]

This happens to me too. A lot. I'm on 21.0.1f1.

Hitting clean did not work for me.

[Florian.Ludwig]

Sorry for the double post - I can't seem to edit.

I noticed when watching the target path that the builder creates a temporary zip file with the correct size.

Only as a final step (happens very fast, but I think the temp file is renamed to an exe file) does the size fall from 150 MB to 311kB - a real rugpull.

[Yamaeda]

---

@Florian.Ludwig wrote:

Sorry for the double post - I can't seem to edit.

I noticed when watching the target path that the builder creates a temporary zip file with the correct size.

Only as a final step (happens very fast, but I think the temp file is renamed to an exe file) does the size fall from 150 MB to 311kB - a real rugpull.

---

That's an interesting find! Renaming a file shouldn't be a problem, what else is going on in that step?

[EthanHenry]

Was there ever a resolution to this problem?  I think I've finally reached the point where I can't build the project.  I've even been able to retrieve the zip file (which seems to be the correct size) before it gets compiled, but can't really do much with it

[Florian.Ludwig]

Sadly, no.

Of all the suggested methods breaking code into more sub vis to limit file size seems to have done the most to alleviate the problem, but it isn't gone.

I'd be interested to know how you managed to grab the zip file.

Maybe there is a way to finish the build process from there?

[wiebe@CARYA]

---

@Yamaeda wrote:

---

@Florian.Ludwig wrote:

Sorry for the double post - I can't seem to edit.

I noticed when watching the target path that the builder creates a temporary zip file with the correct size.

Only as a final step (happens very fast, but I think the temp file is renamed to an exe file) does the size fall from 150 MB to 311kB - a real rugpull.

---

That's an interesting find! Renaming a file shouldn't be a problem, what else is going on in that step?

---

I think that's where the PE stub (that loads the zipped content) is added to the file.

If that fails, the stub is all that's there.

Makes me suspect a virus scanner... The zip file is closed, virus scanner starts (soon), exe conversion starts, but the file is blocked by scanner that started.

As this is time sensitive, it might appear random.

I never had this, but I don't have a (3rd party) virus scanner. Some can be quite aggressive.

So.. If you have this problem:

• Do you have a (file) virus scanner?
• Can you try to exclude the build folder from the automatic scanning? 

[Florian.Ludwig]

For documentation:

Completely deactivating the 3rd party virus scanner (ESET) did nothing for me.

Today, I still have the LabVIEW.exe white listed in the real time scanner module of ESET, and have the build destination folder excluded from scanning as well.This did not help either, but I thought it could hardly hurt.

[wiebe@CARYA]

---

@Florian.Ludwig wrote:

For documentation:

Completely deactivating the 3rd party virus scanner (ESET) did nothing for me.

Today, I still have the LabVIEW.exe white listed in the real time scanner module of ESET, and have the build destination folder excluded from scanning as well.This did not help either, but I thought it could hardly hurt.

---

Those virus scanners can be stubborn... It is their job, and I suppose changing a zip to an exe is very suspicious. I won't rule it out completely.

Can we somehow figure out if this is a project, LV installation or system issue (or a combination)?

I don't recall I ever had this.

[Florian.Ludwig]

I had hoped that the scanner being ostensibly not started up at all would suffice.

I only have this in one very large project.

It does happen on multiple systems and installations with that project.

[wiebe@CARYA]

---

@Florian.Ludwig wrote:

I had hoped that the scanner being ostensibly not started up at all would suffice.

I only have this in one very large project.

It does happen on multiple systems and installations with that project.

---

Same virus scanner too, though?