Modifying Control Set

  • Thread starter Thread starter Howard Kaikow
  • Start date Start date
H

Howard Kaikow

When I wish to modify the control set, which of the following should I do?

1. Modify only CurrentControlSet.
2. Modify Contrlset001 and ControlSet002.
3. Modify all 3 control sets.
4. Alternatives?

I want do this because, recently, I noticed there are WDM drivers running
that were part of software
that has been uninstalled.

For example, on one system, although I uninstalled the Nero/InCD software
and installed Roxio's EMC 7 software, the nerocd2k driver is installed and
running, tho perhaps never used.

On another system, I had long ago uninstalled Roxio's EZCD Creator software,
and installed Nero/InCD, but the EZCD 5 driver is still installed and
running.

Having such drivers running is at best a performance hit, at worst, there
could be a conflict at some point.

What's the best way to assure that the only WDM drivers installed are from
currently installed products?
 
1.

Looking in;
HKEY_LOCAL_MACHINE\SYSTEM\Select
you'll find the D-Word values for
"Current"=dword:00000001
"Default"=dword:00000001
"Failed"=dword:00000000
"LastKnownGood"=dword:00000002

CurrentControlSet is volatile and will always be an image (at boot) of
what's defined in ControlSetx where x = the value of "Current"

Choosing last known good boots the system with the control set that last
successfully booted your system. Control sets contain system configuration
information such as device drivers and services.

To display hidden devices, non-Plug and Play devices, and devices not
attached to the computer (commonly known as "ghosted" or "phantom" devices)
From a command prompt;

set DEVMGR_SHOW_NONPRESENT_DEVICES=1
then
start devmgmt.msc

Then, use Device Manager to remove or reconfigure these devices. Do not edit
the registry.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


:
| When I wish to modify the control set, which of the following should I do?
|
| 1. Modify only CurrentControlSet.
| 2. Modify Contrlset001 and ControlSet002.
| 3. Modify all 3 control sets.
| 4. Alternatives?
|
| I want do this because, recently, I noticed there are WDM drivers running
| that were part of software
| that has been uninstalled.
|
| For example, on one system, although I uninstalled the Nero/InCD software
| and installed Roxio's EMC 7 software, the nerocd2k driver is installed and
| running, tho perhaps never used.
|
| On another system, I had long ago uninstalled Roxio's EZCD Creator
software,
| and installed Nero/InCD, but the EZCD 5 driver is still installed and
| running.
|
| Having such drivers running is at best a performance hit, at worst, there
| could be a conflict at some point.
|
| What's the best way to assure that the only WDM drivers installed are from
| currently installed products?
|
|
| --
| http://www.standards.com/; See Howard Kaikow's web site.
|
|
 
1.

Looking in;
HKEY_LOCAL_MACHINE\SYSTEM\Select
you'll find the D-Word values for
"Current"=dword:00000001
"Default"=dword:00000001
"Failed"=dword:00000000
"LastKnownGood"=dword:00000002

CurrentControlSet is volatile and will always be an image (at boot) of
what's defined in ControlSetx where x = the value of "Current"

Choosing last known good boots the system with the control set that last
successfully booted your system. Control sets contain system configuration
information such as device drivers and services.

To display hidden devices, non-Plug and Play devices, and devices not
attached to the computer (commonly known as "ghosted" or "phantom" devices)
From a command prompt;

set DEVMGR_SHOW_NONPRESENT_DEVICES=1
then
start devmgmt.msc

Then, use Device Manager to remove or reconfigure these devices. Do not edit
the registry.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


:
| When I wish to modify the control set, which of the following should I do?
|
| 1. Modify only CurrentControlSet.
| 2. Modify Contrlset001 and ControlSet002.
| 3. Modify all 3 control sets.
| 4. Alternatives?
|
| I want do this because, recently, I noticed there are WDM drivers running
| that were part of software
| that has been uninstalled.
|
| For example, on one system, although I uninstalled the Nero/InCD software
| and installed Roxio's EMC 7 software, the nerocd2k driver is installed and
| running, tho perhaps never used.
|
| On another system, I had long ago uninstalled Roxio's EZCD Creator
software,
| and installed Nero/InCD, but the EZCD 5 driver is still installed and
| running.
|
| Having such drivers running is at best a performance hit, at worst, there
| could be a conflict at some point.
|
| What's the best way to assure that the only WDM drivers installed are from
| currently installed products?
|
|
| --
| http://www.standards.com/; See Howard Kaikow's web site.
|
|
 
In said:
When I wish to modify the control set, which of the following
should I do?

1. Modify only CurrentControlSet.
2. Modify Contrlset001 and ControlSet002.
3. Modify all 3 control sets.
4. Alternatives?

I want do this because, recently, I noticed there are WDM drivers
running that were part of software
that has been uninstalled.

For example, on one system, although I uninstalled the Nero/InCD
software and installed Roxio's EMC 7 software, the nerocd2k driver
is installed and running, tho perhaps never used.

On another system, I had long ago uninstalled Roxio's EZCD Creator
software, and installed Nero/InCD, but the EZCD 5 driver is still
installed and running.

Having such drivers running is at best a performance hit, at
worst, there could be a conflict at some point.

What's the best way to assure that the only WDM drivers installed
are from currently installed products?

Side note. It is often helpful to disable all services and startup
portions of an application and reboot prior to commencing with the
un-installation. A bit "cleaner" un-installs in many cases.

In most all cases what needs to be done can in fact be done through
Service manager or Device Manager without manual registry editing.
If a few cases the vendor will supply specific instruction (or on MS
KB article specific instruction) for manual editing. Avoid such
unless really needed. And always a full registry backup first.
 
In said:
When I wish to modify the control set, which of the following
should I do?

1. Modify only CurrentControlSet.
2. Modify Contrlset001 and ControlSet002.
3. Modify all 3 control sets.
4. Alternatives?

I want do this because, recently, I noticed there are WDM drivers
running that were part of software
that has been uninstalled.

For example, on one system, although I uninstalled the Nero/InCD
software and installed Roxio's EMC 7 software, the nerocd2k driver
is installed and running, tho perhaps never used.

On another system, I had long ago uninstalled Roxio's EZCD Creator
software, and installed Nero/InCD, but the EZCD 5 driver is still
installed and running.

Having such drivers running is at best a performance hit, at
worst, there could be a conflict at some point.

What's the best way to assure that the only WDM drivers installed
are from currently installed products?

Side note. It is often helpful to disable all services and startup
portions of an application and reboot prior to commencing with the
un-installation. A bit "cleaner" un-installs in many cases.

In most all cases what needs to be done can in fact be done through
Service manager or Device Manager without manual registry editing.
If a few cases the vendor will supply specific instruction (or on MS
KB article specific instruction) for manual editing. Avoid such
unless really needed. And always a full registry backup first.
 
I want only to remove CD-related drivers from non-installed products.
Shouldn't I be able to do that by eliminating the drives from the control
sets?
 
I want only to remove CD-related drivers from non-installed products.
Shouldn't I be able to do that by eliminating the drives from the control
sets?
 
I want to disable the particular driver(s) then delete the files and reboot.
The products were uninstalled but the damn vendor did not uninstall their
precious driver(s).
 
I want to disable the particular driver(s) then delete the files and reboot.
The products were uninstalled but the damn vendor did not uninstall their
precious driver(s).
 
In said:
I want to disable the particular driver(s) then delete the files
and reboot. The products were uninstalled but the damn vendor did
not uninstall their precious driver(s).

If that is how you want or need to do it, then in the most minimal
and practcal terms you need only work with the CurrentControlSet
branch and just ignore those other ControlSets. Full registry
backups are mandatory IMO and you should probably review in advance
the manual recovery procedures against the possibility you might need
them.

If the vendor has provided specific instructions and you are having
difficulty following them, then specific tips and techniques might be
recommended here. I am sure that many responders are reluctant to
advise (without being right there) due to the potential risks and the
rather general nature of your request. This group often deals with
the actual accomplishment of completing the steps in a (by number) MS
Knowledge Base article for example.

I am sure your problem has been "seen" before, but the case-by-case
specifics are important and the general level of the requester's
knowledge and experience are factors to be consided as well.

In general, driver entries are seen within the ...\CCS\Services\
branch and contain a valueaname "Start" which specifies the "start
type" The Start Type values (the data) indicate how/when the driver
is actually started by the system. These are DWORD (REG_DWORD)
values. The Start Types (in decimal) are:

0 Service_boot_start Loaded by NTLDR prior
to Service_system_start drivers
1 Service_system_start Loads after Service_system_start
drivers
2 Service_auto_start Loaded by the SCM

3 Service_demand_start Loaded by the SCM on demand

4 Service_disabled Disabled

Disabling a driver will in effect keep it from starting (loading) at
all and get it "out of your way" Disabling the wrong driver may
prevent the OS from booting. Just leaving it there, but disabled, is
sufficient in practical terms.
 
In said:
I want to disable the particular driver(s) then delete the files
and reboot. The products were uninstalled but the damn vendor did
not uninstall their precious driver(s).

If that is how you want or need to do it, then in the most minimal
and practcal terms you need only work with the CurrentControlSet
branch and just ignore those other ControlSets. Full registry
backups are mandatory IMO and you should probably review in advance
the manual recovery procedures against the possibility you might need
them.

If the vendor has provided specific instructions and you are having
difficulty following them, then specific tips and techniques might be
recommended here. I am sure that many responders are reluctant to
advise (without being right there) due to the potential risks and the
rather general nature of your request. This group often deals with
the actual accomplishment of completing the steps in a (by number) MS
Knowledge Base article for example.

I am sure your problem has been "seen" before, but the case-by-case
specifics are important and the general level of the requester's
knowledge and experience are factors to be consided as well.

In general, driver entries are seen within the ...\CCS\Services\
branch and contain a valueaname "Start" which specifies the "start
type" The Start Type values (the data) indicate how/when the driver
is actually started by the system. These are DWORD (REG_DWORD)
values. The Start Types (in decimal) are:

0 Service_boot_start Loaded by NTLDR prior
to Service_system_start drivers
1 Service_system_start Loads after Service_system_start
drivers
2 Service_auto_start Loaded by the SCM

3 Service_demand_start Loaded by the SCM on demand

4 Service_disabled Disabled

Disabling a driver will in effect keep it from starting (loading) at
all and get it "out of your way" Disabling the wrong driver may
prevent the OS from booting. Just leaving it there, but disabled, is
sufficient in practical terms.
 
I would give Device Manager a go before editing the registry. The latter may
become unrecoverable.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


:
|I want only to remove CD-related drivers from non-installed products.
| Shouldn't I be able to do that by eliminating the drives from the control
| sets?
 
I would give Device Manager a go before editing the registry. The latter may
become unrecoverable.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


:
|I want only to remove CD-related drivers from non-installed products.
| Shouldn't I be able to do that by eliminating the drives from the control
| sets?
 
Lemmee clarify.

I have been referring ONLY to drivers used by CD-recording software.

The spurious drivers are left behind by uninstalls of various CD-recording
products.
The base device drivers are not involved.
 
Lemmee clarify.

I have been referring ONLY to drivers used by CD-recording software.

The spurious drivers are left behind by uninstalls of various CD-recording
products.
The base device drivers are not involved.
 
So is the solution then to disable the drivers in CSS/Services, or do I also
have to remove the driver from the CurrentControlSet?

The drivers to which I am referring are NOT used by any software, they are
debris left around from the uninstall of particular CD-recording products.

My safety valve is these are on multiboot system.

Main sys is on J.
So I can make sure I have up to date backup running from J.
Boot to other sys, which is on C.
Make the desired changes.

If rebooting to C then fails, or if drives are not accessible when booted to
C, then I would reboot to J and restore C.
Ditto for systems on F and G.

For the system on J, my failsafe is rebooting from a Retrospect DR CD and
then restoring J.
 
So is the solution then to disable the drivers in CSS/Services, or do I also
have to remove the driver from the CurrentControlSet?

The drivers to which I am referring are NOT used by any software, they are
debris left around from the uninstall of particular CD-recording products.

My safety valve is these are on multiboot system.

Main sys is on J.
So I can make sure I have up to date backup running from J.
Boot to other sys, which is on C.
Make the desired changes.

If rebooting to C then fails, or if drives are not accessible when booted to
C, then I would reboot to J and restore C.
Ditto for systems on F and G.

For the system on J, my failsafe is rebooting from a Retrospect DR CD and
then restoring J.
 
You didn't mention if you tried my suggestion or not. You may want to get in
touch with the application developer on this as well.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


:
| Device Manager does not list the drivers for CD recording software.
 
Back
Top