How to disable “finalize your device configuration” ?

Anonymous
2024-11-21T10:25:15+00:00

I deselected the three boxes in system settings, notifications and actions tab "Show me the Windows welcome experience after an update and possibly when I log in to highlight new features and suggestions", "Suggest ways to finish setting up my device to get the most out of Windows", "Get tips, tricks, and suggestions when using Windows".

In the registry, under the key Ordinateur\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\UserProfileEngagement the key ScoobeSystemSettingEnabled has the value 0.

But the “finalize your device configuration” interface continues to open.

Could you help me ?

Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2024-11-22T06:05:15+00:00

    Hello Hervé Lecanu,

    Welcome to the Microsoft Community.

    Based on your description, we understand that you want to disable the "Complete device configuration" interface in Windows 10. You have tried to uncheck three options in the system settings and set the value of ScoobeSystemSettingEnabled to 0 in the registry. However, this method does not seem to completely solve the problem, because the interface still pops up.

    After our research, you can also try the following steps to troubleshoot the problem:

    Additional registry modifications: In addition to ScoobeSystemSettingEnabled, you can also try to modify other related registry keys. For example, you can try to modify the registry keys under the following path:

    HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Explorer
    

    Create or modify a DWORD value named NoWelcomeScreen in this path and set its value to 1.

    Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE

    • Set the value of SkipMachineOOBE and SkipUserOOBE to 1.

    Group Policy Editor:

    • Press Win + R, type gpedit.msc, and press Enter.
    • Navigate to Computer Configuration > Administrative Templates > Windows Components > OOBE.
    • Look for the setting named "Don't launch privacy settings experience on user logon" and set it to Enabled.

    Task Scheduler:

    • Press Win + R, type taskschd.msc, and press Enter.
    • Navigate to Task Scheduler Library > Microsoft > Windows > Setup.
    • Disable the task named "SetupCleanupTask".

    Sometimes system file corruption can also cause this type of problem. You can run a System File Checker (SFC) tool that can repair corrupted system files.

    1. Open Command Prompt as an administrator.
    2. Run the following commands one by one:
      DISM /Online /Cleanup-Image /ScanHealth 
      DISM /Online /Cleanup-Image /CheckHealth 
      DISM /Online /Cleanup-Image /RestoreHealth
    3. Run sfc /scannow and wait for the process to complete. Check if there are any detected errors.

    If there's no issue found in result, try to create a new Windows user account by following the steps below, to see if you still have the problem under the new account.

    1. On taskbar, search for CMD, then right click on "Command Prompt" to run it in administrator mode and enter the following command: net user USERNAME PASSWORD /add
    2. After the command runs successfully, enter the following command net localgroup administrators USERNAME /add

    Note: USERNAME PASSWORD can be replaced with your desired account name and password, if you do not need a password, you can skip filling in the PASSWORD.

    Through the above two steps, you have successfully added a "USERNAME" account with the administrator permission. If there is no problem under the new account, it should be the account configuration file failure, please refer to the following article to transfer your data to the new account: Fix a corrupted user profile in Windows - Microsoft Support

    Best Regards,

    William.Y | Microsoft Community Support Specialist

    2 people found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful