Does the new Edge browser work with Kiosk mode?

Question

I set up loaner devices to just use the browser.  I recently updated them to Windows10-2004 and installed the new Edge browser. I just get a blank blue screen when I try to sign in with kiosk mode after setting it up to open with Edge (the Icon that I am able to select still looks like the old one).  Does anyone know if I need to go back to the old OS or the old Edge?

Answer 1

"When you state, you login as local admin, break the kiosk mode, then setup manually, during this step, are you then creating a new association to the MSEdge executable in the kiosk mode setup per computer? What happens when the PC restarts?"

Yes, after restarting the PCs and without loading GPOs overriding the manual settings, kiosk mode would still be associated to new edge chromium and start to the ONE website provided in the UI settings.

But as you got GPOs to configure other settings like opening up 3 tabs of important URLs instead of one, manual configuration doesn't seem to fit your minimal requirements.

Answer 2

Everything worked great for 8-9 months until our parent company pushed the Windows update that ultimately changed the Browser from Legacy to Chromium Edge.

Answer 3

Hello there,

Thanks for the reply.

We get the exact same message on our training computers when they boot up, i.e., 0Xfffffff.

Our setup, we have GPOs applied to our Training computers. One of the GPOs specifies which PS script to run. In this it informs the computer to autologin, with a specific username, only using Edge Legacy while opening up 3 tabs of important URLs that pertain to the training computers.

With the update pushed, the training computers are still attempting to call the Legacy Edge. We went in and changed the AUMID from Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge to MSEdge. This did not solve the issue by simply redirecting the string to call MSEdge oppose to Legacy. I would think this would be as simple as replacing which app the script calls. Maybe there are additional steps but we have yet to find a solution.

When you state, you login as local admin, break the kiosk mode, then setup manually, during this step, are you then creating a new association to the MSEdge executable in the kiosk mode setup per computer? What happens when the PC restarts?

We also have multiple other GPOs set per the 70+ computer assets to configure exactly as the customer needs.

Here is our PS script that runs on each of the machines. See below for the GPOs applied per computer.

Answer 4

Hi Alex, are you still around for guidance?

We had 70+ training desktops/laptops that were configured with LEgacy Edge. Our new parent company pushed an update to our full landscape via SCCM, which the 70+computer assets got updated to the New Edge Chromium. Now when we attempt to start each computer, they are all blue screened. Not the BSOD but blue screened, like the kiosk mode is only presenting a blue screen. If you are someone from you team is around, can you please assist us in pointing us in the correct direction on how to resolve?

Thank you kindly

Phillip

Hi,

like I wrote in my post yesterday, we are in exact the same situation: installing the latest CU for Windows removed edge legacy and installed edge chromium, which breaks kiosk configuration and shows blue screen with error code 0xfffffff.

For the moment we work around this manually with log in with an admin account, deleting and recreating kiosk user (to revert back all broken kiosk configurations with edge legacy etc.) and then set up manually kiosk mode via settings -> accounts -> other users -> Set up a kiosk. Like this at least we are able to work with that kiosk machines.