LLB file is damaged

[wiebe@CARYA]

---

@hadibashiri wrote:

All next backup files are inside the corrupted llb.

---

Another lesson (maybe already learned): DO NOT rename each VI when you make a new version. This is really silly, although I've seen it done many times before. SCC replaced this trick 25 years ago.

[aputman]

In Windows Explorer, right click the LLB and open the properties window.  Click the Previous Versions tab.  If you have Windows Backup running, another version should show up here that you can recover.  Good luck. 

[paul_cardinale]

I was able to recover a dozen VIs from your .llb (but not their names, nor their icons).

Note: .llbs can become corrupted if they are on a drive that you remove while LabVIEW has the .llb open.

[aputman]

Paul,

I was able to recover a few as well using the method described here but they are showing up as LV2014 files.  Yours are LV2016 files (may need to backsave for the OP).  

[aputman]

I did get a name for one file.  FindLength.VI

I can't open it but it does say it's a LV2014 file.

[hadibashiri · Accepted solution]

Dear friends,

Thank everyone for attempting to solve my problem. I read and checked all the comments. The main vi name is "screw sorting 10" . Now I decided to continue from the last existing backup.

Regards.

[billko]

---

@hadibashiri wrote:

Dear friends,

Thank everyone for attempting to solve my problem. I read and checked all the comments. The main vi name is "screw sorting 10" . Now I decided to continue from the last existing backup.

Regards.

---

It's a painful lesson that many, many people (myself included - a loooong time ago) have learned the hard way.  On the positive side... I bet you'll not make the same mistake ever again.  😉  And then you'll find more creative ways to lose your work.  😄