my device manager is empty?

Tip: Run a free scan for common Windows errors ad

Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Thursday, December 8, 2005 at 6:23 pm Posted by jcw (5100 messages posted) The following has been distilled from various sources, notably messages posted in a lengthy thread in this forum spanning well over two years at: »   http://www.annoyances.org/exec/forum/winxp/1051715405 Credit is to be given to those who provided these solutions, and those who endured the trial and error in remedying a blank or empty Device Manager and took the time to post their results. Readers are encouraged to "book-mark" this web-page for future reference for users experiencing a blank or empty Device Manager in Windows XP. Begin with the first potential solution below, and proceed with each subsequent solution, after each opening Device Manager to see if it properly displays devices.  Some solutions may not apply to your situation, e.g. the first and second solutions that apply if you are getting the error messages there described. To undertake these procedures, be logged-in with full administrative powers. 1)  If Device Manager is blank and there is an error message that the Device Manager Snap-in failed to initialize, re-register the devmgr.dll file as follows: •  Close all open programs. •  Start --> Run, and type:   REGSVR32 DEVMGR.DLL   and hit Enter or OK. •  You should get this message:  "DllRegisterServer in devmgr.dll succeeded."  Click OK. 2)  If Device Manager is blank and there is an "Action Cancelled" message stating: "Internet Explorer was unable to link to the Web page you requested. The page might be temporarily unavailable.",  re-register the dmocx.dll file as follows: •  Close all open programs. •  Start --> Run, and type:   REGSVR32 DMOCX.DLL   and hit Enter or OK. •  You should get this message:  "DllRegisterServer in dmocx.dll succeeded."  Click OK. 3)  A totally blank Device Manager (not showing even the computer icon and name) can occur if the Plug and Play service is not started.  Open the Services window and check the Status and Startup Type of that service.  To open the Services window: Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. If that service is not started or if its Startup Type is not set to automatic, follow the instructions in MS KB Art. 311504. 4) Review the Status and Startup Type of all of the Windows services in the Services window.  You may find that many of the services that should be started, are not.  If so, start those services and set their Startup Type to automatic or manual as appropriate.  To open the Services window: Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. If you find a service that should be started, but is not: •  Double-click on the service to be started. •  On the General tab, in the Startup Type drop-down list, click on either Automatic or Manual as appropriate (if in doubt, click on Automatic). •  Click on the Start button. •  Click OK. When finished, close the Services window.  You may need to restart the computer to effect the changes you have made to the services.  Once it appears that the computer is operating properly, you may want to review the Windows services to see if there are any that do not need to be started or whose Startup Type can be set to Manual or Disabled without adversely affecting the computer's operation. 5)  In Control Panel --> Add/Remove Programs, check if Microsoft Windows Update 905749 is installed, and if so, uninstall it.  (That Security Update was released 10-11-05 to resolve a vulnerability in Plug and Play for Windows XP and 2000.)   Restart the computer. 6)  If Device Manager shows the computer icon and name but no devices, check that the security permissions for this registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum meet these requirements: •  the group "Everyone" should be listed and have only "Read" permissions. •  the user "SYSTEM" should be listed and have "Full Control" and "Read" permissions. To do this, open the registry editor (Start --> Run, type:  REGEDIT   and hit Enter or OK). Go to the above registry key, and right-click on the Enum key, and in the context menu click on Permissions. On the Security tab, review the listed group or user names and the permissions checked for each in the "Allow" column to determine if they comply with the above requirements.  If not, use the following instructions, or such of them as needed, to have the listed names and their permissions meet those requirements. To add those names to the Security tab: •  Click on the Add button. •  Add the group "Everyone" and the user "SYSTEM." To set the required permissions for those names on the Security tab: •  Select "Everyone" and check "Read" (only) under "Allow." •  Select "SYSTEM" and check "Full Control" under "Allow" (which also should check "Read"). •  Make sure there is nothing checked under "Deny" for either "SYSTEM" or "Everyone." Then: •  Click on the Advanced button, and on the Permissions tab in the Advanced box check "Replace permission entries on all child objects with . . . ." •  Click OK, and on any warning box click "Yes". When finished, close the registry editor. Note:  If at any time you get a message to the effect that the registry editor cannot set or change security permissions in the selected key or its sub-keys, go to the next step. 7)  In Control Panel --> Add/Remove Programs, check if Context Plus or Ad Channel or POP or Apropos Client, or any combination of those names, is installed.  If so, uninstall it or them.  (That item does not enjoy a good reputation.)  Then review the discussion for possible additional removal procedures (including a downloadable removal tool) at: http://www.norton.com/avcenter/venc/data/spyware.apropos.html When done, restart the computer. 8)  Apropos malware may be on the system, causing the blank or empty Device Manager.  If so: •  Download and save to the desktop AproposFix.exe at: http://swandog46.geekstogo.com/aproposfix.exe •  Reboot into safe mode (logging into the account in which you saved the downloaded file). •  Double or single click (whichever you use to open or run an item) on AproposFix.exe on the desktop, which will place on the desktop an AproposFix folder. •  Open the AproposFix folder, and double or single click on RunThis.bat  to run it. •  Follow the on-screen prompts.  When finished, reboot into normal mode. •  The AproposFix folder now will have a log.txt file showing the actions that AproposFix has taken, which should be reviewed, and saved until it is clear that the Apropos malware has been entirely removed. You then should use proper procedures to scan for and remove any remaining elements of Apropos, which is discussed at various web-sites, such as: http://securityresponse.symantec.com/avcenter/venc/data/spyware.apropos.c.html 9)  One or more sub-keys under the Enum registry key may be corrupt, causing the blank or empty Device Manager.  To check for and remedy corrupt sub-keys: •  Open the registry editor (Start --> Run, type:  REGEDIT   and hit Enter or OK)  and go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum •  Expand the Enum key, and examine each sub-key under it for a name that is a seemingly random, disorderly combination of characters and symbols, e.g.:   $%^&*()24031   (or longer), with little resemblance to the other sub-keys, and perhaps having no values in the right-hand pane.  There may be under the Enum key consecutive sub-keys with such garbled names, each one being longer than the prior one.  These corrupt sub-keys should be deleted. Note:  before deleting any registry keys or sub-keys, first back-up the entire Enum key by right-clicking on it, then click on Export, select where to save it, and click on Save.  In addition, similarly back-up each sub-key that you intend to delete. If upon trying to delete a corrupt sub-key, you get a message that the deletion cannot be accomplished for lack of permission, increase the permissions for the corrupt sub-key before deleting it, as follows: •  Right-click on the corrupt sub-key and in the context menu click on Permissions. •  On the Security tab, select "Everyone" and check "Full Control" under "Allow."  If "Everyone" is not there listed, click on the Add button and add the group "Everyone," and then select it and check "Full Control" under "Allow."   If "Everyone" cannot be added, add the group "Administrators" for whom check "Full Control" under "Allow." •  Make sure there is nothing checked under "Deny" for "Everyone" or "Administrators." •  Click on the Advanced button, and on the Permissions tab in the Advanced box check "Replace permission entries on all child objects with . . . ." •  Click OK, and on any warning box click "Yes" •  Then delete the corrupt sub-key. When finished, close the registry editor. As corruption of the registry might have been caused by a virus or malware, you should use proper procedures to scan for and remove vires and malware from the system. [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Sunday, December 18, 2005 at 3:50 pm Posted by Greg Hendren (3 messages posted) http://swandog46.geekstogo.com/aproposfix.exe website is down!!!. Cant find fix anywhere else, please help! On Thursday, December 8, 2005 at 6:23 pm, jcw wrote: > >The following has been distilled from various sources, notably messages posted in >a lengthy thread in this forum spanning well over two years at: > »   http://www.annoyances.org/exec/forum/winxp/1051715405 > Credit is to be given to those who provided these solutions, and those who endured >the trial and error in remedying a blank or empty Device Manager and took the time >to post their results. > > Readers are encouraged to "book-mark" this web-page for future reference for users >experiencing a blank or empty Device Manager in Windows XP. > > > Begin with the first potential solution below, and proceed with each subsequent >solution, after each opening Device Manager to see if it properly displays devices.  >Some solutions may not apply to your situation, e.g. the first and second solutions >that apply if you are getting the error messages there described. > To undertake these procedures, be logged-in with full administrative powers. > > 1)  If Device Manager is blank and there is an error message that the Device >Manager Snap-in failed to initialize, re-register the devmgr.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DEVMGR.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in devmgr.dll succeeded."  >Click OK. > > 2)  If Device Manager is blank and there is an "Action Cancelled" message >stating: > "Internet Explorer was unable to link to the Web page you requested. The page >might be temporarily unavailable.",  re-register the dmocx.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DMOCX.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in dmocx.dll succeeded."  >Click OK. > > 3)  A totally blank Device Manager (not showing even the computer icon and >name) can occur if the Plug and Play service is not started.  Open the Services window >and check the Status and Startup Type of that service.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If that service is not started or if its Startup Type is not set to automatic, >follow the instructions in >MS KB Art. 311504. > > 4) Review the Status and Startup Type of all of the Windows services in the >Services window.  You may find that many of the services that should be started, >are not.  If so, start those services and set their Startup Type to automatic or >manual as appropriate.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If you find a service that should be started, but is not: > •  Double-click on the service to be started. > •  On the General tab, in the Startup Type drop-down list, click on either Automatic >or Manual as appropriate (if in doubt, click on Automatic). > •  Click on the Start button. > •  Click OK. > When finished, close the Services window.  You may need to restart the computer >to effect the changes you have made to the services.  Once it appears that the computer >is operating properly, you may want to review the Windows services to see if there >are any that do not need to be started or whose Startup Type can be set to Manual >or Disabled without adversely affecting the computer's operation. > > 5)  In Control Panel --> Add/Remove Programs, check if Microsoft Windows Update >905749 is installed, and if so, uninstall it.  (That Security Update was released >10-11-05 to resolve a vulnerability in Plug and Play for Windows XP and 2000.)   >Restart the computer. > > 6)  If Device Manager shows the computer icon and name but no devices, check >that the security permissions for this registry key: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > meet these requirements: > •  the group "Everyone" should be listed and have only "Read" permissions. > •  the user "SYSTEM" should be listed and have "Full Control" and "Read" permissions. > To do this, open the registry editor (Start --> Run, type:  REGEDIT   >and hit Enter or OK). > Go to the above registry key, and right-click on the Enum key, and in the context >menu click on Permissions. > On the Security tab, review the listed group or user names and the permissions >checked for each in the "Allow" column to determine if they comply with the above >requirements.  If not, use the following instructions, or such of them as needed, >to have the listed names and their permissions meet those >requirements. > To add those names to the Security tab: > •  Click on the Add button. > •  Add the group "Everyone" and the user "SYSTEM." > To set the required permissions for those names on the Security tab: > •  Select "Everyone" and check "Read" (only) under "Allow." > •  Select "SYSTEM" and check "Full Control" under "Allow" (which also should >check "Read"). > •  Make sure there is nothing checked under "Deny" for either "SYSTEM" or "Everyone." > Then: > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes". > When finished, close the registry editor. > Note:  If at any time you get a message to the effect that the registry >editor cannot set or change security permissions in the selected key or its sub-keys, >go to the next step. > > 7)  In Control Panel --> Add/Remove Programs, check if Context Plus >or Ad Channel or POP or Apropos Client, or any combination of >those names, is installed.  If so, uninstall it or them.  (That item does not enjoy >a good reputation.)  Then review the discussion for possible additional removal >procedures (including a downloadable removal tool) at: > http://www.norton.com/avcenter/venc/data/spyware.apropos.html > When done, restart the computer. > > 8)  Apropos malware may be on the system, causing the blank or empty Device >Manager.  If so: > •  Download and save to the desktop AproposFix.exe at: > http://swandog46.geekstogo.com/aproposfix.exe > •  Reboot into safe mode (logging into the account in which you saved the downloaded >file). > •  Double or single click (whichever you use to open or run an item) on AproposFix.exe >on the desktop, which will place on the desktop an AproposFix folder. > •  Open the AproposFix folder, and double or single click on RunThis.bat  >to run it. > •  Follow the on-screen prompts.  When finished, reboot into normal mode. > •  The AproposFix folder now will have a log.txt file showing the actions >that AproposFix has taken, which should be reviewed, and saved until it is >clear that the Apropos malware has been entirely removed. > > You then should use proper procedures to scan for and remove any remaining elements >of Apropos, which is discussed at various web-sites, such as: > http://securityresponse.symantec.com/avcenter/venc/data/spyware.apropos.c.html > > 9)  One or more sub-keys under the Enum registry key may be corrupt, causing >the blank or empty Device Manager.  To check for and remedy corrupt sub-keys: > •  Open the registry editor (Start --> Run, type:  REGEDIT   and hit >Enter or OK)  and go to: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > •  Expand the Enum key, and examine each sub-key under it for a name that is >a seemingly random, disorderly combination of characters and symbols, e.g.:   $%^&*()24031 >  (or longer), with little resemblance to the other sub-keys, and perhaps having >no values in the right-hand pane.  There may be under the Enum key consecutive sub-keys >with such garbled names, each one being longer than the prior one.  These corrupt >sub-keys should be deleted. > > Note:  before deleting any registry keys or sub-keys, first back-up the >entire Enum key by right-clicking on it, then click on Export, select where to save >it, and click on Save.  In addition, similarly back-up each sub-key that you intend >to delete. > > If upon trying to delete a corrupt sub-key, you get a message that the deletion >cannot be accomplished for lack of permission, increase the permissions for the corrupt >sub-key before deleting it, as follows: > > •  Right-click on the corrupt sub-key and in the context menu click on Permissions. > •  On the Security tab, select "Everyone" and check "Full Control" under "Allow."  >If "Everyone" is not there listed, click on the Add button and add the group "Everyone," >and then select it and check "Full Control" under "Allow."   If "Everyone" cannot >be added, add the group "Administrators" for whom check "Full Control" under "Allow." > •  Make sure there is nothing checked under "Deny" for "Everyone" or "Administrators." > > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes" > •  Then delete the corrupt sub-key. > > When finished, close the registry editor. > > As corruption of the registry might have been caused by a virus or malware, you >should use proper procedures to scan for and remove vires and malware from the system. > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Sunday, December 18, 2005 at 3:59 pm Posted by jcw (5100 messages posted) Link works for me. On Sunday, December 18, 2005 at 3:50 pm, Greg Hendren wrote: >http://swandog46.geekstogo.com/aproposfix.exe website is down!!!. Cant find fix anywhere >else, please help! > > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Sunday, December 18, 2005 at 4:12 pm Posted by Greg Hendren (3 messages posted) http://swandog46.geekstogo.com/aproposfix.exe This link is down, is fix available elsewhere? Urgent. On Thursday, December 8, 2005 at 6:23 pm, jcw wrote: > >The following has been distilled from various sources, notably messages posted in >a lengthy thread in this forum spanning well over two years at: > »   http://www.annoyances.org/exec/forum/winxp/1051715405 > Credit is to be given to those who provided these solutions, and those who endured >the trial and error in remedying a blank or empty Device Manager and took the time >to post their results. > > Readers are encouraged to "book-mark" this web-page for future reference for users >experiencing a blank or empty Device Manager in Windows XP. > > > Begin with the first potential solution below, and proceed with each subsequent >solution, after each opening Device Manager to see if it properly displays devices.  >Some solutions may not apply to your situation, e.g. the first and second solutions >that apply if you are getting the error messages there described. > To undertake these procedures, be logged-in with full administrative powers. > > 1)  If Device Manager is blank and there is an error message that the Device >Manager Snap-in failed to initialize, re-register the devmgr.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DEVMGR.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in devmgr.dll succeeded."  >Click OK. > > 2)  If Device Manager is blank and there is an "Action Cancelled" message >stating: > "Internet Explorer was unable to link to the Web page you requested. The page >might be temporarily unavailable.",  re-register the dmocx.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DMOCX.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in dmocx.dll succeeded."  >Click OK. > > 3)  A totally blank Device Manager (not showing even the computer icon and >name) can occur if the Plug and Play service is not started.  Open the Services window >and check the Status and Startup Type of that service.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If that service is not started or if its Startup Type is not set to automatic, >follow the instructions in >MS KB Art. 311504. > > 4) Review the Status and Startup Type of all of the Windows services in the >Services window.  You may find that many of the services that should be started, >are not.  If so, start those services and set their Startup Type to automatic or >manual as appropriate.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If you find a service that should be started, but is not: > •  Double-click on the service to be started. > •  On the General tab, in the Startup Type drop-down list, click on either Automatic >or Manual as appropriate (if in doubt, click on Automatic). > •  Click on the Start button. > •  Click OK. > When finished, close the Services window.  You may need to restart the computer >to effect the changes you have made to the services.  Once it appears that the computer >is operating properly, you may want to review the Windows services to see if there >are any that do not need to be started or whose Startup Type can be set to Manual >or Disabled without adversely affecting the computer's operation. > > 5)  In Control Panel --> Add/Remove Programs, check if Microsoft Windows Update >905749 is installed, and if so, uninstall it.  (That Security Update was released >10-11-05 to resolve a vulnerability in Plug and Play for Windows XP and 2000.)   >Restart the computer. > > 6)  If Device Manager shows the computer icon and name but no devices, check >that the security permissions for this registry key: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > meet these requirements: > •  the group "Everyone" should be listed and have only "Read" permissions. > •  the user "SYSTEM" should be listed and have "Full Control" and "Read" permissions. > To do this, open the registry editor (Start --> Run, type:  REGEDIT   >and hit Enter or OK). > Go to the above registry key, and right-click on the Enum key, and in the context >menu click on Permissions. > On the Security tab, review the listed group or user names and the permissions >checked for each in the "Allow" column to determine if they comply with the above >requirements.  If not, use the following instructions, or such of them as needed, >to have the listed names and their permissions meet those >requirements. > To add those names to the Security tab: > •  Click on the Add button. > •  Add the group "Everyone" and the user "SYSTEM." > To set the required permissions for those names on the Security tab: > •  Select "Everyone" and check "Read" (only) under "Allow." > •  Select "SYSTEM" and check "Full Control" under "Allow" (which also should >check "Read"). > •  Make sure there is nothing checked under "Deny" for either "SYSTEM" or "Everyone." > Then: > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes". > When finished, close the registry editor. > Note:  If at any time you get a message to the effect that the registry >editor cannot set or change security permissions in the selected key or its sub-keys, >go to the next step. > > 7)  In Control Panel --> Add/Remove Programs, check if Context Plus >or Ad Channel or POP or Apropos Client, or any combination of >those names, is installed.  If so, uninstall it or them.  (That item does not enjoy >a good reputation.)  Then review the discussion for possible additional removal >procedures (including a downloadable removal tool) at: > http://www.norton.com/avcenter/venc/data/spyware.apropos.html > When done, restart the computer. > > 8)  Apropos malware may be on the system, causing the blank or empty Device >Manager.  If so: > •  Download and save to the desktop AproposFix.exe at: > http://swandog46.geekstogo.com/aproposfix.exe > •  Reboot into safe mode (logging into the account in which you saved the downloaded >file). > •  Double or single click (whichever you use to open or run an item) on AproposFix.exe >on the desktop, which will place on the desktop an AproposFix folder. > •  Open the AproposFix folder, and double or single click on RunThis.bat  >to run it. > •  Follow the on-screen prompts.  When finished, reboot into normal mode. > •  The AproposFix folder now will have a log.txt file showing the actions >that AproposFix has taken, which should be reviewed, and saved until it is >clear that the Apropos malware has been entirely removed. > > You then should use proper procedures to scan for and remove any remaining elements >of Apropos, which is discussed at various web-sites, such as: > http://securityresponse.symantec.com/avcenter/venc/data/spyware.apropos.c.html > > 9)  One or more sub-keys under the Enum registry key may be corrupt, causing >the blank or empty Device Manager.  To check for and remedy corrupt sub-keys: > •  Open the registry editor (Start --> Run, type:  REGEDIT   and hit >Enter or OK)  and go to: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > •  Expand the Enum key, and examine each sub-key under it for a name that is >a seemingly random, disorderly combination of characters and symbols, e.g.:   $%^&*()24031 >  (or longer), with little resemblance to the other sub-keys, and perhaps having >no values in the right-hand pane.  There may be under the Enum key consecutive sub-keys >with such garbled names, each one being longer than the prior one.  These corrupt >sub-keys should be deleted. > > Note:  before deleting any registry keys or sub-keys, first back-up the >entire Enum key by right-clicking on it, then click on Export, select where to save >it, and click on Save.  In addition, similarly back-up each sub-key that you intend >to delete. > > If upon trying to delete a corrupt sub-key, you get a message that the deletion >cannot be accomplished for lack of permission, increase the permissions for the corrupt >sub-key before deleting it, as follows: > > •  Right-click on the corrupt sub-key and in the context menu click on Permissions. > •  On the Security tab, select "Everyone" and check "Full Control" under "Allow."  >If "Everyone" is not there listed, click on the Add button and add the group "Everyone," >and then select it and check "Full Control" under "Allow."   If "Everyone" cannot >be added, add the group "Administrators" for whom check "Full Control" under "Allow." > •  Make sure there is nothing checked under "Deny" for "Everyone" or "Administrators." > > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes" > •  Then delete the corrupt sub-key. > > When finished, close the registry editor. > > As corruption of the registry might have been caused by a virus or malware, you >should use proper procedures to scan for and remove vires and malware from the system. > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Sunday, December 18, 2005 at 4:57 pm Posted by jcw (5100 messages posted) Is the computer experiencing any other problems that frequently result from "malware," e.g. as described in: »  http://www.reesecomputing.com/downloads/files/AproposFix.exe ? If not, it may not be Apropos that is causing the blank or empty device manager. On Sunday, December 18, 2005 at 4:12 pm, Greg Hendren wrote: >http://swandog46.geekstogo.com/aproposfix.exe > >This link is down, is fix available elsewhere? > >Urgent. > > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Monday, December 19, 2005 at 12:09 pm Posted by MatrixCow (7 messages posted) Hello, I have a toshiba tecra S2 (3 months old) and i tried al the sollutions for the empty device manager problem. But nothing worked. It's getting verry enoying. I need this computer for school and i'm having problems to connect devices. Can somebody help me? Please. I don't know what to do anymore. (sorry for my bad spelling, i'm from belgium) On Thursday, December 8, 2005 at 6:23 pm, jcw wrote: > >The following has been distilled from various sources, notably messages posted in >a lengthy thread in this forum spanning well over two years at: > » http://www.annoyances.org/exec/forum/winxp/1051715405 > Credit is to be given to those who provided these solutions, and those who endured >the trial and error in remedying a blank or empty Device Manager and took the time >to post their results. > > Readers are encouraged to "book-mark" this web-page for future reference for users >experiencing a blank or empty Device Manager in Windows XP. > > > Begin with the first potential solution below, and proceed with each subsequent >solution, after each opening Device Manager to see if it properly displays devices. >Some solutions may not apply to your situation, e.g. the first and second solutions >that apply if you are getting the error messages there described. > To undertake these procedures, be logged-in with full administrative powers. > > 1) If Device Manager is blank and there is an error message that the Device >Manager Snap-in failed to initialize, re-register the devmgr.dll file as follows: > • Close all open programs. > • Start --> Run, and type: REGSVR32 DEVMGR.DLL and hit Enter or >OK. > • You should get this message: "DllRegisterServer in devmgr.dll succeeded." >Click OK. > > 2) If Device Manager is blank and there is an "Action Cancelled" message >stating: > "Internet Explorer was unable to link to the Web page you requested. The page >might be temporarily unavailable.", re-register the dmocx.dll file as follows: > • Close all open programs. > • Start --> Run, and type: REGSVR32 DMOCX.DLL and hit Enter or >OK. > • You should get this message: "DllRegisterServer in dmocx.dll succeeded." >Click OK. > > 3) A totally blank Device Manager (not showing even the computer icon and >name) can occur if the Plug and Play service is not started. Open the Services window >and check the Status and Startup Type of that service. To open the Services window: > Start --> Run, type: SERVICES.MSC and hit Enter or OK. > If that service is not started or if its Startup Type is not set to automatic, >follow the instructions in >MS KB Art. 311504. > > 4) Review the Status and Startup Type of all of the Windows services in the >Services window. You may find that many of the services that should be started, >are not. If so, start those services and set their Startup Type to automatic or >manual as appropriate. To open the Services window: > Start --> Run, type: SERVICES.MSC and hit Enter or OK. > If you find a service that should be started, but is not: > • Double-click on the service to be started. > • On the General tab, in the Startup Type drop-down list, click on either Automatic >or Manual as appropriate (if in doubt, click on Automatic). > • Click on the Start button. > • Click OK. > When finished, close the Services window. You may need to restart the computer >to effect the changes you have made to the services. Once it appears that the computer >is operating properly, you may want to review the Windows services to see if there >are any that do not need to be started or whose Startup Type can be set to Manual >or Disabled without adversely affecting the computer's operation. > > 5) In Control Panel --> Add/Remove Programs, check if Microsoft Windows Update >905749 is installed, and if so, uninstall it. (That Security Update was released >10-11-05 to resolve a vulnerability in Plug and Play for Windows XP and 2000.) >Restart the computer. > > 6) If Device Manager shows the computer icon and name but no devices, check >that the security permissions for this registry key: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > meet these requirements: > • the group "Everyone" should be listed and have only "Read" permissions. > • the user "SYSTEM" should be listed and have "Full Control" and "Read" permissions. > To do this, open the registry editor (Start --> Run, type: REGEDIT >and hit Enter or OK). > Go to the above registry key, and right-click on the Enum key, and in the context >menu click on Permissions. > On the Security tab, review the listed group or user names and the permissions >checked for each in the "Allow" column to determine if they comply with the above >requirements. If not, use the following instructions, or such of them as needed, >to have the listed names and their permissions meet those >requirements. > To add those names to the Security tab: > • Click on the Add button. > • Add the group "Everyone" and the user "SYSTEM." > To set the required permissions for those names on the Security tab: > • Select "Everyone" and check "Read" (only) under "Allow." > • Select "SYSTEM" and check "Full Control" under "Allow" (which also should >check "Read"). > • Make sure there is nothing checked under "Deny" for either "SYSTEM" or "Everyone." > Then: > • Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > • Click OK, and on any warning box click "Yes". > When finished, close the registry editor. > Note: If at any time you get a message to the effect that the registry >editor cannot set or change security permissions in the selected key or its sub-keys, >go to the next step. > > 7) In Control Panel --> Add/Remove Programs, check if Context Plus >or Ad Channel or POP or Apropos Client, or any combination of >those names, is installed. If so, uninstall it or them. (That item does not enjoy >a good reputation.) Then review the discussion for possible additional removal >procedures (including a downloadable removal tool) at: > http://www.norton.com/avcenter/venc/data/spyware.apropos.html > When done, restart the computer. > > 8) Apropos malware may be on the system, causing the blank or empty Device >Manager. If so: > • Download and save to the desktop AproposFix.exe at: > http://swandog46.geekstogo.com/aproposfix.exe > • Reboot into safe mode (logging into the account in which you saved the downloaded >file). > • Double or single click (whichever you use to open or run an item) on AproposFix.exe >on the desktop, which will place on the desktop an AproposFix folder. > • Open the AproposFix folder, and double or single click on RunThis.bat >to run it. > • Follow the on-screen prompts. When finished, reboot into normal mode. > • The AproposFix folder now will have a log.txt file showing the actions >that AproposFix has taken, which should be reviewed, and saved until it is >clear that the Apropos malware has been entirely removed. > > You then should use proper procedures to scan for and remove any remaining elements >of Apropos, which is discussed at various web-sites, such as: > http://securityresponse.symantec.com/avcenter/venc/data/spyware.apropos.c.html > > 9) One or more sub-keys under the Enum registry key may be corrupt, causing >the blank or empty Device Manager. To check for and remedy corrupt sub-keys: > • Open the registry editor (Start --> Run, type: REGEDIT and hit >Enter or OK) and go to: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > • Expand the Enum key, and examine each sub-key under it for a name that is >a seemingly random, disorderly combination of characters and symbols, e.g.: $%^&*()24031 > (or longer), with little resemblance to the other sub-keys, and perhaps having >no values in the right-hand pane. There may be under the Enum key consecutive sub-keys >with such garbled names, each one being longer than the prior one. These corrupt >sub-keys should be deleted. > > Note: before deleting any registry keys or sub-keys, first back-up the >entire Enum key by right-clicking on it, then click on Export, select where to save >it, and click on Save. In addition, similarly back-up each sub-key that you intend >to delete. > > If upon trying to delete a corrupt sub-key, you get a message that the deletion >cannot be accomplished for lack of permission, increase the permissions for the corrupt >sub-key before deleting it, as follows: > > • Right-click on the corrupt sub-key and in the context menu click on Permissions. > • On the Security tab, select "Everyone" and check "Full Control" under "Allow." >If "Everyone" is not there listed, click on the Add button and add the group "Everyone," >and then select it and check "Full Control" under "Allow." If "Everyone" cannot >be added, add the group "Administrators" for whom check "Full Control" under "Allow." > • Make sure there is nothing checked under "Deny" for "Everyone" or "Administrators." > > • Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > • Click OK, and on any warning box click "Yes" > • Then delete the corrupt sub-key. > > When finished, close the registry editor. > > As corruption of the registry might have been caused by a virus or malware, you >should use proper procedures to scan for and remove vires and malware from the system. > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Monday, December 19, 2005 at 1:19 pm Posted by jcw (5100 messages posted) You have not supplied enough information to provide help.  Questions (be specific in answering): (a)  Which edition of Windows XP do you use - Professional or Home, and do you have either SP1 or SP2 installed? (b)  Is the device manager entirely blank, or partially blank?  If partially blank, what does it display? (c)  Are you getting any error messages when you try to open or use the device manager, either on-screen or in the Event Viewer (Start menu --> Administrative Tools)? (d)  What problems are you having in connecting to devices?  Which devices? (e)  When did the device manager first appear blank, and when it occurred, had you recently installled any new software, devices, or device drivers? (f)  Did you previously have installed Microsoft Windows Update 905749, and have you since uninstalled it? (g)  What scans have you run for vires and "malware"? (h)  Are you having any other problems with the computer's operation?  If yes, describe them. Specifically, other than the blank device manager, is the computer experiencing any of the following? -- different (undesired) home page set in the internet browser -- pop-up ads or windows -- Windows Explorer is slow to display, e.g., after clicking on My Computer -- not all network connections are shown in Network Connections in Control Panel -- problems in connecting to scanners, printers, or cameras -- a prompt to reactivate Windows XP On Monday, December 19, 2005 at 12:09 pm, MatrixCow wrote: > >Hello, > >I have a toshiba tecra S2 (3 months old) and i tried al the sollutions for the empty >device manager problem. But nothing worked. It's getting verry enoying. I need this >computer for school and i'm having problems to connect devices. Can somebody help >me? Please. I don't know what to do anymore. >(sorry for my bad spelling, i'm from belgium) > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Tuesday, December 20, 2005 at 4:44 am Posted by MatrixCow (7 messages posted) I'm using xp pro with sp2. The device manager is entirely blanc. i don't get any errors. I can connect a usb stick but i can't connect my webcam. I don't think that i had installed something. It just went blanc. I'm running mcafee antivirus, spybot s&d and adaware. The network connections are empty too. I don't have any other problems. I already uninstalled the update. On Monday, December 19, 2005 at 1:19 pm, jcw wrote: >You have not supplied enough information to provide help.  Questions (be specific >in answering): > (a)  Which edition of Windows XP do you use - Professional or Home, and do you >have either SP1 or SP2 installed? > (b)  Is the device manager entirely blank, or partially blank?  If partially >blank, what does it display? > (c)  Are you getting any error messages when you try to open or use the device >manager, either on-screen or in the Event Viewer (Start menu --> Administrative Tools)? > (d)  What problems are you having in connecting to devices?  Which devices? > (e)  When did the device manager first appear blank, and when it occurred, had >you recently installled any new software, devices, or device drivers? > (f)  Did you previously have installed Microsoft Windows Update 905749, and have >you since uninstalled it? > (g)  What scans have you run for vires and "malware"? > (h)  Are you having any other problems with the computer's operation?  If yes, >describe them. > Specifically, other than the blank device manager, is the computer experiencing >any of the following? > -- different (undesired) home page set in the internet browser > -- pop-up ads or windows > -- Windows Explorer is slow to display, e.g., after clicking on My Computer > -- not all network connections are shown in Network Connections in Control Panel > -- problems in connecting to scanners, printers, or cameras > -- a prompt to reactivate Windows XP > > > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Tuesday, December 20, 2005 at 12:20 pm Posted by jcw (5100 messages posted) And you have performed steps 6 through 9 of the possible fixes? In doing steps 6 & 9, did you find anything unusual? Did you download and use the aproposfix.exe in step 8? Does your device manager properly display devices when you are in safe mode? Does your network connections window properly show your connections when you are in safe mode? You said your network connections window is also empty. I assume your network connection(s) is working OK? You might want to take a look at this post, which turned out not to be apropos-related, but registry corruption. -->   http://www.annoyances.org/exec/forum/winxp/1133980151 Finally, I recall a poster who had removed Microsoft Update 905749, and in desperation after trying other things, re-installed that update, and then device manger populated properly. As a last resort, only after when you have tried everything else, might want to try reinstalling that Update 905749. On Tuesday, December 20, 2005 at 4:44 am, MatrixCow wrote: >I'm using xp pro with sp2. >The device manager is entirely blanc. >i don't get any errors. >I can connect a usb stick but i can't connect my webcam. >I don't think that i had installed something. It just went blanc. >I'm running mcafee antivirus, spybot s&d and adaware. >The network connections are empty too. I don't have any other problems. >I already uninstalled the update. > > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Thursday, December 22, 2005 at 7:31 am Posted by MatrixCow (7 messages posted) My network connections are working. I looked at the other topic. I found one key in my registry that i can't open. hklm\system\CurrentControlset\Enum\Root\LEGACY_MRACOMM On Tuesday, December 20, 2005 at 12:20 pm, jcw wrote: >And you have performed steps 6 through 9 of the possible fixes? In doing steps 6 >& 9, did you find anything unusual? Did you download and use the aproposfix.exe >in step 8? > Does your device manager properly display devices when you are in safe mode? > Does your network connections window properly show your connections when you >are in safe mode? > You said your network connections window is also empty. I assume your network >connection(s) is working OK? You might want to take a look at this post, which turned >out not to be apropos-related, but registry corruption. > --> http://www.annoyances.org/exec/forum/winxp/1133980151 > Finally, I recall a poster who had removed Microsoft Update 905749, and in desperation >after trying other things, re-installed that update, and then device manger populated >properly. As a last resort, only after when you have tried everything else, might >want to try reinstalling that Update 905749. > > > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Thursday, December 22, 2005 at 12:38 pm Posted by jcw (5100 messages posted) Some thoughts, that I'll spell out now as I may be unavailable later for a while. You didn't answer all of my previous questions, so I will here only address what you just reported. I won't here try to address all of the possibilites that could stem from answers to all of my previous questions. Back-up that reg key you mentioned: hklm\system\CurrentControlSet\Enum\Root\LEGACY_MRACOMM by exporting it to a convenient location (right-click on that key, then click on Export, select where to save a copy of it, and click on Save). Then go to the backed-up copy in the .reg file, right-click on it and click on Edit. The file should display in Notepad, where you can examine it for irregularities:  either blank (no) entries, or garbled entries as described in step 9 of the original compilation. If review of that .reg file persuades you that the reg key is corrupt and the likely problem, try to delete that key from within the registry editor (regedit). Make sure you have the permissions to do so as explained in step 9 of the compilation. (To be clear, I mean deleting the registry key from within regedit, not deleting its back-up copy in the .reg file, which you should keep until your problem is resolved.) If you can delete the key, reboot and see what happens. (You can restore the key if need be by right-clicking on its back-up .reg file and then clicking on Merge.) If you can't delete the key from within the registry editor (regedit), even after making sure you have the permissions to do so, I would try booting into safe mode with command prompt, and then at the command prompt in its window, use the REG DELETE command to delete the key. (To repeat, I mean deleting the registry key, not its back-up copy in the .reg file.) To boot into safe mode with command prompt, restart the computer and begin repeatedly pressing the F8 key.  When the Windows Advanced Options Menu appears, select Safe Mode with Command Prompt, and press Enter. (A screen-shot of that Menu is at this webpage - at its top, click on "How To Access Safe Mode": »   http://www.webtree.ca/windowsxp/repair_xp.htm   ) To see the syntax for the "reg delete" command, type at the command prompt:   REG DELETE /? If you are unsure about using that command, perhaps you can find someone who can help you. Note:  be careful here, and double-check your command line before entering it at the command prompt, and again before pressing Enter. If any doubt, first back-up the entire HKLM\System\CurrentControlSet\Enum key (right-click on it, click on Export, select a convenient location where to save a copy of it, and click on Save). You also might consider sending a private message to "F15hii" who wrote the post at: http://www.annoyances.org/exec/forum/winxp/1133980151 for more information on what that poster used to delete the legacy key there found to be the problem. The poster's description of a "registry fix" that the poster downloaded, unzipped, and ran as "regfix1 and regfix2" might be helpful to you. I'm not familiar with it. You also could do a Google or other search for it. To send a private message to F15hii, click on that "handle" link at the top of his/her posted message. One other thing:  you mentioned having an empty network connections window. As you can see from F15hii's above-referenced post, you may need to do a manual search for another corrupt registry key causing that problem. Start looking for something called in part "LEGACY_MRACOMM" or "MRACOMM" (in each case without the quote marks). Finally, would you please post your findings and results - good or bad - so that others with a blank or empty device manager might benefit from your experience. On Thursday, December 22, 2005 at 7:31 am, MatrixCow wrote: >My network connections are working. I looked at the other topic. I found one key >in my registry that i can't open. hklm\system\CurrentControlset\Enum\Root\LEGACY_MRACOMM > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Thursday, December 29, 2005 at 4:46 am Posted by MatrixCow (7 messages posted) I can't export the key. "The structure does not exist. Check path." On Thursday, December 22, 2005 at 12:38 pm, jcw wrote: >Some thoughts, that I'll spell out now as I may be unavailable later for a while. > You didn't answer all of my previous questions, so I will here only address what >you just reported. I won't here try to address all of the possibilites that could >stem from answers to all of my previous questions. > Back-up that reg key you mentioned: >hklm\system\CurrentControlSet\Enum\Root\LEGACY_MRACOMM > by exporting it to a convenient location (right-click on that key, then click >on Export, select where to save a copy of it, and click on Save). > Then go to the backed-up copy in the .reg file, right-click on it and click on >Edit. The file should display in Notepad, where you can examine it for irregularities: >either blank (no) entries, or garbled entries as described in step 9 of the original >compilation. > If review of that .reg file persuades you that the reg key is corrupt and the >likely problem, try to delete that key from within the registry editor (regedit). >Make sure you have the permissions to do so as explained in step 9 of the compilation. >(To be clear, I mean deleting the registry key from within regedit, not deleting >its back-up copy in the .reg file, which you should keep until your problem is resolved.) >If you can delete the key, reboot and see what happens. (You can restore the key >if need be by right-clicking on its back-up .reg file and then clicking on Merge.) > If you can't delete the key from within the registry editor (regedit), even after >making sure you have the permissions to do so, I would try booting into safe mode >with command prompt, and then at the command prompt in its window, use the REG >DELETE command to delete the key. (To repeat, I mean deleting the registry key, >not its back-up copy in the .reg file.) > To boot into safe mode with command prompt, restart the computer and begin repeatedly >pressing the F8 key. When the Windows Advanced Options Menu appears, select Safe >Mode with Command Prompt, and press Enter. (A screen-shot of that Menu is at this >webpage - at its top, click on "How To Access Safe Mode": > » http://www.webtree.ca/windowsxp/repair_xp.htm ) > To see the syntax for the "reg delete" command, type at the command prompt: >REG DELETE /? > If you are unsure about using that command, perhaps you can find someone who >can help you. > Note: be careful here, and double-check your command line before entering >it at the command prompt, and again before pressing Enter. If any doubt, first back-up >the entire HKLM\System\CurrentControlSet\Enum key (right-click on it, click on Export, >select a convenient location where to save a copy of it, and click on Save). > You also might consider sending a private message to "F15hii" who wrote the post >at: > http://www.annoyances.org/exec/forum/winxp/1133980151 > for more information on what that poster used to delete the legacy key there >found to be the problem. The poster's description of a "registry fix" that the poster >downloaded, unzipped, and ran as "regfix1 and regfix2" might be helpful to you. >I'm not familiar with it. You also could do a Google or other search for it. > To send a private message to F15hii, click on that "handle" link at the top of >his/her posted message. > One other thing: you mentioned having an empty network connections window. As >you can see from F15hii's above-referenced post, you may need to do a manual search >for another corrupt registry key causing that problem. Start looking for something >called in part "LEGACY_MRACOMM" or "MRACOMM" (in each case without the quote marks). > Finally, would you please post your findings and results - good or bad - so that >others with a blank or empty device manager might benefit from your experience. > > > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Sunday, January 1, 2006 at 5:28 pm Posted by jcw (5100 messages posted) Then try exporting the entire reg key: hklm\system\CurrentControlSet\Enum\Root On Thursday, December 29, 2005 at 4:46 am, MatrixCow wrote: >I can't export the key. "The structure does not exist. Check path." > > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Tuesday, January 3, 2006 at 6:44 am Posted by MatrixCow (7 messages posted) i exported hklm\system\CurrentControlSet\Enum\Root and i cant find hklm\system\CurrentControlSet\Enum\Root\LEGACY_MRACOMM in the exported file. On Sunday, January 1, 2006 at 5:28 pm, jcw wrote: >Then try exporting the entire reg key: > hklm\system\CurrentControlSet\Enum\Root > > > > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Tuesday, January 3, 2006 at 8:38 am Posted by jcw (5100 messages posted) Keep the back-up copy that you made of: hklm\system\CurrentControlSet\Enum\Root Now, make a back-up copy (by exporting) of the entire key: hklm\system\CurrentControlSet\Enum Examine it for the LEGACY_MRACOMM sub-key. I will assume you won't find it there either, but if it is there, let me know what is there. Keep that back-up copy as well, and be sure to label it so that you won't confuse it with the back-up copy of the Enum\Root key. Assuming that the LEGACY_MRACOMM sub-key does not show in the back-up copy of the entire Enum key that you just made, go ahead and try to delete the LEGACY_MRACOMM sub-key in the registry editor; if the deletion succeeds, don't reboot, but instead close the registry editor and open the device manager to see if it is now populated. If you can't delete that sub-key from within the registry editor, then try doing so by first booting into safe mode with command prompt, as instructed in my prior post at: »  http://www.annoyances.org/exec/forum/winxp/1135283897 Then reboot normally and see if the registry editor still shows that sub-key and if the device manager is populated. On Tuesday, January 3, 2006 at 6:44 am, MatrixCow wrote: > >i exported hklm\system\CurrentControlSet\Enum\Root and i cant find hklm\system\CurrentControlSet\Enum\Root\LEGACY_MRACOMM >in the exported file. > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Tuesday, January 3, 2006 at 10:03 am Posted by MatrixCow (7 messages posted) i can't delete the key. not even in save mode. On Tuesday, January 3, 2006 at 8:38 am, jcw wrote: >Keep the back-up copy that you made of: > hklm\system\CurrentControlSet\Enum\Root > Now, make a back-up copy (by exporting) of the entire key: > hklm\system\CurrentControlSet\Enum > Examine it for the LEGACY_MRACOMM sub-key. I will assume you won't find it there >either, but if it is there, let me know what is there. Keep that back-up copy as >well, and be sure to label it so that you won't confuse it with the back-up copy >of the Enum\Root key. > Assuming that the LEGACY_MRACOMM sub-key does not show in the back-up copy of >the entire Enum key that you just made, go ahead and try to delete the LEGACY_MRACOMM >sub-key in the registry editor; if the deletion succeeds, don't reboot, but instead >close the registry editor and open the device manager to see if it is now populated. > If you can't delete that sub-key from within the registry editor, then try doing >so by first booting into safe mode with command prompt, as instructed in my prior >post at: > »  http://www.annoyances.org/exec/forum/winxp/1135283897 > Then reboot normally and see if the registry editor still shows that sub-key >and if the device manager is populated. > > > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Wednesday, January 18, 2006 at 5:27 am Posted by MatrixCow (7 messages posted) I get an error when i trie to delete it in safe mode. Error: acces denied. Can someone help me?? On Tuesday, January 3, 2006 at 10:03 am, MatrixCow wrote: >i can't delete the key. not even in save mode. > > > [Reply or follow-up to this message] Checked if have permission to delete that sub-key? Thursday, January 19, 2006 at 10:54 am Posted by jcw (5100 messages posted) Did you check in the registry editor to make sure you have permission to delete that sub-key, LEGACY_MRACOMM (as mentioned at:   http://www.annoyances.org/exec/forum/winxp/1135283897 ) ? On Wednesday, January 18, 2006 at 5:27 am, MatrixCow wrote: >I get an error when i trie to delete it in safe mode. Error: acces denied. Can someone >help me?? > > > [Reply or follow-up to this message] help. None of the solutions work for me. Thursday, February 23, 2006 at 6:22 pm Posted by mj (3 messages posted) Well, after a couple of weeks of review and playing around with this issue I have thrown up my hands and open to any other suggestions. This is what I know: 1. Device manager is blank after trying all the above solutions mentioned 2. Dial up Modem stopped working. It mentions can not be initialized. I have verified that the modem card is in working order and the line gets detected but it won't initialize 3. I don't have any restore points to go back too 4. I have manually reviewed the part of the registry that seems to be mentioned to the problem area. 5. Noticed that the file manager (i.e, MY COMPUTER) when I go to explore there is a delay to display the files but shows all files. 6. The device manager doesn't work in Safe Mode Verison of Windows: XP SP2 w/ all the latest updates and patches Verified that the PnP services are working, no spyware on computer. Network services working fine. Any suggestions? [Reply or follow-up to this message] re: help. None of the solutions work for me. Friday, February 24, 2006 at 8:54 am Posted by jcw (5100 messages posted) No other suggestions besides what is in this thread. What you describe points to registry corruption - step 9 in the compilation, which can be a tedious search, as you may have noted from some of the posts. While the problem may be related to the inoperative dial-up modem, you may need to search the entire Enum reg key for corruption. [Reply or follow-up to this message] Found corrupt key in registry but won't let me delete Friday, February 24, 2006 at 11:12 am Posted by mj (3 messages posted) Well, After a gruelling search I did manage to find the suspect. However, now I have no way to delete. First, here is the culprit: hklm/system/currentcontrolset/enum/usb/Vid_041e&Pid_'111 This is what I have tried to do to delete it: 1. Delete it directly from the regedit Result: Cannot Delete - Error while deleting Key Additionally there are no permission settings for this key for me to set. Also, I have tried to rename the key to remove the single quote. 2. Booted up in safe mode and tried the command prompt reg Delete to delete the corrupt key with and without double quotes as I noticed that he single quotes throws the command prompt off Result: Error: The system was unable to find the specified registry key or value. Any thoughts or suggestions? On Friday, February 24, 2006 at 8:54 am, jcw wrote: >No other suggestions besides what is in this thread. What you describe points to >registry corruption - step 9 in the compilation, which can be a tedious search, as >you may have noted from some of the posts. While the problem may be related to the >inoperative dial-up modem, you may need to search the entire Enum reg key for corruption. [Reply or follow-up to this message] re: Found corrupt key in registry but won't let me delete Friday, February 24, 2006 at 12:54 pm Posted by jcw (5100 messages posted) A) You said that there are no permission settings for the corrupt key for you to set. Could you explain that? What is there in the Permissions dialog box for the corrupt key? Does the Permissions dialog box for the USB key appear regular and allowing you to make the deletion in regedit? If need be, do you have an upload service account somewhere that you could use to show a screen-shot of the Permission dialog box(es)? B) Can you export the corrupt key to a convenient location, and then open (use the "edit" command in the right-click menu) the saved .reg file so we can see its contents? If not, how about the same thing for the USB key? C) How many subkeys are there in (under) the USB key? [Reply or follow-up to this message] re: Found corrupt key in registry but won't let me delete Friday, February 24, 2006 at 2:26 pm Posted by mj (3 messages posted) A) There isn't a usuable permission dialog box available for the corrupt key. First when I click on the key it responds by saying that "Cannot Open : Error while opening key". Second, when I right click and go to permissions a dialog box pops up with "Unable to show security information" (OK and Cancel buttons active only) There is not much to show. If you like I could get a screen shot of that. On the other hand the parent root USB key has the permission dialog box with two user settings EVERYONE and SYSTEM. EVERYONE have Read access active and faded out and the SYSTEM having Read and Full Control active and faded out. B) Exporting the corrupt key fails with the following message: "Selected branch does not exist. Make sure that the correct path is given" I successfully exported the USB key but found that the corrupted key was not included in the file. I even tried to delete the USB path with the hope of restoring it with exported file but that failed to with the following error message while trying to delete it: "Cannot Delete USB : Error while deleting key" You can find a copy of the reg file at http://s137192784.onlinehome.us/library/USBreBackup.txt C) There are a total of 26 keys in the first level branch below USB. Appreciate all the help. Any ideas? On Friday, February 24, 2006 at 12:54 pm, jcw wrote: > >A) You said that there are no permission settings for the corrupt key for you to >set. >Could you explain that? >What is there in the Permissions dialog box for the corrupt key? >Does the Permissions dialog box for the USB key appear regular and allowing you to >make the deletion in regedit? >If need be, do you have an upload service account somewhere that you could use to >show a screen-shot of the Permission dialog box(es)? > >B) Can you export the corrupt key to a convenient location, and then open (use the >"edit" command in the right-click menu) the saved .reg file so we can see its contents? >If not, how about the same thing for the USB key? > >C) How many subkeys are there in (under) the USB key? > > > > [Reply or follow-up to this message] re: Found corrupt key in registry but won't let me delete Sunday, February 26, 2006 at 8:03 pm Posted by jcw (5100 messages posted) You said: "I even tried to delete the USB path with the hope of restoring it with exported file but that failed too with the following error message while trying to delete it: 'Cannot Delete USB : Error while deleting key'." Did you mean that you tried to delete the entire USB key (under Enum) with the idea of then merging or importing the previously exported USB key back into the registry? If yes, that would have been my next suggestion as well. Did you try deleting the USB key by first booting into safe mode with command prompt (not safe mode boot and then opening the command prompt window) and using the "reg delete" command as I described in a prior post at: -> http://www.annoyances.org/exec/forum/winxp/1135283897 If that doesn't do it, you could try to export/back-up the entire Enum key, check it to assure that it doesn't have the corrupt Vid sub-key, and then try delete the Enum key, and restore it with its backed-up version. BUT before you try that, take a look at my prior post referenced above about contacting "F15hii." I'll ask the same thing I asked of the previous poster: would you please post your findings and results - good or bad - so that others might benefit from your experience. [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Friday, June 2, 2006 at 11:20 pm Posted by Deanna (1 messages posted) What does it mean if device manager is empty in normal mode but is populated in safe mode? On Thursday, December 8, 2005 at 6:23 pm, jcw wrote: > >The following has been distilled from various sources, notably messages posted in >a lengthy thread in this forum spanning well over two years at: > »   http://www.annoyances.org/exec/forum/winxp/1051715405 > Credit is to be given to those who provided these solutions, and those who endured >the trial and error in remedying a blank or empty Device Manager and took the time >to post their results. > > Readers are encouraged to "book-mark" this web-page for future reference for users >experiencing a blank or empty Device Manager in Windows XP. > > > Begin with the first potential solution below, and proceed with each subsequent >solution, after each opening Device Manager to see if it properly displays devices.  >Some solutions may not apply to your situation, e.g. the first and second solutions >that apply if you are getting the error messages there described. > To undertake these procedures, be logged-in with full administrative powers. > > 1)  If Device Manager is blank and there is an error message that the Device >Manager Snap-in failed to initialize, re-register the devmgr.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DEVMGR.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in devmgr.dll succeeded."  >Click OK. > > 2)  If Device Manager is blank and there is an "Action Cancelled" message >stating: > "Internet Explorer was unable to link to the Web page you requested. The page >might be temporarily unavailable.",  re-register the dmocx.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DMOCX.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in dmocx.dll succeeded."  >Click OK. > > 3)  A totally blank Device Manager (not showing even the computer icon and >name) can occur if the Plug and Play service is not started.  Open the Services window >and check the Status and Startup Type of that service.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If that service is not started or if its Startup Type is not set to automatic, >follow the instructions in >MS KB Art. 311504. > > 4) Review the Status and Startup Type of all of the Windows services in the >Services window.  You may find that many of the services that should be started, >are not.  If so, start those services and set their Startup Type to automatic or >manual as appropriate.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If you find a service that should be started, but is not: > •  Double-click on the service to be started. > •  On the General tab, in the Startup Type drop-down list, click on either Automatic >or Manual as appropriate (if in doubt, click on Automatic). > •  Click on the Start button. > •  Click OK. > When finished, close the Services window.  You may need to restart the computer >to effect the changes you have made to the services.  Once it appears that the computer >is operating properly, you may want to review the Windows services to see if there >are any that do not need to be started or whose Startup Type can be set to Manual >or Disabled without adversely affecting the computer's operation. > > 5)  In Control Panel --> Add/Remove Programs, check if Microsoft Windows Update >905749 is installed, and if so, uninstall it.  (That Security Update was released >10-11-05 to resolve a vulnerability in Plug and Play for Windows XP and 2000.)   >Restart the computer. > > 6)  If Device Manager shows the computer icon and name but no devices, check >that the security permissions for this registry key: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > meet these requirements: > •  the group "Everyone" should be listed and have only "Read" permissions. > •  the user "SYSTEM" should be listed and have "Full Control" and "Read" permissions. > To do this, open the registry editor (Start --> Run, type:  REGEDIT   >and hit Enter or OK). > Go to the above registry key, and right-click on the Enum key, and in the context >menu click on Permissions. > On the Security tab, review the listed group or user names and the permissions >checked for each in the "Allow" column to determine if they comply with the above >requirements.  If not, use the following instructions, or such of them as needed, >to have the listed names and their permissions meet those >requirements. > To add those names to the Security tab: > •  Click on the Add button. > •  Add the group "Everyone" and the user "SYSTEM." > To set the required permissions for those names on the Security tab: > •  Select "Everyone" and check "Read" (only) under "Allow." > •  Select "SYSTEM" and check "Full Control" under "Allow" (which also should >check "Read"). > •  Make sure there is nothing checked under "Deny" for either "SYSTEM" or "Everyone." > Then: > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes". > When finished, close the registry editor. > Note:  If at any time you get a message to the effect that the registry >editor cannot set or change security permissions in the selected key or its sub-keys, >go to the next step. > > 7)  In Control Panel --> Add/Remove Programs, check if Context Plus >or Ad Channel or POP or Apropos Client, or any combination of >those names, is installed.  If so, uninstall it or them.  (That item does not enjoy >a good reputation.)  Then review the discussion for possible additional removal >procedures (including a downloadable removal tool) at: > http://www.norton.com/avcenter/venc/data/spyware.apropos.html > When done, restart the computer. > > 8)  Apropos malware may be on the system, causing the blank or empty Device >Manager.  If so: > •  Download and save to the desktop AproposFix.exe at: > http://swandog46.geekstogo.com/aproposfix.exe > •  Reboot into safe mode (logging into the account in which you saved the downloaded >file). > •  Double or single click (whichever you use to open or run an item) on AproposFix.exe >on the desktop, which will place on the desktop an AproposFix folder. > •  Open the AproposFix folder, and double or single click on RunThis.bat  >to run it. > •  Follow the on-screen prompts.  When finished, reboot into normal mode. > •  The AproposFix folder now will have a log.txt file showing the actions >that AproposFix has taken, which should be reviewed, and saved until it is >clear that the Apropos malware has been entirely removed. > > You then should use proper procedures to scan for and remove any remaining elements >of Apropos, which is discussed at various web-sites, such as: > http://securityresponse.symantec.com/avcenter/venc/data/spyware.apropos.c.html > > 9)  One or more sub-keys under the Enum registry key may be corrupt, causing >the blank or empty Device Manager.  To check for and remedy corrupt sub-keys: > •  Open the registry editor (Start --> Run, type:  REGEDIT   and hit >Enter or OK)  and go to: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > •  Expand the Enum key, and examine each sub-key under it for a name that is >a seemingly random, disorderly combination of characters and symbols, e.g.:   $%^&*()24031 >  (or longer), with little resemblance to the other sub-keys, and perhaps having >no values in the right-hand pane.  There may be under the Enum key consecutive sub-keys >with such garbled names, each one being longer than the prior one.  These corrupt >sub-keys should be deleted. > > Note:  before deleting any registry keys or sub-keys, first back-up the >entire Enum key by right-clicking on it, then click on Export, select where to save >it, and click on Save.  In addition, similarly back-up each sub-key that you intend >to delete. > > If upon trying to delete a corrupt sub-key, you get a message that the deletion >cannot be accomplished for lack of permission, increase the permissions for the corrupt >sub-key before deleting it, as follows: > > •  Right-click on the corrupt sub-key and in the context menu click on Permissions. > •  On the Security tab, select "Everyone" and check "Full Control" under "Allow."  >If "Everyone" is not there listed, click on the Add button and add the group "Everyone," >and then select it and check "Full Control" under "Allow."   If "Everyone" cannot >be added, add the group "Administrators" for whom check "Full Control" under "Allow." > •  Make sure there is nothing checked under "Deny" for "Everyone" or "Administrators." > > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes" > •  Then delete the corrupt sub-key. > > When finished, close the registry editor. > > As corruption of the registry might have been caused by a virus or malware, you >should use proper procedures to scan for and remove vires and malware from the system. > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Tuesday, June 6, 2006 at 9:47 am Posted by jcw (5100 messages posted) It could signal that the Device Manager problem may be caused by a virus or malware. Did you execute steps 7 and 8 of the compilation? On Friday, June 2, 2006 at 11:20 pm, Deanna wrote: >What does it mean if device manager is empty in normal mode but is populated in safe >mode? [Reply or follow-up to this message] ahh the ENUM KEY!! Wednesday, July 5, 2006 at 6:49 am Posted by leon (1 messages posted) thank you to the person that discovered the stupid enum key! what would cause this thing to drop dead? i went thru everything from every forum until i checked the permissions of this enum key thing. ahh is good now. ta Leon On Thursday, December 8, 2005 at 6:23 pm, jcw wrote: > >The following has been distilled from various sources, notably messages posted in >a lengthy thread in this forum spanning well over two years at: > »   http://www.annoyances.org/exec/forum/winxp/1051715405 > Credit is to be given to those who provided these solutions, and those who endured >the trial and error in remedying a blank or empty Device Manager and took the time >to post their results. > > Readers are encouraged to "book-mark" this web-page for future reference for users >experiencing a blank or empty Device Manager in Windows XP. > > > Begin with the first potential solution below, and proceed with each subsequent >solution, after each opening Device Manager to see if it properly displays devices.  >Some solutions may not apply to your situation, e.g. the first and second solutions >that apply if you are getting the error messages there described. > To undertake these procedures, be logged-in with full administrative powers. > > 1)  If Device Manager is blank and there is an error message that the Device >Manager Snap-in failed to initialize, re-register the devmgr.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DEVMGR.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in devmgr.dll succeeded."  >Click OK. > > 2)  If Device Manager is blank and there is an "Action Cancelled" message >stating: > "Internet Explorer was unable to link to the Web page you requested. The page >might be temporarily unavailable.",  re-register the dmocx.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DMOCX.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in dmocx.dll succeeded."  >Click OK. > > 3)  A totally blank Device Manager (not showing even the computer icon and >name) can occur if the Plug and Play service is not started.  Open the Services window >and check the Status and Startup Type of that service.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If that service is not started or if its Startup Type is not set to automatic, >follow the instructions in >MS KB Art. 311504. > > 4) Review the Status and Startup Type of all of the Windows services in the >Services window.  You may find that many of the services that should be started, >are not.  If so, start those services and set their Startup Type to automatic or >manual as appropriate.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If you find a service that should be started, but is not: > •  Double-click on the service to be started. > •  On the General tab, in the Startup Type drop-down list, click on either Automatic >or Manual as appropriate (if in doubt, click on Automatic). > •  Click on the Start button. > •  Click OK. > When finished, close the Services window.  You may need to restart the computer >to effect the changes you have made to the services.  Once it appears that the computer >is operating properly, you may want to review the Windows services to see if there >are any that do not need to be started or whose Startup Type can be set to Manual >or Disabled without adversely affecting the computer's operation. > > 5)  In Control Panel --> Add/Remove Programs, check if Microsoft Windows Update >905749 is installed, and if so, uninstall it.  (That Security Update was released >10-11-05 to resolve a vulnerability in Plug and Play for Windows XP and 2000.)   >Restart the computer. > > 6)  If Device Manager shows the computer icon and name but no devices, check >that the security permissions for this registry key: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > meet these requirements: > •  the group "Everyone" should be listed and have only "Read" permissions. > •  the user "SYSTEM" should be listed and have "Full Control" and "Read" permissions. > To do this, open the registry editor (Start --> Run, type:  REGEDIT   >and hit Enter or OK). > Go to the above registry key, and right-click on the Enum key, and in the context >menu click on Permissions. > On the Security tab, review the listed group or user names and the permissions >checked for each in the "Allow" column to determine if they comply with the above >requirements.  If not, use the following instructions, or such of them as needed, >to have the listed names and their permissions meet those >requirements. > To add those names to the Security tab: > •  Click on the Add button. > •  Add the group "Everyone" and the user "SYSTEM." > To set the required permissions for those names on the Security tab: > •  Select "Everyone" and check "Read" (only) under "Allow." > •  Select "SYSTEM" and check "Full Control" under "Allow" (which also should >check "Read"). > •  Make sure there is nothing checked under "Deny" for either "SYSTEM" or "Everyone." > Then: > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes". > When finished, close the registry editor. > Note:  If at any time you get a message to the effect that the registry >editor cannot set or change security permissions in the selected key or its sub-keys, >go to the next step. > > 7)  In Control Panel --> Add/Remove Programs, check if Context Plus >or Ad Channel or POP or Apropos Client, or any combination of >those names, is installed.  If so, uninstall it or them.  (That item does not enjoy >a good reputation.)  Then review the discussion for possible additional removal >procedures (including a downloadable removal tool) at: > http://www.norton.com/avcenter/venc/data/spyware.apropos.html > When done, restart the computer. > > 8)  Apropos malware may be on the system, causing the blank or empty Device >Manager.  If so: > •  Download and save to the desktop AproposFix.exe at: > http://swandog46.geekstogo.com/aproposfix.exe > •  Reboot into safe mode (logging into the account in which you saved the downloaded >file). > •  Double or single click (whichever you use to open or run an item) on AproposFix.exe >on the desktop, which will place on the desktop an AproposFix folder. > •  Open the AproposFix folder, and double or single click on RunThis.bat  >to run it. > •  Follow the on-screen prompts.  When finished, reboot into normal mode. > •  The AproposFix folder now will have a log.txt file showing the actions >that AproposFix has taken, which should be reviewed, and saved until it is >clear that the Apropos malware has been entirely removed. > > You then should use proper procedures to scan for and remove any remaining elements >of Apropos, which is discussed at various web-sites, such as: > http://securityresponse.symantec.com/avcenter/venc/data/spyware.apropos.c.html > > 9)  One or more sub-keys under the Enum registry key may be corrupt, causing >the blank or empty Device Manager.  To check for and remedy corrupt sub-keys: > •  Open the registry editor (Start --> Run, type:  REGEDIT   and hit >Enter or OK)  and go to: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > •  Expand the Enum key, and examine each sub-key under it for a name that is >a seemingly random, disorderly combination of characters and symbols, e.g.:   $%^&*()24031 >  (or longer), with little resemblance to the other sub-keys, and perhaps having >no values in the right-hand pane.  There may be under the Enum key consecutive sub-keys >with such garbled names, each one being longer than the prior one.  These corrupt >sub-keys should be deleted. > > Note:  before deleting any registry keys or sub-keys, first back-up the >entire Enum key by right-clicking on it, then click on Export, select where to save >it, and click on Save.  In addition, similarly back-up each sub-key that you intend >to delete. > > If upon trying to delete a corrupt sub-key, you get a message that the deletion >cannot be accomplished for lack of permission, increase the permissions for the corrupt >sub-key before deleting it, as follows: > > •  Right-click on the corrupt sub-key and in the context menu click on Permissions. > •  On the Security tab, select "Everyone" and check "Full Control" under "Allow."  >If "Everyone" is not there listed, click on the Add button and add the group "Everyone," >and then select it and check "Full Control" under "Allow."   If "Everyone" cannot >be added, add the group "Administrators" for whom check "Full Control" under "Allow." > •  Make sure there is nothing checked under "Deny" for "Everyone" or "Administrators." > > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes" > •  Then delete the corrupt sub-key. > > When finished, close the registry editor. > > As corruption of the registry might have been caused by a virus or malware, you >should use proper procedures to scan for and remove vires and malware from the system. > > [Reply or follow-up to this message] re: ahh the ENUM KEY!! Wednesday, July 5, 2006 at 11:15 am Posted by Annoyed-With-Windows (39 messages posted) You asked: "what would cause this thing [the enum key] to drop dead?" In many cases, the installation of a new device - due to a badly written installation program - resulting in bad entries in the registry. On Wednesday, July 5, 2006 at 6:49 am, leon wrote: >thank you to the person that discovered the stupid enum key! > >what would cause this thing to drop dead? i went thru everything from every forum >until i checked the permissions of this enum key thing. > >ahh is good now. ta > >Leon > > > [Reply or follow-up to this message] re: ahh the ENUM KEY!! Wednesday, August 16, 2006 at 2:12 am Posted by MC (1 messages posted) I had a corrupt key in ENUM and could not delete it however I tried. I noticed that the key in "current control set 2" could be deleted, so I did. I rebooted, held down F8, and selected "Last known good configuration" from the boot menu. And it worked - my device manager is back again. [Reply or follow-up to this message] Xp SP3 was my problem - found the fix! Sunday, October 12, 2008 at 2:29 pm Posted by Lee Grissom (1 messages posted) http://support.microsoft.com/?kbid=953979 [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Sunday, December 21, 2008 at 6:38 am Posted by Luke (1 messages posted) Add the following MS article to the list. http://support.microsoft.com/?kbid=953979 On Thursday, December 8, 2005 at 6:23 pm, jcw wrote: > >The following has been distilled from various sources, notably messages posted in >a lengthy thread in this forum spanning well over two years at: > »   http://www.annoyances.org/exec/forum/winxp/1051715405 > Credit is to be given to those who provided these solutions, and those who endured >the trial and error in remedying a blank or empty Device Manager and took the time >to post their results. > > Readers are encouraged to "book-mark" this web-page for future reference for users >experiencing a blank or empty Device Manager in Windows XP. > > > Begin with the first potential solution below, and proceed with each subsequent >solution, after each opening Device Manager to see if it properly displays devices.  >Some solutions may not apply to your situation, e.g. the first and second solutions >that apply if you are getting the error messages there described. > To undertake these procedures, be logged-in with full administrative powers. > > 1)  If Device Manager is blank and there is an error message that the Device >Manager Snap-in failed to initialize, re-register the devmgr.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DEVMGR.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in devmgr.dll succeeded."  >Click OK. > > 2)  If Device Manager is blank and there is an "Action Cancelled" message >stating: > "Internet Explorer was unable to link to the Web page you requested. The page >might be temporarily unavailable.",  re-register the dmocx.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DMOCX.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in dmocx.dll succeeded."  >Click OK. > > 3)  A totally blank Device Manager (not showing even the computer icon and >name) can occur if the Plug and Play service is not started.  Open the Services window >and check the Status and Startup Type of that service.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If that service is not started or if its Startup Type is not set to automatic, >follow the instructions in >MS KB Art. 311504. > > 4) Review the Status and Startup Type of all of the Windows services in the >Services window.  You may find that many of the services that should be started, >are not.  If so, start those services and set their Startup Type to automatic or >manual as appropriate.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If you find a service that should be started, but is not: > •  Double-click on the service to be started. > •  On the General tab, in the Startup Type drop-down list, click on either Automatic >or Manual as appropriate (if in doubt, click on Automatic). > •  Click on the Start button. > •  Click OK. > When finished, close the Services window.  You may need to restart the computer >to effect the changes you have made to the services.  Once it appears that the computer >is operating properly, you may want to review the Windows services to see if there >are any that do not need to be started or whose Startup Type can be set to Manual >or Disabled without adversely affecting the computer's operation. > > 5)  In Control Panel --> Add/Remove Programs, check if Microsoft Windows Update >905749 is installed, and if so, uninstall it.  (That Security Update was released >10-11-05 to resolve a vulnerability in Plug and Play for Windows XP and 2000.)   >Restart the computer. > > 6)  If Device Manager shows the computer icon and name but no devices, check >that the security permissions for this registry key: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > meet these requirements: > •  the group "Everyone" should be listed and have only "Read" permissions. > •  the user "SYSTEM" should be listed and have "Full Control" and "Read" permissions. > To do this, open the registry editor (Start --> Run, type:  REGEDIT   >and hit Enter or OK). > Go to the above registry key, and right-click on the Enum key, and in the context >menu click on Permissions. > On the Security tab, review the listed group or user names and the permissions >checked for each in the "Allow" column to determine if they comply with the above >requirements.  If not, use the following instructions, or such of them as needed, >to have the listed names and their permissions meet those >requirements. > To add those names to the Security tab: > •  Click on the Add button. > •  Add the group "Everyone" and the user "SYSTEM." > To set the required permissions for those names on the Security tab: > •  Select "Everyone" and check "Read" (only) under "Allow." > •  Select "SYSTEM" and check "Full Control" under "Allow" (which also should >check "Read"). > •  Make sure there is nothing checked under "Deny" for either "SYSTEM" or "Everyone." > Then: > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes". > When finished, close the registry editor. > Note:  If at any time you get a message to the effect that the registry >editor cannot set or change security permissions in the selected key or its sub-keys, >go to the next step. > > 7)  In Control Panel --> Add/Remove Programs, check if Context Plus >or Ad Channel or POP or Apropos Client, or any combination of >those names, is installed.  If so, uninstall it or them.  (That item does not enjoy >a good reputation.)  Then review the discussion for possible additional removal >procedures (including a downloadable removal tool) at: > http://www.norton.com/avcenter/venc/data/spyware.apropos.html > When done, restart the computer. > > 8)  Apropos malware may be on the system, causing the blank or empty Device >Manager.  If so: > •  Download and save to the desktop AproposFix.exe at: > http://swandog46.geekstogo.com/aproposfix.exe > •  Reboot into safe mode (logging into the account in which you saved the downloaded >file). > •  Double or single click (whichever you use to open or run an item) on AproposFix.exe >on the desktop, which will place on the desktop an AproposFix folder. > •  Open the AproposFix folder, and double or single click on RunThis.bat  >to run it. > •  Follow the on-screen prompts.  When finished, reboot into normal mode. > •  The AproposFix folder now will have a log.txt file showing the actions >that AproposFix has taken, which should be reviewed, and saved until it is >clear that the Apropos malware has been entirely removed. > > You then should use proper procedures to scan for and remove any remaining elements >of Apropos, which is discussed at various web-sites, such as: > http://securityresponse.symantec.com/avcenter/venc/data/spyware.apropos.c.html > > 9)  One or more sub-keys under the Enum registry key may be corrupt, causing >the blank or empty Device Manager.  To check for and remedy corrupt sub-keys: > •  Open the registry editor (Start --> Run, type:  REGEDIT   and hit >Enter or OK)  and go to: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > •  Expand the Enum key, and examine each sub-key under it for a name that is >a seemingly random, disorderly combination of characters and symbols, e.g.:   $%^&*()24031 >  (or longer), with little resemblance to the other sub-keys, and perhaps having >no values in the right-hand pane.  There may be under the Enum key consecutive sub-keys >with such garbled names, each one being longer than the prior one.  These corrupt >sub-keys should be deleted. > > Note:  before deleting any registry keys or sub-keys, first back-up the >entire Enum key by right-clicking on it, then click on Export, select where to save >it, and click on Save.  In addition, similarly back-up each sub-key that you intend >to delete. > > If upon trying to delete a corrupt sub-key, you get a message that the deletion >cannot be accomplished for lack of permission, increase the permissions for the corrupt >sub-key before deleting it, as follows: > > •  Right-click on the corrupt sub-key and in the context menu click on Permissions. > •  On the Security tab, select "Everyone" and check "Full Control" under "Allow."  >If "Everyone" is not there listed, click on the Add button and add the group "Everyone," >and then select it and check "Full Control" under "Allow."   If "Everyone" cannot >be added, add the group "Administrators" for whom check "Full Control" under "Allow." > •  Make sure there is nothing checked under "Deny" for "Everyone" or "Administrators." > > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes" > •  Then delete the corrupt sub-key. > > When finished, close the registry editor. > > As corruption of the registry might have been caused by a virus or malware, you >should use proper procedures to scan for and remove vires and malware from the system. > > [Reply or follow-up to this message] re: Blank or Empty Device Manager in Windows XP - A Compilation of Solutions Friday, January 30, 2009 at 8:36 am Posted by Oki Bayu (1 messages posted) Hi, Thanks for the solutions and i was fixed my device manager :D... On Thursday, December 8, 2005 at 6:23 pm, jcw wrote: > >The following has been distilled from various sources, notably messages posted in >a lengthy thread in this forum spanning well over two years at: > »   http://www.annoyances.org/exec/forum/winxp/1051715405 > Credit is to be given to those who provided these solutions, and those who endured >the trial and error in remedying a blank or empty Device Manager and took the time >to post their results. > > Readers are encouraged to "book-mark" this web-page for future reference for users >experiencing a blank or empty Device Manager in Windows XP. > > > Begin with the first potential solution below, and proceed with each subsequent >solution, after each opening Device Manager to see if it properly displays devices.  >Some solutions may not apply to your situation, e.g. the first and second solutions >that apply if you are getting the error messages there described. > To undertake these procedures, be logged-in with full administrative powers. > > 1)  If Device Manager is blank and there is an error message that the Device >Manager Snap-in failed to initialize, re-register the devmgr.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DEVMGR.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in devmgr.dll succeeded."  >Click OK. > > 2)  If Device Manager is blank and there is an "Action Cancelled" message >stating: > "Internet Explorer was unable to link to the Web page you requested. The page >might be temporarily unavailable.",  re-register the dmocx.dll file as follows: > •  Close all open programs. > •  Start --> Run, and type:   REGSVR32 DMOCX.DLL   and hit Enter or >OK. > •  You should get this message:  "DllRegisterServer in dmocx.dll succeeded."  >Click OK. > > 3)  A totally blank Device Manager (not showing even the computer icon and >name) can occur if the Plug and Play service is not started.  Open the Services window >and check the Status and Startup Type of that service.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If that service is not started or if its Startup Type is not set to automatic, >follow the instructions in >MS KB Art. 311504. > > 4) Review the Status and Startup Type of all of the Windows services in the >Services window.  You may find that many of the services that should be started, >are not.  If so, start those services and set their Startup Type to automatic or >manual as appropriate.  To open the Services window: > Start --> Run, type:  SERVICES.MSC   and hit Enter or OK. > If you find a service that should be started, but is not: > •  Double-click on the service to be started. > •  On the General tab, in the Startup Type drop-down list, click on either Automatic >or Manual as appropriate (if in doubt, click on Automatic). > •  Click on the Start button. > •  Click OK. > When finished, close the Services window.  You may need to restart the computer >to effect the changes you have made to the services.  Once it appears that the computer >is operating properly, you may want to review the Windows services to see if there >are any that do not need to be started or whose Startup Type can be set to Manual >or Disabled without adversely affecting the computer's operation. > > 5)  In Control Panel --> Add/Remove Programs, check if Microsoft Windows Update >905749 is installed, and if so, uninstall it.  (That Security Update was released >10-11-05 to resolve a vulnerability in Plug and Play for Windows XP and 2000.)   >Restart the computer. > > 6)  If Device Manager shows the computer icon and name but no devices, check >that the security permissions for this registry key: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > meet these requirements: > •  the group "Everyone" should be listed and have only "Read" permissions. > •  the user "SYSTEM" should be listed and have "Full Control" and "Read" permissions. > To do this, open the registry editor (Start --> Run, type:  REGEDIT   >and hit Enter or OK). > Go to the above registry key, and right-click on the Enum key, and in the context >menu click on Permissions. > On the Security tab, review the listed group or user names and the permissions >checked for each in the "Allow" column to determine if they comply with the above >requirements.  If not, use the following instructions, or such of them as needed, >to have the listed names and their permissions meet those >requirements. > To add those names to the Security tab: > •  Click on the Add button. > •  Add the group "Everyone" and the user "SYSTEM." > To set the required permissions for those names on the Security tab: > •  Select "Everyone" and check "Read" (only) under "Allow." > •  Select "SYSTEM" and check "Full Control" under "Allow" (which also should >check "Read"). > •  Make sure there is nothing checked under "Deny" for either "SYSTEM" or "Everyone." > Then: > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes". > When finished, close the registry editor. > Note:  If at any time you get a message to the effect that the registry >editor cannot set or change security permissions in the selected key or its sub-keys, >go to the next step. > > 7)  In Control Panel --> Add/Remove Programs, check if Context Plus >or Ad Channel or POP or Apropos Client, or any combination of >those names, is installed.  If so, uninstall it or them.  (That item does not enjoy >a good reputation.)  Then review the discussion for possible additional removal >procedures (including a downloadable removal tool) at: > http://www.norton.com/avcenter/venc/data/spyware.apropos.html > When done, restart the computer. > > 8)  Apropos malware may be on the system, causing the blank or empty Device >Manager.  If so: > •  Download and save to the desktop AproposFix.exe at: > http://swandog46.geekstogo.com/aproposfix.exe > •  Reboot into safe mode (logging into the account in which you saved the downloaded >file). > •  Double or single click (whichever you use to open or run an item) on AproposFix.exe >on the desktop, which will place on the desktop an AproposFix folder. > •  Open the AproposFix folder, and double or single click on RunThis.bat  >to run it. > •  Follow the on-screen prompts.  When finished, reboot into normal mode. > •  The AproposFix folder now will have a log.txt file showing the actions >that AproposFix has taken, which should be reviewed, and saved until it is >clear that the Apropos malware has been entirely removed. > > You then should use proper procedures to scan for and remove any remaining elements >of Apropos, which is discussed at various web-sites, such as: > http://securityresponse.symantec.com/avcenter/venc/data/spyware.apropos.c.html > > 9)  One or more sub-keys under the Enum registry key may be corrupt, causing >the blank or empty Device Manager.  To check for and remedy corrupt sub-keys: > •  Open the registry editor (Start --> Run, type:  REGEDIT   and hit >Enter or OK)  and go to: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum > •  Expand the Enum key, and examine each sub-key under it for a name that is >a seemingly random, disorderly combination of characters and symbols, e.g.:   $%^&*()24031 >  (or longer), with little resemblance to the other sub-keys, and perhaps having >no values in the right-hand pane.  There may be under the Enum key consecutive sub-keys >with such garbled names, each one being longer than the prior one.  These corrupt >sub-keys should be deleted. > > Note:  before deleting any registry keys or sub-keys, first back-up the >entire Enum key by right-clicking on it, then click on Export, select where to save >it, and click on Save.  In addition, similarly back-up each sub-key that you intend >to delete. > > If upon trying to delete a corrupt sub-key, you get a message that the deletion >cannot be accomplished for lack of permission, increase the permissions for the corrupt >sub-key before deleting it, as follows: > > •  Right-click on the corrupt sub-key and in the context menu click on Permissions. > •  On the Security tab, select "Everyone" and check "Full Control" under "Allow."  >If "Everyone" is not there listed, click on the Add button and add the group "Everyone," >and then select it and check "Full Control" under "Allow."   If "Everyone" cannot >be added, add the group "Administrators" for whom check "Full Control" under "Allow." > •  Make sure there is nothing checked under "Deny" for "Everyone" or "Administrators." > > •  Click on the Advanced button, and on the Permissions tab in the Advanced box >check "Replace permission entries on all child objects with . . . ." > •  Click OK, and on any warning box click "Yes" > •  Then delete the corrupt sub-key. > > When finished, close the registry editor. > > As corruption of the registry might have been caused by a virus or malware, you >should use proper procedures to scan for and remove vires and malware from the system. > > [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum