Cannot Unlock Taskbar Pinning with LimitedAccessFeatureStatus

Question

I want to pin my application to the taskbar. I followed the steps here, obtained my LAF keys from Microsoft, and now I am trying to implement the feature. Not sure if the LAF keys are bound to a specific application name have other restrictions.

I attempted to use two different functions (both C++ and C#), one from Chromium and one from Microsoft samples. For both, I receive a "Feature not available" message when calling the Status/getStatus function.

My C# code is as follows:

public static readonly string Feature = "com.microsoft.windows.taskbar.pin";
public static readonly string Token = <token1 received from MS>;
public static readonly string Attestation = "
<token2 received from MS> has registered their use of com.microsoft.windows.taskbar.pin with Microsoft and agrees to the terms of use.";

I want to note that for the Microsoft samples, I used the packaged versions, as the unpackaged ones do not work due to this bug.

I tested it on two computers, one with Win10 build 19045 and the other with Win11 24H2, and I get the same result. Is there a way to make it work or at least understand why the status is always "unavailable"?

Answer 1

It seems like you're running into issues while trying to implement taskbar pinning using the LAF keys and encountering the "Feature not available" message when calling the Status/getStatus function. Let's break down the issue and potential solutions:

1. LAF Keys and Restrictions

LAF (Launch and Find) keys are part of a broader set of Microsoft APIs designed to manage application launching and pinning to the taskbar. From the code you've shared, you're using the com.microsoft.windows.taskbar.pin feature, which is part of a taskbar pinning API.

Application Identity: LAF keys are often associated with Microsoft Store-registered apps or apps that meet certain criteria in the Windows Store. If you are working with an unpackaged app (like one you've built yourself), you may encounter limitations or issues related to the identity of your app. This could explain why the API isn't working as expected.

• Ensure that your app is correctly packaged or registered. Unpackaged apps often cannot access some features, and pinning to the taskbar may be one of them.

Feature Availability: The "Feature not available" message likely means that the feature you're trying to use isn’t enabled or accessible for your application, either due to the type of app you're building or permissions issues.

2. "Feature Not Available" Error

The error you're encountering—"Feature not available"—could be due to several things:

Incompatibility with App Type: If you're using an unpackaged app, some Windows APIs might not be available for it. As you mentioned, the unpackaged versions don’t work due to a bug. This confirms that you need a packaged app to use these APIs.

Package and Identity Setup: You need to ensure your app is properly packaged and registered with Windows. You might need to use the AppX packaging model (for UWP apps) or MSIX for desktop apps to ensure your app can access the taskbar pinning API. Apps that aren’t part of the Windows Store ecosystem (either private apps or self-distributed apps) can still be pinned, but only if they’re correctly registered with Windows.

Windows Version: Although you tested it on Windows 10 (19045) and Windows 11 (24H2), it's worth verifying that the versions of Windows you’re using have support for taskbar pinning APIs. These APIs may not be available on all builds, and updating to the latest patch version could help.

3. Unpackaged vs Packaged Apps

As you noted, unpackaged apps aren’t working due to a bug. This is because the Windows taskbar pinning API is intended to work with packaged apps or apps that are properly registered.

To make this work, package your app correctly using MSIX or AppX. The packaged app should be registered and should include the appropriate manifest entries that allow it to interact with the Windows taskbar API.

For example, ensure your AppX manifest or MSIX package is correctly set up for interaction with the taskbar. The manifest should specify the AppUserModelID and declare permission for the app to interact with system resources like the taskbar.

4. Token & Attestation

The Token and Attestation you received from Microsoft are critical for validating that your application has the rights to use the taskbar pinning feature. Ensure:

You’re using the correct LAF keys and they haven’t expired or been revoked.

The attestation you received is valid and hasn’t encountered any issues with Microsoft’s system.

Important: Sometimes, if the attestation doesn’t match your application's configuration, the taskbar features might be unavailable. Ensure your app is properly registered in the Microsoft Developer portal if necessary.

5. Steps to Troubleshoot:

Here are a few things to check:

1. Ensure your app is packaged and registered (either as UWP with AppX/MSIX packaging or registered as a desktop app).
2. Update your system: Ensure both Windows 10 and Windows 11 are up to date, as there could be updates to these features that you're missing.
3. Verify LAF key permissions: Double-check that the LAF keys you received from Microsoft are correctly tied to your application.
4. Check the manifest: Verify your app’s manifest includes the appropriate permissions and settings for interacting with the taskbar.
5. Use the Microsoft Samples: Ensure you're testing with the latest Microsoft sample code, especially the packaged versions, which you’ve already identified as necessary.
6. Consider Using Other APIs for Taskbar Pinning

In case the LAF-based approach doesn't resolve the issue or if you're not tied to using it, you could explore Shell APIs for pinning to the taskbar, though they might not offer the full functionality that LAF provides. These APIs allow interaction with taskbar shortcuts for Windows desktop apps, but there may still be restrictions based on app type and permissions.It seems like you're running into issues while trying to implement taskbar pinning using the LAF keys and encountering the "Feature not available" message when calling the Status/getStatus function. Let's break down the issue and potential solutions:

1. LAF Keys and Restrictions

LAF (Launch and Find) keys are part of a broader set of Microsoft APIs designed to manage application launching and pinning to the taskbar. From the code you've shared, you're using the com.microsoft.windows.taskbar.pin feature, which is part of a taskbar pinning API.

Application Identity: LAF keys are often associated with Microsoft Store-registered apps or apps that meet certain criteria in the Windows Store. If you are working with an unpackaged app (like one you've built yourself), you may encounter limitations or issues related to the identity of your app. This could explain why the API isn't working as expected.

• Ensure that your app is correctly packaged or registered. Unpackaged apps often cannot access some features, and pinning to the taskbar may be one of them.

Feature Availability: The "Feature not available" message likely means that the feature you're trying to use isn’t enabled or accessible for your application, either due to the type of app you're building or permissions issues.

2. "Feature Not Available" Error

The error you're encountering—"Feature not available"—could be due to several things:

Incompatibility with App Type: If you're using an unpackaged app, some Windows APIs might not be available for it. As you mentioned, the unpackaged versions don’t work due to a bug. This confirms that you need a packaged app to use these APIs.

Package and Identity Setup: You need to ensure your app is properly packaged and registered with Windows. You might need to use the AppX packaging model (for UWP apps) or MSIX for desktop apps to ensure your app can access the taskbar pinning API. Apps that aren’t part of the Windows Store ecosystem (either private apps or self-distributed apps) can still be pinned, but only if they’re correctly registered with Windows.

Windows Version: Although you tested it on Windows 10 (19045) and Windows 11 (24H2), it's worth verifying that the versions of Windows you’re using have support for taskbar pinning APIs. These APIs may not be available on all builds, and updating to the latest patch version could help.

3. Unpackaged vs Packaged Apps

As you noted, unpackaged apps aren’t working due to a bug. This is because the Windows taskbar pinning API is intended to work with packaged apps or apps that are properly registered.

To make this work, package your app correctly using MSIX or AppX. The packaged app should be registered and should include the appropriate manifest entries that allow it to interact with the Windows taskbar API.

For example, ensure your AppX manifest or MSIX package is correctly set up for interaction with the taskbar. The manifest should specify the AppUserModelID and declare permission for the app to interact with system resources like the taskbar.

4. Token & Attestation

The Token and Attestation you received from Microsoft are critical for validating that your application has the rights to use the taskbar pinning feature. Ensure:

You’re using the correct LAF keys and they haven’t expired or been revoked.

The attestation you received is valid and hasn’t encountered any issues with Microsoft’s system.

Important: Sometimes, if the attestation doesn’t match your application's configuration, the taskbar features might be unavailable. Ensure your app is properly registered in the Microsoft Developer portal if necessary.

5. Steps to Troubleshoot:

Here are a few things to check:

1. Ensure your app is packaged and registered (either as UWP with AppX/MSIX packaging or registered as a desktop app).
2. Update your system: Ensure both Windows 10 and Windows 11 are up to date, as there could be updates to these features that you're missing.
3. Verify LAF key permissions: Double-check that the LAF keys you received from Microsoft are correctly tied to your application.
4. Check the manifest: Verify your app’s manifest includes the appropriate permissions and settings for interacting with the taskbar.
5. Use the Microsoft Samples: Ensure you're testing with the latest Microsoft sample code, especially the packaged versions, which you’ve already identified as necessary.
6. Consider Using Other APIs for Taskbar Pinning

In case the LAF-based approach doesn't resolve the issue or if you're not tied to using it, you could explore Shell APIs for pinning to the taskbar, though they might not offer the full functionality that LAF provides. These APIs allow interaction with taskbar shortcuts for Windows desktop apps, but there may still be restrictions based on app type and permissions.

If these suggestions don’t solve the issue, I recommend reaching out to Microsoft Developer Support for further assistance on LAF keys and taskbar pinning, as they might be able to provide specific insights into your app’s configuration or any recent changes to the API that could affect your use case.