Sys 32
-
- SilverLounger
- Posts: 1849
- Joined: 27 Jan 2010, 19:15
- Location: Darlington, Co. Durham. UK
Sys 32
suddenly when booting up I get the attached message on a blacked out screen, what might have precipitated this and how can it be prevented from happening please. Dave.
You do not have the required permissions to view the files attached to this post.
-
- Panoramic Lounger
- Posts: 8128
- Joined: 25 Jan 2010, 09:09
- Location: retirement
Re: Sys 32
What's behind the command box? Your normal desktop?
If so, just close the command prompt window using the X in the top right and then look in your Start Menu, specifically in All Programs | Startup. Is there an entry in there for Command Prompt? If so right click on it and delete it.
However, if the command prompt is all you get on boot, i.e. it's not a normal window on an otherwise normal desktop then I suspect something serious has happened but I've no idea what.
Ken
If so, just close the command prompt window using the X in the top right and then look in your Start Menu, specifically in All Programs | Startup. Is there an entry in there for Command Prompt? If so right click on it and delete it.
However, if the command prompt is all you get on boot, i.e. it's not a normal window on an otherwise normal desktop then I suspect something serious has happened but I've no idea what.
Ken
Last edited by stuck on 09 Mar 2012, 16:02, edited 1 time in total.
-
- Administrator
- Posts: 78238
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Sys 32
If you don't already have it, download and install the free WhatInStartup utility.
When you run it, it will show you all programs that start automatically when you start Windows. Hopefully it will give you a clue. If you find the culprit, WhatInStartup lets you disable it.
Also run a full scan with your favorite anti-virus/anti-malware program.
When you run it, it will show you all programs that start automatically when you start Windows. Hopefully it will give you a clue. If you find the culprit, WhatInStartup lets you disable it.
Also run a full scan with your favorite anti-virus/anti-malware program.
Best wishes,
Hans
Hans
-
- PlatinumLounger
- Posts: 3757
- Joined: 24 Jan 2010, 11:00
- Location: Lexington, KY, USA
Re: Sys 32
Sheesh, I had this happen once but it's been a long time ago. The WhatInStartup is the right choice. It might take some further digging into what IS starting.
Seems to me mine was some legit program that was doing something valid on startup but "forgetting" to close the CMD prompt window. I wish I could remember more...
Seems to me mine was some legit program that was doing something valid on startup but "forgetting" to close the CMD prompt window. I wish I could remember more...
-
- SilverLounger
- Posts: 1849
- Joined: 27 Jan 2010, 19:15
- Location: Darlington, Co. Durham. UK
Re: Sys 32
Yes Ken, the normal desktop is behind the Command box I only took a Faststone capture of it by itself to save size. I do have Whatinstartup and show a shot of what it shows. maybe it will reveal something to your guys that means nothing to me. Would it be prudent to delete any of those shown please? Thanks Dave.
You do not have the required permissions to view the files attached to this post.
-
- PlatinumLounger
- Posts: 5401
- Joined: 24 Jan 2010, 08:33
- Location: A cathedral city in England
Re: Sys 32
Disable the GEST line and reboot. I'm not sure what the fsm line does, either...
There's a whole bunch of other stuff that I'd disable, but it wouldn't cause the problem with CMD.EXE.
There's a whole bunch of other stuff that I'd disable, but it wouldn't cause the problem with CMD.EXE.
John Gray
Venison is quiet deer, and quite dear.
Venison is quiet deer, and quite dear.