At Startup a cmd and temp window open...

The same thing I thought yesterday when I saw the screenshots...

 

That's, once again, a case where knowing the parent ("Who started me?") actually helps.

 

Thank you I will get into that, slowly, as I as usual have to translate that into a language I understand...

Could you tell me a bit what is meant by registered service? Registered by MS, by Fujitsu, by something I installed, by something that should not be there?
Everything on that laptop works the way it is supposed to... what does that tell me (or you) about the content?

 

"...everything works as it should..." means that everything works as its should. There is a cmd window opening, then a few seconds later a failure notics pops. Both can be closed with one mouseclick, everything "else" works as it should. Nothing noticable "fails".

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I agree to some extent....but.
I don't think that it would cause that issue because it is in a temp folder, which would be likely be cleaned at some point in time. I suspect that the offending software or software's related to Avast were ripped out by random deletions instead of being properly un-installed. I would think that re-installing and then un-installing it (Avast or Avast related software) properly would also fix this issue.

 

You need to login to view this posts content.

 

I think DukiSync already explained that.
Have you looked into your "services.msc" to find anything related and or checked Black Vipers Windows 7 Configuration settings yet?
Several people attempting to help asked you this and you are not making any replies...Why?

 

Yes, there is nothing in the temp folder, and the problem is not a non-existing Avast file, it is something that triggers the search for this non existing file.
As Avast was NEVER installed on that computer I cannot re-install it. Even if I did install it and then uninstalled it, I would be back were I am, the process that triggers the .cmd search for a non-existing file that neither exists now, nor will it after uninstalling Avast, will still be running.

Yes, I have checked that, and as we are at post #92 of the thread somewhere in there must be that answer already. Alone yesterday I wrote six answers, and all but two were repeats of previous answers. The Fujitsu laptop will be back here in a few days, and then I will try to find.
As Carlos and Duki wrote, the point is who triggers the search, and that has most probably nothing at all to do with anything Avast...

Once again, I thank everybody, even the wild goose chase for a never existing avast file taught me something. I made the mistake of not realizing sooner, that the question actually is, what triggers the .-cmd command.
Only shows you, that no matter how high your IQ was when you were young, once you get beyond 70, you better deduct quite a lot of points....

 

We all became old ... When you're ready - let's continue!

 

Point is, its not my computer, she brings it over about twice a week... some young kid only 60...

 

I am sort of trying to limit new things to learn.. right now I am busy with sysinternals-pro.
And I have a life away from my friend's computer. When I asked, what looked to me like pretty simple question, I thought I will get maybe one or two suggestions, which will probably both work. Which is what usually happens when I ask a question, and which is the reason why I ask here. But I admit it is a weird question to ask why a computer cannot find something that was never on the computer in the first place...
But... Thank You

 

You need to login to view this posts content.

 

Try this:
Start - Control panel - Administrative tools - Services
And examine list of services
...

 

If you relly want to find something you have to be logged in as "Administrator" and run things "As Administrator"...
It is easier to search registry with "RegScanner" or "Reg Finder", you will get complete search list list at once, so you can "jump on keys", in windows regedit you have to "Find next" from pull down menu...
...