Windows Black Screen Personalized Settings

Return to site

Windows Black Screen Personalized Settings

Windows 10 Personalized Settings Background
Windows 10 Personalize Settings
Power down the computer completely. If it won't shut down, hold the power button for 5 to 10.
If you're greeted with a dark screen with this Personalized Settings (Not Responding) box in the upper left after Windows Update, don't panic. Many users have reported the same. But luckily they've solved this woe with the fixes below. So read on and check them out…
6 Fixes for Personalized Settings (Not Responding) Windows 10 Personalized Settings BackgroundThe screenshots below are from Windows 10, but the fixes work in Windows 8.1 and 7 as well.
Mar 23, 2019 Windows 7 Forums is the largest help and support community, providing friendly help and advice for Microsoft Windows 7 Computers such as Dell, HP, Acer, Asus or a custom build. 'Personalizing Settings (Not Responding)' window with black desktop wallpaper after recent windows update, how to fix? Windows won't load properly. I can get to the log in screen and when I log in it comes to a black screen with a window in the top left corner saying Personalized settings. The forums say open task manager and restart explorer. But task manager won't open. Ctrl, alt, del works but nothing after. After recent MS patching, we noticed an issue on few Win 10 (1703) computers. When users tried to login, they got a black screen with 'Personalized Settings (Not responding)' message. It took almost between 10 to 30 mins for the normal desktop to show up. BTW, the computers are AWS workspaces. Actually I've tried in different Windows 7 Workstation, but I can log on as Administrator without black screen, it appears it is related to Windows 7 issue. Wednesday, June 26, 2013 10:30 PM text/html 6/28/2013 7:59:03 AM Karen Hu 0.
You may not have to try all these fixes; just work your way down the list until the problem is resolved.
Fix 1: Restart your computerOn your keyboard, press Ctrl, Alt and Del keys at the same time.
In the bottom right of your screen, click the Power button 
and choose Restart.
 Hopefully your desktop comes up normally this time. If not, continue with Fix 2.
Fix 2: Switch the network connection

On your keyboard, press Ctrl, Alt and Del keys at the same time.
In the bottom right of your screen, click the airplane mode icon 
 (or the computer network icon ). Then click Airplane mode whether it's On or Off to switch the network connection.
In the middle of your computer screen, click Sign out.
Log in your computer and see if you get your desktop back this time. If the Personalized Settings (Not Responding) still lingers on, you should try Fix 3, below.
Fix 3: Re-launch Windows explorerOn your keyboard, press Ctrl, Alt and Del keys at the same time, then click Task Manager.
Right-click on Windows Explorer and click End task.
Click File > Run new task.
Type explorer into the box, tick the box before Create this task with administrative privileges and click OK.
Now you should have your desktop back.
Restart your computer and login again to see if this Personalized Settings (Not Responding) issue has been solved.
Fix 4: Run SFC CommandOn your keyboard, press the Windows logo key and type cmd. Then right click on Command Prompt and click Run as administrator.
Click Yes when prompted to confirm.
In the command prompt window, type sfc /scannow and press Enter.
It'll take some time for the SFC to replace the corrupted system files with new ones if it detects any, so please be patient. 🙂
Restart your computer and see if your desktop loads properly. If the Personalized Settings (Not Responding) issue still persists, continue with Fix 5.
Fix 5: Delete a file in regeditPlease note: any modifications in regedit must be proceeded with caution to avoid further problems.
On your keyboard, press the Windows logo key and type regedit, then right-click on regedit and click Run as administrator.
Click Yes when prompted to confirm.
Locate and double-click on HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Active Setup > Installed Components. 
Right-click on the last file and click Export to back up the file. 
If this fix doesn't help with the situation, you might want to import the file to restore the backup. Check out this link for further information.
Right-click on the last file and click Delete.
Restart your computer and see if your desktop comes back.
Fix 6: Want us to fix the problem for you?If the fix above didn't work, and you don't have the time or confidence to troubleshoot the problem for yourself, get us to fix it for you. All you need to do is buy a 1-year subscription to Driver Easy(just $29.95) and you get free technical support as part of your purchase. This means you can contact our computer technicians directly and explain your problem, and they'll investigate to see if they can resolve it remotely.
How have the fixes above helped you with your troubleshooting? Do you have any ideas or tips to share with us? Drop a comment below and let us know your thoughts. 
-->Use SMISettings settings to customize the device with custom shell, suppress Windows UI during boot and sign-in, and block or allow specific keys.
Applies toSettingDesktop editionsMobile editionsSurface HubHoloLensIoT Core
All settingsX
All settings in SMISettingsThe following table describes the settings in SMISettings. Some settings have additional details in sections after the table.
SettingValueDescription
AutoLogonEnable
Domain name
Password
UserNameAllows automatic sign-in at startup so that the user does not need to enter a user name and password.
BrandingNeutralSee BrandingNeutral valuesSpecifies which UI elements display on the Welcome screen.
CrashDumpEnabledSee CrashDumpEnabled valuesSpecifies the type of information to be saved in the event of a crash.
DisableBootMenuTrue or falseDisables the F8 and F10 keys during startup to prevent access to the Advanced Startup Options menu.
DisplayDisabledTrue or falseConfigures the device to display a blank screen when the OS encounters an error that it cannot recover from.
HideAllBootUITrue or falseSuppresses all Windows UI elements (logo, status indicator, and status message) during startup.
HideAutologonUITrue or falseHides the Welcome screen when automatic sign-in (AutoLogon) is enabled.
HideBootLogoTrue or falseSuppresses the default Windows logo that displays during the OS loading phase.
HideBootStatusIndicatorTrue or falseSuppresses the status indicator that displays during the OS loading phase.
HideBootStatusMessagesTrue or falseSuppresses the startup status text that displays during the OS loading phase.
HideFirstLogonAnimationTrue or falseDisable the animation during the first sign-in.
KeyboardFilterSee KeyboardFilter settingsUse these settings to configure devices to suppress key presses or key combinations.
NoLockScreenTrue or falseDisables the lock screen functionality and UI elements
ShellLauncherSee ShellLauncher settingsSettings used to specify the application or executable to use as the default custom shell.
UIVerbosityLevelSuppress or do not suppressDisables the Windows status messages during device startup, sign-in, and shut down.
BrandingNeutral valuesThe following table shows the possible values. You can combine these values using bitwise exclusive-OR logic to disable multiple Welcome screen UI elements.
Windows 10 Personalize SettingsThe default value is 17, which disables all Welcome screen UI elements and the Switch user button.
ValueDescription
1Disables all Welcome screen UI elements
2Disables the Power button
4Disables the Language button
8Disables the Ease of access button
16Disables the Switch user button
32Disables the blocked shutdown resolver (BSDR) screen so that restarting or shutting down the system causes the OS to immediately force close any applications that are blocking system shut down. No UI is displayed and users are not given a chance to cancel the shutdown process. This can result in a loss of data if any open applications have unsaved data.
CrashDumpEnabled valuesContains an integer that specifies the type of information to capture in a dump (.dmp) file that is generated when the system stops unexpectedly.
The .dmp file is typically saved in %SystemRoot% as Memory.dmp.
Set CrashDumpEnabled to one of the following values:
ValueDescription
1Records all the contents of system memory. This dump file may contain data from processes that were running when the information was collected.
2Records only the kernel memory. This dump file includes only memory that is allocated to the kernel, kernel-mode drivers, and other kernel-mode programs. It does not include unallocated memory or any memory that is allocated to user-mode programs.
For most purposes, this kind of dump file is the most useful because it is significantly smaller than the complete memory dump file, but it contains information that is most likely to have been involved in the issue.
If a second problem occurs, the dump file is overwritten with new information.
3Records the smallest amount of useful information that may help identify why the device stopped unexpectedly. This type of dump file includes the following information:
- A list of loaded drivers
- The processor context (PRCB) for the processor that stopped
- The process information and kernel context (EPROCESS) for the process that stopped
- The process information and kernel context (ETHREAD) for the thread that stopped
- The kernel-mode call stack for the thread that stopped
This kind of dump file can be useful when space is limited. However, because of the limited information included, errors that were not directly caused by the thread that was running at the time of the problem may not be discovered by analyzing this file.
The date is encoded in the file name. If a second problem occurs, the previous file is preserved and the new file is given a distinct name. A list of all small memory dump files is kept in the %SystemRoot%Minidump folder.
4Records the smallest amount of useful information. This value produces the same results as entering a value of 3.
7Records only the kernel memory. This value produces the same results as entering a value of 2. This is the default value.
Any other valueDisables crash dump and does not record anything.
KeyboardFilter settingsYou can use KeyboardFilter to suppress undesirable key presses or key combinations. KeyboardFilter works with physical keyboards, the Windows on-screen keyboard, and the touch keyboard.
When you enable KeyboardFilter, a number of other settings become available for configuration.
SettingValueDescription
CustomKeyFiltersAllow or blockAdd your own key filters to meet any special requirements that you may have that are not included in the predefined key filters. 
Enter a custom key combination in CustomKeyFilter, and then select it to allow or block it. The format to add custom filter combinations is 'Alt+F9.' This also appears as the CustomKey name, which is specified without '+'. For more information, see WEKF_CustomKey.
CustomScancodeFiltersAllow or blockBlocks the list of custom scan codes. When a key is pressed on a physical keyboard, the keyboard sends a scan code to the keyboard driver. The driver then sends the scan code to the OS and the OS converts the scan code into a virtual key based on the current active layout.
Enter a custom scancode in CustomScancodeFilter, and then select it to allow or block it. For more information, see WEKF_Scancode.
DisableKeyboardFilterForAdministratorsTrue or falseDisables the keyboard filter for administrators.
ForceOffAccessibilityTrue or falseDisables all Ease of Access features and prevents users from enabling them.
PredefinedKeyFiltersAllow or blockSpecifies the list of predefined keys. For each key, the value will default to Allow. Specifying Block will suppress the key combination.
ShellLauncher settingsUse ShellLauncher to specify the application or executable to use as the default custom shell. One use of ShellLauncher is to create a kiosk (fixed-purpose) device running a Windows desktop application.
Hp nc6400 video driver. Warning
Windows 10 doesn't support setting a custom shell prior to OOBE. If you do, you won't be able to deploy the resulting image.
You can also configure ShellLauncher to launch different shell applications for different users or user groups.
Important
You may specify any executable file to be the default shell except C:WindowsSystem32Eshell.exe. Using Eshell.exe as the default shell will result in a blank screen after a user signs in.
You cannot use ShellLauncher to launch a Windows app as a custom shell. However, you can use Windows 10 application launcher to launch a Windows app at startup.
ShellLauncher processes the Run and RunOnce registry keys before starting the custom shell, so your custom shell doesn't need to handle the automatic startup of other applications or services. ShellLauncher also handles the behavior of the system when your custom shell exits. You can configure the shell exit behavior if the default behavior does not meet your needs.
Important
A custom shell is launched with the same level of user rights as the account that is signed in. This means that a user with administrator rights can perform any system action that requires administrator rights, including launching other applications with administrator rights, while a user without administrator rights cannot. If your shell application requires administrator rights and needs to be elevated, and User Account Control (UAC) is present on your device, you must disable UAC in order for ShellLauncher to launch the shell application.

Setting	Value	Description
AutoLogon	Enable Domain name Password UserName	Allows automatic sign-in at startup so that the user does not need to enter a user name and password.
BrandingNeutral	See BrandingNeutral values	Specifies which UI elements display on the Welcome screen.
CrashDumpEnabled	See CrashDumpEnabled values	Specifies the type of information to be saved in the event of a crash.
DisableBootMenu	True or false	Disables the F8 and F10 keys during startup to prevent access to the Advanced Startup Options menu.
DisplayDisabled	True or false	Configures the device to display a blank screen when the OS encounters an error that it cannot recover from.
HideAllBootUI	True or false	Suppresses all Windows UI elements (logo, status indicator, and status message) during startup.
HideAutologonUI	True or false	Hides the Welcome screen when automatic sign-in (AutoLogon) is enabled.
HideBootLogo	True or false	Suppresses the default Windows logo that displays during the OS loading phase.
HideBootStatusIndicator	True or false	Suppresses the status indicator that displays during the OS loading phase.
HideBootStatusMessages	True or false	Suppresses the startup status text that displays during the OS loading phase.
HideFirstLogonAnimation	True or false	Disable the animation during the first sign-in.
KeyboardFilter	See KeyboardFilter settings	Use these settings to configure devices to suppress key presses or key combinations.
NoLockScreen	True or false	Disables the lock screen functionality and UI elements
ShellLauncher	See ShellLauncher settings	Settings used to specify the application or executable to use as the default custom shell.
UIVerbosityLevel	Suppress or do not suppress	Disables the Windows status messages during device startup, sign-in, and shut down.

Value	Description
1	Disables all Welcome screen UI elements
2	Disables the Power button
4	Disables the Language button
8	Disables the Ease of access button
16	Disables the Switch user button
32	Disables the blocked shutdown resolver (BSDR) screen so that restarting or shutting down the system causes the OS to immediately force close any applications that are blocking system shut down. No UI is displayed and users are not given a chance to cancel the shutdown process. This can result in a loss of data if any open applications have unsaved data.

Value	Description
1	Records all the contents of system memory. This dump file may contain data from processes that were running when the information was collected.
2	Records only the kernel memory. This dump file includes only memory that is allocated to the kernel, kernel-mode drivers, and other kernel-mode programs. It does not include unallocated memory or any memory that is allocated to user-mode programs. For most purposes, this kind of dump file is the most useful because it is significantly smaller than the complete memory dump file, but it contains information that is most likely to have been involved in the issue. If a second problem occurs, the dump file is overwritten with new information.
3	Records the smallest amount of useful information that may help identify why the device stopped unexpectedly. This type of dump file includes the following information: - A list of loaded drivers - The processor context (PRCB) for the processor that stopped - The process information and kernel context (EPROCESS) for the process that stopped - The process information and kernel context (ETHREAD) for the thread that stopped - The kernel-mode call stack for the thread that stopped This kind of dump file can be useful when space is limited. However, because of the limited information included, errors that were not directly caused by the thread that was running at the time of the problem may not be discovered by analyzing this file. The date is encoded in the file name. If a second problem occurs, the previous file is preserved and the new file is given a distinct name. A list of all small memory dump files is kept in the %SystemRoot%Minidump folder.
4	Records the smallest amount of useful information. This value produces the same results as entering a value of 3.
7	Records only the kernel memory. This value produces the same results as entering a value of 2. This is the default value.
Any other value	Disables crash dump and does not record anything.

Setting	Value	Description
CustomKeyFilters	Allow or block	Add your own key filters to meet any special requirements that you may have that are not included in the predefined key filters. Enter a custom key combination in CustomKeyFilter, and then select it to allow or block it. The format to add custom filter combinations is 'Alt+F9.' This also appears as the CustomKey name, which is specified without '+'. For more information, see WEKF_CustomKey.
CustomScancodeFilters	Allow or block	Blocks the list of custom scan codes. When a key is pressed on a physical keyboard, the keyboard sends a scan code to the keyboard driver. The driver then sends the scan code to the OS and the OS converts the scan code into a virtual key based on the current active layout. Enter a custom scancode in CustomScancodeFilter, and then select it to allow or block it. For more information, see WEKF_Scancode.
DisableKeyboardFilterForAdministrators	True or false	Disables the keyboard filter for administrators.
ForceOffAccessibility	True or false	Disables all Ease of Access features and prevents users from enabling them.
PredefinedKeyFilters	Allow or block	Specifies the list of predefined keys. For each key, the value will default to Allow. Specifying Block will suppress the key combination.