reagentc /enable failing with error code 3bc3, Windows Update failing with error 800F0922












0














A while back I cloned my Windows partition from my old hard drive over to a new SSD. I'm now having trouble with the latest cumulative Windows update (which is failing repeatedly with error 0x800F0922) and want to use the Windows Recovery Environment to troubleshoot.



Since I only cloned the Windows partition itself, there is currently no recovery partition, and when I tried reagentc /enable to create a new one, this fails with error code 3bc3 which translates to "The requested system device cannot be found."



What's going on and is there any way of stopping it?










share|improve this question



























    0














    A while back I cloned my Windows partition from my old hard drive over to a new SSD. I'm now having trouble with the latest cumulative Windows update (which is failing repeatedly with error 0x800F0922) and want to use the Windows Recovery Environment to troubleshoot.



    Since I only cloned the Windows partition itself, there is currently no recovery partition, and when I tried reagentc /enable to create a new one, this fails with error code 3bc3 which translates to "The requested system device cannot be found."



    What's going on and is there any way of stopping it?










    share|improve this question

























      0












      0








      0







      A while back I cloned my Windows partition from my old hard drive over to a new SSD. I'm now having trouble with the latest cumulative Windows update (which is failing repeatedly with error 0x800F0922) and want to use the Windows Recovery Environment to troubleshoot.



      Since I only cloned the Windows partition itself, there is currently no recovery partition, and when I tried reagentc /enable to create a new one, this fails with error code 3bc3 which translates to "The requested system device cannot be found."



      What's going on and is there any way of stopping it?










      share|improve this question













      A while back I cloned my Windows partition from my old hard drive over to a new SSD. I'm now having trouble with the latest cumulative Windows update (which is failing repeatedly with error 0x800F0922) and want to use the Windows Recovery Environment to troubleshoot.



      Since I only cloned the Windows partition itself, there is currently no recovery partition, and when I tried reagentc /enable to create a new one, this fails with error code 3bc3 which translates to "The requested system device cannot be found."



      What's going on and is there any way of stopping it?







      windows windows-10 uefi recovery-partition






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 15 at 3:53









      Harry Johnston

      4,38652248




      4,38652248






















          1 Answer
          1






          active

          oldest

          votes


















          0














          This will happen if the EFI partition has the wrong GPT partition type. As it turned out, this was also causing the problem with the cumulative update.



          If you are having similar issues, you can check whether this is the problem with the diskpart command. Assuming you have only one hard disk drive,



          select disk 0
          list partition


          You should see something like this:



            Partition ###  Type              Size     Offset
          ------------- ---------------- ------- -------
          Partition 1 System 500 MB 1024 KB
          Partition 2 Primary 445 GB 501 MB


          The smaller partition named "System" is the one you want, usually partition 1, so



          select partition 1
          detail partition


          And you should see something like this



          Partition 1
          Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
          Hidden : Yes
          Required: No
          Attrib : 0XC000000000000000
          Offset in Bytes: 1048576

          Volume ### Ltr Label Fs Type Size Status Info
          ---------- --- ----------- ----- ---------- ------- --------- --------
          * Volume 3 FAT32 Partition 500 MB Healthy System


          If the file system is not FAT32 then you are not looking at the right partition. It should also be Hidden, and will not usually have a drive letter assigned unless (as in the originally posted question) it has been explicitly given one for troubleshooting purposes. It might not be exactly 500MB, but should only be taking up a small fraction of the hard disk.



          The type of the EFI partition should be c12a7328-f81f-11d2-ba4b-00a0c93ec93b as shown above. If it is not, and in particular if it is ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 (see Microsoft Basic Data Partition on Wikipedia) then that is likely to be the cause of the problem.



          If the partition type is incorrect, you can fix this with the set id command,



          set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b


          The reagentc /enable command should then work, and if you are lucky, so will Windows Update.






          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%2f1383751%2freagentc-enable-failing-with-error-code-3bc3-windows-update-failing-with-error%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














            This will happen if the EFI partition has the wrong GPT partition type. As it turned out, this was also causing the problem with the cumulative update.



            If you are having similar issues, you can check whether this is the problem with the diskpart command. Assuming you have only one hard disk drive,



            select disk 0
            list partition


            You should see something like this:



              Partition ###  Type              Size     Offset
            ------------- ---------------- ------- -------
            Partition 1 System 500 MB 1024 KB
            Partition 2 Primary 445 GB 501 MB


            The smaller partition named "System" is the one you want, usually partition 1, so



            select partition 1
            detail partition


            And you should see something like this



            Partition 1
            Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
            Hidden : Yes
            Required: No
            Attrib : 0XC000000000000000
            Offset in Bytes: 1048576

            Volume ### Ltr Label Fs Type Size Status Info
            ---------- --- ----------- ----- ---------- ------- --------- --------
            * Volume 3 FAT32 Partition 500 MB Healthy System


            If the file system is not FAT32 then you are not looking at the right partition. It should also be Hidden, and will not usually have a drive letter assigned unless (as in the originally posted question) it has been explicitly given one for troubleshooting purposes. It might not be exactly 500MB, but should only be taking up a small fraction of the hard disk.



            The type of the EFI partition should be c12a7328-f81f-11d2-ba4b-00a0c93ec93b as shown above. If it is not, and in particular if it is ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 (see Microsoft Basic Data Partition on Wikipedia) then that is likely to be the cause of the problem.



            If the partition type is incorrect, you can fix this with the set id command,



            set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b


            The reagentc /enable command should then work, and if you are lucky, so will Windows Update.






            share|improve this answer


























              0














              This will happen if the EFI partition has the wrong GPT partition type. As it turned out, this was also causing the problem with the cumulative update.



              If you are having similar issues, you can check whether this is the problem with the diskpart command. Assuming you have only one hard disk drive,



              select disk 0
              list partition


              You should see something like this:



                Partition ###  Type              Size     Offset
              ------------- ---------------- ------- -------
              Partition 1 System 500 MB 1024 KB
              Partition 2 Primary 445 GB 501 MB


              The smaller partition named "System" is the one you want, usually partition 1, so



              select partition 1
              detail partition


              And you should see something like this



              Partition 1
              Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
              Hidden : Yes
              Required: No
              Attrib : 0XC000000000000000
              Offset in Bytes: 1048576

              Volume ### Ltr Label Fs Type Size Status Info
              ---------- --- ----------- ----- ---------- ------- --------- --------
              * Volume 3 FAT32 Partition 500 MB Healthy System


              If the file system is not FAT32 then you are not looking at the right partition. It should also be Hidden, and will not usually have a drive letter assigned unless (as in the originally posted question) it has been explicitly given one for troubleshooting purposes. It might not be exactly 500MB, but should only be taking up a small fraction of the hard disk.



              The type of the EFI partition should be c12a7328-f81f-11d2-ba4b-00a0c93ec93b as shown above. If it is not, and in particular if it is ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 (see Microsoft Basic Data Partition on Wikipedia) then that is likely to be the cause of the problem.



              If the partition type is incorrect, you can fix this with the set id command,



              set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b


              The reagentc /enable command should then work, and if you are lucky, so will Windows Update.






              share|improve this answer
























                0












                0








                0






                This will happen if the EFI partition has the wrong GPT partition type. As it turned out, this was also causing the problem with the cumulative update.



                If you are having similar issues, you can check whether this is the problem with the diskpart command. Assuming you have only one hard disk drive,



                select disk 0
                list partition


                You should see something like this:



                  Partition ###  Type              Size     Offset
                ------------- ---------------- ------- -------
                Partition 1 System 500 MB 1024 KB
                Partition 2 Primary 445 GB 501 MB


                The smaller partition named "System" is the one you want, usually partition 1, so



                select partition 1
                detail partition


                And you should see something like this



                Partition 1
                Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
                Hidden : Yes
                Required: No
                Attrib : 0XC000000000000000
                Offset in Bytes: 1048576

                Volume ### Ltr Label Fs Type Size Status Info
                ---------- --- ----------- ----- ---------- ------- --------- --------
                * Volume 3 FAT32 Partition 500 MB Healthy System


                If the file system is not FAT32 then you are not looking at the right partition. It should also be Hidden, and will not usually have a drive letter assigned unless (as in the originally posted question) it has been explicitly given one for troubleshooting purposes. It might not be exactly 500MB, but should only be taking up a small fraction of the hard disk.



                The type of the EFI partition should be c12a7328-f81f-11d2-ba4b-00a0c93ec93b as shown above. If it is not, and in particular if it is ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 (see Microsoft Basic Data Partition on Wikipedia) then that is likely to be the cause of the problem.



                If the partition type is incorrect, you can fix this with the set id command,



                set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b


                The reagentc /enable command should then work, and if you are lucky, so will Windows Update.






                share|improve this answer












                This will happen if the EFI partition has the wrong GPT partition type. As it turned out, this was also causing the problem with the cumulative update.



                If you are having similar issues, you can check whether this is the problem with the diskpart command. Assuming you have only one hard disk drive,



                select disk 0
                list partition


                You should see something like this:



                  Partition ###  Type              Size     Offset
                ------------- ---------------- ------- -------
                Partition 1 System 500 MB 1024 KB
                Partition 2 Primary 445 GB 501 MB


                The smaller partition named "System" is the one you want, usually partition 1, so



                select partition 1
                detail partition


                And you should see something like this



                Partition 1
                Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
                Hidden : Yes
                Required: No
                Attrib : 0XC000000000000000
                Offset in Bytes: 1048576

                Volume ### Ltr Label Fs Type Size Status Info
                ---------- --- ----------- ----- ---------- ------- --------- --------
                * Volume 3 FAT32 Partition 500 MB Healthy System


                If the file system is not FAT32 then you are not looking at the right partition. It should also be Hidden, and will not usually have a drive letter assigned unless (as in the originally posted question) it has been explicitly given one for troubleshooting purposes. It might not be exactly 500MB, but should only be taking up a small fraction of the hard disk.



                The type of the EFI partition should be c12a7328-f81f-11d2-ba4b-00a0c93ec93b as shown above. If it is not, and in particular if it is ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 (see Microsoft Basic Data Partition on Wikipedia) then that is likely to be the cause of the problem.



                If the partition type is incorrect, you can fix this with the set id command,



                set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b


                The reagentc /enable command should then work, and if you are lucky, so will Windows Update.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 15 at 3:53









                Harry Johnston

                4,38652248




                4,38652248






























                    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%2f1383751%2freagentc-enable-failing-with-error-code-3bc3-windows-update-failing-with-error%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

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                    Eduardo VII do Reino Unido