Forum Home
Press F1
Thread ID: 139321	2015-04-14 02:35:00	cmd.exe missing	B.M. (505)	Press F1

Post ID	Timestamp	Content	User
1398530	2015-04-16 01:30:00	All these other suggestions are avoiding what needs to be looked at. msconfig, type that in a run dialogue (winkey + r), open start up tab, screenshot the list and post here. Otherwise the usual fix was reformat and reinstall years ago as this is taking too long. Cheers, KK	Kame (312)
1398531	2015-04-16 02:32:00	The hijack log doesn't look to bad. If you look at the original Picture posted, its not actually the real cmd in the way it looks, ( compare to the other picture posted) & its actually saying the c:\windows\system32 cant be found bingo !!! what its saying is a file in the system32 folder cant be found cmd.exe is just the ~name~ of that dos box popup :-) Have a look in scheduled tasks, there may be something(now deleted) in there trying to run on startup Also , start disabling start items via msconfig:trial & error to find if its in there If you go start , run, cmd.exe that should work, showing cmd.exe is there & working correctly. :)	1101 (13337)
1398532	2015-04-16 03:01:00	All these other suggestions are avoiding what needs to be looked at . msconfig, type that in a run dialogue (winkey + r), open start up tab, screenshot the list and post here . Otherwise the usual fix was reformat and reinstall years ago as this is taking too long . Cheers, KK Ok, here's what is running . 6391 But bear in mind we are on selective start-up after a clean boot . 6392	B.M. (505)
1398533	2015-04-16 03:08:00	bingo !!! what its saying is a file in the system32 folder cant be found cmd.exe is just the ~name~ of that dos box popup :-) Have a look in scheduled tasks, there may be something(now deleted) in there trying to run on startup Also , start disabling start items via msconfig:trial & error to find if its in there If you go start , run, cmd.exe that should work, showing cmd.exe is there & working correctly. :) Dahhhh, I thought it was trying to tell me it couldn't find cmd.exe and as I said at the begining of my lead post, cmd.exe was where it should be and worked fine. I'll move onto scheduled tasks. :)	B.M. (505)
1398534	2015-04-16 03:45:00	Well scheduled items doesn't spoil us with choice. :D Take your pick. :) 6393	B.M. (505)
1398535	2015-04-16 05:58:00	Windows updater looks suspicious since its being called from the programs directory but that could be the correct location, but may as well remove it since support is dropped and there should not be any new updates. In your task scheduler, you can remove the notifications, I'm sure by now you know support has been dropped and you don't need reminders. Cheers, KK	Kame (312)
1398536	2015-04-16 07:00:00	From the two Pic's concerned, in MSCONFIG disable the Lot. They are not needed. Heres what they do. HDD Sentinel runs in the background and verifies SSD / HDD health status by inspecting the SMART status of the disk(s). CCleaner -- its only in the Icon Tray CTFMON -- monitors the active windows and provides text input service support for speech recognition, handwriting recognition, keyboard, translation, and other alternative user input technologies. Windows updater looks suspicious since its being called from the programs directory but that could be the correct location, Just checked on two different XP's, and its not even there in msconfig. The actual file - the is spelling is wrong -- it should be Windows Update not Updater Some reading on it www.file.net	wainuitech (129)
1398537	2015-04-16 22:06:00	Just personally, I would delete wise care & wise turbo from scheduled tasks. Then uninstall it. Its dangerous crapware (a regcleaner) "Wise Care 365 is a bundle of important tools including a registry cleaner,disk cleaner, program uninstaller, memory optimizer and more." memory optimiser, so thats like a ram defragger ? :punk	1101 (13337)
1398538	2015-05-03 06:21:00	Well thanks guy’s for all the ideas, but unfortunately none of them solved the issue. So I put it to one side and forgot about it. Experience has taught me that often if I put something aside and clear the mind I will think of something out of the blue. Well today I thought I’d try a repair from the XP disk. Grrrr, that was a fail because I got a message telling me the files on the disk were older than those on the computer. That probably figures, given that the CD is SP1. So I thought I’d try reinstalling SP2 off the disk MS provided all those years ago. That was another fail because the SP2 disk had somehow become cracked in the envelope they were supplied in. OK, I’ll reinstall SP3. That went fine but on reboot up came the same message BUT then up came a second message with cmd.exe on it and then they both disappeared. Multiple restarts and all is still good. :banana So, the only thing I can put it down to is a corrupt or missing registry entry as sfc /scannow claimed the files were fine and although I restored the registry from a back-up, it seems the back-up was only added to the registry as opposed to replacing the registry??? Not sure what the problem was, but I’m off to pour myself another G&T. :D	B.M. (505)
1 2 3 4