Registry key disappears after a while The 2019 Stack Overflow Developer Survey Results Are...

How did the audience guess the pentatonic scale in Bobby McFerrin's presentation?

High Q peak in frequency response means what in time domain?

Simulating Exploding Dice

Simulation of a banking system with an Account class in C++

Wall plug outlet change

system() function string length limit

What do you call a plan that's an alternative plan in case your initial plan fails?

Mortgage adviser recommends a longer term than necessary combined with overpayments

How is simplicity better than precision and clarity in prose?

Did the new image of black hole confirm the general theory of relativity?

ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?

Difference between "generating set" and free product?

Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?

What are these Gizmos at Izaña Atmospheric Research Center in Spain?

Can the prologue be the backstory of your main character?

Take groceries in checked luggage

Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?

Am I ethically obligated to go into work on an off day if the reason is sudden?

Can the DM override racial traits?

First use of “packing” as in carrying a gun

Would an alien lifeform be able to achieve space travel if lacking in vision?

Wolves and sheep

Are my PIs rude or am I just being too sensitive?

Does Parliament hold absolute power in the UK?



Registry key disappears after a while



The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Printer options follow Office documentsCannot Create Key: Error Writing to the Windows 7 RegistryWindows box occasionally repeating key “a” endlesslyWord 2010 - Registry Key for AutoCorrect OptionsUnable to delete registry keyEditing registry for the error - One of your object libraries (I) is missing or damaged. Please run setup to install itMS Office 2013 refers to old file serverChange Windows permissions on single registry keyHow to recover lost Microsoft Office 2013 Product Key after Windows 10 Reset PC'Microsoft Access Database' persists in 'Create New' Explorer menu after deleting .accdb ShellNew registry key





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















One of my users has had a problem in the past when printing documents from Office 2012. After attempting to print, she got the message that the printer could not be found. Apparently, the cause of this was Office 2012, which would prevent printing after it detected a problem.



I found a solution in the following link: https://support.microsoft.com/en-us/help/983035/how-to-prevent-office-2010-from-disabling-printers . I added the registry key "DisablePrintFeaturesOnCrash" under HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0CommonGeneral and set it to 0, which seemed to solve the problems she was having.



Flash forward a couple of months, and I got a call from her telling me that the problem had resurfaced. After checking the registry, I found out that the registry key was gone. I added it again, and she could print again.



A few days later however, the registry key has disappeared again! She herself cannot remove the key (she can't access the registry), and none of my colleagues has touched that computer in weeks.



What could possibly remove that key? Is there a way to find out what process removed that key? And is it possible to prevent deletion of the key?



Thanks!










share|improve this question





























    0















    One of my users has had a problem in the past when printing documents from Office 2012. After attempting to print, she got the message that the printer could not be found. Apparently, the cause of this was Office 2012, which would prevent printing after it detected a problem.



    I found a solution in the following link: https://support.microsoft.com/en-us/help/983035/how-to-prevent-office-2010-from-disabling-printers . I added the registry key "DisablePrintFeaturesOnCrash" under HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0CommonGeneral and set it to 0, which seemed to solve the problems she was having.



    Flash forward a couple of months, and I got a call from her telling me that the problem had resurfaced. After checking the registry, I found out that the registry key was gone. I added it again, and she could print again.



    A few days later however, the registry key has disappeared again! She herself cannot remove the key (she can't access the registry), and none of my colleagues has touched that computer in weeks.



    What could possibly remove that key? Is there a way to find out what process removed that key? And is it possible to prevent deletion of the key?



    Thanks!










    share|improve this question

























      0












      0








      0








      One of my users has had a problem in the past when printing documents from Office 2012. After attempting to print, she got the message that the printer could not be found. Apparently, the cause of this was Office 2012, which would prevent printing after it detected a problem.



      I found a solution in the following link: https://support.microsoft.com/en-us/help/983035/how-to-prevent-office-2010-from-disabling-printers . I added the registry key "DisablePrintFeaturesOnCrash" under HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0CommonGeneral and set it to 0, which seemed to solve the problems she was having.



      Flash forward a couple of months, and I got a call from her telling me that the problem had resurfaced. After checking the registry, I found out that the registry key was gone. I added it again, and she could print again.



      A few days later however, the registry key has disappeared again! She herself cannot remove the key (she can't access the registry), and none of my colleagues has touched that computer in weeks.



      What could possibly remove that key? Is there a way to find out what process removed that key? And is it possible to prevent deletion of the key?



      Thanks!










      share|improve this question














      One of my users has had a problem in the past when printing documents from Office 2012. After attempting to print, she got the message that the printer could not be found. Apparently, the cause of this was Office 2012, which would prevent printing after it detected a problem.



      I found a solution in the following link: https://support.microsoft.com/en-us/help/983035/how-to-prevent-office-2010-from-disabling-printers . I added the registry key "DisablePrintFeaturesOnCrash" under HKEY_CURRENT_USERSoftwareMicrosoftOffice14.0CommonGeneral and set it to 0, which seemed to solve the problems she was having.



      Flash forward a couple of months, and I got a call from her telling me that the problem had resurfaced. After checking the registry, I found out that the registry key was gone. I added it again, and she could print again.



      A few days later however, the registry key has disappeared again! She herself cannot remove the key (she can't access the registry), and none of my colleagues has touched that computer in weeks.



      What could possibly remove that key? Is there a way to find out what process removed that key? And is it possible to prevent deletion of the key?



      Thanks!







      windows-7 microsoft-office windows-registry printing






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked yesterday









      JoeJoe

      54




      54






















          1 Answer
          1






          active

          oldest

          votes


















          0














          You must enable auditing to track changes with the registry, though you must specify an object to audit. To do this in the registry, right click a key, select permissions, advanced, auditing -> then add the object in here that you'd like to audit, and the actions that the object has taken that you want to track. You will then see the specified changes to the key made by the object in event viewer under windows logs -> Security.



          Because you are trying to track changes for an object you do not know (the cause of the registry key removal), it would be best to check permissions on the key just to see what has access to delete it. If there are no permissions in there that you were not expecting, then I suspect it was the application itself. The registry entries can be updated or regenerated following an application update, depending on how the application update is designed to interact with the registry (in this case I assume regenerate as your custom key is being deleted). I would not recommend amending the permissions on these keys as you could consequently then receive application errors.



          Therefore, if you have noticed that the issue has arisen when the user first tries to print on a given day, a logon group policy to import your custom registry key should suffice. However, if you notice that the issue can happen suddenly, i.e. the user can print a number of times, then suddenly it stops working- then you would need to manually intervene unfortunately. I would have suggested to give the user access to import their own registry key (through a .reg file) though if the registry key IS being regenerated then her permissions will also be removed making that suggestion unreliable. These are proposed solely on the symptoms you have stated.






          share|improve this answer
























            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%2f1424584%2fregistry-key-disappears-after-a-while%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            You must enable auditing to track changes with the registry, though you must specify an object to audit. To do this in the registry, right click a key, select permissions, advanced, auditing -> then add the object in here that you'd like to audit, and the actions that the object has taken that you want to track. You will then see the specified changes to the key made by the object in event viewer under windows logs -> Security.



            Because you are trying to track changes for an object you do not know (the cause of the registry key removal), it would be best to check permissions on the key just to see what has access to delete it. If there are no permissions in there that you were not expecting, then I suspect it was the application itself. The registry entries can be updated or regenerated following an application update, depending on how the application update is designed to interact with the registry (in this case I assume regenerate as your custom key is being deleted). I would not recommend amending the permissions on these keys as you could consequently then receive application errors.



            Therefore, if you have noticed that the issue has arisen when the user first tries to print on a given day, a logon group policy to import your custom registry key should suffice. However, if you notice that the issue can happen suddenly, i.e. the user can print a number of times, then suddenly it stops working- then you would need to manually intervene unfortunately. I would have suggested to give the user access to import their own registry key (through a .reg file) though if the registry key IS being regenerated then her permissions will also be removed making that suggestion unreliable. These are proposed solely on the symptoms you have stated.






            share|improve this answer




























              0














              You must enable auditing to track changes with the registry, though you must specify an object to audit. To do this in the registry, right click a key, select permissions, advanced, auditing -> then add the object in here that you'd like to audit, and the actions that the object has taken that you want to track. You will then see the specified changes to the key made by the object in event viewer under windows logs -> Security.



              Because you are trying to track changes for an object you do not know (the cause of the registry key removal), it would be best to check permissions on the key just to see what has access to delete it. If there are no permissions in there that you were not expecting, then I suspect it was the application itself. The registry entries can be updated or regenerated following an application update, depending on how the application update is designed to interact with the registry (in this case I assume regenerate as your custom key is being deleted). I would not recommend amending the permissions on these keys as you could consequently then receive application errors.



              Therefore, if you have noticed that the issue has arisen when the user first tries to print on a given day, a logon group policy to import your custom registry key should suffice. However, if you notice that the issue can happen suddenly, i.e. the user can print a number of times, then suddenly it stops working- then you would need to manually intervene unfortunately. I would have suggested to give the user access to import their own registry key (through a .reg file) though if the registry key IS being regenerated then her permissions will also be removed making that suggestion unreliable. These are proposed solely on the symptoms you have stated.






              share|improve this answer


























                0












                0








                0







                You must enable auditing to track changes with the registry, though you must specify an object to audit. To do this in the registry, right click a key, select permissions, advanced, auditing -> then add the object in here that you'd like to audit, and the actions that the object has taken that you want to track. You will then see the specified changes to the key made by the object in event viewer under windows logs -> Security.



                Because you are trying to track changes for an object you do not know (the cause of the registry key removal), it would be best to check permissions on the key just to see what has access to delete it. If there are no permissions in there that you were not expecting, then I suspect it was the application itself. The registry entries can be updated or regenerated following an application update, depending on how the application update is designed to interact with the registry (in this case I assume regenerate as your custom key is being deleted). I would not recommend amending the permissions on these keys as you could consequently then receive application errors.



                Therefore, if you have noticed that the issue has arisen when the user first tries to print on a given day, a logon group policy to import your custom registry key should suffice. However, if you notice that the issue can happen suddenly, i.e. the user can print a number of times, then suddenly it stops working- then you would need to manually intervene unfortunately. I would have suggested to give the user access to import their own registry key (through a .reg file) though if the registry key IS being regenerated then her permissions will also be removed making that suggestion unreliable. These are proposed solely on the symptoms you have stated.






                share|improve this answer













                You must enable auditing to track changes with the registry, though you must specify an object to audit. To do this in the registry, right click a key, select permissions, advanced, auditing -> then add the object in here that you'd like to audit, and the actions that the object has taken that you want to track. You will then see the specified changes to the key made by the object in event viewer under windows logs -> Security.



                Because you are trying to track changes for an object you do not know (the cause of the registry key removal), it would be best to check permissions on the key just to see what has access to delete it. If there are no permissions in there that you were not expecting, then I suspect it was the application itself. The registry entries can be updated or regenerated following an application update, depending on how the application update is designed to interact with the registry (in this case I assume regenerate as your custom key is being deleted). I would not recommend amending the permissions on these keys as you could consequently then receive application errors.



                Therefore, if you have noticed that the issue has arisen when the user first tries to print on a given day, a logon group policy to import your custom registry key should suffice. However, if you notice that the issue can happen suddenly, i.e. the user can print a number of times, then suddenly it stops working- then you would need to manually intervene unfortunately. I would have suggested to give the user access to import their own registry key (through a .reg file) though if the registry key IS being regenerated then her permissions will also be removed making that suggestion unreliable. These are proposed solely on the symptoms you have stated.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered yesterday









                RhysPickettRhysPickett

                586




                586






























                    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.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1424584%2fregistry-key-disappears-after-a-while%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

                    Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

                    VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                    Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...