This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 68%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEK%3C/text%3E%3C/svg%3E)
Environment:
Hello! I'm trying to use Windows Hello API by C++/WinRT without MSIX packaging.
I have two question about this.
First question is package identity.
Second question is "Methods that use the Request naming pattern".
According to "APIs that require package identity"
I don't understand this list either : most of them work in non-packaged Desktop apps (like Windows.Graphics and others)
(not Windows Hello : I had tested Create a Windows Hello login app in a Desktop app and it returns as you said :
"The process has no package identity. (Exception from HRESULT: 0x80073D54)"
1: if exception isn't thrown, is it okay to use WinRT classes without MSIX packaging?
Could you please tell us what type of project are you developing? Whether have you selected Packaged when you created the project? What do you mean "without MSIX packaging"?
2: What does "desktop apps" mean?
Refer to the Doc: Other app types
Win32 desktop apps (also sometimes called classic desktop apps) are the original app type for native Windows applications that require direct access to Windows and hardware. This makes this the app type of choice for applications that need the highest level of performance and direct access to system hardware.
Re-registered the comment.
What do you mean "without MSIX packaging"?
Whether have you selected Packaged when you created the project?
Packaged.Could you please tell us what type of project are you developing?
#include <winrt/windows.foundation.collections.h>
#include <winrt/windows.security.credentials.h>
#include <winrt/windows.security.cryptography.h>
#include <iostream>
#include <string_view>
using namespace winrt;
using namespace winrt::Windows;
using namespace winrt::Windows::Security;
int main()
{
const auto retrievalResult = Credentials::KeyCredentialManager::RequestCreateAsync(L"windows hello", Credentials::KeyCredentialCreationOption::ReplaceExisting).get();
const auto keyCredentialStatus = retrievalResult.Status();
if (keyCredentialStatus != Credentials::KeyCredentialStatus::Success)
{
return -1;
}
const auto keyCredential = retrievalResult.Credential();
const auto publicKeyBuffer = keyCredential.RetrievePublicKey();
const auto publicKeyBase64 = Cryptography::CryptographicBuffer::EncodeToBase64String(publicKeyBuffer);
std::wcout << std::wstring_view(publicKeyBase64);
system("pause");
return 0;
}
The documentation you refer to belongs to the Windows App SDK. And you're creating a Windows console application.
The documentation said:
Although you can use most Windows Runtime (WinRT) APIs (see Windows UWP namespaces) in your C# or C++ desktop app, there are two main sets of WinRT APIs that aren't supported in desktop apps, or that have restrictions: APIs that have dependencies on user interface (UI) features that were designed for use only in a Universal Windows Platform (UWP) app. APIs that require package identity (see Features that require package identity). Such APIs are supported only in desktop apps that are packaged using MSIX.
As far as I'm concerned, the document is based on desktop applications.
If you want to develop a Windows Hello app, I suggest you could start from the Doc:
I'm sorry. Windows Console Application was just a sample.
I want to add authentication process using Windows Hello in an already developed mfc application.
It’s quite confusing since i was able to call "KeyCredentialManager.RequestCreateAsync Method" or was able to use "Windows.Storage.Streams.DataReader" without exceptions when i tested in mfc application which is GetPackageFamilyName function returned APPMODEL_ERROR_NO_PACKAGE.
And when I called function "Application.Current Method" in mfc application, "The process has no package identity. (Exception from HRESULT: 0x80073D54)" exception thrown.
It seems to be a documentation issue. I suggest you could feedback the issue base on the document link.