Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
If Windows signs in but shows a black or blank screen, no taskbar or Start menu, or only a cursor, start explorer.exe from Task Manager to restore the current session. Then check the Winlogon shell settings, which control the default Windows desktop shell at logon. The steps below move from temporary recovery to targeted repairs without assuming that every blank desktop has the same cause.
Windows 10 note: Microsoft ended ordinary Windows 10 support on October 14, 2025. These troubleshooting steps can still help with the shell problem, but they do not restore security updates; see Microsoft’s Windows Startup Settings and support information for current details.
Restore the desktop for this session
- Press Ctrl + Shift + Esc to open Task Manager.
- If Task Manager opens in compact view, select More details.
- Select File → Run new task.
- Type
explorer.exeand press Enter.
If the desktop and taskbar return, that confirms Explorer can start at least temporarily. It does not fix why it failed to launch automatically at sign-in. If Task Manager’s Processes tab already lists Windows Explorer, select it and choose Restart. If it is not listed, use Run new task as above. Microsoft gives the same fallback for a blank screen with a cursor in its blank-screen troubleshooting guide.
A missing desktop shell is not identical to File Explorer failing to open a folder: individual folder windows may work even when the desktop, taskbar, and Start menu do not. Conversely, Explorer may crash as soon as it starts or repeatedly restart. The distinction helps choose the next step.
#1 Best Overall
1. Check the Winlogon shell settings
For a standard Windows desktop, the default shell is explorer.exe. Windows’ logon process uses Winlogon settings and userinit.exe to establish the user session. A changed or damaged value can leave Windows signed in without the usual shell. Microsoft documents these settings in its guidance on Windows logon and Winlogon values.
Back up before editing
- If Windows is accessible, create a restore point if practical.
- In Registry Editor, export the key you intend to change: select the key, choose File → Export, and save the backup somewhere accessible.
- Record the existing values. Do not replace the entire
Winlogonkey, and do not import a registry file from an unknown source. - If this is a work-managed, kiosk, or custom-shell computer, ask its administrator before changing a shell value. Such systems may intentionally use something other than Explorer.
Inspect the machine-wide Shell value
- Press Win + R, enter
regedit, and press Enter. Approve the prompt if shown. - Go to
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon. - In the right pane, inspect the string value named
Shell. For a standard desktop installation, it should beexplorer.exe. - If it is clearly incorrect and this is not a custom-shell device, edit
Shelltoexplorer.exe, then restart Windows and test sign-in.
If you cannot use Registry Editor but can open an elevated Command Prompt inside the affected Windows installation, the machine-wide standard shell can be set with:
reg add "HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWinlogon" /v Shell /t REG_SZ /d explorer.exe /fUse that command only when a standard Explorer shell is intended. It overwrites the existing machine-wide value. Do not run it from Windows Recovery Environment as though HKLM automatically refers to the offline Windows installation; recovery may assign different drive letters and uses a different registry context.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Inspect a user-specific Shell value
Also check HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWinlogon for a value named Shell. If one exists, export the key and note the value before changing anything. A user-level override that points to an unfamiliar program may explain why only one account lacks the desktop, but some managed systems deliberately configure one. Do not delete it automatically. Correct or remove it only when you have established that it is an unintended override. A Microsoft Q&A response also recommends checking both locations: Winlogon shell values discussion.
Verify Userinit without guessing at formatting
In the same machine-wide Winlogon key, inspect Userinit. The standard executable is C:WindowsSystem32userinit.exe. Preserve legitimate installation-specific formatting, including any trailing punctuation already present; do not add or remove a comma blindly. Treat an unfamiliar executable or a path in a user-writable folder as a security warning, not as something to normalize casually. Microsoft’s logon guidance describes the standard Userinit path and shell relationship in more detail.
Rank #2
- 15.6" diagonal, HD (1366 x 768), micro-edge, BrightView, 220 nits, 45% NTSC.
2. Repair Windows system files
Run system-file repair from an elevated Command Prompt—search for Command Prompt, right-click it, and choose Run as administrator. On Windows 10 and Windows 8.1, run DISM first and then System File Checker:
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannowDISM repairs the Windows component source; SFC then checks protected system files and replaces damaged copies where possible. See Microsoft’s DISM and SFC repair instructions.
When SFC finishes:
- “Windows Resource Protection did not find any integrity violations.” SFC did not find protected system-file corruption; continue to the other checks because registry, profile, or software problems remain possible.
- “Windows Resource Protection found corrupt files and successfully repaired them.” Restart and test whether Explorer now loads automatically.
- Some corrupt files could not be repaired, or SFC cannot complete. Retry in Safe Mode or from recovery tools; then consider System Restore or a supported repair installation. Microsoft explains how to review the SFC result and its log in the linked instructions.
Windows 7: Run sfc /scannow from an elevated Command Prompt. Do not assume the Windows 10/8.1 DISM repair command above applies: Microsoft’s cited Windows upgrade troubleshooting guidance says the relevant DISM options are unavailable in Windows 7. Use Windows 7 recovery or installation media for version-appropriate repair options.
3. Test in Safe Mode
Safe Mode loads Windows with a limited set of files and drivers. If the desktop works there, a third-party service, driver, shell extension, or startup program becomes more likely; if it fails there too, prioritize core Windows, profile, permissions, or security causes. Microsoft’s Startup Settings guidance covers the Windows 10 recovery path.
In Windows 10, from the sign-in screen or a working desktop, hold Shift while selecting Power → Restart. Then choose Troubleshoot → Advanced options → Startup Settings → Restart. After the restart, press:
Rank #3
- 10th Generation Intel Core i5-1035G1 processor
- 12GB system memory for full-power multitasking
- 256GB Solid State Drive
- 15.6" Micro-edge touchscreen display
- 4 or F4 for Safe Mode
- 5 or F5 for Safe Mode with Networking
- 6 or F6 for Safe Mode with Command Prompt
If Explorer works in Safe Mode, move to a clean boot. If it still fails, Safe Mode has narrowed the cause but does not by itself identify it. Windows 7 and Windows 8/8.1 use different recovery and boot-menu routes; do not assume the Windows 10 screens above are identical on those versions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
4. Use a clean boot to isolate third-party software
A clean boot systematically disables non-Microsoft services and startup items for diagnosis. On Windows 10, sign in as an administrator, then:
- Press Win + R, type
msconfig, and press Enter. - On Services, select Hide all Microsoft services, then select Disable all.
- Open the Startup tab and select Open Task Manager.
- Disable enabled third-party startup items in Task Manager, then close it.
- Select OK in System Configuration and restart.
If Explorer now loads, re-enable disabled services and startup items in batches, restarting after each batch until the failure returns. Narrow down the responsible item, then update, uninstall, or leave it disabled as appropriate. Pay particular attention to desktop customization or shell-replacement tools, context-menu utilities, synchronization clients, security software, and utilities installed shortly before the problem began. Microsoft’s clean boot guide cautions that troubleshooting temporarily reduces functionality; restore Normal startup in System Configuration when finished.
Explorer is not simply an ordinary application that should be enabled in Task Manager’s Startup tab. It is normally the Windows shell launched as part of logon. Disabling and re-enabling random Startup-tab entries is not a substitute for checking Winlogon or performing a controlled clean boot.
5. Find out whether the user profile is damaged
A profile problem is more likely if another account on the same PC gets a normal desktop while the affected account does not, particularly when the machine-wide shell setting is correct. Create or use another local administrator account, sign in, and test Explorer. If the second account works, back up the affected account’s files before attempting profile repair or recreation.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #4
- Latitude 7480 Laptop 14"
- Intel Core i7 6th Gen i7-6600U -Core Processor 2.6GHz (3.4GHz With Turbo Boost)
- 256 GB SSD Hard Drive & 16GB Memory
- 1920x1080 FHD resolution Non-Touch with Webcam and an integrated graphics chip
- Wireless Wifi & Bluetooth
Do not delete a profile until you have checked documents, browser data, application settings, credentials, and encryption keys. A new account is a diagnostic comparison, not proof that every item in the old profile can be safely discarded.
6. Check group membership only when the permissions issue is indicated
Microsoft documents a specific blank-desktop failure in which missing default members of the local Users group—including Interactive and Authenticated Users—can prevent the standard user token from launching Explorer. This is an advanced, conditional repair, not a routine first step. Confirm that this membership issue applies and have an administrator assess the machine before changing local group membership. Microsoft’s explanation is at Windows logon process failed to spawn user app. Its documented commands are:
Net localgroup Users Interactive /add
Net localgroup Users "Authenticated Users" /addDo not run these commands just because the desktop is blank; group membership changes should address the documented condition, not be used as a guess.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.7. Treat unfamiliar shell values or recurring changes as a security issue
Custom shells can be legitimate on kiosk or managed computers, and shell values can also be changed by desktop utilities, remote-management software, incomplete uninstalls, migrations, or malware. Stop before overwriting a value if it points to an unfamiliar executable, script, command processor, or path outside the Windows directory—especially a location under AppData or Downloads. The same caution applies if a value changes back after repair or security software has reported a threat.
Free tools Windows power users keep installed
One-click scans. No signup required.
If compromise is plausible, disconnect the PC from sensitive networks, preserve important data carefully, and run an offline or trusted security scan. Do not treat restoring explorer.exe as proof that the machine is clean. If system integrity cannot be established, recovery or reinstalling Windows may be safer than continued registry edits. Microsoft’s Windows Recovery Environment overview and recovery options guide describe available recovery routes.
Best Value
8. Roll back a recent change or use recovery tools
If the problem began after a driver, update, registry edit, or desktop utility installation, try reversing that change. Depending on what is available in your Windows edition and recovery environment, options may include uninstalling a recent update, rolling back a display driver, removing the utility, or using System Restore to return to a restore point from before the failure.
System Restore is a reasonable choice for a recent software or configuration change. Startup Repair, found in Windows Recovery Environment under Troubleshoot → Advanced options → Startup Repair, is aimed mainly at problems that prevent Windows from starting. It may help when this Explorer issue is part of a broader startup failure, but it is not designed to fix every post-sign-in profile or shell-extension problem. Microsoft’s recovery options explain which tool fits different failure types.
If the screen is completely black and Task Manager will not open, enter Windows Recovery Environment. One documented route is to interrupt startup twice; on the next start, Windows should enter Automatic Repair, where Advanced options provides recovery tools. This may not be available in every hardware or managed configuration. If it fails, use Windows installation or recovery media. Back up important data before reset or reinstall steps whenever possible.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Escalate carefully
- Back up important files using Task Manager, Command Prompt, Safe Mode, or recovery media.
- Undo a recent application, update, driver, or configuration change where possible.
- Try System Restore if an appropriate restore point exists.
- Consider a repair installation or in-place upgrade only where supported for that Windows version.
- Use Reset this PC or a clean installation only after reviewing backup needs and the applications that must be reinstalled. If malware is suspected or severe corruption remains, a clean installation may be the more trustworthy option.
Windows 7 and Windows 8/8.1 have older recovery interfaces and no longer receive ordinary support. Menu names and available reset or repair options differ by version. Windows 10’s ordinary support ended October 14, 2025; any extended-support arrangements depend on the specific user or organization and are not a general continuation of standard support.
Quick Recap
What the symptoms suggest
| What happens | Where to look next |
|---|---|
| Explorer starts manually but not at sign-in | Winlogon Shell and Userinit, a user-specific override, startup conflict, profile damage, or malware. |
| Explorer will not start manually | System-file damage, incorrect paths, profile or permissions problems, malware, or an Explorer crash. |
| Explorer works in Safe Mode | Third-party services, startup applications, shell extensions, or drivers; use a clean boot to isolate them. |
| Only one account is affected | Compare with another account and investigate the affected profile before changing machine-wide settings. |
| Shell values look correct | Continue: correct values do not rule out crashes, profile or permissions problems, damaged system files, or software interference. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
