> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/desktop/web-vault-+-desktop-app/older/vault-version-16.0.1.md). # Vault Version 16.0.1 Released on May 21, 2021 This is a bug fix release that mainly focuses on the new Record Types feature (still in beta). Therefore most customers are not affected by the bug fixes listed below. ## Bug Fixes * KDE-1077: Logout from KeeperFill for Apps generates an error * KDE-1067: Record Type creation not using the generated password * VAUL-4811: Australia data center link to Keeper Importer generates 404 * VAUL-4784: Edit button missing * VAUL-4790: Decryption issue with Linked Record Types * VAUL-4786: Privacy Screen is hiding notes and custom fields * VAUL-4789: Uploading large number of files produces "throttle" errors * VAUL-4791: Decryption errors inside Shared Folders with Record Types * VAUL-4667: Error message when using Account Recovery flow * VAUL-4524: BreachWatch status failure with "status 400" * VAUL-4787: Vault grid view now showing new Record Type icons * VAUL-4800: Sharing and Emergency Access showing confusing messages * VAUL-4805: Deleting shared record not showing in Deleted Items * VAUL-4810: Newly attached files not creating record links, produces error with Record Types * VAUL-4825: BreachWatch admin reports not getting updated ## Improvements * KDE-1072: Update Electron Framework to 12.0.6 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.keeper.io/release-notes/desktop/web-vault-+-desktop-app/older/vault-version-16.0.1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.