[Solved] Programs won't run after startup

[ozwanderer]

This one has me baffled at the moment - I've just rebuilt my laptop with Vista Home Premium, SP2 and all updates. After what looks like a normal bootup, applications will not start. The mouse moves normally over icons, but will not show the info popup in the Quick Launch or the System Tray. Clicking these icons is ineffective. I can open other items on the desktop - eg Computer - but this will not explore further or close.

The only workaround I have at the moment is to start Task Manager, and this is the baffler. As soon as TM is opened everything behaves normally and continues to do so until next bootup. Closing TM immediately is also ok. I've uninstalled Avast AV and installed MSE instead, both seem to work but the problem remains (it was also there before I finished the updates) I've put Task Manager in Startup, but this doesn't work. Only running TM manually after startup seems to have an effect.

Any ideas??

[KenB]

Hi and welcome to ExTS

 

I've just rebuilt my laptop with Vista Home Premium, SP2 and all updates

When you say "rebuilt" do you mean you have re-installed Vista or have you replaced internal hardware and used the old Hard Drive with Vista on it?

[ozwanderer]

Rebuilt=return to out of the box state-reformat HDD, reinstall OS and other programs. No hardware issues.

[KenB]

Hi

 

If you right click on an icon that will not open > Properties

It should say C:\Program Files \software name.exe

Does it ?

[ozwanderer]

I've just rebooted to have a look - right click on items in Quick Launch tray has no effect; on desktop >Properties the normal info appears (Target pathway etc) but the window will do no more - move, close, minimise, open another tab - none of these works. Firing up Task manager makes all ok.

[KenB]

it was also there before I finished the updates

Don't understand why you continued installing programs etc

It would have been easier to re-install again.

 

right click on items in Quick Launch tray has no effect;

This is odd as they are the same icons as the desktop

 

Target pathway

When you right click a desktop icon is this what it says ( "Target Pathway" ) .......... where C:\Program Files .........exe is ?

 

What did you use to return to out of the box state ?

If it was a disk what exactly is written on it ?

 

Have you always had Vista on this machine ?

[ozwanderer]

Sorry my "reply with quote" doesn't seem to work ...

 

The install was complete. Windows Update was set to automatic before I realised and took control. Besides I have a wife who uses the computer more than I do and she needed to get back to it quickly.

 

The Quick Launch icons do behave differently from Desktop icons. Strange.

 

Yes, the Properties window does seem to be giving the correct info re. the Target.

 

The machine came with Vista and Toshiba Utils on a hidden partition. First install was done from there after purchase, and my current reinstall comes from there too.

 

BTW have you removed your post about Malwarebytes? I ran it and it removed 3 minor cases from my Download folder (uninstalled setup files) The initial problem remains.

Jim

[KenB]

BTW have you removed your post about Malwarebytes?

Yes I did - sorry - I hoped you had not read it.

It is OK to have run it - a log would help ....just to be sure.

It is located in "Logs" if you open MBAM

 

Start > type in .....cmd ......right click on cmd.exe that will appear top left of screen > Click on Run as Administrator

At the prompt type ...

sfc /scannow

[there is a space after sfc]

 

This will scan the system files and correct any errors.

 

Let me know the results.

[ozwanderer]

First the MBAM log:

Malwarebytes Anti-Malware 1.70.0.1100

www.malwarebytes.org

Database version: v2013.01.31.09

Windows Vista Service Pack 2 x86 NTFS

Internet Explorer 9.0.8112.16421

 

1/02/2013 6:27:10 AM

mbam-log-2013-02-01 (06-27-10).txt

Scan type: Full scan (C:\|)

Scan options enabled: Memory | Startup | Registry | File System | Heuristics/Extra | Heuristics/Shuriken | PUP | PUM

Scan options disabled: P2P

Objects scanned: 374275

Time elapsed: 1 hour(s), 26 minute(s), 37 second(s)

Memory Processes Detected: 0

(No malicious items detected)

Memory Modules Detected: 0

(No malicious items detected)

Registry Keys Detected: 0

(No malicious items detected)

Registry Values Detected: 0

(No malicious items detected)

Registry Data Items Detected: 0

(No malicious items detected)

Folders Detected: 0

(No malicious items detected)

Files Detected: 3

C:\Our downloads\util RegKill2702.exe (Adware.CommonName) -> Quarantined and deleted successfully.

C:\Our downloads\setup (1).exe (PUP.Offerware) -> Quarantined and deleted successfully.

C:\Our downloads\setup.exe (PUP.Offerware) -> Quarantined and deleted successfully.

(end)

[ozwanderer]

Well, I've done the System File Scan - it did find corrupt files and successfully repaired them, and supplied an enormous log file. But on reboot the problem is still there.

[Armageddon]

** Ozwanderer you could try resetting the .exe .bat file associations a small program called Rkill will do this for you , download and save to your desktop you must rename the file double click it let it run when finished close it then try your desktop programs don't reboot if this works then it's likely malware is the culprit and the security guys will help further.

[ozwanderer]

Don't reboot............

There's no way to test if it has worked other than rebooting, as it only happens at bootup. To get and run Rkill I would have to use Task Manager to get round the problem and then it is solved anyway. Do you mean run Malware bytes immediately after the Rkill fix??

[ozwanderer]

The plot thickens...... Now I've worked out that it isn't Task Manager that is enabling desktop to work normally - it is just pressing Ctrl Alt Del that does it. If I cancel the screen that comes up, normal service is resumed! Still don't know why though.

[KenB]

Hi,

 

I will ask one of our security experts to take a look at this thread to see if they can assist.

[etavares]

Hi ozwanderer,

 

That's a bit odd that SFC found so many things wrong after a reinstall. Did you have this issue before reinstalling and it continued after you reinstalled? Any other odd behavior? Let's take a look to see if anything is different in running processes before and after pressing Ctrl-Alt-Delete or launching taskmanager.

 

Download PsTools

Extract PsList to C:\

Reboot so that it resets the issue.

Click Start -> type cmd.exe

Type cd \ and press Enter

Type the command PsList >c:\before.txt exactly as shown and press Enter

Do your trick to get Windows to respond.

Click Start -> type cmd.exe

Type the command PsList >c:\after.txt exactly as shown and press Enter

Please attach both C:\before.txt and c:\after.txt in your reply.

 

 

Other questions:

• Does this happen in Safe Mode?
  
• Is anything else wrong with the computer?
  

 

-etavares

[ozwanderer]

Well .... Thanks for the help Ken and etavates, but now I don't have the issue anymore! The last 3 boots have been clean. The only thing I can think of is - prior to these clean boots I was playing with user accounts. I just have the one admin account so boot straight to the desktop. Just to see what happens I turned on the guest account, logged off mine and onto guest. Then I logged off, logged back into my account and turned off the guest account. Since then (I'm fairly certain) there has been no problem. Any ideas??

 

BTW etavares, It did happen in Safe Mode, there is nothing else wrong (hence my reluctance to rebuild again) and it was not an issue before the recent rebuild. If it does come back I'll give the PsList procedure a go.

[KenB]

now I don't have the issue anymore!

That is good to hear.

 

As to why your Admin account suddenly corrected itself after you used the Guest account ............... ???

Usually if the Admin account is corrupt it has to be re-created.

 

At least your machine is behaving itself now :)

[ozwanderer]

Thanks for your patient help.

[KenB]

Thanks for your patient help.

 

You are welcome :)

[etavares]

Glad to hear it's resolved. Thanks for letting us know!