Proper way to remove an old driver from %systemroot%system32drivers

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












6














Recently I was trying to find why out Windows 10 updates were failing on my computer. The Driver Verifier utility indicated a problem with dcrypt.sys, a file that had been left in %systemroot%system32drivers even after I had uninstalled DiskCryptor several years ago.



I made the mistake of deleting dcrypt.sys myself, but when I did that, Windows stopped loading. My inference is that, despite its being third party software, its presence was somehow required by the Windows startup sequence. (I ended up solving this by reinstalling Windows completely.)



What would have been the proper way to get rid of such a file?










share|improve this question




























    6














    Recently I was trying to find why out Windows 10 updates were failing on my computer. The Driver Verifier utility indicated a problem with dcrypt.sys, a file that had been left in %systemroot%system32drivers even after I had uninstalled DiskCryptor several years ago.



    I made the mistake of deleting dcrypt.sys myself, but when I did that, Windows stopped loading. My inference is that, despite its being third party software, its presence was somehow required by the Windows startup sequence. (I ended up solving this by reinstalling Windows completely.)



    What would have been the proper way to get rid of such a file?










    share|improve this question


























      6












      6








      6


      2





      Recently I was trying to find why out Windows 10 updates were failing on my computer. The Driver Verifier utility indicated a problem with dcrypt.sys, a file that had been left in %systemroot%system32drivers even after I had uninstalled DiskCryptor several years ago.



      I made the mistake of deleting dcrypt.sys myself, but when I did that, Windows stopped loading. My inference is that, despite its being third party software, its presence was somehow required by the Windows startup sequence. (I ended up solving this by reinstalling Windows completely.)



      What would have been the proper way to get rid of such a file?










      share|improve this question















      Recently I was trying to find why out Windows 10 updates were failing on my computer. The Driver Verifier utility indicated a problem with dcrypt.sys, a file that had been left in %systemroot%system32drivers even after I had uninstalled DiskCryptor several years ago.



      I made the mistake of deleting dcrypt.sys myself, but when I did that, Windows stopped loading. My inference is that, despite its being third party software, its presence was somehow required by the Windows startup sequence. (I ended up solving this by reinstalling Windows completely.)



      What would have been the proper way to get rid of such a file?







      windows drivers system32






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 15 at 18:20









      Twisty Impersonator

      17.7k136395




      17.7k136395










      asked Dec 15 at 14:34









      adam.baker

      1333




      1333




















          3 Answers
          3






          active

          oldest

          votes


















          10














          If you prefer a GUI method, use Microsoft's Autoruns for Windows. It requires no installation. Simply run it elevated, then navigate to the Drivers tab, clear the checkmark next to the driver you wish to disable, then reboot the computer:



          enter image description here



          Not only is this a simple way to enable/disable drivers and services (along with pretty much anything else that starts automatically in Windows), but it's very easy to undo changes if you find they have unwanted consequences or you're simply experimenting with your configuration.



          By the way, the next time you disable a critical startup item and Windows will not boot, try using System Restore. It is capable of restoring the driver file you deleted as well as any Registry settings you might change (including changed made by Autoruns) in an effort to disable it.



          Windows automatically creates Restore Points when certain critical actions are about to be taken (such as before installing Updates), but it's a good idea to create one manually before making changes to important startup items. And if your system fails to boot and you need to use a Restore Point, here are directions on how to do that.






          share|improve this answer






























            2














            Start regedit. In the left pane, navigate to:



            HKEY_LOCAL_MACHINESystemCurrentControlSetServices


            Now look for a subkey under services called dcrypt.



            • If it’s not there, look for something of a similar name, like dskcrypt.


            • If you still can’t find it, use regedit’s Find command to search for dcrypt.sys in
              a subkey under Services. The string dcrypt.sys should be in a value called
              ImagePath.


            When you find the key, navigate to it and check that you do indeed see
            ImagePath: ...dcrypt.sys in the right pane. Now double-click the value
            called Start and change it to 4, which means Disabled.



            That should do it.






            share|improve this answer






























              1














              Apparently /enum-drivers is a windows 10 option and not windows 7 or 8.1



              In Windows 7 and 8.1 its just -e not --enum-drivers



              From and administrative command prompt:



              pnputil /enum-drivers


              Find the driver on the list, get the name of the INF file.



              pnputil /delete-driver oem0.inf


              Windows 7,8.1



              pnputil -d oem0.inf


              change oem0.inf to whatever you discovered windows named it in the step above.



              If windows was broken and didn't start.



              Boot off the windows install media



              Use F10 (or maybe F8) to get to a command prompt



              do a dir command on each letter until you find the windows folder.



              dir c:
              dir d:
              dir e:
              ....



              Find the offending driver.



              dism /image:d: /Get-Drivers


              replace something.inf with the offending driver name.



              dism /image:d: /remove-driver /driver:something.inf





              share|improve this answer






















              • you can test it yourself developer.microsoft.com/en-us/microsoft-edge/tools/vms - in the meantime please update to reflect that this is windows 10 only - as it doesnt work on windows 8.1 either
                – Steven Penny
                Dec 16 at 17:36










              • @StevenPenny updated answer based on results from a Windows 7 vm.
                – cybernard
                Dec 18 at 15:31










              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "3"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1384835%2fproper-way-to-remove-an-old-driver-from-systemroot-system32-drivers%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              10














              If you prefer a GUI method, use Microsoft's Autoruns for Windows. It requires no installation. Simply run it elevated, then navigate to the Drivers tab, clear the checkmark next to the driver you wish to disable, then reboot the computer:



              enter image description here



              Not only is this a simple way to enable/disable drivers and services (along with pretty much anything else that starts automatically in Windows), but it's very easy to undo changes if you find they have unwanted consequences or you're simply experimenting with your configuration.



              By the way, the next time you disable a critical startup item and Windows will not boot, try using System Restore. It is capable of restoring the driver file you deleted as well as any Registry settings you might change (including changed made by Autoruns) in an effort to disable it.



              Windows automatically creates Restore Points when certain critical actions are about to be taken (such as before installing Updates), but it's a good idea to create one manually before making changes to important startup items. And if your system fails to boot and you need to use a Restore Point, here are directions on how to do that.






              share|improve this answer



























                10














                If you prefer a GUI method, use Microsoft's Autoruns for Windows. It requires no installation. Simply run it elevated, then navigate to the Drivers tab, clear the checkmark next to the driver you wish to disable, then reboot the computer:



                enter image description here



                Not only is this a simple way to enable/disable drivers and services (along with pretty much anything else that starts automatically in Windows), but it's very easy to undo changes if you find they have unwanted consequences or you're simply experimenting with your configuration.



                By the way, the next time you disable a critical startup item and Windows will not boot, try using System Restore. It is capable of restoring the driver file you deleted as well as any Registry settings you might change (including changed made by Autoruns) in an effort to disable it.



                Windows automatically creates Restore Points when certain critical actions are about to be taken (such as before installing Updates), but it's a good idea to create one manually before making changes to important startup items. And if your system fails to boot and you need to use a Restore Point, here are directions on how to do that.






                share|improve this answer

























                  10












                  10








                  10






                  If you prefer a GUI method, use Microsoft's Autoruns for Windows. It requires no installation. Simply run it elevated, then navigate to the Drivers tab, clear the checkmark next to the driver you wish to disable, then reboot the computer:



                  enter image description here



                  Not only is this a simple way to enable/disable drivers and services (along with pretty much anything else that starts automatically in Windows), but it's very easy to undo changes if you find they have unwanted consequences or you're simply experimenting with your configuration.



                  By the way, the next time you disable a critical startup item and Windows will not boot, try using System Restore. It is capable of restoring the driver file you deleted as well as any Registry settings you might change (including changed made by Autoruns) in an effort to disable it.



                  Windows automatically creates Restore Points when certain critical actions are about to be taken (such as before installing Updates), but it's a good idea to create one manually before making changes to important startup items. And if your system fails to boot and you need to use a Restore Point, here are directions on how to do that.






                  share|improve this answer














                  If you prefer a GUI method, use Microsoft's Autoruns for Windows. It requires no installation. Simply run it elevated, then navigate to the Drivers tab, clear the checkmark next to the driver you wish to disable, then reboot the computer:



                  enter image description here



                  Not only is this a simple way to enable/disable drivers and services (along with pretty much anything else that starts automatically in Windows), but it's very easy to undo changes if you find they have unwanted consequences or you're simply experimenting with your configuration.



                  By the way, the next time you disable a critical startup item and Windows will not boot, try using System Restore. It is capable of restoring the driver file you deleted as well as any Registry settings you might change (including changed made by Autoruns) in an effort to disable it.



                  Windows automatically creates Restore Points when certain critical actions are about to be taken (such as before installing Updates), but it's a good idea to create one manually before making changes to important startup items. And if your system fails to boot and you need to use a Restore Point, here are directions on how to do that.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Dec 15 at 18:30

























                  answered Dec 15 at 18:15









                  Twisty Impersonator

                  17.7k136395




                  17.7k136395























                      2














                      Start regedit. In the left pane, navigate to:



                      HKEY_LOCAL_MACHINESystemCurrentControlSetServices


                      Now look for a subkey under services called dcrypt.



                      • If it’s not there, look for something of a similar name, like dskcrypt.


                      • If you still can’t find it, use regedit’s Find command to search for dcrypt.sys in
                        a subkey under Services. The string dcrypt.sys should be in a value called
                        ImagePath.


                      When you find the key, navigate to it and check that you do indeed see
                      ImagePath: ...dcrypt.sys in the right pane. Now double-click the value
                      called Start and change it to 4, which means Disabled.



                      That should do it.






                      share|improve this answer



























                        2














                        Start regedit. In the left pane, navigate to:



                        HKEY_LOCAL_MACHINESystemCurrentControlSetServices


                        Now look for a subkey under services called dcrypt.



                        • If it’s not there, look for something of a similar name, like dskcrypt.


                        • If you still can’t find it, use regedit’s Find command to search for dcrypt.sys in
                          a subkey under Services. The string dcrypt.sys should be in a value called
                          ImagePath.


                        When you find the key, navigate to it and check that you do indeed see
                        ImagePath: ...dcrypt.sys in the right pane. Now double-click the value
                        called Start and change it to 4, which means Disabled.



                        That should do it.






                        share|improve this answer

























                          2












                          2








                          2






                          Start regedit. In the left pane, navigate to:



                          HKEY_LOCAL_MACHINESystemCurrentControlSetServices


                          Now look for a subkey under services called dcrypt.



                          • If it’s not there, look for something of a similar name, like dskcrypt.


                          • If you still can’t find it, use regedit’s Find command to search for dcrypt.sys in
                            a subkey under Services. The string dcrypt.sys should be in a value called
                            ImagePath.


                          When you find the key, navigate to it and check that you do indeed see
                          ImagePath: ...dcrypt.sys in the right pane. Now double-click the value
                          called Start and change it to 4, which means Disabled.



                          That should do it.






                          share|improve this answer














                          Start regedit. In the left pane, navigate to:



                          HKEY_LOCAL_MACHINESystemCurrentControlSetServices


                          Now look for a subkey under services called dcrypt.



                          • If it’s not there, look for something of a similar name, like dskcrypt.


                          • If you still can’t find it, use regedit’s Find command to search for dcrypt.sys in
                            a subkey under Services. The string dcrypt.sys should be in a value called
                            ImagePath.


                          When you find the key, navigate to it and check that you do indeed see
                          ImagePath: ...dcrypt.sys in the right pane. Now double-click the value
                          called Start and change it to 4, which means Disabled.



                          That should do it.







                          share|improve this answer














                          share|improve this answer



                          share|improve this answer








                          edited Dec 15 at 21:23

























                          answered Dec 15 at 14:45









                          Jamie Hanrahan

                          17.8k34078




                          17.8k34078





















                              1














                              Apparently /enum-drivers is a windows 10 option and not windows 7 or 8.1



                              In Windows 7 and 8.1 its just -e not --enum-drivers



                              From and administrative command prompt:



                              pnputil /enum-drivers


                              Find the driver on the list, get the name of the INF file.



                              pnputil /delete-driver oem0.inf


                              Windows 7,8.1



                              pnputil -d oem0.inf


                              change oem0.inf to whatever you discovered windows named it in the step above.



                              If windows was broken and didn't start.



                              Boot off the windows install media



                              Use F10 (or maybe F8) to get to a command prompt



                              do a dir command on each letter until you find the windows folder.



                              dir c:
                              dir d:
                              dir e:
                              ....



                              Find the offending driver.



                              dism /image:d: /Get-Drivers


                              replace something.inf with the offending driver name.



                              dism /image:d: /remove-driver /driver:something.inf





                              share|improve this answer






















                              • you can test it yourself developer.microsoft.com/en-us/microsoft-edge/tools/vms - in the meantime please update to reflect that this is windows 10 only - as it doesnt work on windows 8.1 either
                                – Steven Penny
                                Dec 16 at 17:36










                              • @StevenPenny updated answer based on results from a Windows 7 vm.
                                – cybernard
                                Dec 18 at 15:31















                              1














                              Apparently /enum-drivers is a windows 10 option and not windows 7 or 8.1



                              In Windows 7 and 8.1 its just -e not --enum-drivers



                              From and administrative command prompt:



                              pnputil /enum-drivers


                              Find the driver on the list, get the name of the INF file.



                              pnputil /delete-driver oem0.inf


                              Windows 7,8.1



                              pnputil -d oem0.inf


                              change oem0.inf to whatever you discovered windows named it in the step above.



                              If windows was broken and didn't start.



                              Boot off the windows install media



                              Use F10 (or maybe F8) to get to a command prompt



                              do a dir command on each letter until you find the windows folder.



                              dir c:
                              dir d:
                              dir e:
                              ....



                              Find the offending driver.



                              dism /image:d: /Get-Drivers


                              replace something.inf with the offending driver name.



                              dism /image:d: /remove-driver /driver:something.inf





                              share|improve this answer






















                              • you can test it yourself developer.microsoft.com/en-us/microsoft-edge/tools/vms - in the meantime please update to reflect that this is windows 10 only - as it doesnt work on windows 8.1 either
                                – Steven Penny
                                Dec 16 at 17:36










                              • @StevenPenny updated answer based on results from a Windows 7 vm.
                                – cybernard
                                Dec 18 at 15:31













                              1












                              1








                              1






                              Apparently /enum-drivers is a windows 10 option and not windows 7 or 8.1



                              In Windows 7 and 8.1 its just -e not --enum-drivers



                              From and administrative command prompt:



                              pnputil /enum-drivers


                              Find the driver on the list, get the name of the INF file.



                              pnputil /delete-driver oem0.inf


                              Windows 7,8.1



                              pnputil -d oem0.inf


                              change oem0.inf to whatever you discovered windows named it in the step above.



                              If windows was broken and didn't start.



                              Boot off the windows install media



                              Use F10 (or maybe F8) to get to a command prompt



                              do a dir command on each letter until you find the windows folder.



                              dir c:
                              dir d:
                              dir e:
                              ....



                              Find the offending driver.



                              dism /image:d: /Get-Drivers


                              replace something.inf with the offending driver name.



                              dism /image:d: /remove-driver /driver:something.inf





                              share|improve this answer














                              Apparently /enum-drivers is a windows 10 option and not windows 7 or 8.1



                              In Windows 7 and 8.1 its just -e not --enum-drivers



                              From and administrative command prompt:



                              pnputil /enum-drivers


                              Find the driver on the list, get the name of the INF file.



                              pnputil /delete-driver oem0.inf


                              Windows 7,8.1



                              pnputil -d oem0.inf


                              change oem0.inf to whatever you discovered windows named it in the step above.



                              If windows was broken and didn't start.



                              Boot off the windows install media



                              Use F10 (or maybe F8) to get to a command prompt



                              do a dir command on each letter until you find the windows folder.



                              dir c:
                              dir d:
                              dir e:
                              ....



                              Find the offending driver.



                              dism /image:d: /Get-Drivers


                              replace something.inf with the offending driver name.



                              dism /image:d: /remove-driver /driver:something.inf






                              share|improve this answer














                              share|improve this answer



                              share|improve this answer








                              edited Dec 18 at 15:30

























                              answered Dec 15 at 14:44









                              cybernard

                              9,95431525




                              9,95431525











                              • you can test it yourself developer.microsoft.com/en-us/microsoft-edge/tools/vms - in the meantime please update to reflect that this is windows 10 only - as it doesnt work on windows 8.1 either
                                – Steven Penny
                                Dec 16 at 17:36










                              • @StevenPenny updated answer based on results from a Windows 7 vm.
                                – cybernard
                                Dec 18 at 15:31
















                              • you can test it yourself developer.microsoft.com/en-us/microsoft-edge/tools/vms - in the meantime please update to reflect that this is windows 10 only - as it doesnt work on windows 8.1 either
                                – Steven Penny
                                Dec 16 at 17:36










                              • @StevenPenny updated answer based on results from a Windows 7 vm.
                                – cybernard
                                Dec 18 at 15:31















                              you can test it yourself developer.microsoft.com/en-us/microsoft-edge/tools/vms - in the meantime please update to reflect that this is windows 10 only - as it doesnt work on windows 8.1 either
                              – Steven Penny
                              Dec 16 at 17:36




                              you can test it yourself developer.microsoft.com/en-us/microsoft-edge/tools/vms - in the meantime please update to reflect that this is windows 10 only - as it doesnt work on windows 8.1 either
                              – Steven Penny
                              Dec 16 at 17:36












                              @StevenPenny updated answer based on results from a Windows 7 vm.
                              – cybernard
                              Dec 18 at 15:31




                              @StevenPenny updated answer based on results from a Windows 7 vm.
                              – cybernard
                              Dec 18 at 15:31

















                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Super User!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1384835%2fproper-way-to-remove-an-old-driver-from-systemroot-system32-drivers%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown






                              Popular posts from this blog

                              How to check contact read email or not when send email to Individual?

                              Bahrain

                              Postfix configuration issue with fips on centos 7; mailgun relay