FAQ
TL;DR: In 1 Windows 7 case, cmd closed instantly due to malware altering Winlogon Shell; “Like what? Infection.” Remove unwanted tools, run FRST fixlist, and clean the Shell entry to stop cmd/Library popups. [Elektroda, Kolobos, post #16837788]
Why it matters: This FAQ helps Windows 7 users fix a cmd window that opens then closes and a Library folder that pops up at logon.
Quick Facts
- Affected platform: Windows 7; Safe Mode did not help the symptom. [Elektroda, Lasek001, post #16836128]
- Root cause found: malicious Winlogon Shell calling cmd and SoundMixer.exe from AppData. [Elektroda, krzychupar, post #16837358]
- Diagnostic recommended: Farbar Recovery Scan Tool (FRST) with FRST.txt and Addition.txt logs. [Elektroda, RADU23, post #16836256]
- Fix actions used: uninstall Spybot S&D, apply FRST fixlist, remove bad tasks/entries. [Elektroda, Kolobos, post #16837973]
- Outcome: Issue confirmed solved by Nov 21, 2017, without reinstalling Windows. [Elektroda, Lasek001, post #16839721]
How do I fix a Windows 7 cmd window that opens and closes immediately?
Treat it as malware. Uninstall conflicting tools like Spybot, run FRST, and apply a provided fixlist to clean Winlogon Shell and scheduled tasks. Reboot and confirm cmd no longer flashes and no Library window appears. “Like what? Infection.” [Elektroda, Kolobos, post #16837973]
Why does the Library folder open at startup along with a flashing cmd?
A malicious Winlogon Shell command chained cmd.exe and then launched explorer.exe, which triggers the Library window. Cleaning the Shell value and any referenced binaries stops both the cmd flash and the Library popup at sign‑in. [Elektroda, krzychupar, post #16837358]
Is Safe Mode enough to bypass this problem?
No. The original report notes that booting in Safe Mode did not change the behavior. That indicates a persistent logon hook, not a normal startup item that Safe Mode disables. [Elektroda, Lasek001, post #16836128]
What is FRST and why use it here?
FRST (Farbar Recovery Scan Tool) produces detailed logs of autoruns, tasks, and registry keys. Helpers use it to craft a targeted fixlist that removes malicious entries without reinstalling the OS. Attach FRST.txt and Addition.txt. [Elektroda, RADU23, post #16836256]
How do I safely run a FRST fixlist?
- Save FRST.exe and the provided Fixlist.txt in the same folder.
- Run FRST as Administrator and click Fix.
- Reboot when prompted and share the Fixlog for review. [Elektroda, Kolobos, post #16837973]
Should I remove Spybot Search & Destroy before cleaning?
Yes. The helper advised uninstalling Spybot before applying the fixlist. This avoids conflicts and removes related shell extensions and services referenced in the logs. [Elektroda, Kolobos, post #16837973]
How do I confirm the infection is gone?
After reboot, the desktop should load without a cmd popup, and the Library folder should not open. The user confirmed success on Nov 21, 2017, after following cleanup steps. [Elektroda, Lasek001, post #16839721]
What logs should I post for help?
Generate and attach FRST.txt and Addition.txt from FRST. These logs show autoruns, tasks, and critical registry values needed for a tailored fixlist. [Elektroda, RADU23, post #16836256]
What exactly changed in the registry?
The Winlogon Shell value was altered to run cmd.exe and conditionally start SoundMixer.exe, then explorer.exe. Restoring Shell to explorer.exe fixes the startup chain. [Elektroda, Acorus 20, post #16837359]
Could a USB device have introduced this?
It’s possible. The logs list MountPoints2 entries pointing to autorun‑style executables on drive H:. Disable autorun and scan removable media when cleaning. [Elektroda, Acorus 20, post #16837359]
How long did the successful fix take in this case?
It was confirmed solved by Nov 21, 2017. That is within roughly one day of the initial report on Nov 20, 2017. [Elektroda, Lasek001, post #16839721]
What if cmd still opens at startup after I run the fixlist?
Rescan with FRST, post fresh FRST.txt and Addition.txt, and confirm the behavior after boot. A helper explicitly checked whether cmd still appeared at start. [Elektroda, Kolobos, post #16838694]
What is SoundMixer.exe in AppData in this context?
It is a malicious file referenced by the altered Shell command in AppData\Roaming\Microsoft\SoundMixer. Remove it during the fix to stop reinfection. [Elektroda, krzychupar, post #16837358]
Can running cmd as Administrator or from .bat help?
No. The user tried Run as Administrator and .bat wrappers, but cmd still closed immediately. The root cause was the Shell hijack, not permissions. [Elektroda, Lasek001, post #16837237]
What is the Windows Winlogon Shell?
It’s a registry value that defines the program launched after user logon. Here, malware replaced the default explorer.exe with a chained cmd call. Restore it to explorer.exe only. [Elektroda, Acorus 20, post #16837359]