How do I stop a File Explorer window from opening after the source has been sysprepped.

HOJNACKI, ANDY 0 Reputation points
2023-11-17T18:42:16.0233333+00:00

I have a Windows 10 machine configured the way I need. all windows are closed only thing available are the shortcuts on the desktop.

I copy a unattend.xlm file to c:\windows\panther

I open a command prompt change to c:\windows\system32\sysprep and execute sysprep /generalize /oobe /shutdown.

Process is successful.

When I power this machine back on it goes thru the boot process as expected and after all reboots are completed the desktop appears but a File Explorer window opens as well.

I cannot find why this file explorer window now opens every time the machine is rebooted.

I checked things like startup and runonce registry keys.

Any help is appreciated

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
5,410 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Wesley Li 9,020 Reputation points
    2023-12-25T09:54:18.3766667+00:00

    Hello

    Will the explorer opened automatically when we change to another account?

    If the explorer was opened automatically when we change to another account. It indicates the configuration is based on the account settings.

    If it is not, it indicates the issue should be related to machine settings. We could try the autoruns tool to check all the automatic entries.

    Autoruns for Windows - Sysinternals | Microsoft Learn

    If the issue occurred when we changed the account, we could try the process monitor tool to capture the login process then analyze.

    1. Download the Process Monitor tool.

    https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

    1. Extract the Process Monitor tool.
    2. Open the process monitor, press “Ctrl+E” to “suspend” it, “Ctrl+X” to clear present process information.
    3. Press “Ctrl+E” to start the process monitor again, change to login with another account then reproduce the issue.
    4. Login back to previous account then Press“Ctrl+E” to “Suspend” it again then save the present log(Ctrl+S).
    5. Then navigate to "Tools" tab and choose "Process Tree". Look for explorer process and check the detailed information for why it was opened.

    If the issue only occurred when we reboot the machine, we could try to capture the boot log with process monitor.

    a.Run procmon.exe; Choose Options->"Enable Boot Logging".

    4.Don't choose "Generate Profiling events", click OK.

    1. Reboot and open process monitor again, you will get a popup window to save the boot log. Save the boot and check the "Tools" tab and choose "Process Tree". Look for explorer process and check the detailed information for why it was opened.

    You could share the logs here, and we may try to check the log for you.

    0 comments No comments

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. HOJNACKI, ANDY 0 Reputation points
    2023-12-27T15:21:50.87+00:00

    I found out that I needed to change the following key before running sysprep.

    open registry and delete any userint strings in the key.

    HKLM\SOFTWARE\Microsoft\Windows NT\Current Version\WinLogon userinit key

    0 comments No comments

Your answer

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