Somehow with recent NV 20110611 release — wrong libraries were tested and included: ones using old reference storage method — instead of new ones shared memory based. As nature of those — remember that after an update, old ones can be still in use (rarely, but happens) — simpliest way to unlock those, and let NV update those on start is system restart.
Additionally — possibly issue with x64 library not always found, even when in the same directory — was solved. As far as we get reports — it seems most likely issue. Other fix to this issue would be — in theory — copying dll to System32 directory, or any other which is searched during DLL calls.
Using buttons below you can quickly share it with others.
The share anchors above have been provided in good faith. All trademarks and registered trademarks are the property of their respective owners. To the best of our knowledge, including but not limited to, sharing subject is not affiliated with, nor has been authorized, sponsored, or otherwise approved by trademarks respective owners.
Google is a registered trademark of Google Inc. Google+™ social service is a trademark of Google Inc.
The buttons above are anchors (links) set to be opened in a new window.
This website is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License. Information on this website is non-binding and intended for general information purposes only. All trademarks and registered trademarks are the property of their respective owners.