Flagging for awareness after request from NI in this Post:
"Library information could not be updated" message? - NI Community

Got this popup during my build process. I eventually tracked it back to a commit where I had added a unit test (*.lvtest) file to a *.lvlib in the project.
(the reason being I was concerned about scoping and keeping the unit test bundled with the code)
Closing the dialog allows the build to complete as expected, however the dialog does not auto exit and it's been hanging/crashing my CI release process by stopping the EXE build for days at a time until I found the root cause.
Turns out that removing the unit test from the library resolves the issue in my case.
I am building with the options

- due to other issues in the project, but I didn't expect removal of the lvtest file to break the lvlib saving in the build.
(built using LabVIEW 2020 SP1 on Win 10 & Win 11.)
Hope this helps others.
James
CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed