Error 7026

[bronan]

After each reboot I have this error in Event Viewer:
-Product: Windows OS
-ID: 7026
-Source: Service Control Manager
-Version: 5.2
-Symbolic Name: EVENT_BOOT_SYSTEM_DRIVERS_FAILED

Message: The following boot-start or system-start driver(s) failed to load.
-------
Please let me know what caused this error and what can I do to fix it.

 

[BadBigBen]

You have not listed the driver or the cause, without it, it will become difficult to figure out what is the cause!

see:

Event ID 7026 Source Service Control Manager

http://www.eventid.net/display.asp?eventid=7026&eventno=452&source=Service Control Manager&phase=1

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[bronan]

Sorry , I omit this:
The following boot-start or system-start driver(s) failed to load:
SSI

 

[BadBigBen]

Sounds like an "Server-Side Include" problem if you have IIS installed that is, so try installing it new (reinstalling) or updating it...

Run a plethora of antimalware, antispyware, antiviral scans... e.g. MalwareBytes AntiMalware AND SuperAntiSpyware, your installed AV solution and back that up with an Online scan... Just to be on the safe side...

you could also DL HiJackThis from the TrendMicro website, and post a log, for our perusal, that way you could be sure that all is well...

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[bronan]

SSI driver is situated in Device Manager under Non-Plug and Play Drivers.
Is marked with yellow sign and after double click appear window with this message:
This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)

Click Troubleshoot to start the troubleshooter for this device.

Other details for driver are:
Service name: SSI
Display name: SSI

Status: Stopped
Type: Boot

If try to "Start" the driver ,receiving this:
The system encountered the following error while attempting to start the service
The system cannot find the file specified.

SSI driver details:
Device Instance ld
ROOT\LEGACY_SSI\0000
--------
Seems that SSI driver is missing.

 

[linney]

If you don't need or use this driver maybe it is something remaining from a previous install/uninstall.

If we are looking for drivers that load at Startup or Bootup these can be disabled via the Recovery Console and the Listsvc command followed by the Disable command.

How to install and use the Recovery Console in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;307654&FR=1&PA=1&SD=HSCH

If you know the names of the loading drivers you can probably remove them from the Registry instead of the Recovery Console.

Removing the startup driver is one way to stop the error in the Event Viewer.

Is your problem, a new problem, or left overs from this thread?

How to uninstall Phantom programs from OS
thread779-1560987

 

[bronan]

All information abt the SSI driver what I have are in above post.
I disabled the driver in Device Manager and error in Event Viewer disappear.
Now in Device Manager near to SSI driver is small red cross sign.
Probably by mistake thinking this driver belongs to Webroot SpySweeper I've uninstalled some years ago , I delete it recently .
I am completely confused now as I am not sure for what this driver serves.
I can uninstall it , but my problem is I don't have necessary data to find and reinstall SSI driver.
This driver as a type is Boot, so I am afraid that some of vital PC functions are damaged or jeopardized

 

[BadBigBen]

As I mentioned it is part of the IIS that comes with XP...

now that we know it is in the Device Manager, we can tell you how to get rid of it completely...

1. uninstall it from the Device Manager...

2. Open regedit (START >> RUN >> regedit >> return), then navigate to the following KEY:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services

there look for the SUBKEY called SSI... click on it...

now, either change the parameters (significant ones listed below with their respective values and what these do) in the right pane, or right-click on it (SSI) and DELETE the KEY...

Parameter: ErrorControl
Type: REG_DWORD
Values: 0 - Ignore: If the driver fails to load or initialize, startup proceeds, and no warning message appears.
1 - Normal: If the driver fails to load or initialize, startup proceeds, but a warning message appears.
2 - Severe: If the driver fails to load or initialize, declares the startup as having failed and restarts by using the LastKnownGood control set. If startup is already using the LastKnownGood control set, continues startup.
3 - Critical: If the driver fails to load or initialize, declares the startup as having failed and restarts by by using the LastKnownGood control set. If startup is already using the LastKnownGood control set, stops startup and runs a debugging program.

Parameter: Start
Type: REG_DWORD
Values:
0 Boot: Loaded by kernel loader. Components of the driver stack for the boot (startup) volume must be loaded by the kernel loader.
1 System: Loaded by I/O subsystem. Specifies that the driver is loaded at kernel initialization.
2 Automatic: Loaded by Service Control Manager. Specifies that the service is loaded or started automatically.
3 Manual:. The service does not start until the user starts it manually, such as by using Services or Devices in Control Panel.
4 Disabled: Specifies that the service should not be started.


Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[bronan]

@BadBigBen,
Thank you very much for your advice.
I would prefer to reinstall SSI driver because probably by mistake I delete it thinking that is a part of Webroot SpySweeper .
I repeat I've been afraid to damage some important device or something else if I delete this driver and Registry string.
Any chance to get SSI and reinstall it, or this is impossible.

 

[linney]

If you go in to Add or remove and from there into Add or Remove Windows Components, you can uninstall or reinstall IIS and perhaps hopefully any driver associated with it.

 

[BadBigBen]

Bronan - try that what Linney suggested, or you may update to a newer version, go to the MS Update website and enter IIS as search criteria...



Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[bronan]

Are you 100% sure that SSI driver is a part of IIS ( Internet Information Service) and not a part of Webroot SpySweeper v. 4.5.5.607.
Going to Add or Remove Windows Components, found IIS not checked with size of 13,5 MB.
Clicking on Details found some of items checked and other ones -no.
How can check whether this SSI is a part of Webroot, or something else as IIS for example.
If is part of Webroot, then the best solution is what BadBigBen suggested - uninstall it and make Registry cleaning of SSI residues.

 

[bronan]

In addition of my above post- looking in the Registry have seen name of the driver file is system32\Drivers\SSI.SYS.This one is missing from my system32\Drivers folder.
Can you please copy this file from your XP SP3 machine and send it to me.
I believe this will solve this problem 100%.

 

[BadBigBen]

Now the picture is clearing up... ;-)

with that added info, I was able to find what it is, with just SSI, which is part of the IIS installation and other web page apps (Apache), it was my understanding that it was part of that...

now with the full driver/server name it cleared up the misconception and YES it is part of Webroot SpySweeper, so time to go ahead and follow the instructions on the REGISTRY cleaning...

PS: you may have to take ownership of the said key, by right clicking it and then checking permissions...


Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[bronan]

@BadBigBen ,

Thanks a lot m'8, you save me time and headache confirming that his driver is a part of Webroot.
Now I will uninstall SSI driver from Divace Manager and then let me know please, what is best solution to do in the Registry- Delete completely SSI in the left pane or make changes you mention in your earlier post , i.e. change the parameters on right pane .

 

[BadBigBen]

what is best solution to do in the Registry- Delete completely SSI in the left pane or make changes you mention in your earlier post , i.e. change the parameters on right pane .

Left pane delete, since it is not installed anymore you might as well delete it completely...

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[bronan]

Thanks ,O.K. for this one-sorted.
Would like to ask you one more Q.
From a long time am receiving in Event Viewer this error :



Details
Product: Windows Operating System
ID: 4311
Source: NetBT
Version: 5.2
Symbolic Name: EVENT_NBT_CREATE_DEVICE
Message: Initialization failed because the driver device could not be created


Contacted MS Tech and Support stuff , but they did not succeed to help - result was " ignore it"
Try what you wrote and change in Error Control REG DWORD to "0" for NetBT to stop showing error in Event Viewer , but after rebot, in System found same error warning.
This is very anoing and I kindly ask you if there is anything I can do in Registry to stop this Error message to appear again.
Sorry to be invasive , but I feel free to ask you

 

[BadBigBen]

Try what you wrote and change in Error Control REG DWORD to "0" for NetBT to stop showing error in Event Viewer , but after reboot, in System found same error warning.

of course not, since the driver is present, and it does not fail to load/initialize it will still warn you...

at which SP are you at? since that error appeared in SP1 and previous versions, if you deleted the drivers (Device Manager) for your NIC and had XP reinstall them...

so you might want to try:

1. update the NIC drivers and see if it cures the problem...

2. in the properties of you NIC uncheck IPv6 and reboot...

3. CMD window (DOS box) type: netsh int ip reset
And reboot.

4. also in the properties of your NIC, uninstall TCP/IP, then reboot, and re install TCP/IP...

also have a read:

Event ID 4311 appears in the system log when you reinstall a network adapter in Windows XP

http://support.microsoft.com/kb/833747

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[bronan]

Hi Ben,
I am at SP3 now.
This error is very old - from 2005, in the time I was at SP 2.
Try all hints you suggest and much more- even received a tool from MS to cure this error 4311 , but this one was created for SP 2 , so was useless in my case.
My hope was to find the way if possible, to avoid this error message to appear each time I reboot- that's all, not to fix the error itself because seems this "enigma" is to big even for MS.

 

[linney]

Some very old articles but they may be worth checking.

Event ID 4119 and 4311 After Removal of Remote Access Service

http://support.microsoft.com/kb/q181548/

Event IDs 4307 and 4311 Occur After Disabling WINS Bindings

http://support.microsoft.com/kb/123981

Event ID 4311 Source NetBT

http://www.eventid.net/display.asp?eventid=4311&eventno=910&source=NetBT&phase=1

Are you still seeing any errors in the Device Manager?