Cannot open VI file Labview 2018 on Labview 2020

[weerapong]

Dear All

On my Windows 10 PC LabVIEW 2020 is installed. A file I created in LabVIEW 2018 . When I doubleklick  VI file which created with 2018 version then LabVIEW starts opening and after that it show only getting started windows of Labview.

Could you please help advise me how to fix this ?

Thank you.

Br,

Bee

[PinguX]

Hi,

Maybe you could attach this VI, so that we can try to reproduce the problem on our side.

[Andrey_Dmitriev]

---

@weerapong wrote:

Dear All

On my Windows 10 PC LabVIEW 2020 is installed. A file I created in LabVIEW 2018 . When I doubleklick  VI file which created with 2018 version then LabVIEW starts opening and after that it show only getting started windows of Labview.

Could you please help advise me how to fix this ?

Thank you.

Br,

Bee

---

This is what usually happened if you have in the file's name some "unsupported" unicode characters (for example, if I will rename file to cyrillic, then it will be not opened any longer in LabVIEW on my German OS). Windows will start LabVIEW on double click, but the file will be not opened.

Try to rename it in Explorer, then open not by double click, but by choosing File->Open... in LabVIEW.

Or may be your file is corrupted, so post it here, we will try top open it in different LabVIEW versions.

[weerapong]

Hi

Thank for your replying.

You can find my vi file as attached.

Br

Bee

[Andrey_Dmitriev]

---

@weerapong wrote:

Hi

Thank for your replying.

You can find my vi file as attached.

Br

Bee

---

I haven't 2020 in my hands, but in 2024Q1 is Ok (except some missing SubVIs):

It is saved in LabVIEW 2019.

I re-saved for 2020 - try to open

[weerapong]

Hi

Yes it is correct to show missing sub VI , it is clear for me , it seem my PC may have some problem may related with Windows , your verification can show me that my Vi file still can use.

Thank you.

Br,

Bee

[crossrulz]

Your VI opened just fine for me in LabVIEW 2019SP1.  I would "repair" or uninstall and reinstall your copy of LabVIEW and see if that fixes your issue.