question

AllanJAshinoff-5533 avatar image
0 Votes"
AllanJAshinoff-5533 asked LukeSchwingler-0906 commented

Assigned Access will not start

I've setup a dozen or so Assigned Access Windows 10 systems (MS Kiosk) in the past. A recent system purchased required a Kiosk interface but the kiosk consistently fails to start.

"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 0xffffffff."

Specs:
Windows 10 19042.685, 20H2
Celeron N3450 Processor
8GB memory
128GB storage Space

windows-10-general
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Can you specific how you set up the UWP application? Is this the same application that you have set up before?
There are couple ways to setup assigned access, multi app and single app, what steps are you following to set up Assigned Access?

0 Votes 0 ·
LucasBurlingham avatar image
1 Vote"
LucasBurlingham answered LukeSchwingler-0906 commented

I think that the issue here is the fact that MS Edge Chromium is not running as a UWP, the only type of app that is able to run in Kiosk mode. MS Edge Legacy was updated in the 20H2 update to the newer MS Edge Chromium, causing the issue.

I may be wrong, but this is the most likely thing I can think of.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

It's a logical assumption that I can agree with. Thank you.
Is it just me of has it become par for the course for Microsoft to do thing half-assed way? Seriously, Windows 10, Edge and the Assigned Access are all their products and they don't ensure compatibility when they make updates? We use the Kiosk on quite a few machines and this is a huge issue for us, particularly because assigned access requires Edge.

Thank you again. Since the MS Techs have avoided offering a troubleshooting path.

0 Votes 0 ·
0 Votes 0 ·
AllanJAshinoff-5533 avatar image
0 Votes"
AllanJAshinoff-5533 answered AllanJAshinoff-5533 commented

We use a single application that uses Edge. All of my systems for this department run the same application. Administrative access is required to do anything other than use the Kiosk application.

Without the Kiosk enabled the application runs fine. On the previous Win10 systems (approximately 25) the application works fine in Kiosk mode.

The procedure is pretty straight forward. I'm working off the cuff so this may be out of sequence.

  1. Pick a user name

  2. Choose the mode (single app or restricted browser)

  3. Choose the primary application (in my case Edge)

  4. Set your intranet link

  5. Save

  6. exit

  7. reboot.


Assigned access consistently fails. I can do a ctrl+alt-del to switch to an administrative account to gain access, so the system itself isn't hung or faulting. I'm pretty sure this is an MS update issue and I just need to know how to get around it.


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

One problem I ran into was if a UWP application was just installed for all users, Assigned access was not working until the application was registered in that user account. It might be that Edge was updated and needs to be registered with the account. Run the following PowerShell call and attempt assign access again:

 Get-AppxPackage -allusers | foreach {Add-AppxPackage -register "$($_.InstallLocation)\appxmanifest.xml" -DisableDevelopmentMode}
0 Votes 0 ·

Unfortunately, that didn't work for me. This only seems to impact the updated systems. I'll just avoid updating for the time being until I find a solution or I'll move to Chrome and use its native kiosk capability.

Thanks

0 Votes 0 ·