LabVIEW crashes on Win11 at startup

[wiebe@CARYA]

---

@Hooovahh wrote:

---

wiebe@CARYA wrote:

As a side note, is Windows 11 supported?

---

I didn't think it was, but apparently 2022 Q3 is according to this table.

---

That is good to know...

Wish they told me, for a wide range of reasons...

[Frozen]

---

@Bob_Schor wrote:

There is only one safe way to uninstall LabVIEW...

---

C:\> Format C:

🤣🤣🤣

[Yamaeda]

---

@Frozen wrote:

---

@Bob_Schor wrote:

There is only one safe way to uninstall LabVIEW...

---

C:\> Format C:

🤣🤣🤣

---

I wouldn't say that's a way to uninstall the program, but it is a way to get rid of it.

I run the Community edition on Win11 at home, it works without issue (though i don't do much in it). As usual, unsupported just means untested, the differences from Win10 are pretty small.

[Bob_Schor]

---

@Frozen wrote:

---

@Bob_Schor wrote:

There is only one safe way to uninstall LabVIEW...

---

C:\> Format C:

🤣🤣🤣

---

No, that's the only way to recover from "forcibly yanking out LabVIEW and all files/folders connected with National Instruments" from a Windows PC.  I (unfortunately) have done this "experiment" at least twice, and found (as they say) that "my goose was cooked", no more ability to reinstall LabVIEW short of starting with @Frozen's First Step (see above).  [Actually, I did "BS's First Step", save your Profile, make a list of your installed programs, get Installation media, and then reformat, saying a few prayers interspersed when necessary.]

Bob Schor

[santo_13]

Unfortunately, you cut the wrong wire of the bomb, now you've to cleanup the mess the bomb left behind. 

As others have pointed out, either you do a system restore from a backup or reformat the OS partition.

[altenbach]

---

@santo_13 wrote:

As others have pointed out, either you do a system restore from a backup or reformat the OS partition.

---

There is also a solution in-between these extremes. Less dramatic than reformatting would be to restore windows (i.e. reset your PC ).

[wiebe@CARYA]

Does msiblast.exe still work?

Manually uninstalling NI products with MSIBlast - Application Builder, Installers and code distribut...

[norbi597@gmail.com]

Actually, reinstalling Windows takes less time than deleting the whole LabVIEW and then reinstall it. But let's get over it.

I'm using LabVIEW 2021 32-bit on my PC which is running windows 11. 

My LabVIEW crashing several times a day! Without any error report or message, all LV windows disappear randomly without any sign. Usually, I manage to open my project for the 3rd or 4th time (it also crashes at the first 2-3 attempts).

My project relatively huge, it loads >1100 elements (>200 classes, including several actors) when I open the project (without crashing). I did not experience this with smaller projects.

I've also noticed when my laptop is unplugged from the power source and it is in battery saver mode, Labview crashes every time. When the power is applied, Labview crashes less frequently.

What do you think, what could be the issue?

[wiebe@CARYA]

---

norbi597@gmail.com wrote:

Actually, reinstalling Windows takes less time than deleting the whole LabVIEW and then reinstall it. But let's get over it.

---

But does reinstall Windows clear all application settings?

I guess that depends on how you reinstall Windows (if you format the disk LV will obviously be gone).

---

norbi597@gmail.com wrote:

I'm using LabVIEW 2021 32-bit on my PC which is running windows 11. 

My LabVIEW crashing several times a day! Without any error report or message, all LV windows disappear randomly without any sign. Usually, I manage to open my project for the 3rd or 4th time (it also crashes at the first 2-3 attempts).

My project relatively huge, it loads >1100 elements (>200 classes, including several actors) when I open the project (without crashing). I did not experience this with smaller projects.

---

That's relatively not that big (sorry 😋), and it shouldn't be a reason to crash LabVIEW (nothing is a good reason).

However, complexity is much more important. recursive use of classes, multiple interfaces. malleable VIs are a more likely reason for crashes. Some nodes might be more difficult to load, like .net assemblies or CLFNs (dlls). The order of loading might become a factor.

Statistically, you'd have less change on something that tickles LV the wrong way with small projects, but the size itself shouldn't be the cause.

---

norbi597@gmail.com wrote:

I've also noticed when my laptop is unplugged from the power source and it is in battery saver mode, Labview crashes every time. When the power is applied, Labview crashes less frequently.

---

The fast startup 'feature' might be related. I have a faint recollection of a similar issue, but the fast startup option is the only thing that comes to mind...

I use a wacom pen, and usually double click on in the getting started window as this is convenient with the pen configuration. This seems to hang one of my projects, while loading, more often. I often repeat this and it keeps hanging, and when I single click it loads normally. This could just be statistics, or a very red haring...
 

Clearing the compile cache often recovers from the crash, but this doesn't resolve the cause. So, if you have to clear compile cache every time, it's not really a solution.

---

norbi597@gmail.com wrote:

What do you think, what could be the issue?

---

These ideas are all unrelated to Windows 11... I suppose it could be a defender issue, a rights issue, or some other tiny (or big) detail that MS changed in Windows 11.

[Bob_Schor]

---

wiebe@CARYA wrote:

---

norbi597@gmail.com wrote:

Actually, reinstalling Windows takes less time than deleting the whole LabVIEW and then reinstall it. But let's get over it.

---

But does reinstall Windows clear all application settings?

I guess that depends on how you reinstall Windows (if you format the disk LV will obviously be gone).

---

---

Re-installing Windows will certainly give you a new Windows Registry, the repository of all of the information about all of the software (and much of the Data, I venture to guess) that is present on the current system.  Thus almost nothing will carry over to the new system.  That is why you need to be prepared to (a) reinstall all applications that existed on the previous Windows machine and (b) restore (from backups) all "data" (such things as all "My Documents" and other User Profile information).

Usually when I describe this process, I always mention that Step 1 is to reformat the C: drive (assuming Windows is installed on the C: drive), with Step 2 being "Install Windows", Step 3 being "Install other Apps", and Step 4 being "Restore User Profiles and data".  Best to avoid needing to do this, of course ...

Bob Schor