EVENT ERROR 7026

Avatar

Please consider registering
Guest

Search

— Forum Scope —






— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

Register Lost password?
sp_Feed sp_topic_old
EVENT ERROR 7026
Avatar
dsweiner
S.E. Florida
Member
Forum Posts: 109
Member Since:
March 13, 2010
sp_UserOfflineSmall Offline
1
October 24, 2011 - 3:19 pm
sp_Permalink sp_Print

I've noticed recently that this error code is showing up each time I boot the system. Has anyone any idea on how to remedy the problem.

Thanks,

David

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7026
Date: 10/24/2011
Time: 2:06:58 PM
User: N/A
Computer: DAVID
Description:
The following boot-start or system-start driver(s) failed to load:
SASDIFSV
SASKUTIL

For more information, see Help and Support Center at http://go.microsoft.com/fwlink.....events.asp.

Avatar
Jim Hillier
Admin
Forum Posts: 2492
Member Since:
August 9, 2011
sp_UserOfflineSmall Offline
2
October 24, 2011 - 11:22 pm
sp_Permalink sp_Print

Hey David - Both those processes (SASDIFSV and SASKUTIL) are associated with SuperAntiSpyware. What is the current status of the SuperAntiSpyware software on your PC - is it still installed and you are still using it or have you uninstalled it at some time and no longer use it at all??

Cheers...Jim

Avatar
dsweiner
S.E. Florida
Member
Forum Posts: 109
Member Since:
March 13, 2010
sp_UserOfflineSmall Offline
3
October 25, 2011 - 12:06 pm
sp_Permalink sp_Print

Hi Dave:
Thanks for the reply.

That program is no longer installed. What do I do now?

Thank you,

David

Avatar
Jim Hillier
Admin
Forum Posts: 2492
Member Since:
August 9, 2011
sp_UserOfflineSmall Offline
4
October 25, 2011 - 3:14 pm
sp_Permalink sp_Print

Hi David - It's Jim mate!!.

[quote:3riioa35]That program is no longer installed[/quote:3riioa35]
As I suspected. I'm pretty certain the error is being caused by remnants leftover from the uninstall. How confident are you about working with the registry David? You will need to locate and delete a couple of registry keys:

Open a 'Run' dialogue box and type in [b:3riioa35]regedit[/b:3riioa35] and then click [b:3riioa35]OK[/b:3riioa35] (or press the 'Enter' key).
In the registry editor; Click on "View" in the menu and select "Find" ( or press Ctrl + F)
In the search dialogue box, type in "SASDIFSV" (without the quotes) and then click on the "Find next" button.
This should bring up an entry called "LEGACY_SASDIFSV" (in the side panel of the registry editor). Right click on that entry and select "Delete".
Go through exactly the same routine for "SASKUTIL".
[b:3riioa35]**NOTE: You may actually see the "LEGACY_SASKUTIL" entry directly under the "SASDIFSV" entry.[/b:3riioa35]

Working with the registry can be risky so please use caution. If you are uncertain about anything, let me know and I will clarify.

Pretty sure getting rid of those left over registry entries will fix the problem.

Cheers mate...Jim

Avatar
dsweiner
S.E. Florida
Member
Forum Posts: 109
Member Since:
March 13, 2010
sp_UserOfflineSmall Offline
5
October 25, 2011 - 3:55 pm
sp_Permalink sp_Print

Hi David - It's Jim mate!!.

That program is no longer installed[/quote:1xswt42a]
As I suspected. I'm pretty certain the error is being caused by remnants leftover from the uninstall. How confident are you about working with the registry David? You will need to locate and delete a couple of registry keys:

Open a 'Run' dialogue box and type in [b:1xswt42a]regedit[/b:1xswt42a] and then click [b:1xswt42a]OK[/b:1xswt42a] (or press the 'Enter' key).
In the registry editor; Click on "View" in the menu and select "Find" ( or press Ctrl + F)
In the search dialogue box, type in "SASDIFSV" (without the quotes) and then click on the "Find next" button.
This should bring up an entry called "LEGACY_SASDIFSV" (in the side panel of the registry editor). Right click on that entry and select "Delete".
Go through exactly the same routine for "SASKUTIL".
[b:1xswt42a]**NOTE: You may actually see the "LEGACY_SASKUTIL" entry directly under the "SASDIFSV" entry.[/b:1xswt42a]

Working with the registry can be risky so please use caution. If you are uncertain about anything, let me know and I will clarify.

Pretty sure getting rid of those left over registry entries will fix the problem.

Cheers mate...Jim[/quote:1xswt42a]

Hi Mate:
You're not going to believe this but they are both gone.

Thanks for your help. Hope all is well with you and the family.

Cheers,

David

Avatar
Jim Hillier
Admin
Forum Posts: 2492
Member Since:
August 9, 2011
sp_UserOfflineSmall Offline
6
October 25, 2011 - 4:24 pm
sp_Permalink sp_Print

All fine this end thanks mate.

So that problem is now fixed then David?

Avatar
dsweiner
S.E. Florida
Member
Forum Posts: 109
Member Since:
March 13, 2010
sp_UserOfflineSmall Offline
7
October 26, 2011 - 11:43 am
sp_Permalink sp_Print

All fine this end thanks mate.

So that problem is now fixed then David?[/quote:2onen5h3]

Hi Mate:
That's good to hear.

Yes, for some reason there is not a trace.

Cheers,

David

Forum Timezone: America/Indiana/Indianapolis

Most Users Ever Online: 188

Currently Online:
14 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Member Stats:

Guest Posters: 10

Members: 1273

Moderators: 3

Admins: 4

Forum Stats:

Groups: 8

Forums: 19

Topics: 1538

Posts: 11824

Administrators: Jim Hillier, Richard Pedersen, David Hartsock, Marc Thomas

Moderators: Judy Novotny, Jason Shuffield, Mail Poet