Windows 7 - Failure Configuring Windows Updates Reverting Changes Hang / stuck












2















I've done a clean install of Windows 2 weeks ago, and got 235 updates yesterday, it took roughly 2.5 hours to download them all.



When I booted back up today it was "Preparing to configure Windows" for 1 hour, and then "Failure configuring Windows Updates Reverting Changes Do not Turn off your pc" showed up



It hung / got stuck on this progress, and now whenever I boot up my PC it says "Preparing to configure Windows" for 3 seconds & then immediately goes to the "reverting changes" part.. which gets stuck immediately.



I can't spam the function keys on bootup as my keyboard will crash & not work.










share|improve this question





























    2















    I've done a clean install of Windows 2 weeks ago, and got 235 updates yesterday, it took roughly 2.5 hours to download them all.



    When I booted back up today it was "Preparing to configure Windows" for 1 hour, and then "Failure configuring Windows Updates Reverting Changes Do not Turn off your pc" showed up



    It hung / got stuck on this progress, and now whenever I boot up my PC it says "Preparing to configure Windows" for 3 seconds & then immediately goes to the "reverting changes" part.. which gets stuck immediately.



    I can't spam the function keys on bootup as my keyboard will crash & not work.










    share|improve this question



























      2












      2








      2


      2






      I've done a clean install of Windows 2 weeks ago, and got 235 updates yesterday, it took roughly 2.5 hours to download them all.



      When I booted back up today it was "Preparing to configure Windows" for 1 hour, and then "Failure configuring Windows Updates Reverting Changes Do not Turn off your pc" showed up



      It hung / got stuck on this progress, and now whenever I boot up my PC it says "Preparing to configure Windows" for 3 seconds & then immediately goes to the "reverting changes" part.. which gets stuck immediately.



      I can't spam the function keys on bootup as my keyboard will crash & not work.










      share|improve this question
















      I've done a clean install of Windows 2 weeks ago, and got 235 updates yesterday, it took roughly 2.5 hours to download them all.



      When I booted back up today it was "Preparing to configure Windows" for 1 hour, and then "Failure configuring Windows Updates Reverting Changes Do not Turn off your pc" showed up



      It hung / got stuck on this progress, and now whenever I boot up my PC it says "Preparing to configure Windows" for 3 seconds & then immediately goes to the "reverting changes" part.. which gets stuck immediately.



      I can't spam the function keys on bootup as my keyboard will crash & not work.







      windows-7 boot windows-update updates






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 12 '16 at 12:29









      DavidPostill

      105k25227262




      105k25227262










      asked May 12 '16 at 10:08









      GerwinGerwin

      14418




      14418






















          5 Answers
          5






          active

          oldest

          votes


















          3














          First download and create a bootable operating system, I'd suggest MiniXP from Hiren.



          Boot into MiniXP and run net stop wuauserv then del %systemroot%SoftwareDistributionDataStoreLogsedb.log (note this location may change when in MiniXP)



          Once this is done, reboot your PC and attempt to install the updates again - check your AV to ensure it is not restricting the install.






          share|improve this answer
























          • if you can start in Safe Mode with Command Prompt then these commands also work from there. In my case wuauserv was not started, but moving the edb.log aside fixed the update lock-up.

            – mike
            Mar 13 '18 at 8:55



















          1














          Boot into Windows recovery environment and run a system repair few times. Probably 3 times. It should fix the boot and service related issues. Alternatively, try safemode and if you can get through, you can do a system restore.



          If nothing works, please try this procedure. This also lists how you should get into the repair environment.




          1. If you are an experienced user, try booting into recovery console by pressing F8 continuously during start, click the recovery options from the boot menu.

          2. You may be prompted to choose a keyboard layout and language. You usually have no need to change these options.

          3. Click, Repair your computer.

          4. Click Next when you see the System Recovery Options dialog box.

          5. Click Cancel when you are presented with the options to recover your computer.

          6. Click View advanced options for system recovery and support.

          7. Click Command Prompt link in the next window.

          8. Navigate to the following location. *C:WindowsWinSxS* If you are on the X drive (X:/>Source) change the partition to the Windows drive. As an example, type C: and press enter to change to C and type DIR and press enter to list the folders. If you see a Windows folder, that is the system partition. You could also use diskpart but I am not going to list it here. To change to the C:WindowsWinSxS try the following commands. I am listing the basic method here.
            cd windows
            cd WinSxS

          9. Run the DIR command again and look for a file ending with 'pending.xml'.

          10. Now, rename it. Try this syntax: Rename filename.xml
            i.e. If the file has a long name, press the first character and press the tab key to automatically populate the full name. Let's assume the file name is 1234.pending.xml. Therefore, your command is: rename 1234.pending.xml backup
            This will change the name of the file to 'backup.

          11. Now, exit the command prompt by typing exit and reboot the computer. This should eliminate the pending tasks.






          share|improve this answer































            0














            My mother-in-law's win7 laptop was stuck in this boot loop. What worked for me was getting to the cmd line from the windows repair and running:




            dism.exe /image:D: /cleanup-image /revertpendingactions



            Got an error message the first time I ran it, ran a second time with no errors. Restarted and voila.



            Credit to: https://www.404techsupport.com/2016/04/updates-reverting-loop-windows7/






            share|improve this answer































              0














              Here's an anecdote that might help you have some patience to wait out a very long update reversal, if you see your hard disk light very active during the rollback.



              My computer took 8 hours to roll back a failed update, but it succeeded.



              I believe the cause of my Windows Update failure was triggered by Windows Disk Cleanup tool, which I used for the first time the other day. Then Office wanted to do an update. I read many reports about Windows Disk Cleanup damaging the update files.



              Despite the long process, I got back to the desktop, nothing was broken, but then I was out of disk space.



              Looking around I found c:ProgramDataMicrosoftWindowsWER filled with files dated the same time of the rollback. The files were monstrous, like 400MB to 14GB! I'm guessing it took so much time writing these error dump files, and once it eventually ran out of disk space the roll back completed in minutes.



              My theory - the more disk space you have, the longer the wait.



              I manually deleted all that WER debris and am back running fine. (Delete was another long delay!)






              share|improve this answer































                -1














                I am giving the simplest way out. When you get the repair options, click on windows image recovery, then don' select anything. Select, the 2nd option that is select a system image, and then click advanced and then it should open up windows explorer. Now go to D or C wherever windows is , then Software Update after that, you will see many folders, delete datastore,download,selfupdate,post boot event cache.Then cancel the image recovery and reboot, it will show configuring windows but within 5 minutes , pc will boot up. THIS IS 100% WORKING, GOT THIS SOLUTION WHILE EXPERIMENTING. AND WORKS WITH ALL PCS.









                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%2f1076012%2fwindows-7-failure-configuring-windows-updates-reverting-changes-hang-stuck%23new-answer', 'question_page');
                  }
                  );

                  Post as a guest















                  Required, but never shown

























                  5 Answers
                  5






                  active

                  oldest

                  votes








                  5 Answers
                  5






                  active

                  oldest

                  votes









                  active

                  oldest

                  votes






                  active

                  oldest

                  votes









                  3














                  First download and create a bootable operating system, I'd suggest MiniXP from Hiren.



                  Boot into MiniXP and run net stop wuauserv then del %systemroot%SoftwareDistributionDataStoreLogsedb.log (note this location may change when in MiniXP)



                  Once this is done, reboot your PC and attempt to install the updates again - check your AV to ensure it is not restricting the install.






                  share|improve this answer
























                  • if you can start in Safe Mode with Command Prompt then these commands also work from there. In my case wuauserv was not started, but moving the edb.log aside fixed the update lock-up.

                    – mike
                    Mar 13 '18 at 8:55
















                  3














                  First download and create a bootable operating system, I'd suggest MiniXP from Hiren.



                  Boot into MiniXP and run net stop wuauserv then del %systemroot%SoftwareDistributionDataStoreLogsedb.log (note this location may change when in MiniXP)



                  Once this is done, reboot your PC and attempt to install the updates again - check your AV to ensure it is not restricting the install.






                  share|improve this answer
























                  • if you can start in Safe Mode with Command Prompt then these commands also work from there. In my case wuauserv was not started, but moving the edb.log aside fixed the update lock-up.

                    – mike
                    Mar 13 '18 at 8:55














                  3












                  3








                  3







                  First download and create a bootable operating system, I'd suggest MiniXP from Hiren.



                  Boot into MiniXP and run net stop wuauserv then del %systemroot%SoftwareDistributionDataStoreLogsedb.log (note this location may change when in MiniXP)



                  Once this is done, reboot your PC and attempt to install the updates again - check your AV to ensure it is not restricting the install.






                  share|improve this answer













                  First download and create a bootable operating system, I'd suggest MiniXP from Hiren.



                  Boot into MiniXP and run net stop wuauserv then del %systemroot%SoftwareDistributionDataStoreLogsedb.log (note this location may change when in MiniXP)



                  Once this is done, reboot your PC and attempt to install the updates again - check your AV to ensure it is not restricting the install.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered May 12 '16 at 12:03









                  ThisIsNotMyRealNameThisIsNotMyRealName

                  481213




                  481213













                  • if you can start in Safe Mode with Command Prompt then these commands also work from there. In my case wuauserv was not started, but moving the edb.log aside fixed the update lock-up.

                    – mike
                    Mar 13 '18 at 8:55



















                  • if you can start in Safe Mode with Command Prompt then these commands also work from there. In my case wuauserv was not started, but moving the edb.log aside fixed the update lock-up.

                    – mike
                    Mar 13 '18 at 8:55

















                  if you can start in Safe Mode with Command Prompt then these commands also work from there. In my case wuauserv was not started, but moving the edb.log aside fixed the update lock-up.

                  – mike
                  Mar 13 '18 at 8:55





                  if you can start in Safe Mode with Command Prompt then these commands also work from there. In my case wuauserv was not started, but moving the edb.log aside fixed the update lock-up.

                  – mike
                  Mar 13 '18 at 8:55













                  1














                  Boot into Windows recovery environment and run a system repair few times. Probably 3 times. It should fix the boot and service related issues. Alternatively, try safemode and if you can get through, you can do a system restore.



                  If nothing works, please try this procedure. This also lists how you should get into the repair environment.




                  1. If you are an experienced user, try booting into recovery console by pressing F8 continuously during start, click the recovery options from the boot menu.

                  2. You may be prompted to choose a keyboard layout and language. You usually have no need to change these options.

                  3. Click, Repair your computer.

                  4. Click Next when you see the System Recovery Options dialog box.

                  5. Click Cancel when you are presented with the options to recover your computer.

                  6. Click View advanced options for system recovery and support.

                  7. Click Command Prompt link in the next window.

                  8. Navigate to the following location. *C:WindowsWinSxS* If you are on the X drive (X:/>Source) change the partition to the Windows drive. As an example, type C: and press enter to change to C and type DIR and press enter to list the folders. If you see a Windows folder, that is the system partition. You could also use diskpart but I am not going to list it here. To change to the C:WindowsWinSxS try the following commands. I am listing the basic method here.
                    cd windows
                    cd WinSxS

                  9. Run the DIR command again and look for a file ending with 'pending.xml'.

                  10. Now, rename it. Try this syntax: Rename filename.xml
                    i.e. If the file has a long name, press the first character and press the tab key to automatically populate the full name. Let's assume the file name is 1234.pending.xml. Therefore, your command is: rename 1234.pending.xml backup
                    This will change the name of the file to 'backup.

                  11. Now, exit the command prompt by typing exit and reboot the computer. This should eliminate the pending tasks.






                  share|improve this answer




























                    1














                    Boot into Windows recovery environment and run a system repair few times. Probably 3 times. It should fix the boot and service related issues. Alternatively, try safemode and if you can get through, you can do a system restore.



                    If nothing works, please try this procedure. This also lists how you should get into the repair environment.




                    1. If you are an experienced user, try booting into recovery console by pressing F8 continuously during start, click the recovery options from the boot menu.

                    2. You may be prompted to choose a keyboard layout and language. You usually have no need to change these options.

                    3. Click, Repair your computer.

                    4. Click Next when you see the System Recovery Options dialog box.

                    5. Click Cancel when you are presented with the options to recover your computer.

                    6. Click View advanced options for system recovery and support.

                    7. Click Command Prompt link in the next window.

                    8. Navigate to the following location. *C:WindowsWinSxS* If you are on the X drive (X:/>Source) change the partition to the Windows drive. As an example, type C: and press enter to change to C and type DIR and press enter to list the folders. If you see a Windows folder, that is the system partition. You could also use diskpart but I am not going to list it here. To change to the C:WindowsWinSxS try the following commands. I am listing the basic method here.
                      cd windows
                      cd WinSxS

                    9. Run the DIR command again and look for a file ending with 'pending.xml'.

                    10. Now, rename it. Try this syntax: Rename filename.xml
                      i.e. If the file has a long name, press the first character and press the tab key to automatically populate the full name. Let's assume the file name is 1234.pending.xml. Therefore, your command is: rename 1234.pending.xml backup
                      This will change the name of the file to 'backup.

                    11. Now, exit the command prompt by typing exit and reboot the computer. This should eliminate the pending tasks.






                    share|improve this answer


























                      1












                      1








                      1







                      Boot into Windows recovery environment and run a system repair few times. Probably 3 times. It should fix the boot and service related issues. Alternatively, try safemode and if you can get through, you can do a system restore.



                      If nothing works, please try this procedure. This also lists how you should get into the repair environment.




                      1. If you are an experienced user, try booting into recovery console by pressing F8 continuously during start, click the recovery options from the boot menu.

                      2. You may be prompted to choose a keyboard layout and language. You usually have no need to change these options.

                      3. Click, Repair your computer.

                      4. Click Next when you see the System Recovery Options dialog box.

                      5. Click Cancel when you are presented with the options to recover your computer.

                      6. Click View advanced options for system recovery and support.

                      7. Click Command Prompt link in the next window.

                      8. Navigate to the following location. *C:WindowsWinSxS* If you are on the X drive (X:/>Source) change the partition to the Windows drive. As an example, type C: and press enter to change to C and type DIR and press enter to list the folders. If you see a Windows folder, that is the system partition. You could also use diskpart but I am not going to list it here. To change to the C:WindowsWinSxS try the following commands. I am listing the basic method here.
                        cd windows
                        cd WinSxS

                      9. Run the DIR command again and look for a file ending with 'pending.xml'.

                      10. Now, rename it. Try this syntax: Rename filename.xml
                        i.e. If the file has a long name, press the first character and press the tab key to automatically populate the full name. Let's assume the file name is 1234.pending.xml. Therefore, your command is: rename 1234.pending.xml backup
                        This will change the name of the file to 'backup.

                      11. Now, exit the command prompt by typing exit and reboot the computer. This should eliminate the pending tasks.






                      share|improve this answer













                      Boot into Windows recovery environment and run a system repair few times. Probably 3 times. It should fix the boot and service related issues. Alternatively, try safemode and if you can get through, you can do a system restore.



                      If nothing works, please try this procedure. This also lists how you should get into the repair environment.




                      1. If you are an experienced user, try booting into recovery console by pressing F8 continuously during start, click the recovery options from the boot menu.

                      2. You may be prompted to choose a keyboard layout and language. You usually have no need to change these options.

                      3. Click, Repair your computer.

                      4. Click Next when you see the System Recovery Options dialog box.

                      5. Click Cancel when you are presented with the options to recover your computer.

                      6. Click View advanced options for system recovery and support.

                      7. Click Command Prompt link in the next window.

                      8. Navigate to the following location. *C:WindowsWinSxS* If you are on the X drive (X:/>Source) change the partition to the Windows drive. As an example, type C: and press enter to change to C and type DIR and press enter to list the folders. If you see a Windows folder, that is the system partition. You could also use diskpart but I am not going to list it here. To change to the C:WindowsWinSxS try the following commands. I am listing the basic method here.
                        cd windows
                        cd WinSxS

                      9. Run the DIR command again and look for a file ending with 'pending.xml'.

                      10. Now, rename it. Try this syntax: Rename filename.xml
                        i.e. If the file has a long name, press the first character and press the tab key to automatically populate the full name. Let's assume the file name is 1234.pending.xml. Therefore, your command is: rename 1234.pending.xml backup
                        This will change the name of the file to 'backup.

                      11. Now, exit the command prompt by typing exit and reboot the computer. This should eliminate the pending tasks.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered May 12 '16 at 12:34









                      EpoxyEpoxy

                      38716




                      38716























                          0














                          My mother-in-law's win7 laptop was stuck in this boot loop. What worked for me was getting to the cmd line from the windows repair and running:




                          dism.exe /image:D: /cleanup-image /revertpendingactions



                          Got an error message the first time I ran it, ran a second time with no errors. Restarted and voila.



                          Credit to: https://www.404techsupport.com/2016/04/updates-reverting-loop-windows7/






                          share|improve this answer




























                            0














                            My mother-in-law's win7 laptop was stuck in this boot loop. What worked for me was getting to the cmd line from the windows repair and running:




                            dism.exe /image:D: /cleanup-image /revertpendingactions



                            Got an error message the first time I ran it, ran a second time with no errors. Restarted and voila.



                            Credit to: https://www.404techsupport.com/2016/04/updates-reverting-loop-windows7/






                            share|improve this answer


























                              0












                              0








                              0







                              My mother-in-law's win7 laptop was stuck in this boot loop. What worked for me was getting to the cmd line from the windows repair and running:




                              dism.exe /image:D: /cleanup-image /revertpendingactions



                              Got an error message the first time I ran it, ran a second time with no errors. Restarted and voila.



                              Credit to: https://www.404techsupport.com/2016/04/updates-reverting-loop-windows7/






                              share|improve this answer













                              My mother-in-law's win7 laptop was stuck in this boot loop. What worked for me was getting to the cmd line from the windows repair and running:




                              dism.exe /image:D: /cleanup-image /revertpendingactions



                              Got an error message the first time I ran it, ran a second time with no errors. Restarted and voila.



                              Credit to: https://www.404techsupport.com/2016/04/updates-reverting-loop-windows7/







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Feb 22 '17 at 4:45









                              riotburnriotburn

                              1011




                              1011























                                  0














                                  Here's an anecdote that might help you have some patience to wait out a very long update reversal, if you see your hard disk light very active during the rollback.



                                  My computer took 8 hours to roll back a failed update, but it succeeded.



                                  I believe the cause of my Windows Update failure was triggered by Windows Disk Cleanup tool, which I used for the first time the other day. Then Office wanted to do an update. I read many reports about Windows Disk Cleanup damaging the update files.



                                  Despite the long process, I got back to the desktop, nothing was broken, but then I was out of disk space.



                                  Looking around I found c:ProgramDataMicrosoftWindowsWER filled with files dated the same time of the rollback. The files were monstrous, like 400MB to 14GB! I'm guessing it took so much time writing these error dump files, and once it eventually ran out of disk space the roll back completed in minutes.



                                  My theory - the more disk space you have, the longer the wait.



                                  I manually deleted all that WER debris and am back running fine. (Delete was another long delay!)






                                  share|improve this answer




























                                    0














                                    Here's an anecdote that might help you have some patience to wait out a very long update reversal, if you see your hard disk light very active during the rollback.



                                    My computer took 8 hours to roll back a failed update, but it succeeded.



                                    I believe the cause of my Windows Update failure was triggered by Windows Disk Cleanup tool, which I used for the first time the other day. Then Office wanted to do an update. I read many reports about Windows Disk Cleanup damaging the update files.



                                    Despite the long process, I got back to the desktop, nothing was broken, but then I was out of disk space.



                                    Looking around I found c:ProgramDataMicrosoftWindowsWER filled with files dated the same time of the rollback. The files were monstrous, like 400MB to 14GB! I'm guessing it took so much time writing these error dump files, and once it eventually ran out of disk space the roll back completed in minutes.



                                    My theory - the more disk space you have, the longer the wait.



                                    I manually deleted all that WER debris and am back running fine. (Delete was another long delay!)






                                    share|improve this answer


























                                      0












                                      0








                                      0







                                      Here's an anecdote that might help you have some patience to wait out a very long update reversal, if you see your hard disk light very active during the rollback.



                                      My computer took 8 hours to roll back a failed update, but it succeeded.



                                      I believe the cause of my Windows Update failure was triggered by Windows Disk Cleanup tool, which I used for the first time the other day. Then Office wanted to do an update. I read many reports about Windows Disk Cleanup damaging the update files.



                                      Despite the long process, I got back to the desktop, nothing was broken, but then I was out of disk space.



                                      Looking around I found c:ProgramDataMicrosoftWindowsWER filled with files dated the same time of the rollback. The files were monstrous, like 400MB to 14GB! I'm guessing it took so much time writing these error dump files, and once it eventually ran out of disk space the roll back completed in minutes.



                                      My theory - the more disk space you have, the longer the wait.



                                      I manually deleted all that WER debris and am back running fine. (Delete was another long delay!)






                                      share|improve this answer













                                      Here's an anecdote that might help you have some patience to wait out a very long update reversal, if you see your hard disk light very active during the rollback.



                                      My computer took 8 hours to roll back a failed update, but it succeeded.



                                      I believe the cause of my Windows Update failure was triggered by Windows Disk Cleanup tool, which I used for the first time the other day. Then Office wanted to do an update. I read many reports about Windows Disk Cleanup damaging the update files.



                                      Despite the long process, I got back to the desktop, nothing was broken, but then I was out of disk space.



                                      Looking around I found c:ProgramDataMicrosoftWindowsWER filled with files dated the same time of the rollback. The files were monstrous, like 400MB to 14GB! I'm guessing it took so much time writing these error dump files, and once it eventually ran out of disk space the roll back completed in minutes.



                                      My theory - the more disk space you have, the longer the wait.



                                      I manually deleted all that WER debris and am back running fine. (Delete was another long delay!)







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Jan 3 at 23:53









                                      jwsjws

                                      1956




                                      1956























                                          -1














                                          I am giving the simplest way out. When you get the repair options, click on windows image recovery, then don' select anything. Select, the 2nd option that is select a system image, and then click advanced and then it should open up windows explorer. Now go to D or C wherever windows is , then Software Update after that, you will see many folders, delete datastore,download,selfupdate,post boot event cache.Then cancel the image recovery and reboot, it will show configuring windows but within 5 minutes , pc will boot up. THIS IS 100% WORKING, GOT THIS SOLUTION WHILE EXPERIMENTING. AND WORKS WITH ALL PCS.









                                          share|improve this answer




























                                            -1














                                            I am giving the simplest way out. When you get the repair options, click on windows image recovery, then don' select anything. Select, the 2nd option that is select a system image, and then click advanced and then it should open up windows explorer. Now go to D or C wherever windows is , then Software Update after that, you will see many folders, delete datastore,download,selfupdate,post boot event cache.Then cancel the image recovery and reboot, it will show configuring windows but within 5 minutes , pc will boot up. THIS IS 100% WORKING, GOT THIS SOLUTION WHILE EXPERIMENTING. AND WORKS WITH ALL PCS.









                                            share|improve this answer


























                                              -1












                                              -1








                                              -1







                                              I am giving the simplest way out. When you get the repair options, click on windows image recovery, then don' select anything. Select, the 2nd option that is select a system image, and then click advanced and then it should open up windows explorer. Now go to D or C wherever windows is , then Software Update after that, you will see many folders, delete datastore,download,selfupdate,post boot event cache.Then cancel the image recovery and reboot, it will show configuring windows but within 5 minutes , pc will boot up. THIS IS 100% WORKING, GOT THIS SOLUTION WHILE EXPERIMENTING. AND WORKS WITH ALL PCS.









                                              share|improve this answer













                                              I am giving the simplest way out. When you get the repair options, click on windows image recovery, then don' select anything. Select, the 2nd option that is select a system image, and then click advanced and then it should open up windows explorer. Now go to D or C wherever windows is , then Software Update after that, you will see many folders, delete datastore,download,selfupdate,post boot event cache.Then cancel the image recovery and reboot, it will show configuring windows but within 5 minutes , pc will boot up. THIS IS 100% WORKING, GOT THIS SOLUTION WHILE EXPERIMENTING. AND WORKS WITH ALL PCS.










                                              share|improve this answer












                                              share|improve this answer



                                              share|improve this answer










                                              answered Nov 14 '17 at 19:16









                                              user815514user815514

                                              1




                                              1






























                                                  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%2f1076012%2fwindows-7-failure-configuring-windows-updates-reverting-changes-hang-stuck%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

                                                  Список кардиналов, возведённых папой римским Каликстом III

                                                  Deduzione

                                                  Mysql.sock missing - “Can't connect to local MySQL server through socket”