So far disabling the few start up items has had no effect. With the ZA ones it seems that (see att) only one in the list may be disabled at a time. Also I see in the list ( again see att) that some other items seem to be duplicated too. I am sole user with Admin rights can those dups be right?
They are probably not duplicates, they are probably 3 different things from ZoneAlarm (which you should uninstall) and 3 different things from Intel. You need to expand the column for the command to tell what is actually being started. One seems to start with Cmd.exe - you minght want to uncheck that one.
Whoever worked on your pc enabled the boot time diagnostics screen, if you go into your bios you can disable it. You should then see the manufacturer`s logo again.
There`s no reason to tinker with msconfig, it has nothing to do with what you`re seeing.
@UsernameIssues
It was the cmd exe item that I hadn't disabled, it being an MSoft item. Another incidental matter is that the boot tab reveals as in attachment one current and three old versions. Despite being deleted under advanced options the old ones come back on restarts
Highlight each listing shown above besides C and delete it there in the Boot tab.
You don't need the Intel Startup items unless you're overclocking or using other specialized settings found only the intel panels.
I would not use ZoneAlarm as we see nothing but problems with it here.
Uninstall ZoneAlarm and install Microsoft Security Essentials or Avast free with the Windows 7 firewall which is perfected in Win7.
Got rid of Intel lines.
I installed ZA Av and Fw as Avast was apparently mucking things up,but that was when I was having lots of BSODs leading to clean install and new graphics card, and ZA Fw seemed to be the easiest to use and not intrusive like others. How does ZA cause problems as you have stated?
I have only seen it mentioned here causing problems, nothing else. The Windows firewall is perfected in Win7 so it seems unnecessary to replace it.
But if it works for you and you paid for it then keep it. Let us know how it goes.
Just curious, what was the cmd prompt entry [was] doing?
If you still have the entry in msconfig, maybe you could expand the command column and see what else is on that line.
Last edited by UsernameIssues; 18 Apr 2013 at 13:57. Reason: typo
Quote
Free version, too mean for bought!