Assigned Access will not start

Allan J. Ashinoff 531 Reputation points
2020-12-20T16:42:33.313+00:00

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
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,677 questions
Accepted answer
  1. Lucas Burlingham 81 Reputation points
    2021-02-25T20:46:13.653+00:00

    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.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Allan J. Ashinoff 531 Reputation points
    2020-12-20T17:00:50.137+00:00

    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.