Share via

How revert kiosk mode in windows 11 after activating it using Windows configuration Designer?

Daniele Pichierri 0 Reputation points
2023-12-15T09:56:45.2866667+00:00

Good morning,

I created a basic kiosk profile for Windows 11 PRO, with Windows Configuration Designer, on a PC that already has an administrator account.

After starting the created script, both the kiosk user and the PC administrator user no longer see the start menu and desktop when they log in, but only a black screen.

It is possible to start Task Manager via CTRL+ALT+DEL and trying to start explorer.exe in administrator mode or not, but only explorer appears but no desktop.

Tried a system restore but nothing: Windows is unusable without User Interface since Kiosk is activated again.

Below code of xml generated (changed only Wifi Password):


<?xml version="1.0" encoding="utf-8"?> 

<WindowsCustomizations> 

  <PackageConfig xmlns="urn:schemas-Microsoft-com:Windows-ICD-Package-Config.v1.0"> 

    <ID>{c755b28f-5e6f-4b52-a4d3-2208e24b10a3}</ID> 

    <Name>Project_1</Name> 

    <Version>1.2</Version> 

    <OwnerType>OEM</OwnerType> 

    <Rank>0</Rank> 

    <Notes /> 

  </PackageConfig> 

  <Settings xmlns="urn:schemas-microsoft-com:windows-provisioning"> 

    <Customizations> 

      <Common> 

        <Accounts> 

          <Users> 

            <User UserName="kioskk"> 

              <Password>kioskk</Password> 

              <UserGroup>Standard Users</UserGroup> 

            </User> 

          </Users> 

        </Accounts> 

        <AssignedAccess> 

          <AssignedAccessSettings>{"Account":"kioskk", "AUMID":""}</AssignedAccessSettings> 

        </AssignedAccess> 

        <ConnectivityProfiles> 

          <WLAN> 

            <WLANSetting> 

              <WLANConfig SSID="xxxxxxxx"> 

                <WLANXmlSettings> 

                  <SecurityKey>00000000</SecurityKey> 

                  <SecurityType>WPA2-Personal</SecurityType> 

                </WLANXmlSettings> 

              </WLANConfig> 

            </WLANSetting> 

          </WLAN> 

        </ConnectivityProfiles> 

        <DevDetail> 

          <DNSComputerName>Device</DNSComputerName> 

        </DevDetail> 

        <OOBE> 

          <Desktop> 

            <HideOobe>False</HideOobe> 

          </Desktop> 

        </OOBE> 

        <Policies> 

          <ApplicationManagement> 

            <AllowAllTrustedApps>Yes</AllowAllTrustedApps> 

          </ApplicationManagement> 

        </Policies> 

        <ProvisioningCommands> 

          <PrimaryContext> 

            <Command> 

              <CommandConfig Name="InstallShellLauncher"> 

                <CommandLine>dism /online /enable-feature /FeatureName:Client-EmbeddedShellLauncher /all</CommandLine> 

              </CommandConfig> 

              <CommandConfig Name="0" /> 

            </Command> 

          </PrimaryContext> 

        </ProvisioningCommands> 

        <SMISettings> 

          <AutoLogon> 

            <Enable>ENABLE</Enable> 

            <Password>kioskk</Password> 

            <UserName>kioskk</UserName> 

          </AutoLogon> 

          <HideAutologonUI>False</HideAutologonUI> 

          <ShellLauncher> 

            <Enable>ENABLE</Enable> 

            <UserSpecificSettings> 

              <LocalUserSpecificSettings> 

                <LocalUserShellSetting Username="LocalUserShellSetting"> 

                  <UserCustomShell>"C:\TSC_2022.1.4.0\DriverWizard.exe"</UserCustomShell> 

                </LocalUserShellSetting> 

                <LocalUserShellSetting Username="kioskk"> 

                  <UserCustomShell>"C:\TSC_2022.1.4.0\DriverWizard.exe"</UserCustomShell> 

                </LocalUserShellSetting> 

              </LocalUserSpecificSettings> 

            </UserSpecificSettings> 

          </ShellLauncher> 

        </SMISettings> 

      </Common> 

    </Customizations> 

  </Settings> 

</WindowsCustomizations>



Hope this could clarify in some way.

Is possible to restore the User Interface of the Administrator user? E.G. using modified xml?

Thank you for your suppport

Kind regards

Daniele

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Daniele Pichierri 0 Reputation points
    2024-01-08T11:12:26.52+00:00

    Dear wesley,

    thank you for your hints.

    Perhaps, even starting in Safe Mode, still no start menu and other stuff as mentioned before.

    Cheching User Account, it's (as it should be, Administrator account.

    I think problem is script created by Windows Configuration Designer Tool, and IMHO solution could be another sscript to revert, but I'm not able to do this.

    If someone can suggest some workaround or a correct script, probably this issue can be solved

    Many thanks for your precious support

    Kind Regards

    Daniele

    Was this answer helpful?

    0 comments No comments

  2. Wesley Li 11,770 Reputation points
    2023-12-25T08:19:59.8766667+00:00

    Hello,

    You can try enter safe mode to check the issue:

    1.restart the computer, press and hold the F8 key as your computer restarts

    2.The machine will show advanced boot options

    3.Select Safe Mode to boot into Safe Mode

    4.Check if the issue disappears in Safe mode

    5.If so, safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default settings and basic device drivers aren't causing the issue. Observing Windows in safe mode enables you to narrow down the source of a problem, and can help you troubleshoot problems on your PC.

    Besides, regarding your question about restore the User Interface of the Administrator user, maybe you can also try check at Settings > Accounts > Your Info to see if it says Admin account. Sometimes an Admin account can become corrupted.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.