I have a Tauri (https://tauri.app/) react app. (latest 1.1, and latest react versions).
I used the Windows Configuration Designer to provision a kiosk device.
I attached the MSI installer of the react application in the kiosk device provision.
The provision worked and I tried to apply it on a different windows 10 PC.
A new account was created for the kiosk user (based on the configuration) but when I`m trying to use this kiosk user a bluescreen appears with the following error message:
We weren't able to start your app. Press Ctrl+Alt+Del to sign out or contact your system Admin. For more info, search online for error code: 0x80070057
My question is, how can I set up a kiosk provision package with a Tauri app?
I wanna use my custom desktop app (Tauri & react) in kiosk mode on windows 10.
Related
We developed an Outlook Web addin in React, build with Webpack. It works on the web, on apps, and on desktop.
We have a very strange case we cannot explain with a customer. We did test on a virtual machine (Windows : 10.0.16299.0 ; Office license : Microsoft Office 365 ProPlus ; Outlook desktop version : Outlook for Office 365 MSO 16.0.10730.20264 32 bit) with both administrator account and normal user account :
Addin is working well with an administrator account, web and desktop.
Addin is working well on web with non admin account, but JS seems not to be executed on desktop. Static HTML content appears, meaning it is not a network or firewall issue.
We have another version of the addin, not using Webpack and React, just pure JS : it is working well both on web and desktop, meaning JS can be executed on the non admin account. We can see the addin loaded in the cache files of AppData.
Is there any problem of React based addin which could explain this very strange behavior (why this difference between an admin and non admin account ? how could JS could be interpreted differently depending on the type of account ?) ? Or any known incompatibility with Webpack ?
Microsoft Store developers did not find this problem running tests on the code...
We have WPF desktop application which we have packed in setup executable. Because of SmartScreen we need to certificate our application. We have used Windows App Certification Kit (WACK) from Windows 10 SDK to generate XML reports. And now we have to submit those reports to Microsoft.
https://learn.microsoft.com/en-us/windows/desktop/win_cert/windows-certification-portal
We have created developer account as company, and when I click on submitting reports:
Test locally and upload the results
After your run the Windows App Certification Kit tests, upload the results to the Windows Certification Dashboard.
https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/
It directs me to Windows Hardware Dev Center dashboard?!?
Were do we upload our WACK reports for our desktop application certification?
I have opened a ticket with Microsoft regarding this and it turns out the "classic desktop" logo program has been discontinued.
The only way you can "certify" your application is either the Ready for Windows program or the Windows Desktop Application program.
I have Windows 10 Ent and WPF app with installer. I want get .ppkg file with configuration this WPF app in kiosk mode, but I get some validation errors in Windows Configuration Designer on the step Configure kiosk account and app. I follow the guides:
https://learn.microsoft.com/en-us/windows-hardware/customize/enterprise/create-a-kiosk-image#shell-launcher
https://learn.microsoft.com/ru-ru/windows/configuration/kiosk-single-app
Short. I am doing:
Turn on Shell Launcher in Windows features
Install Windows Configuration Designer
Set up a kiosk using the kiosk wizard in Windows Configuration Designer (guide 2)
I get an error at step 6
I try create KioskUser without Win Conf Designer. I try use another standart win app (for example notepad.exe), UWP app (calc). I create a kiosk user account with WCD and without WCD (Settings -> Account -> Family & other people). Anyway I fail in step 6. I guess the problem can be in the kiosk user.
In the end I want to get the .ppkg file with my WPF app in the kiosk mode.
Has anyone encountered a similar problem?
I have a client WPF app that uses NativeMessagingHost feature in Chromium browsers.
I've packaged my WPF app into Windows Store Package (.appx) via Desktop Bridge using VisualStudio to publish it in Windows Store in the future.
My app works correctly from Store package. Creates ChromeManifest.json file. But cannot link manifest to chrome NativaMessagingHost name via registry.
Desktop Bridge Apps cannot modify HKCU\Software\Google\Chrome\NativeMessagingHosts\. This is allowed but it's modified in sandbox (proof), so chrome do not see the registry value.
Result: chrome extension cannot find NativeMessagingHost.
NOTE: If I change the registry value to valid value manually via regedit.exe - everything works fine!
So, is there any way/workaround to modify registry key or link ChromeManifest.json from Desktop Bridge App? Maybe on package install?
This is not allowed from a Store app. You would also need to take care of the Chrome-specific registration when the user installs/registers the app as Chrome extension.
I install windows phone 8 sdk, but I created project with target version 7.1
When I try deploy app on wp 7 device I get message that the device locked for developer.
I checked my account on market device is registered there.
Can I deploy app on this device or is it impossible?
You can read about the whole process here.
Here are the steps but if you encounter any issue while following these steps go the the page linked above to see how to fix your problems.
Turn on your phone and unlock the phone screen.
On your phone, ensure that the date and time are correct.
Connect your phone to your computer by using the USB cable that came with your phone.
On your computer’s Start screen, switch to All apps view.
Under Windows Phone SDK 8.0, click Windows Phone Developer Registration. The app starts, as shown in the following image.
Verify that the Status message displays Identified Windows Phone 8 device. Click the Register button to unlock the phone.
If your phone is already registered, the Status message indicates this and you see an Unregister button.
Click Register.
In the Sign In dialog box for your Microsoft account (formerly known as a Windows Live ID), enter the email address and password for your Microsoft account.
Click Sign In.
If you’re a registered developer, be sure to use the Microsoft account associated with your developer account.
After your phone is successfully registered, the Status message displays Congratulations! You have successfully unlocked your Windows Phone.
Note: You need to have Zune installed and running with wp7 devices
If Your Device is Registered and not working so You Should Un-Register your Device from Dev Center and Re-Register it.
The Registration Process is Shown here for WP7.
then Try to Deploy app on Device.