Darknote.ai - Cannot run on PC - Need Technical Guidance - Product ID: 9N7KCPCHRJT9

Hello,

I'm seeking technical guidance regarding a Microsoft Store submission that has been rejected multiple times with the error:

"Unusable Feature: Cannot run on PC"

Current Setup

Technology Stack: Tauri 2.9.5 + React 19 + TypeScript

Target Output: MSI

Signing: No local signing (Store handles signing)

Build Process

Step 1 – Build MSI without signing

yarn tauri build --config tauri.windows.conf.json --no-sign

Step 2 – Convert MSI to MSIX Using MSIX Packaging Tool (latest version from Microsoft Store):

Conversion method: Convert existing package (MSI → MSIX)

Certificate: None (unsigned, letting Microsoft Store sign)

Dependencies: Default

WebView2 handled via bootstrapper

Uploaded resulting MSIX to Partner Center

Tauri Configuration

Using tauri.windows.conf.json

webviewInstallMode: "downloadBootstrapper" (previously set to "skip")

CSP properly configured

Store Test Environment (as reported)

Fails on:

ASUS ExpertBook

Dell Inspiron

Surface Laptop Go

Reported OS Build:

Windows build 26200.7623

The app reportedly works correctly on a Microsoft Surface Laptop in local testing.

---

Questions

Detailed Error Logs Is there any way to obtain more detailed logs or crash diagnostics from the Store validation devices? What exactly triggers the “Cannot run on PC” classification?

MSI → MSIX Conversion Could converting MSI to MSIX via MSIX Packaging Tool cause this issue? Would generating MSIX directly from Tauri be more reliable?

WebView2 Runtime Even with downloadBootstrapper, could WebView2 runtime installation be causing launch failure in the Store test environment?

Architecture Targeting Should I explicitly build for x64 and ARM64 instead of relying on default configuration?

Dependencies Are there known Windows dependencies or redistributables required for Tauri apps when packaged as MSIX?

Recommended Approach For Store submissions, is MSI → MSIX conversion considered acceptable practice, or is direct MSIX generation strongly recommended?

---

I would greatly appreciate any technical insight into why an application would pass local testing but fail with “Cannot run on PC” during Store validation.

Thank you in advance for any guidance.Hello,

I'm seeking technical guidance regarding a Microsoft Store submission that has been rejected multiple times with the error:

"Unusable Feature: Cannot run on PC"

Current Setup

Technology Stack: Tauri 2.9.5 + React 19 + TypeScript

Target Output: MSI

Signing: No local signing (Store handles signing)

Build Process

Step 1 – Build MSI without signing

yarn tauri build --config tauri.windows.conf.json --no-sign

Step 2 – Convert MSI to MSIX
Using MSIX Packaging Tool (latest version from Microsoft Store):

Conversion method: Convert existing package (MSI → MSIX)

Certificate: None (unsigned, letting Microsoft Store sign)

Dependencies: Default

WebView2 handled via bootstrapper

Uploaded resulting MSIX to Partner Center

Tauri Configuration

Using tauri.windows.conf.json

webviewInstallMode: "downloadBootstrapper" (previously set to "skip")

CSP properly configured

Store Test Environment (as reported)

Fails on:

ASUS ExpertBook

Dell Inspiron

Surface Laptop Go

Reported OS Build:

Windows build 26200.7623

The app reportedly works correctly on a Microsoft Surface Laptop in local testing.

---

Questions

Detailed Error Logs
Is there any way to obtain more detailed logs or crash diagnostics from the Store validation devices? What exactly triggers the “Cannot run on PC” classification?

MSI → MSIX Conversion
Could converting MSI to MSIX via MSIX Packaging Tool cause this issue?
Would generating MSIX directly from Tauri be more reliable?

WebView2 Runtime
Even with downloadBootstrapper, could WebView2 runtime installation be causing launch failure in the Store test environment?

Architecture Targeting
Should I explicitly build for x64 and ARM64 instead of relying on default configuration?

Dependencies
Are there known Windows dependencies or redistributables required for Tauri apps when packaged as MSIX?

Recommended Approach
For Store submissions, is MSI → MSIX conversion considered acceptable practice, or is direct MSIX generation strongly recommended?

---

I would greatly appreciate any technical insight into why an application would pass local testing but fail with “Cannot run on PC” during Store validation.

Thank you in advance for any guidance.