Windows 10: HELP! A Command Prompt Window Keeps Flashing Quickly On Screen on Windows 10

A few weeks ago, I started noticing a black window flashing on my screen quickly. At first, I wasn't able to make up what it was, but then I recorded my screen for a few minutes to capture it on video, and here's what it is:I haven't found a solution to what this might be or how to get rid of it. I've scanned for malware and removed everything it found, but this still continues to flash on the screen every few minutes. Can somebody tell me what this is and how do I get rid of it?

:)

 

GPU-Z what command line parameter ?

Suggestion: /? (-?) and /help (-help) command-line arguments to show a list of all possible arguments in a small window. *Smile

 

Installation media boots to command prompt

I've just booted from known working install media to see exactly what it does when booting. The sequence of events is...

1. Windows logo on a black screen
2. circling dots appear beneath the logo
3. light blue 'Please wait' screen with circling dots
4. a command prompt window (very briefly)
5. the initial Setup page appears

Do you see steps 1-3? If so, it appears you have stopped at step 4, suggesting that something on the disc cannot be read.

Does the disc boot properly in another machine? If so, try cleaning the laptop's drive lens then try booting from the disc again.

If not, make new install media with Microsoft's Media Creation Tool, either as a bootable USB, on an ISO that you can burn to another disc. At Step 8 in Option One of this tutorial you can choose between making a USB or an ISO.

Download Windows 10 ISO File

 

Command Prompt Window Keeps Flashing


This is what it is:
Schtasks.exe (Windows)

You can try a capture with Sysinternals procmon (free, just search and download it).

As you're looking for a particular process, you can search the (extensive) capture quite easily. Hopefully it will give you a clue.

If I run it from a normal command prompt (I'm logged in as admin) I get a long listing, the first part being this:




- you could try that and see what happens.

Shorter is
schtasks.exe /?

If it's not able to run, you may have some sort of permissions error or other corruption.

- I'm surprised...