If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Endless "Please Wait" during recent update.
Today I updated the computer as usual, but this did not complete and I
am left with an endless "Please Wait" on a black screen. I am locked out of the system. How do I cpmplete this updtae and get back to normal? |
Ads |
#2
|
|||
|
|||
Endless "Please Wait" during recent update.
Mark Senter wrote:
Today I updated the computer as usual, but this did not complete and I am left with an endless "Please Wait" on a black screen. I am locked out of the system. How do I cpmplete this updtae and get back to normal? It really depends on where you're stuck, as to what to do. If it says "Please Wait" just before shutdown, you could try pushing the reset button and rebooting. This would presumably trash the incoming update, and it would be downloaded again. (Unplug the network interface, if after the reboot you want to take your time analyzing the machine state.) If the machine was in the process of rebooting, it has tried to come up, it says "Please Wait", that could signify that an update is installed, but it failed to work properly on the reboot. You can try reverting it, if the status of the update isn't "entered" into the history. A poster "Cameo" found this command for updates that "fail in flight". You would boot the computer with the emergency boot CD or with a Windows 10 installer DVD (Troubleshooting section, Command Prompt) and do a variant of: DISM /image:c:\ /cleanup-image /revertpendingactions The "/image:c:\" part means the DISM command is working in offline mode. The command is being applied to an OS which is currently at drive C: . emergency boot media uses a drive letter of X: , so the c: drive letter is supposed to be free to use. In the Command Prompt, you could try dir C: dir C:\users\user name\Downloads and verify that it's really your C: drive. Sometimes the OS happens to be at a different drive letter. If a check of D: looked like a system disk you'd use the command as: DISM /image:d:\ /cleanup-image /revertpendingactions The other kind of command available is (something like): DISM /image:c:\ /remove-package /packagename:xxxxxxxx where you would somehow have to figure out what package just got added. Since it's Patch Tuesday today, you could check on the web for which KB just updated the version of Windows 10 you're running (17134 or 17663 perhaps). I would check on the web, to see if the Cumulative for patch tuesday (today) is somehow defective and this is a known issue. My machine running Win10 right now, hasn't received anything for a while, and I'm almost afraid to guess what the machine is up to. I don't think it's "busted" as it seems to get Defender updates, but the other updates seem to be busted right now. Paul |
#3
|
|||
|
|||
Endless "Please Wait" during recent update.
On Tue, 08 Jan 2019 19:38:37 -0500, Paul
wrote: Mark Senter wrote: Today I updated the computer as usual, but this did not complete and I am left with an endless "Please Wait" on a black screen. I am locked out of the system. How do I cpmplete this updtae and get back to normal? It really depends on where you're stuck, as to what to do. If it says "Please Wait" just before shutdown, you could try pushing the reset button and rebooting. This would presumably trash the incoming update, and it would be downloaded again. (Unplug the network interface, if after the reboot you want to take your time analyzing the machine state.) If the machine was in the process of rebooting, it has tried to come up, it says "Please Wait", that could signify that an update is installed, but it failed to work properly on the reboot. You can try reverting it, if the status of the update isn't "entered" into the history. A poster "Cameo" found this command for updates that "fail in flight". You would boot the computer with the emergency boot CD or with a Windows 10 installer DVD (Troubleshooting section, Command Prompt) and do a variant of: DISM /image:c:\ /cleanup-image /revertpendingactions The "/image:c:\" part means the DISM command is working in offline mode. The command is being applied to an OS which is currently at drive C: . emergency boot media uses a drive letter of X: , so the c: drive letter is supposed to be free to use. In the Command Prompt, you could try dir C: dir C:\users\user name\Downloads and verify that it's really your C: drive. Sometimes the OS happens to be at a different drive letter. If a check of D: looked like a system disk you'd use the command as: DISM /image:d:\ /cleanup-image /revertpendingactions The other kind of command available is (something like): DISM /image:c:\ /remove-package /packagename:xxxxxxxx where you would somehow have to figure out what package just got added. Since it's Patch Tuesday today, you could check on the web for which KB just updated the version of Windows 10 you're running (17134 or 17663 perhaps). I would check on the web, to see if the Cumulative for patch tuesday (today) is somehow defective and this is a known issue. My machine running Win10 right now, hasn't received anything for a while, and I'm almost afraid to guess what the machine is up to. I don't think it's "busted" as it seems to get Defender updates, but the other updates seem to be busted right now. Paul Thank you. Presently I am running on another instance of Windows10 on this machine (which has just gone thru the above update routine without trouble) and I have done the CHKDSK /R on other connected drives some of which required "repair", implying the original update did some damage. I cannot get into the..... "dir C:\users\user name\Downloads" because of ''permissions'' which I dare not touch because of past disasters. I have a 3-day old image backup that I'll probably apply later today. Also because of this I'd better arrange for a daily complete image backup. |
#4
|
|||
|
|||
Endless "Please Wait" during recent update.
Mark Senter wrote:
On Tue, 08 Jan 2019 19:38:37 -0500, Paul wrote: Mark Senter wrote: Today I updated the computer as usual, but this did not complete and I am left with an endless "Please Wait" on a black screen. I am locked out of the system. How do I cpmplete this updtae and get back to normal? It really depends on where you're stuck, as to what to do. If it says "Please Wait" just before shutdown, you could try pushing the reset button and rebooting. This would presumably trash the incoming update, and it would be downloaded again. (Unplug the network interface, if after the reboot you want to take your time analyzing the machine state.) If the machine was in the process of rebooting, it has tried to come up, it says "Please Wait", that could signify that an update is installed, but it failed to work properly on the reboot. You can try reverting it, if the status of the update isn't "entered" into the history. A poster "Cameo" found this command for updates that "fail in flight". You would boot the computer with the emergency boot CD or with a Windows 10 installer DVD (Troubleshooting section, Command Prompt) and do a variant of: DISM /image:c:\ /cleanup-image /revertpendingactions The "/image:c:\" part means the DISM command is working in offline mode. The command is being applied to an OS which is currently at drive C: . emergency boot media uses a drive letter of X: , so the c: drive letter is supposed to be free to use. In the Command Prompt, you could try dir C: dir C:\users\user name\Downloads and verify that it's really your C: drive. Sometimes the OS happens to be at a different drive letter. If a check of D: looked like a system disk you'd use the command as: DISM /image:d:\ /cleanup-image /revertpendingactions The other kind of command available is (something like): DISM /image:c:\ /remove-package /packagename:xxxxxxxx where you would somehow have to figure out what package just got added. Since it's Patch Tuesday today, you could check on the web for which KB just updated the version of Windows 10 you're running (17134 or 17663 perhaps). I would check on the web, to see if the Cumulative for patch tuesday (today) is somehow defective and this is a known issue. My machine running Win10 right now, hasn't received anything for a while, and I'm almost afraid to guess what the machine is up to. I don't think it's "busted" as it seems to get Defender updates, but the other updates seem to be busted right now. Paul Thank you. Presently I am running on another instance of Windows10 on this machine (which has just gone thru the above update routine without trouble) and I have done the CHKDSK /R on other connected drives some of which required "repair", implying the original update did some damage. I cannot get into the..... "dir C:\users\user name\Downloads" because of ''permissions'' which I dare not touch because of past disasters. I have a 3-day old image backup that I'll probably apply later today. Also because of this I'd better arrange for a daily complete image backup. If you are going to restore over it, as your primary recovery mechanism, then you could take a moment or two to try reverting it. Just to gather more info about what happened. What I meant by using the "dir" command, is verify that you're pointed at the correct partition. You don't have to list your Downloads - but check sufficient folders so you know that C: is the partition needing repair. And not some other drive letter. When I've messed around like this, some of my setups require the usage of d: instead. You can run CHKDSK while you're there. But I draw the line on CHKDSK, when you're seeing signs that great damage has been done. CHKDSK works best for "tiny damage". If things are really messed up, you need to archive the drive before doing anything else to it. (The words "backup" or "clone" might not be appropriate, because not a lot of software can handle a messed up disk.) Paul |
#5
|
|||
|
|||
Endless "Please Wait" during recent update.
On Wed, 09 Jan 2019 11:18:43 +1100, Mark Senter
wrote: Today I updated the computer as usual, but this did not complete and I am left with an endless "Please Wait" on a black screen. I am locked out of the system. How do I cpmplete this updtae and get back to normal? THis happened to me with the first 1809 update. After contacting MS on another machine they told me to try switching off and restarting. I did that with trepidation but it all worked. The machine came on line as per normal. -- Regards, Eric Stevens |
#6
|
|||
|
|||
Endless "Please Wait" during recent update.
On Thu, 10 Jan 2019 22:29:22 +1300, Eric Stevens
wrote: On Wed, 09 Jan 2019 11:18:43 +1100, Mark Senter wrote: Today I updated the computer as usual, but this did not complete and I am left with an endless "Please Wait" on a black screen. I am locked out of the system. How do I cpmplete this updtae and get back to normal? THis happened to me with the first 1809 update. After contacting MS on another machine they told me to try switching off and restarting. I did that with trepidation but it all worked. The machine came on line as per normal. A brief note: Switching off and restarting is almost always the first thing you should try for any problem. |
#7
|
|||
|
|||
Endless "Please Wait" during recent update.
In article , Ken Blake
wrote: A brief note: Switching off and restarting is almost always the first thing you should try for any problem. no. that's the sledgehammer approach and rarely a good idea. the first thing should be to determine what the problem actually *is* and *then* decide what the best course of action should be. many times, a restart is *not* needed. it could be as simple as deleting a file or reinstalling an app. |
#8
|
|||
|
|||
Endless "Please Wait" during recent update.
On 10/01/2019 16:52, Ken Blake wrote:
A brief note: Switching off and restarting is almost always the first thing you should try for any problem. IAWTP 100% -- David B. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|